Online Shopping System Design

Online Shopping System 1
Online Shopping System
By (Name)
The Name of the Class (Course)
Professor (Tutor)
The Name of the School (University)
The City and State where it is located
The Date

Online Shopping System 2
Online Shopping System
Design
The design phase of the software development lifecycle (SDLC) transforms software
requirements into detailed specifications by covering all aspects of the systems as defined during
the requirement engineering and data modeling phases (Yang, et al., 2008). A ‘tangible' system is
developed following a suitable software development methodology to meet or to satisfy all user
requirements that were elicited during the initial development phases. At this stage, the
development team assesses and plans for security risks and countermeasures, and aims at getting
approval to continue with the next phase in the lifecycle - development phase by transforming
the requirements into a complete into complete and detailed system design specifications and
upon its completion, the development phase takes root.
The project team has to take critical decisions regarding system design approach,
execution of decisions and how these decisions are to be continued based on the identified
system needs. Consultations held with technical resources and operations staff help the
development team to identify all technical issues related to the installation, operations and
maintenance phase of the software (Dawson, 2015). Software deliverables from this stage create
a universal system understanding among all stakeholders and serve as reminders for critical
milestones throughout the project implementation phase. These deliverables also serve as a
mapping that directs the implementation phase by suggesting best design practices.
Successful design is founded on strict adherence to standards and applicable software
laws and ethics. This phase is brought to conclusion with the team delivering: system design
documentation, system's security consensus document, security plans, and data and disaster

Online Shopping System 3
retention plans. They also define and initiate unit and integration plans, conversion documents
and the implementation plans. The system design documents outline is used to specify the
construction details of the system and how each of the components interact with each other and
external entities as well as the interfaces through which these interactions take place. The
system's security architecture, policies, security tests, and assessments any risks are also
included.
System design begins by reviewing the requirements as elicited during the requirements
engineering phase, and cascades through the phases of monitoring project performance, updating
and performing management activities, and submitting periodical reviews of updates. Design
activities are then initiated and are followed by a revalidation of the project's scope. Throughout
the designing processes, the requirement traceability matrix is constantly updated to ensure that
design for all requirements is satisfactorily met. Risk management activities are periodically
conducted to identify all project risk factors, determine their qualitative and quantitative effects,
and provide methods for risk mitigation, transfer and/or avoidance and to provide a definition of
risk tracking procedures and how response plans are to be executed. It must be understood that
after ambiguous requirements- attributed to most projects’ failure, poor design principles also
lead to projects’ failure (Whitten, et al., 2000). Decisions made at this phase greatly affect the
technology used, the project's framework, the implementation phase, and change management
activities which ensure adherence to design principles and standards.
Design goals
The design of the online shopping system involved the design of all forms of listing the
products, products searching bar, and the display of complete specification and products’
descriptions. It also involved the design of an interactive system that enables clients and admins

Online Shopping System 4
alike to filter products based on different parameters and that which decreases data exchanges
between system servers and the clients.
Architectural design
The above contextual diagram identifies all the information provided to the system and
that which is received from the system- represented by the arrows. Sources and sinks of the
information are represented as closed boxes. This implies that the clients will use graphical
interfaces to interact with the application.
The agile development methodology will be used in during the development phase since
it requires less planning and it works by dividing complex problems into smaller manageable
tasks which are implemented incrementally (Grässle, et al., 2005). The software development
lifecycle (SDLC) based on agile methodology consists of requirement engineering, analysis,
design, coding, testing and maintenance phases. Agile methodology is an iterative process and