Scribd
Upload
9 views

Assignment

Uploaded by

razasami693
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 views

Assignment

Uploaded by

razasami693
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/ 6

MNS

University of Engineering & Technology, Multan

Assignment # 01

Subject Name:
Software Engineering
Submitted By:
Muhammad Sami
Submitted To:
Ms. Sehrish Saleem
Registration No:
2022-CS-39
Assignment Structure:

1. Part 1: Research and Explain Models


❖ Waterfall Model
❖ Spiral Model
❖ Iterative Model
❖ Prototype Model

1. Waterfall Model:
Key Characteristics
➢ Linear and Sequential Phases
➢ Emphasis on Documentation
➢ Defined Milestones
➢ Limited Flexibility for Changes
➢ Testing After Implementation

Advantages
➢ Simplicity and Clarity
➢ Structured Phases
➢ Comprehensive Documentation
➢ Early Requirement Definition
➢ Predictable Outcomes
Disadvantages
➢ Inflexibility to Changes
➢ High Risk and Uncertainty
➢ Limited User Involvement
➢ Maintenance is Difficult
➢ Hard to Measure Progress in Mid-Phase
Situations where the model is best suited

➢ Well-Defined Requirements
➢ Small to Medium-Sized Projects
➢ Regulatory or Compliance Projects
➢ Documentation Needs
➢ Predictable Outcomes
➢ Maintenance of Legacy Systems
➢ Client Availability
➢ Fixed Budget Projects

2. Spiral Model
Key Characteristics
• Iterative Development
• Risk Management
• Prototyping
• User Involvement
• Phases of Development
• Focus on Documentation
• Flexibility
• Gradual Refinement
Advantages
• Enhanced Risk Mitigation
• Iterative Refinement
• Robust Stakeholder Engagement
• Focus on Prototyping
• Dynamic Planning
Disadvantages
• Inherent Complexity
• Cost Implications
• Scop Creep Risk
• Documentation Demands
• Evaluation Overhead

Situations where the model is best suited


• Complex and Large-Scale Projects
• High-Risk Projects
• Projects with Vague or Evolving Requirements
• Development of New, Cutting-Edge Technology
• Projects Requiring Frequent Customer Feedback
• Long-Term, Continuous Development Projects
3. Iterative Model
Key Characteristics
• Incremental Development
• Repeated Cycles
• Progressive Refinement:
• Risk Mitigation
• Adaptability to Changes
• Early Feedback
• Parallel Development
• Evaluation after Each Iteration
• Less Initial Planning
• Evolving Requirements

Advantages

• Early detection of problems


• Client feedback
• Flexibility
• Lower risk

Disadvantages

• Difficult to Manage and Track


• Increased Complexity
• Not Suitable for Smaller Projects
• Requires Skilled Team Members
• High Risk of Scope Creep
• Heavy Testing and Rework
Situations where the model is best suited

• Projects with Unclear or Incomplete Requirements


• Large and Complex Projects
• Risky or High-Uncertainty Projects
• Projects Requiring Frequent Feedback and Changes
• Projects with Long Development Timelines

4. Prototype Model
Key Characteristics
• Early Development of a Prototype
• Customer Feedback-Oriented
• Exploration of Unclear Requirements
• Quick and Inexpensive
• Flexible to Requirement Changes
Advantages
• Helps in refining unclear or incomplete requirements.
• Reduces risk of misunderstanding between developers and users.
• Allows for early detection of design or usability issues.
• Encourages customer and user involvement throughout the development process.

Disadvantages

• Increased Cost and Time


• Scope Creep
• Misleading User Expectations
• Suboptimal Design Choices
• Wasted Effort if Discarded

Situations where the model is best suited


• Unclear Requirements
• User Interface Design
• Complex Systems
• High-Risk Projects
• Incremental Development
• Stakeholder Engagement
• Rapid Application Development (RAD)
• Training and Demonstration
• Requirement Validation
• Product Evolution
Part 2: Project Scenario Analysis
The Project Scenario is:

Government Tax Filing System


A government agency is commissioning the development of a tax filing system that citizens can use to file their taxes online.
The system must handle sensitive personal data, calculate taxes accurately, and comply with existing tax laws. The client
has provided very detailed and clear requirements from the outset, and there is little room for change during development
due to the legal and regulatory environment. The system is large-scale and complex, needing to integrate with several legacy
systems, ensure high availability, and manage huge volumes of data securely.

Suggested Development Model:

Waterfall Development Model

1. Project Size and Complexity:


This is a large, complex system involving multiple integrations and high security needs. Waterfall is ideal for
such a project because it supports detailed upfront planning and structured phases, ensuring that all aspects of the
system are well-designed before development begins.
2. Client Requirements Clarity:
The client has clear and fixed requirements that are unlikely to change due to legal constraints. Waterfall works
best when the requirements are known upfront and unlikely to evolve during the project.
3. Flexibility to Change:
There is minimal flexibility to change due to the regulatory nature of the project. Waterfall's rigid structure helps
keep the project on track without introducing mid-development changes.
4. Risk Management Needs:
Risk management is critical, especially concerning security and compliance with tax laws. Waterfall allows for
comprehensive risk analysis and mitigation during the early stages (requirements and design), which reduces risks
as development progresses.
5. Time Constraints:
The project must be completed in 18 months. Waterfall's phase-based approach ensures that there is a clear
timeline with well-defined milestones, making it easier to manage large projects within strict deadlines.

Part 3: Project Implementation Guidelines:

Reason for Choosing the Waterfall Model:

• Well-Defined Requirements: Government systems like a tax filing system often have strict regulatory
requirements, such as legal compliance and standard forms, that are unlikely to change drastically over the
project lifecycle.

• Clear Documentation: The Waterfall model emphasizes thorough documentation at each stage, which is
important in government projects to ensure compliance with laws and to maintain a clear record for audits.

• Fixed Project Scope: In this project, the scope and features are relatively fixed, with clear objectives such as
e-filing, tax calculations, and report generation.

• Predictability: Waterfall allows for a structured approach where progress can be tracked easily, making it
ideal for large, well-defined systems like government applications.
Phases of the Waterfall Model for Implementing the Tax Filing System:

• Requirement Gathering and Analysis


• System Design
• Implementation (Coding)
• Integration and Testing
• Deployment
• Maintenance

Managing Client Feedback, Risk, and Quality at Each Stage:

Client Feedback

• Limited changes or feedback are incorporated once the design phase is completed, as Waterfall is a
linear process. Therefore, thorough feedback gathering in early stages is critical.

Risk Management

• Requirements Phase
• Design Phase
• Implementation Phase
• Testing Phase

Quality Control

• Documentation
• Testing
• Standards

You might also like