0% found this document useful (0 votes)
28 views7 pages

Se Assignment 1

The document discusses two software development models: the Prototype Model and the Spiral Model. The Prototype Model focuses on creating a basic version of software for user feedback and iterative improvement, while the Spiral Model emphasizes planning, risk analysis, and user feedback in a repetitive cycle for large and high-risk projects. Both models aim to enhance user satisfaction and ensure successful software development through continuous refinement and testing.

Uploaded by

arifahassan0209
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
0% found this document useful (0 votes)
28 views7 pages

Se Assignment 1

The document discusses two software development models: the Prototype Model and the Spiral Model. The Prototype Model focuses on creating a basic version of software for user feedback and iterative improvement, while the Spiral Model emphasizes planning, risk analysis, and user feedback in a repetitive cycle for large and high-risk projects. Both models aim to enhance user satisfaction and ensure successful software development through continuous refinement and testing.

Uploaded by

arifahassan0209
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/ 7

ASSIGNMENT 01

Subject: Software Engineering

Submitted To: Miss Sadaf Masood

Submitted By: Arifa Hassan- 70145488 (4C)


Date of Submission: 03.03.2025

Department of Computer science and IT, The University of Lahore.


Prototype and Spiral Model In software engineering:

Prototype Model:

Definition:

The Prototype Model is a software development approach where a basic version (dummy
version) of the software is created before building the final product. This prototype is shown to
customers for feedback, and improvements are made based on their suggestions. This process
continues until the final software meets user expectations.

Uses:

Following are the uses of Prototype Model in Software Engineering:

• When Requirements Are unclear

If users are unsure about what they need, a prototype helps them visualize the software
and refine their requirements.

• For Complex and Large Systems

In large projects with many features, a prototype helps break down complexity by
focusing on key functionalities first.

• To Improve User Experience (UI/UX)

Helps in designing user-friendly interfaces by allowing users to interact with the system
and suggest improvements.

• In Rapid Application Development (RAD)

When quick software development is required, prototypes help speed up the process by
reducing rework.

• For Customer Engagement

Businesses use prototypes to show clients how the final product will look, gaining their
trust and approval before full-scale development.

• In Research and Experimentation

When developing innovative software, prototypes allow testing new ideas before
committing to full development.
Benefits of Prototype Model:

The benefits of Prototype model are listed below:

• Better Understanding of Requirements

Users can see the software early and suggest changes, helping developers understand
what they really need.

• Early Error Detection

Mistakes or missing features are found and fixed in the prototype stage, preventing
bigger issues later.

• Improved User Satisfaction

Since users give feedback throughout development, the final software meets their
expectations and is easier to use.

• Saves Time and Cost

Finding and fixing problems early reduces rework, saving development time and money.

• Faster Development

Developers and users work together to refine the software, speeding up the
development process.

Process of Prototype Development

The Prototype Model follows a step-by-step process to create a basic version of the software,
get feedback, and improve it. Here’s how it works:

1. Requirement Gathering

• Developers talk to users to understand their needs.


• Instead of collecting full details, only key requirements are identified.

2. Quick Design

• A simple design of the software is created with the main features.


• This is not the final design but a rough idea of how the software will look and function.
3. Prototype Development

• A basic working model (prototype) is built with the core features.


• It may not have complete functionality but helps users understand the concept.

4. User Testing & Feedback

• Users test the prototype and provide feedback.


• They suggest changes, improvements, and missing features.

5. Refinement & Improvement

• Developers make changes based on feedback.


• The improved prototype is tested again, and this cycle continues until users are
satisfied.

6. Final Product Development

• Once the prototype meets user expectations, the final software is developed with all
features.
• Proper testing is done before launching the product.

Example:

Imagine developing a food delivery app:


Step 1: Discuss features like food menu, order placement, and payment.
Step 2: Create a rough design of the app layout.
Step 3: Develop a basic app with a menu and order option.
Step 4: Users test it and say, "Add payment options!"
Step 5: Developers add payments and improve navigation.
Step 6: The final app is developed and launched.

Spiral Model:

Definition:

The Spiral Model is a software development approach that combines planning, risk analysis,
development, and user feedback in a repetitive cycle. It is used for large and high-risk projects,
ensuring that risks are identified and solved at an early stage.
The Spiral Model is divided into four main sectors (or phases) in each cycle (or spiral). These
sectors help in systematically developing software while managing risks.

1️. Planning Phase

• Identify software requirements.


• Set goals for the next phase of development.
• Estimate cost, time, and resources.

2️. Risk Analysis Phase

• Identify potential risks (e.g., security issues, performance problems).


• Find solutions to minimize risks before development.
• Create a prototype to test risky features.

3️. Engineering Phase

• Develop a small part of the software.


• Test and verify that it works as expected.

4️. Evaluation Phase

• Show the developed part to users.


• Collect feedback and suggestions.
• Decide whether to continue, make changes, or stop the project.

How the Spiral Continues:

After completing one cycle, the process repeats with improvements in the next spiral.
More features are added, risks are addressed, and the software improves with each round.

This continues until the software is fully developed, tested, and ready for launch.

Uses:

The Spiral Model is used in software development when projects are large, complex, and
involve risks. Here are its main uses:

1️. When Project is Large and Complex

• Used for big software projects where requirements may change over time.
• Example: Banking Systems, ERP (Enterprise Resource Planning) Software
2️. When There are High Risks

• Used in projects where security, performance, or technical challenges need careful


handling.
• Example: Aviation Software, Military Systems

3️. When Requirements are Unclear

• If users are unsure about what they want, the Spiral Model allows gradual development
with feedback.
• Example: Developing a new mobile operating system

4️. When Frequent Changes are Expected

• Ideal for projects where updates and modifications are needed at different stages.
• Example: Artificial Intelligence (AI) and Machine Learning Projects

5️. For High-Budget and High-Importance Projects

• Suitable for projects where failure is not an option due to high investment.
• Example: NASA’s Space Missions, Healthcare Software

6️. When Prototyping is Needed

• When a prototype (sample version) is required to test features before full development.
• Example: Developing a new gaming engine

Example

Imagine you are developing a food delivery app. Instead of creating everything at once, you
follow the Spiral Model step by step:

1️. First Spiral:

• Plan basic features (restaurant list, food menu).


• Identify risks (slow loading, payment security).
• Develop a simple version where users can browse restaurants.
• Get feedback from users.

2️. Second Spiral:

• Add order placement and cart functionality.


• Test for any bugs or performance issues.
• Improve based on feedback (e.g., better navigation).

3️. Third Spiral:

• Introduce online payment and delivery tracking.


• Solve security risks in payment processing.
• Fix issues and optimize speed.

4️. Final Spiral:

• Fully develop the app with all features.


• Perform final testing and launch the app.
• Provide updates based on user reviews.

You might also like