Software Engineering BN209: Amazon Online Store Application Report

This report provides a comprehensive overview of the software engineering process for the Amazon Online Store application. It begins by recommending the prototype modeling approach, detailing its four stages: establishing objectives, defining objectives, development, and evaluation. The report then discusses requirement verification methods, emphasizing stakeholder involvement. Key actors and use cases are identified using use case diagrams, followed by fully developed use case descriptions and activity diagrams illustrating system performance and flow. Sequence diagrams demonstrate interactions for online registration and purchase. A class diagram outlines the system's objects, qualities, and operations. Finally, the report covers system specifications, including technical, economic, and operational feasibility, and details software testing and acceptance criteria. The document concludes with a list of references used for the report. Desklib is a platform where students can find past papers and solved assignments.

Running head: SOFTWARE ENGINEERING
SOFTWARE ENGINEERING
Name of the Student
Name of the University
Author Note:

1SOFTWARE ENGINEERING
Recommended software Model
Prototype modelling has been selected as the proper kind of software engineering process
for the given project. This model mainly helps development of a prototype of the version of
given client needs or requirements. The process of prototype modelling mainly consists of four
stages that is establishment of objectives, defining of objectives, development and evaluation of
proper kind of prototype. There are large number of factors that is mainly responsible for given
working model which is both for client and distinguish of various kinds of features and any kind
of practical needs of the project and along with required tweaking. Apart from there should be
any kind of constraint for given time and budget which mainly affects the factors for any given
project.
In Amazon Online Store, a proper kind of prototype is required to be designed for proper
establishment of aims and after that defining of it in proper way. The various kinds of objective
and definition are mainly set out various kinds of objectives of the client was to create an E-
commerce site which is mainly used for selling of range of products and various definition of the
site which is mainly inclusive of various kinds of functional needs or requirements. Starting from
the prototype store come up with Microsoft access database that is mainly used for setting up of
data entry and splash kind of screen. In the end the proper kind of evaluation is mainly done by
the client which is mainly used for verification and request of validation.

2SOFTWARE ENGINEERING
Fig 1. Prototyping Process Model.
Selection of Requirement Model and verification of requirement with various stakeholders
Validation of requirement is mainly guarantee that is mainly ensured for the product
which is mainly created for fulling of various kinds of users with fulfilment with various kinds of
users. Checking with the requirements of products and various kinds of software requirements
for all the products that is mainly used for satisfying the needs of the customers, top level
requirements and various kinds of software requirements.

3SOFTWARE ENGINEERING
Fig 2. Software development.
Excellent kind of approval by both the end that is client and user, are considered to be more
available for determination and demonstration of prerequisites and also enable various kinds of
partners to look for any kind of issue and problem that may arise.

4SOFTWARE ENGINEERING
Identification of various actors
Use case is mainly used for various kinds of actors that is mainly defined in the given section by
help of use case diagram. The diagram mainly focusses on specific kind of action that is mainly
can be undertaken by list of actors or system that is mainly associated with it.
Fig.3 New Customer Use Case
(Source: Created by Author)

5SOFTWARE ENGINEERING
Fig. 4 Existing Customer Use Case.
(Source: Created by Author)
Fig.5 Courier Use Case Diagram
(Source: Created by Author)

6SOFTWARE ENGINEERING
Fig 6. Administrator Use Case Diagram.
(Source: Created by Author)

7SOFTWARE ENGINEERING
Use Case Diagram
Use case Diagram is a model that is used for functionality which is provided by a system
with respect to users and their goals and dependencies with respect to things that are mainly
described in the visual manners which is mainly provided. The diagram provided below provides
interaction between external entities that is various kinds of actors in online store system. The
four actors provided above comes up with specific and varying interaction with the given system.
With the help of actor administrator which mainly establish interaction with various system. It is
mainly used for establishment of with super user performance which allows various kinds of
users to base on performance maintenance and proper updating that is mainly used for listing.
Along with this the interaction between various kinds of actors that is “Existing customer “ and
the given system that mainly allows various kinds of users to act along and login in the given
network, make purchase and tracking of orders and pickup of various kinds of orders.

8SOFTWARE ENGINEERING
Fig 7. Entire Use Case Diagram.
(Source: Created by Author)

9SOFTWARE ENGINEERING
Fully develop using case description
Use Case Name: Create Account
Scenario: Create a new user account
Brief Description: Allows the user to create an account in order to view, buy and send
items
Actors: New customer, Administrator
Related Use Cases: None.
Stakeholders: Administrator, New Customer, Courier
Preconditions: Account must be verified
Postconditions: Profile created and payment method added
Flow of Activities Actor System
1. Account details
entered
2. Account Verified
3. Validate personal
details
1.1 Account name
must be available
2.1 Verification
success
3.1 Personal details
are compared to
publicly available
records
Exception Conditions 1.1 If account name unavailable, select another
22. If verification fails more than twice suspend
3.1 If details are not located request further docs

10SOFTWARE ENGINEERING
Use Case Name: Deliver Items
Scenario: Deliver customer items
Brief Description: Courier will pick up items from warehouse and ship to customer
Actors: Existing customer, Administrator
Related Use Cases: None.
Stakeholders: Administrator, Existing Customer, Courier
Preconditions: Payment must be received
Postconditions: Profile created and payment method added, Shipping address received and items dispatched
Flow of Activities Actor System
1.1Shipping request received
2.1Shipping Assigns
shipper
3.1Dispatch items
1.2 Locate purchase record
2.1 System creates shipping
items
3.1 Shipping marks item as
sent
Exception Conditions 1.2 If location is not reachable return to warehouse
22. If item is damaged get new item
3.1 If item is not marked double order
Activity Diagram
Scene 1: The activity chart provides an idea regarding performance of system and its
flow in those of the activities in a proper sequence. Apart from this it also defines the proper
method that can be used for performing in the coming sequential task. The diagram drawn below
provides an idea regarding new kind of user account. Along with this it can be also observed an
individual can also see or create an account that can be easily seen by large number of people.

11SOFTWARE ENGINEERING
For processing with the given stage of verification and various details of the account one
must focus on two kind of outcomes that is” successful or unsuccessful verification”. If the given
verification proceeds with add profile and the outcome must be proceeded for the details of the
account.
Scene 2: The given activity chart provides an idea regarding the way in which the given
diagram works in a proper way and followed by making a kind of purchase. Along with this it
can be also observed sequential kind of flow comes up or begins with the given user like
“Adding a proper item cart” and selection of new kind of payment mode must be there. After that
verification of account must be done in the given swim lane of the given bank. If there is
sufficient amount of balance is need to be done for purchase item. If it comes up with sufficient
amount of value, then new kind of user needs to be selected for the given for the select new kind
of payment type. After that a purchase is made from the confirm purchase then a proper kind of
activity for running which mainly provides a proper kind of sequence for the given activity.