INTRODUCTION TO SOFTWARE ENGINEERING
Final Report
SUBMITTED BY:
SUBMITTED TO:
,Contents
Introduction .................................................................................................................................................. 3
Purpose ..................................................................................................................................................... 3
Scope ......................................................................................................................................................... 3
Overview ................................................................................................................................................... 3
Software Process Model ............................................................................................................................... 3
Requirements................................................................................................................................................ 3
Functional Requirements .......................................................................................................................... 3
Non-Functional Requirements .................................................................................................................. 4
Security ................................................................................................................................................. 4
Reliability............................................................................................................................................... 4
Availability ............................................................................................................................................. 4
Diagrams ....................................................................................................................................................... 5
Context Diagram ....................................................................................................................................... 5
Class Diagram ............................................................................................................................................ 6
Use Case Diagram ..................................................................................................................................... 7
Object Diagram ......................................................................................................................................... 8
Activity Diagram ........................................................................................................................................ 9
State Machine Diagram........................................................................................................................... 10
Sequence Diagrams................................................................................................................................. 11
................................................................................................................................................................ 13
Deployment Diagram .............................................................................................................................. 14
Data Flow Diagram level 1 and level 2 .................................................................................................... 15
LEVEL 1 DFD ........................................................................................................................................ 15
LEVEL 2 DFD ........................................................................................................................................ 16
Entity Relationship Diagram ................................................................................................................... 17
Approaches ................................................................................................................................................. 18
Testing ..................................................................................................................................................... 18
Equivalence Test for Password ............................................................................................................... 18
Cyclomatic Complexity for Searching ..................................................................................................... 19
WORK BREAKDOWN STRUCTURE (WBS) ................................................................................................ 20
GANTT CHART ......................................................................................................................................... 21
User Interface ............................................................................................................................................. 22
, Introduction
Purpose
The Online Shopping System for electronics item shop web application is intended to provide
complete solutions for both sellers and customers via a single access point via i.e. the internet. It will allow
sellers to set up online shops and customers to browse and purchase items without having to physically
visit the shop. The administration module will allow a system administrator to approve and reject requests
for new shops, as well as maintain various shop category lists.
Scope
The System will allow the user to maintain their cart i.e. add and remove items from it. The user
will have different options for single type of item (i.e. Same item from different companies). Moreover,
it will give provide a function known as “Artificial Reality” that will allow the user to view the product in
a 3600 view, they are buying.
Overview
This system makes it simple for customers to purchase products without having to visit a store, as
well as for store owners to sell products. This proposed system can be used by any user and does not
require any educational level, experience, or technical expertise in the computer field; however, it will
be useful if the user has a good understanding of how to operate a computer.
Software Process Model
• We use Agile software process model in our project because of constant requirements from our
customers.
• We know that our project is small and less in cost so Agile method is the best approach for this
because of rapid testing after every stage.
• If we does something wrong we have the opportunity to check it every day and discuss it through
sprint meetings.
• We have a Scrum and scrum master. We arrange a 15 minute meeting every day to discuss which
task we performed the last.
• If changes are required it is easy for us to change.
There are four members in our team and all are well experienced (senior developers). So, that’s why we
adopted agile method because we have a single development team. For example. Teacher gave us
comments and we make changes in it rapidly.
Requirements
Functional Requirements
The system will have the following functional requirements:
Final Report
SUBMITTED BY:
SUBMITTED TO:
,Contents
Introduction .................................................................................................................................................. 3
Purpose ..................................................................................................................................................... 3
Scope ......................................................................................................................................................... 3
Overview ................................................................................................................................................... 3
Software Process Model ............................................................................................................................... 3
Requirements................................................................................................................................................ 3
Functional Requirements .......................................................................................................................... 3
Non-Functional Requirements .................................................................................................................. 4
Security ................................................................................................................................................. 4
Reliability............................................................................................................................................... 4
Availability ............................................................................................................................................. 4
Diagrams ....................................................................................................................................................... 5
Context Diagram ....................................................................................................................................... 5
Class Diagram ............................................................................................................................................ 6
Use Case Diagram ..................................................................................................................................... 7
Object Diagram ......................................................................................................................................... 8
Activity Diagram ........................................................................................................................................ 9
State Machine Diagram........................................................................................................................... 10
Sequence Diagrams................................................................................................................................. 11
................................................................................................................................................................ 13
Deployment Diagram .............................................................................................................................. 14
Data Flow Diagram level 1 and level 2 .................................................................................................... 15
LEVEL 1 DFD ........................................................................................................................................ 15
LEVEL 2 DFD ........................................................................................................................................ 16
Entity Relationship Diagram ................................................................................................................... 17
Approaches ................................................................................................................................................. 18
Testing ..................................................................................................................................................... 18
Equivalence Test for Password ............................................................................................................... 18
Cyclomatic Complexity for Searching ..................................................................................................... 19
WORK BREAKDOWN STRUCTURE (WBS) ................................................................................................ 20
GANTT CHART ......................................................................................................................................... 21
User Interface ............................................................................................................................................. 22
, Introduction
Purpose
The Online Shopping System for electronics item shop web application is intended to provide
complete solutions for both sellers and customers via a single access point via i.e. the internet. It will allow
sellers to set up online shops and customers to browse and purchase items without having to physically
visit the shop. The administration module will allow a system administrator to approve and reject requests
for new shops, as well as maintain various shop category lists.
Scope
The System will allow the user to maintain their cart i.e. add and remove items from it. The user
will have different options for single type of item (i.e. Same item from different companies). Moreover,
it will give provide a function known as “Artificial Reality” that will allow the user to view the product in
a 3600 view, they are buying.
Overview
This system makes it simple for customers to purchase products without having to visit a store, as
well as for store owners to sell products. This proposed system can be used by any user and does not
require any educational level, experience, or technical expertise in the computer field; however, it will
be useful if the user has a good understanding of how to operate a computer.
Software Process Model
• We use Agile software process model in our project because of constant requirements from our
customers.
• We know that our project is small and less in cost so Agile method is the best approach for this
because of rapid testing after every stage.
• If we does something wrong we have the opportunity to check it every day and discuss it through
sprint meetings.
• We have a Scrum and scrum master. We arrange a 15 minute meeting every day to discuss which
task we performed the last.
• If changes are required it is easy for us to change.
There are four members in our team and all are well experienced (senior developers). So, that’s why we
adopted agile method because we have a single development team. For example. Teacher gave us
comments and we make changes in it rapidly.
Requirements
Functional Requirements
The system will have the following functional requirements:
