Scribd
Upload
9 views12 pages

Linear Sequential Model (Waterfall Model) : A. Year: 1970s B. Proposed By: Winston W. Royce C. Diagram

Uploaded by

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

Linear Sequential Model (Waterfall Model) : A. Year: 1970s B. Proposed By: Winston W. Royce C. Diagram

Uploaded by

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

1.

**Linear Sequential Model (Waterfall Model)**:


A. Year: 1970s
B. Proposed by: Winston W. Royce
C. Diagram:

```
Requirements --> Design --> Implementation --> Testing -->
Maintenance
```
D. Brief Description: The linear sequential model follows a
sequential and non-iterative approach, where each phase must be
completed before moving to the next. It is a rigid model suitable for
projects with well-defined requirements and stable technologies.
E. Advantages:
- Simple and easy to understand.
- Clear documentation at each stage.
F. Disadvantages:
- Lack of flexibility.
- Difficulties in accommodating changes late in the development
process.
G. When Best Suited: Best suited for projects with clear, stable
requirements and technologies.

2. **Prototyping Model**:
A. Year: 1960s (Concept), 1980s (Formalization)
B. Proposed by: Barry Boehm
C. Diagram:
```

Requirements --> Prototype --> Feedback --> Prototype


Modification
```
D. Brief Description: The prototyping model involves the creation of
an initial version of the system, which is then refined through
iterations based on user feedback. It is useful for exploring
requirements, reducing risks, and enhancing user involvement.
E. Advantages:
- Provides early feedback and validation.
- Increases user involvement and satisfaction.
F. Disadvantages:
- Can lead to scope creep if not managed properly.
- Initial prototype may lack scalability and robustness.
G. When Best Suited: Best suited for projects with evolving or
unclear requirements, and where user involvement is crucial.

3. **RAD Model (Rapid Application Development)**:


A. Year: 1980s
B. Proposed by: James Martin
C. Diagram:
```
Requirements Planning --> User Design --> Rapid Construction --
> Cutover
```
D. Brief Description: The RAD model emphasizes rapid prototyping
and iterative development, aiming to deliver functional software
quickly. It involves user feedback and active user participation
throughout the development process.
E. Advantages:
- Rapid delivery of software.
- High level of customer involvement.
F. Disadvantages:
- Requires highly skilled developers.
- May lead to increased project complexity.
G. When Best Suited: Best suited for projects with short
development cycles, where user involvement is critical, and
requirements are well-understood.

4. **Incremental Model**:
A. Year: 1970s
B. Proposed by: Winston W. Royce (Concept), Barry Boehm
(Formalization)
C. Diagram:
```

Requirements --> Design --> Implementation --> Testing -->


Maintenance
↑ ↑
Increment 1 Increment 2
```
D. Brief Description: The incremental model divides the project
into small, manageable increments, with each increment delivering
a portion of the functionality. It allows for early delivery of useful
features and facilitates easier testing and debugging.
E. Advantages:
- Early delivery of working software.
- Flexibility to accommodate changes.
F. Disadvantages:
- Requires careful planning and design upfront.
- May encounter integration issues if increments are not well-
coordinated.
G. When Best Suited: Best suited for large projects with well-
defined modules, where early delivery of useful functionality is
required.

5. **Spiral Model**:
A. Year: 1988
B. Proposed by: Barry Boehm
C. Diagram: Spiral-shaped diagram
D. Brief Description: The spiral model combines iterative
development with elements of the waterfall model's systematic
approach. It involves iterative cycles of risk analysis, development,
and customer evaluation, allowing for flexibility and risk
management.
E. Advantages:
- Emphasizes risk management and mitigation.
- Allows for early user feedback and change incorporation.
F. Disadvantages:
- Requires experienced personnel for risk assessment.
- Can be complex to manage and requires thorough
documentation.
G. When Best Suited: Best suited for large, high-risk projects with
changing requirements and evolving technologies.

6. **Component Assembly Model**:


- This model focuses on assembling pre-existing components or
modules to build software applications. It emphasizes reuse and
integration of existing components to accelerate development and
improve quality. The specific details regarding year, proposed by,
diagram, advantages, disadvantages, and when best suited may
vary depending on the specific implementation or variant of this
model.

7. **RUP (Rational Unified Process)**:


A. Year: 1990s
B. Proposed by: Rational Software (later acquired by IBM)
C. Diagram: Various diagrams representing phases, iterations, and
disciplines
D. Brief Description: RUP is a customizable software development
process framework that provides guidelines, templates, and best
practices for iterative development. It emphasizes iterative
development, architecture-centric approach, and continuous
stakeholder involvement.
E. Advantages:
- Tailorable to project-specific needs.
- Emphasizes architecture and design early in the development
process.
F. Disadvantages:
- Can be overly bureaucratic if not tailored appropriately.
- Requires skilled practitioners for effective implementation.
G. When Best Suited: Best suited for medium to large projects with
a focus on architecture, where flexibility and adaptability are crucial.

8. **Agile Processes**:
- Agile encompasses various iterative and incremental software
development methodologies, including Scrum, Kanban, Extreme
Programming (XP), etc. These methodologies prioritize individuals
and interactions over processes and tools, working software over
comprehensive documentation, customer collaboration over
contract negotiation, and responding to change over following a
plan.
- Year, proposed by, diagram, advantages, disadvantages, and
when best suited may vary depending on the specific agile
methodology being discussed.

9. **CMM (Capability Maturity Model)**:


A. Year: 1987 (Initial Version)
B. Proposed by: Software Engineering Institute (SEI)
C. Diagram: Maturity levels (Initial, Repeatable, Defined, Managed,
Optimizing)
D. Brief Description: CMM is a process improvement framework
that helps organizations improve their software development and
maintenance processes. It defines five maturity levels, each
representing increasingly mature and effective processes.
E. Advantages:
- Provides a structured framework for process improvement.
- Helps organizations assess and benchmark their process
maturity.
F. Disadvantages:
- Can be time-consuming and resource-intensive to implement.
- May focus too much on process compliance rather than actual
business value.
G. When Best Suited: Best suited for organizations looking to
systematically

You might also like