Scribd
Upload
6 views

Model Life Cycle (Task-1)

Uploaded by

vtu21739
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
6 views

Model Life Cycle (Task-1)

Uploaded by

vtu21739
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Task 1.

Finalizing Problem statement and Process Model

The Electronic Cash counter project is mainly developed for the Account Division of
a Banking sector to provide better interface of the entire banking transactions.
This system is aimed to give a better out look to the user interfaces and to
implement all the banking transactions like:
•Supply of Account Information •New Account Creations
•Deposits •Withdraws
•Cheque book issues •Stop payments
•Transfer of accounts •Report Generations.
The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.
•User friendliness is provided in the application with various controls.
•The system makes the overall project management much easier and flexible.
•Readily upload the latest updates, allows user to download the alerts by clicking
the URL.
•There is no risk of data mismanagement at any level while the project development
is under process.
•It provides high level of security with different level of authentication

sol/:

In software engineering, there are various process models that guide the
development of software systems. These models define how software development
progresses, including stages such as planning, design, coding, testing, and
maintenance. Below are *6 common software engineering process models*:

### 1. *Waterfall Model*


- *Description*: The Waterfall model is a linear and sequential approach where
each phase of development must be completed before moving to the next. It is one of
the earliest models and is straightforward, making it easy to understand and
manage.
- *Phases*:
1. Requirement analysis
2. System design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
- *Advantages*: Simple and easy to understand, clearly defined stages.
- *Disadvantages*: Inflexible, as it’s hard to go back to a previous phase once
it’s completed. Not suitable for projects with evolving requirements.
- *Use Cases*: Best suited for small projects or projects with well-defined
requirements.

### 2. *V-Model (Verification and Validation)*


- *Description*: The V-Model is an extension of the Waterfall model where each
development stage is associated with a corresponding testing phase. It emphasizes
the importance of validation and verification during each step.
- *Phases*:
1. Requirements analysis (Validation)
2. System design (Verification)
3. Architecture design (Verification)
4. Module design (Verification)
5. Coding (Verification)
6. Unit testing (Validation)
7. Integration testing (Validation)
8. System testing (Validation)
9. Acceptance testing (Validation)
- *Advantages*: Clear structure, easy to manage with each phase having a
corresponding testing phase.
- *Disadvantages*: Like Waterfall, it is rigid and doesn’t allow for changes
once the development is underway.
- *Use Cases*: Best for projects where requirements are well understood from the
beginning.

### 3. *Incremental Model*


- *Description*: In the Incremental Model, the system is designed, developed,
and tested in small segments (increments). Each increment is a part of the final
product and builds on previous ones.
- *Phases*:
1. Requirement gathering
2. Design
3. Development and testing (done in increments)
4. Integration of each increment
5. Maintenance and updates
- *Advantages*: Allows partial implementation and delivery of features early,
offers flexibility to change as requirements evolve.
- *Disadvantages*: Can lead to architectural issues if not managed properly, as
changes may accumulate over time.
- *Use Cases*: Suitable for large systems that need to be delivered in phases or
when requirements are not fully clear at the outset.

### 4. *Spiral Model*


- *Description*: The Spiral Model combines iterative development with the
systematic aspects of Waterfall. It is particularly focused on risk management. The
project is developed in repeated cycles (spirals), with each cycle involving
planning, risk analysis, engineering, and evaluation.
- *Phases*:
1. Planning and requirements gathering
2. Risk analysis and mitigation
3. Engineering and development
4. Testing and validation
5. Customer evaluation
- *Advantages*: Strong focus on risk management, iterative approach allows for
continuous feedback, flexible.
- *Disadvantages*: Can be complex to manage due to its cyclical nature, more
costly due to frequent reviews and iterations.
- *Use Cases*: Ideal for large, complex, and high-risk projects, such as
military and aerospace software.

### 5. *Agile Model*


- *Description*: The Agile model focuses on iterative development and emphasizes
flexibility, customer collaboration, and rapid delivery of small, functional
software increments. The Agile Manifesto promotes principles such as working
software, responding to change, and collaboration.
- *Phases* (for Scrum, a popular Agile framework):
1. Sprint planning
2. Development and testing (done iteratively in short sprints)
3. Daily stand-up meetings
4. Sprint review and retrospective
- *Advantages*: Highly flexible and adaptive to change, promotes continuous
feedback from users, encourages collaboration.
- *Disadvantages*: Can be difficult to manage with larger teams, the scope can
easily expand (scope creep).
- *Use Cases*: Suitable for dynamic, evolving projects where requirements are
not fully understood upfront, or where flexibility is critical.
### 6. *RAD (Rapid Application Development) Model*
- *Description*: RAD focuses on rapid prototyping and quick development. The
model is designed to speed up the software development process by using tools like
CASE (Computer-Aided Software Engineering) to automate parts of the development.
- *Phases*:
1. Requirements planning
2. User design (Prototyping)
3. Construction (Building prototypes)
4. Cutover (Implementation and deployment)
- *Advantages*: Faster delivery, allows for early user feedback through
prototypes, flexible to user needs.
- *Disadvantages*: Not suitable for large, complex systems, may lead to
incomplete solutions or under-defined requirements.
- *Use Cases*: Best for applications that need to be developed quickly and can
be scaled or adjusted as the project progresses.

You might also like