Software Engineering for E-Commerce Website 'The Iconic'

Running head: SOFTWARE ENGINEERING
Software Engineering: E-Commerce Website “The Iconic”
Student Name:
University Name:

1SOFTWARE ENGINEERING
Table of Contents
1. Assignment #1 Progression................................................................................................................2
2. Recommended software engineering process model........................................................................2
3. Requirement verification method.....................................................................................................3
4. Context Diagram for the complete overall system............................................................................4
5. Actors and use cases for the system..................................................................................................4
6. Fully developed use case description................................................................................................5
Use case 1.........................................................................................................................................5
Use case 2.........................................................................................................................................5
7. Activity diagram for 2 scenarios.........................................................................................................6
8. Sequence diagrams for 2 scenarios...................................................................................................8
9. Class diagram for the complete overall system...............................................................................10
10. Verification of user requirements..................................................................................................10
11. System Specification......................................................................................................................11
Technical feasibility.........................................................................................................................11
Economical feasibility......................................................................................................................11
Operational feasibility.....................................................................................................................11
12. Software testing and acceptance criteria......................................................................................12
13. Proposed deployment strategy.....................................................................................................12
14. Project Activity Journal..................................................................................................................12
Bibliography.........................................................................................................................................14

2SOFTWARE ENGINEERING
1. Assignment #1 Progression
Version Date Author(s) Change Description
1.1 14/05/2018 [Please Fill Your
Name]
Preparation of second draft of system requirements
specification document
1.1 17/05/2018 [Please Fill Your
Name]
Providing recommendation of process model for
software engineering
1.1 19/05/2018 [Please Fill Your
Name]
Selecting the method for requirement verification
along with verifying the requirements of user and
stakeholder
1.1 21/05/2018 [Please Fill Your
Name]
Preparation of various modelling diagrams for the
system
1.1 24/05/2018 [Please Fill Your
Name]
Verifying the requirements of user and documenting
the system specification
1.1 28/05/2018 [Please Fill Your
Name]
Defining the process for software testing along with
criteria for acceptance of the system
1.1 30/05/218 [Please Fill Your
Name]
Proposing the strategy for deployment of system
2. Recommended software engineering process model
The Waterfall Model was first model introduced for development of systems and it has been
chosen as the suitable method for the e-commerce website. It is likewise alluded to as a direct
consecutive life cycle display. It is extremely easy to comprehend and utilize. In a waterfall display,
each stage must be finished completely before the following stage can start. This sort of
programming improvement demonstrate is essentially utilized for the task which is little and there
are no indeterminate necessities. Toward the finish of each stage, a survey happens to decide
whether the venture is on the correct way and regardless of whether to proceed or dispose of the
task. In this model programming testing begins simply after the advancement is finished. In waterfall
demonstrate stages do not cover. The waterfall display underscores that an intelligent movement of
steps be taken all through the product advancement life cycle (SDLC), much like the falling strides
down an incremental waterfall. While the prevalence of the waterfall display has melted away

3SOFTWARE ENGINEERING
finished late years for more deft strategies, the intelligent idea of the successive procedure utilized
as a part of the waterfall strategy cannot be denied, and it remains a typical outline process in the
business.
The upside of waterfall improvement is that it takes into account departmentalization and
administrative control. A calendar can be set with due dates for each phase of advancement and an
item can continue through the improvement procedure like an auto in a carwash, and
hypothetically, be conveyed on time. Advancement moves from idea, through plan, usage, testing,
establishment, investigating, and winds up at task and upkeep. Each period of improvement
continues in strict request, with no covering or iterative advances.
The detriment of waterfall advancement is that it does not takes into consideration much
reflection or correction. Once an application is in the testing stage, it is extremely hard to return and
change something that was not well-thoroughly considered in the idea arrange. Other options to the
waterfall demonstrate incorporate joint application improvement (JAD), quick application
advancement (RAD), sync and balance out, form and settle, and spiral model.
3. Requirement verification method
The verification of requirements indicate the confirmation occasions expected to
demonstrate the fulfillment of the item prerequisites and help to characterize the check procedure
and condition. The four principal strategies for confirmation are Inspection, Demonstration, Test,
and Analysis. The four techniques are to some degree various leveled in nature, as each checks
prerequisites of an item or framework with expanding thoroughness. Test is the check of an item or
framework utilizing a controlled and predefined arrangement of sources of info, information, or jolts
to guarantee that the item or framework will deliver an unmistakable and predefined yield as
determined by the prerequisites.
Investigation is the check of an item or framework utilizing models, computations and
testing gear. Examination enables somebody to put forth prescient expressions about the normal
execution of an item or framework in light of the affirmed test aftereffects of an example set or by
consolidating the result of individual tests to close something new about the item or framework.
Usually used to anticipate the limit or disappointment of an item or framework by utilizing
nondestructive tests to extrapolate the disappointment point.