Scribd
Upload
38 views2 pages

Assignment 1 SE

The document outlines the use of the Incremental Process Model for developing an Online Shopping Application, emphasizing the complexity and modular nature of the project. It details the key software process activities including communication, planning, modeling, construction, deployment, and maintenance, along with their respective outputs. Each phase is designed to facilitate gradual development and user feedback integration, ensuring a functional and user-friendly application.

Uploaded by

vishakha.code
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
38 views2 pages

Assignment 1 SE

The document outlines the use of the Incremental Process Model for developing an Online Shopping Application, emphasizing the complexity and modular nature of the project. It details the key software process activities including communication, planning, modeling, construction, deployment, and maintenance, along with their respective outputs. Each phase is designed to facilitate gradual development and user feedback integration, ensuring a functional and user-friendly application.

Uploaded by

vishakha.code
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

Case Study: Identify process model and activities for Online Shopping Application

Case Study: Online Shopping Application

1. Identified Software Process Model:

Incremental Process Model

Justification:

 The online shopping application is complex and contains several modules like user
authentication, product catalog, cart management, payment gateway, etc.

 Each module can be developed and delivered incrementally.

 Feedback from users after each increment can help improve the next phase.

 The incremental model allows early delivery of basic functionality (e.g., product browsing)
and then adds features gradually.

2. Software Process Activities:

A. Communication (Requirement Gathering)

 Activities:

o Meetings with stakeholders to understand features like browsing, cart, payment,


user profile, etc.

o Gathering both functional and non-functional requirements.

 Output:

o Software Requirement Specification (SRS)

B. Planning

 Activities:

o Dividing the project into modules (increments) like login, product catalog, payment,
etc.

o Resource allocation, cost estimation, scheduling.

 Output:

o Project plan and timelines for each increment.

C. Modeling (Design)

 Activities:

o High-level and low-level design of application components.


o Database design (e.g., user table, product table, orders).

o UI/UX design for user interaction.

 Output:

o System architecture, ER diagrams, wireframes.

D. Construction (Implementation and Testing)

 Activities:

o Coding modules based on the design.

o Unit testing of individual components.

o Integration testing for combined modules.

 Tools:

o Programming languages (e.g., JavaScript, Python)

o Frameworks (e.g., React, Django)

 Output:

o Working software increments.

E. Deployment

 Activities:

o Hosting the application on a live server (e.g., AWS, Azure).

o User training and documentation.

 Output:

o Live application for end-users.

F. Maintenance

 Activities:

o Bug fixing.

o Adding new features like order tracking or wishlist.

o System updates and patches.

 Output:

o Stable and updated software.

You might also like