Embed Size (px)
Citation preview
CAPSTON PROJECT
On
Foreign language learner
Submitted to:
The Controller of Examinations,
University of Sargodha,
Sargodha.
Through
Mr. UMAIR YAQUB
Lecturer,
Standard College for Girls,
Sialkot.
Submitted by:
Sidra Shahid (15 MIT 1306)
Fatima Saeed (15 MIT 1307)
Hajra Khalil (15 MIT 1309)
MSC- IT
Session 2015-2017
Standard College for Girls
Affiliated With
CAPSTON PROJECT
On
Foreign language learner
Certificate
It is certified that Sidra Shahid D/o M Shahid, Fatima Saeed D/O M.Saeed, Hajra Khalil D/o M.
Khalil have submitted this capston project for partial fulfillment of degree of MSC (IT) under
Term System from Standard College for Girls, Sialkot in Affiliation with
University of Sargodha.
Internal Examiner _______________________
_______________________
In charge MSC IT _______________________
_______________________
Director _______________________
_______________________
External Examiner _______________________
_______________________
CAPSTON PROJECT
On
Foreign language learner
Declaration
We hereby declare that this work has been done by our self and no portion of the work contained
in this project has been submitted in support of any application for any other degree or qualification
of this or any other University or Institute of learning.
Signature: __________________________
Name: Sidra Shahid
Ftima Saeed
Hajra Khalil
Roll.No.: 15 MIT 1306
15 MIT 1307
15 MIT 1309
Class: MSC IT
Session: 2015-2017
CAPSTON PROJECT
On
Foreign language learner
Acknowledgement
We are very thankful to Allah Almighty who gave us the courage to complete this complex task
and to our ever caring and loving parents whose prayers helped us to reach this stage of our life.
We are highly thank you to all the teachers who always helped us and guide us at every step.
CAPSTON PROJECT
On
Foreign language learner
Dedication
We want to dedicate this project to our Beloved Parents
&
Respectable Teachers
Revision History
This section describes the revision history of this document.
Distribution List
Date
Version Description of Change Author
18-12-2016 1.0 First Draft of Final Project Deliverable
Guideline
Project
Coordination
Office
25-12-2016 1.1 First Deliverable Template
10-01-2017 1.2 Chapter No.1 Review again
01-02-2017 1.2 Chapter No.2
03-03-2017 1.3 Use case diagrams change and some
modified
05-04-2017 1.4 Change Sequence diagram according to use
case
29-05-2017 1.5 Change font and style according to the
template
This section describes the distribution list for the recipients of this document.
Recipient
Role / Designation Office Contact Details
Umair yaqub Lecturer,
Standard College
for Girls, Sialkot
Department of Computer
Science & Information
Technology
0524-268943
Umair yaqub Lecturer,
Standard College
for Girls, Sialkot
Department of Computer
Science & Information
Technology
0524-268943
Umair yaqub Lecturer,
Standard College
for Girls, Sialkot
Department of Computer
Science & Information
Technology
0524-268943
Umair yaqub Lecturer,
Standard College
for Girls, Sialkot
Department of Computer
Science & Information
Technology
0524-268943
Umair yaqub
Lecturer,
Standard College
for Girls, Sialkot
Department of Computer
Science & Information
Technology
0524-268943
CAPSTON PROJECT
On
Foreign language learner
Table of ContentsError! Bookmark not defined.
CHAPTER 1: FINAL PROJECT PROPOSAL ........................................................... 10
1.1. PROJECT OVERVIEW STATEMENT: ........................................................................... 11
1.2. PROJECT GOALS & OBJECTIVES: ............................................................................. 12
1.3. HIGH-LEVEL SYSTEM COMPONENTS: ....................................................................... 13
1.4. LIST OF OPERATIONAL FUNCTIONAL UNITS: ............................................................ 13
1.5. EXCLUSION: ............................................................................................................. 14
1.6. APPLICATION ARCHITECTURE: ................................................................................ 14
1.7. GANTT CHART: ........................................................................................................ 15
1.8. HARDWARE AND SOFTWARE SPECIFICATION: ............................................................. 15
CHAPTER 2: FIRST DELIVERABLE ........................................................................ 16
2.1. PROJECT/PRODUCT FEASIBILITY REPORT .................................................................17
2.2. PROJECT/PRODUCT SCOPE ...................................................................................... 17
2.3. TASK DEPENDENCY TABLE ..................................................................................... 18
2.4. TASK AND MEMBER ASSIGNMENT TABLE ............................................................... 19
2.5. TOOLS AND TECHNOLOGY WITH REASONING .......................................................... 20
2.6. RISK LIST ................................................................................................................ 21
2.7.PRODUCT FEATURES: ............................................................................................... 22
CHAPTER 3: SECOND DELIVERABLE .................................................................. 23
3.1 INTRODUCTION: ....................................................................................................... 24
3.2USECASE DESCRIPTION: ............................................................................................ 24
3.3 USECASE DIAGRAM: ................................................................................................ 25
3.3.1. Usecase Diagram of Login.............................................................................. 26
3.3.2. Usecase Diagram of Admin Panel .................................................................. 27
3.3.3. Usecase Diagram of Product Management ..................................................... 28
3.3.4. Usecase Diagram of User Management .......................................................... 29
3.3.5. Usecase Diagram of Insurnce Management ................................................... 30
3.3.6. Usecase Diagram of Order Management ........................................................ 31
3.3.7. Usecase Diagram of Sale Report .................................................................... 32
3.3.8. Usecase Diagram of Register .......................................................................... 33
3.3.9. Usecase Diagram of Brand Showcase ............................................................ 34
3.3.10. Usecase Diagram of Product Detail .............................................................. 35
3.3.11. Usecase Diagram of Order Placement .......................................................... 36
3.3.12. Usecase Diagram of Payment Processing ..................................................... 37
CHAPTER 4: THIRD DELIVERABLE ...................................................................... 38
4.1. INTRODUCTION: ...................................................................................................... 39
4.2. SYSTEM SEQUENCE DIAGRAM ................................................................................ 39
4.3. COLLABORATION DIAGRAM .......................... ERROR! BOOKMARK NOT DEFINED.54
4.4. DESIGN CLASS DIAGRAM ........................................................................................ 56
4.5. DATA MODEL.......................................................................................................... 57
CHAPTER 5: 2ND& 3RD DELIVERABLE APPROACH .......................................... 62
5.1. INTRODUCTION: ...................................................................................................... 63
5.2. ENTITY RELATION DIAGRAM: .................................................................................. 63
5.3. DATA FLOW DIAGRAM: ........................................................................................... 64
User Manual……………………………………………………………………………..66
Reference…………………………………………………………………………………80
Chapter 1: Final Project Proposal
Project Overview Statement
Project Title: Foreign Language Learner
Project Manager: Umair yaqub
Project Members:
Name Registration # Email Address Signature
Sidra Shahid 15 MIT 1306 [email protected]
Fatima Saeed 15 MIT 1307 [email protected]
Hajra Khalil 15 MIT 1309 [email protected]
Project Goal:
▪ Help to learn and pronounce words offline
▪ Eliminate Travel Time and Cost
▪ Provide information
▪ Remain Open All the Time
▪ Beginners can learn easily
▪ Test the answers with the feature of VR
Objectives:
1 Explore the Language / View details
2 Purchase product
3 Get product delivery in a specified period
4 Generate Sale Report
5 Create purchase orders and process these orders
Project Success Criteria: After downloading the APP, the learner can learn the pronunciation of
words and correct sentence making.
Assumptions, Risks and Obstacles:
Organization Address (if Any): The Standard College.
Type of Project: Research Development
Target End Users: Learners and developers
Development Technology: Object Oriented Structured
Platform: Mobile Based Distributed Desktop Based
Setup Configuration Other
Project Goals:
The title of our project is "FOREIGN LANGUAGE LEARNER” is aimed to provide a mobile
APP, which will facilitate the learner from anywhere. Basically, it is a mobile application that will
facilitate the People to learn the stuff online as well as offline. We offer number of words,
alphabets, their pronunciations, sentence making so the people can learn it easily without any cost.
Mostly people have to pay lots of money on learning by joining different kinds of institutes, and
they are unable to learn because English is a very wide language and it has no end. So we ensure
that by this APP, once downloading it the learner can learn the pronunciation of different words
and different sentences, alphabets , or confirm in case if they are confuse between different words
easily by sitting their homes or from anywhere.
▪ Help to learn and pronounce words offline
▪ Eliminate Travel Time and Cost
▪ Provide information
▪ Remain Open All the Time
▪ Beginners can learn easily
▪ Test the answers with the feature of VR
Project Objectives:
• Login Page
• Student Profile
• Different modules
• Select module
• All stuff related to selected module
• Quiz/MCQs
• Result of quiz/ MCQs
• Complains related to problems
High Level Components:
There are two sub modules in this phase.
a. Nouns, Pronouns, Adjective, Verbs, Proverbs etc.
Approved By:
Date:
b. Tense
Reading modules: 1. Beginner level
a) Alphabet reading and recognizing(Visual media)
b) Phonemes(Audio media)
c) Worlds making(Audio, video)
2. Medium level
a) Sentence reading
b) Understanding sentence structure
3. Expert level
a) Paragraphs reading
b) Comprehension
4. Testing a) MCQs based
b) Game based
5. Learning Material
a) Learning through audio Media
b) Learning through Videos
c) Learning through Text
Writing Module
1. Beginner level
a) Writing alphabets
b) Making words
2. Medium level
a) Sentence formulation
b) Grammar learning
3. Expert level
a. Paragraph writing
b. Picture illustration
4. Testing
c. MCQ’s based
d. Game based
5. Learning material e. Learning through Audio Media
f. Learning through Videos
g. Learning through Text
List of Optional Functional Units:
• Functionality: In information technology, functionality is the sum or any aspect of what a product,
such as a software application or computing device, can do for a user.
• Availability:
In information technology, high availability refers to a system or component that
is continuously operational for a desirable long length of time. Availability can b
measured relative to “100 operational” or “never falling”.
• Security:
Confidential data stored online from unauthorized access and modification.
Software security is an idea implemented to protect software against the malicious
attacks and other hacker risks so that the software continuous to function correctly
under such potential risks. Security is necessary to provide integrity, authentication and
availability.
• Reliability:
Reliability is an attribute of any computer related component that consistently
performs according to its specifications. It has long been considered one of three related
attributes that must be considered when making, buying or using a computer product or
component.
• Serviceability:
Serviceability is the measure of and the set of the features that support the ease and
speed of which corrective maintenance and preventive maintenance can b conducted
on a system.
• Usability:
Usability is the degree to which a software can be used by specified customers to
achieve quantified objectives with effectiveness, efficiency, and satisfaction in a
quantified context of use.
• Manageability:
The ability of a system to be controlled easily.
• Recoverability:
The item can be recoverable after being any loss.
Exclusions:
Following functional units will be developed in future:
• Solving problems online by comment procedure.
• Add vocabulary and latest words according to present era.
Application Architecture:
Gantt chart:
Hardware and Software Specification:
Memory requirements:
• 1 GB of RAM or more
• 1.2 GHz QUAD CORE CPU
• IN ALL ANDROID VERSION
Operating Systems:
In order to use this web based application, operating system that can be used is selected from
the following list of operating systems.
ID. Task Name Duration Start Finish Predecessors
1. Project Planning 2 weeks 01/03/2016 14/03/2016
2. Requirements 3 weeks 15/03/2016 05/04/2016 1
3. Proposal 2 weeks 06/04/2016 20/04/2016 2
4. Analysis 2 weeks 05/05/2016 19/05/2016 2
5. Design 1 Month 20/05/2016 20/06/2016 4
6. Development 2 Month 21/06/2016 20/08/2016 5
7. Implementation 10 days 21/08/2016 31/08/2016
8. Testing 5 days 01/09/2016 05/09/2016 5
9. Final product 5 days 06/09/2016 11/09/2016
Chapter 2: First Deliverable
Project Feasibility:
We thoroughly assess the proposed system to check its feasibility and concluded that this system
is feasible to develop. We have the required technology and technical expertise to complete the
system. Users could operate it and easily find solution to certain problems. We have applied cost
estimation and found that the proposed system is economically feasible. We can completely
developed and implement the system in time with the available team members and resources.
Requirements are clearly defined with scope of the system. In short we can say that this proposed
system is technically, operationally and economical feasible to develop.
Project Scope:
App will facilitate learners to learn English from home or anywhere. Planed approach will be
used to develop this project. It gathers requirements by searching standard oxford
English books for beginners and medium level and at export level different website’s
will be searched to gather data. Then is design phase, models will be developed to
understand different modules of the system. Implementation will take place
afterward and android studio will be used as main IDE to develop. System will be
tested at unit testing approach, as the test will be conduct beside implementation and
final integration testing will be done on Samsung handsets.
Task Dependency Table:
Tasks and Member Assignment Table:
ID. Task Name Duration Predecessors
1. Project Planning 2 weeks
2. Requirements 3 weeks 1
3. Proposal 2 weeks 2
4. Analysis 2 weeks 2
5. Design 1 Month 4
6. Development 2 Month 5
7. Implementation 10 days
8. Testing 5 days 5
9. Final product 5 days
Tools and Technologies Used with Reasoning:
Android studio
Android studio is an integrated development environment (IDE) from Google that provide
developers with tools needed to build applications for the android OS platform. Android studio is
available for download on windows, Mac and Linux. The foundation of android studio is based on
intelliJ IDEA. The android studio is free to download and use. It has a rich UI development
environment with templates to give new developers a launching pad with android development.
Developers will find that studio give them the tools to build phone and template solutions as well
as emerging technology solutions for android TV, android wear, android auto, glass and additional
contextual model.
JDK
People new to java maybe confused about whether to use the JRE or the JDK. To run java
applications and applets, simply download the JRE. However, to develop java applications and
applets as well as run them the JDK is needed. Java developers are initially presented with two
JDK tools java and javac. Both are run from the command prompt.
ID. Task Name Task Assign to
1 Project Planning Sidra ,Hajra
2 Requirements Hajra
3 Proposal Fatima
4 Analysis Sidra
5 Design Sidra , Fatima
6 Development
Sidra ,Fatima
,Hajra
7 Implementation
Sidra, Fatima
,Hajra
8 Testing Hajra
ECLIPS
Eclipse is an integrated development Environment. Eclipse basically encodes the data. The
Android SDK requires Eclipse version 3.3 or later. Eclipse is the recommended integrated
development environment for Android development, though developers may also use a text
editor and command-line tools to create Android apps. Eclipse supports many programming
languages, including Java, C++, Python, Perl, Ruby on Rails and more.
SDK
A software development kit is typically a software development tools that allow the creations of
applications for a certain software package, software framework, hardware platform, computer
system, video game console, operating system, or similar development platform.
Risk List:
• Is the customer technically sophisticated in the product area?
• Estimated size of the product in LOC or FP?
• Number of users of the system?
• Affect of any product on company revenue?
• Governmental constraints on the system?
• On-line help and documentation for the system?
• End-user insists on new requirements.
Product Features:
1. Search Box: Having a search box positioned well, will allow our visitors to quickly search
for the product that they are looking for.
2. Featured Products: By displaying featured products on our home page or on the side
columns of our site will inform visitors of top selling products, sales offers or it can be a
general products that would be push further and make sure they get noticed.
3. Related product: This is a great up selling feature, which will show visitors what other
products they can purchase along side what they are currently viewing, a cleaver way of
positioning this is with a heading,Customers who bought this also bought: This will
encourage your visitors to purchase more then one item at once.
4. Product Zoom: Having a good zoom feature for our product images, is always a plus point
online, as it allows visitors to see the minute details of products, which works well, as some
times customers prefer to feel and touch, so we can easily replace this by having a good zoom
feature, which really brings out the details in our product.
5. Categories: Have clear categories on our site to listproducts into, and have categories
displayed somewhere easy to access, e.g. across the top or on the side columns.
6. Good Navigation: Navigation is extremely important on an e-commence site, users should
be able to easily access various sections of the site, along with a quick link back to the
shopping cart.
7. Good Return Policy: When buyers see a good return policy they will have more assurance
and peace of mind if eversomething was to go wrong they can easily return their product. A
good policy generally increases sales, as customers feel more safer to buy.
8. Customer login & registration: Give the option for customers to register on our site, so
when they do return they don’t need to enter all their billing and payment details in again,
giving them the flexibility to quickly check out.
9. Good Graphics: Make good use of graphics banners and images on the site, to attract
visitors.
10. Delivery Information: Always inform how we are going to be delivering your products to
the customers, along with clear time scales, so that our customers know when to expect the
delivery.
Chapter 3: Second Deliverable For Object Oriented Approach
3.1 Introduction:
Requirements engineering process provides the appropriate mechanism for understanding what
the customer wants, analyzing need, assessing feasibility, negotiating a reasonable solution,
specifying the solution unambiguously, validating the specification and managing the
requirements as they are transformed into an operational system.
3.2 Use Case:
A use case is a series of related interactions between a user (or more generally an “actor”)and a
system that enables the user to achieve a goal.
Use Case Diagram
Admin
Login & Logout
Product
Management
User
Management
Insurance
Management
Order
Management
Sale Report
Register
Brand Showcase
Search
View Product
Detail
Order
Placement
Payment
Processing
Customer
Use Case Diagram Related toAdmin Side
3.2.1 Use Case 01_Log_in
This is the entry point of Suleman Electronics Sales Center. Only authorize user can login to the
system with authorize user name and password.
Use case ID: Use Case 01_Log_in
Use Case Name: Admin Login
Actors
Admin
Purpose
Allow the member to log in
Pre-Conditions
System running perfectly.
Course of Event
• Member enters the username and password.
• System will check the username & password.
• The system will allow the user to log in if the entered data is
authentic.
Alternate course
of event
System will not response.
3.2.2 Use Case 02_Admin_Panel
The admin can interact with all other modules in the system after logging in. This will provide
the all functions in a single view point.
Admin
Login & Logout
Product
Management
User
Management
Insurance
Management
Order
Management
Sale Report
Use case ID: Use Case 02_Admin_Panel
Use Case Name: Admin Login
Actors
Admin
Purpose
Allow the member visit main window
Pre-Conditions
System running perfectly.
Course of Event
• User can visit all
• System will check the username & password.
• The system will allow the user to log in if the entered data is
authentic.
Alternate course
of event
System will not response
3.2.3Use Case 03_ Product_Management
This module contains the information about the products. It will enable the admin add, delete,
update the products.
Admin
Product
Add Product
Delete Product
Update Product
Use case ID: Use Case 03_Product_Management
Use Case Name: Product_Management
Actors
Admin
Purpose
Admin manage product detail and model description.
Pre-Conditions
System running perfectly.
Course of Event
• The Admin manage the product.
• User was assigned the rightful access to the application to do the
order of desired product.
Alternate
course of event
System will not response.
3.2.4 Use Case 4_User_Management
This module contains the information about the users. It will enable the admin add, delete, update
the users.
Admin
User
Add User
Delete User
Update User
Use case ID: Use Case 4_User_Mangement
Use Case Name: User_Management
Actors
Admin
Purpose
Admin have the authority to manage the EndUser.
Pre-Conditions
System running perfectly.
Course of Event
• The Admin manage the product.
• This will allow the user to keep the record about users.
Alternate course
of event
System will not response.
3.2.5 Use Case 5_ Insurance_Management
This module will provide the facility to insure the products to the customers.
Admin
New
Warranty
Insurance
Use case ID: Use Case 5_Insurance_Management
Use Case Name: Insurance_Management
Actors
Admin
Purpose
Admin can be insure the products.
Pre-Conditions
System running perfectly.
Course of Event
• Insurity about the products is provided to the customers.
• Products must be Insure.
Alternate course
of event
System will not response
3.2.6 Use Case 6_ Order_Management
This module will store the information about all the orders and managed them.
Admin
Order
Login
Send Massage
<<include>>
<<include>>
Check Order<<include>
>
Use case ID: Use Case 6_Order_Management
Use Case Name: Order_Management
Actors
Admin
Purpose
Admin has the authority to manage and accept the order of the products.
Pre-Conditions
System running perfectly.
Course of Event
• Customers will visited the website anytime.
• Message should be sent to the customers about the order.
Alternate course
of event
System will not response
3.2.7 Use Case 7_ Sale_Report
This will provide the reports about the sales and purchases on daily, weekly, monthly and annual.
This will also provide the reports of staff, items and categories.
Admin
Sale
Report
Daily
Items
Use case ID: Use Case 7_Sale_ Report
Use Case Name: Sale_Report
Actors
Admin
Purpose Admin generate the report on weekly and monthly basis.
Pre-Conditions System running perfectly.
Course of Event
• The admin can generates reports on the bases of different time
period e.g daily, monthly, annually.
• The admin can also generate reports about the staff, category and
items.
Alternate course
of event
System will not response
Use Case Diagram Related to Customer side
3.2.8 Use Case 01_Register
This is the registration point of uleman Electronics Sales Center. The person who brought
desired products fill the registration form for login to the system with authorize user name and
password.
Customer
User Name
FAILED
Password
Login
Reject
Accept
Use case ID: Use Case 1_Regiater
Use Case Name: Inventory
Actors Customer
Purpose Allow the customer to Register.
Pre-Conditions System running perfectly.
Course of Event • Customer will Request for registration
• The System will load the register form and Display.
• Customer will provide the register form information.
• The System will verify and if correct will provide account.
Alternate course
of event
System will not response.
3.2.9 Use Case 02_ Brands_Showcase
This module can describe the brands of multiple products to the customer.
Customer
Brands
Add Brands
Delete barnds
Edit Brands
Use case ID: Use Case 2_Brands_showcase
Use Case Name: Category
Actors Customer
Purpose Allow the customers to view the brands.
Pre-Conditions System running perfectly.
Course of Event • Customer visited the website any time.
• Customer was assigned the rightful access to the application to do
the order for desired product of multiple brands.
Alternate course of
event
System will not response.
3.2.10 Use Case 3_View_Product_Detail
This module provide the interface to the customer to view different products and know about their
details.
Customer
Search
View Product
Detail
Search Product
Use case ID: Use Case 3_View_product_detail
Use Case Name: Category
Actors Customer
Purpose Allow the customers to view the products of different brands.
Pre-Conditions System running perfectly.
Course of Event • Customers can see different products and their detail.
• Customer will visited the website anytime
Alternate course of
event
System will not response.
3.2.11 Use Case 4_ Order_Placement
This module allow the customers to Browse and select the items and place the order.
Customer
Order
Placement
Browse &
Select Items
Place Order
Use case ID: Use Case 4_ Order_Placement
Use Case Name: Order_Placement
Actors Customer
Purpose Allow the customer to access the system for placing an order.
Pre-Conditions
System running perfectly.
Course of Event • Customer will Place an order and Check the status.
• Customer was assigned the rightful access to the application to do
the order for desired products.
Alternate course of
event
System will not response
3.2.12 Use Case 5_ Payment_Processing
This module contains the information about the sales being performed and enables the
administrator to print the detail information.
Customer
Payment
Processing
Submit Payment
Submit Payment
Details
<<include>
>
<<include>>
Use case ID: Use Case 5_ Payment_Processing
Use Case Name: Payment_Processing
Actors Customer
Purpose Customer needs to know about the Payment Method.
Pre-Conditions
System running perfectly.
Course of Event • Customers have to view the payment methods.
• Customer was assigned the rightful access to the
application to do the order for desired products.
Alternate course
of event
System will not response
Chapter 4: Third Deliverable For Object Oriented Approach
4.1 Introduction:
Third deliverable is all about the software design. In the previous deliverable, analysis of the
system is completed. So we understand the current situation of the problem domain. Now we are
ready to strive for a solution for the problem domain by using object-oriented approach. Following
artifacts must be included in the 3rd deliverable.
1. System Sequence Diagram
2. Sequence Diagram
3. Collaboration Diagram
4. Design Class Diagram
5. State Transition Diagram
6. Data Model
Now we discuss these artifacts one by one as follows:
4.2 System Sequence Diagram:
A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of
methods in each object, and the order in which the invocation occurs is captured in a Sequence
diagram. This makes the Sequence diagram a very useful tool to easily represent the dynamic
behavior of a system.
4.2.1 Admin Login
Admin HomePageDatabaseLogin
login page
Enter
username &
password
verify
check enter
data
invalidvalid
homepage
▪ Admin visit the log in page.
▪ Admin enter the username and password.
▪ System check the entered data if data is valid then main page will display.
▪ In cases of invalid data the error message will be display.
4.2.2 Admin add new Product
Admin ProductHomepage
login page
enter
username &
password
Succes
savewrong
username &
password
add
product
▪ Admin first login.
▪ Visit the product page and click Add product.
▪ Then add the product.
▪ And save the setting.
4.2.3 Admin Edit New Product.
Admin ProductHomepage
login page
enter
username &
password
edit product
Succes
savewrong
username &
password
▪ Admin first login.
▪ Visit the product page and click edit product.
▪ Then edit the product.
▪ And save the setting.
4.2.4 Admin Delete Product
Admin ProductHomepage
login page
enter
username &
password
Succes
savewrong
username &
password
delete
product
▪ Admin first login.
▪ Visit the product page and select and then delete product.
▪ And save the setting.
4.2.5 Add New User
Admin UserHomepage
login page
enter
username &
pass
Succes
save
wrong
username &
password
add user
Valid
invalid
▪ Admin first login.
▪ Visit the User page and click Add user.
▪ Then enter the user.
▪ And save the setting.
4.2.6 Admin Edit User
Admin Edit UserHomepage
login page
enter
username &
password edit user
Succes
save
wrong
username &
password Valid
invalid
▪ Admin first login.
▪ Visit the User page and Select the user.
▪ Edit the selected user .
▪ And save the setting.
4.2.7 Delete User
Admin Edit UserHomepage
login page
enter
username &
password edit user
Succes
save
wrong
username &
password Valid
invalid
▪ Admin first login.
▪ Visit the User page and Select the user.
▪ Delete the selected user .
▪ And save the setting.
4.2.8 Order Management
Admin Email OrderHomepage
login
process order
send email
enter
username &
password
Invalid
▪ Admin first login.
▪ Visit the order page and check the detail.
▪ Process the order
▪ Send sms to the User.
4.2.9 Sale Report
Admin DailyReport Items
• Admin Click the Reporting.
▪ He/she can generate Reporting on Daily bases.
▪ He /she can also generate reports of items..
4.2.10 Customer Register
Customer SuccessDatabaseSignup
registration
fill the form
verify
check enter the
data
invalid form
data
valid form
data(save)return
▪ Customer visit the registration page.
▪ Customer enter the username and password.
▪ System check the entered data if data is valid then main page will display.
▪ In cases of invalid data the error message will be display.
4.2.11 Brand Showcase
select brands
Customer ProductBrandWebsite
visit website
display
product
▪ Customervisit the website.
▪ Customer Select the brand.
▪ System check the selected brand if brand is available then the Product page will display.
4.2.12 View Product Detail
select product
Customer View Detail ProductSearch
search product
view product
detail
▪ Customersearch the product(s).
▪ CustomerSelect the product(s).
▪ System check the selected product if product is available then the product description
page will display.
4.2.13 Order Placement
view
shopping cart
Customer CheckoutShopping cartProduct
select
product(s)
select
checkout
Showcase
Add to cart
▪ CustomerUser visit the page.
▪ CustomerSelect the product(s)
▪ Click add to cart.
▪ View Add to cart.
▪ Add select Checkout.
4.2.14 Payment Processing
Customer Payment InfoOrder DetailOrder
place an order
check detail
check
payment
info
Succes
save
▪ CustomerUser visit the page.
▪ Place an order.
▪ Click the detail related to the order.
▪ Check payment info about the order.
▪ Save the setting.
4.2.15 Change Password
Admin/
CustomerDatabaseSystem
login
change password
request
ask for old &new
password
enter old & new
password
change password
successfully
verify old password
& set new password
password change
• Admin/ user have to login
• Click on change password
• Enter old password
• Verify the new password
4.3 Collaboration Diagram
4.3.1 For Customer Registration
4.3.2 For Online Customer
4.3.3 For Online Administrator
4.4 Design Class Diagram
Class diagrams are the most common diagrams used in UML. Class diagram consists of classes,
interfaces, associations and collaboration. Class diagrams basically represent the object oriented
view of a system which is static in nature. Active class is used in a class diagram to represent the
concurrency of the system. Class diagram represents the object orientation of a system. So it is
generally used for development purpose. This is the most widely used diagram at the time of
system construction
4.5 Data Model
The data model is a subset of the implementation model, which describes the logical and physical
representation of persistent data in the system.
The Relational Data Model
4.5.1 Brands
brand
brand_id brand_name
4.5.2 Cart
cart
username
prod_id
cart_nameuser_cnic
prod_name prod_price
4.5.3 Content
content
content_id content_positioncontent_pagecontent_text
4.5.4 Delivery
delivery
deliv_answerdeliv_questionsrno
4.5.5 Insurance
insurance
ins_valueid
4.5.6 News
news
news_img
news_desc
news_date
news_title
news_id
4.5.7 Order Details
order_details
prod_price
prod_qty
prod_name
prod_id
order_id
4.5.8 Order Status
order_status
order_statusis_insuredorder_amount
order_datecust_idorder_id
4.5.9 Product
product
prod_featuredprod_img_nameprod_desc
brand_id
prod_price
prod_qtyprod_color
prod_modelprod_nameprod_id
4.5.10 Register
register
cust_addresscust_cniccust_contactno
cust_emailcust_namecust_id
4.5.11 User
user user_levelpassword
usernameregister_iduser_id
Chapter 5: 2nd & 3rd Deliverable For structured Approach
5.1. Introduction:
Analysis & Design Model for structured approach must contain following artifacts:
1. Entity Relationship Diagram 2. Data Flow Diagram (Functional Model) 3. State Transition Diagram (Behavioral Model) 4. Architecture Design 5. Component Level Design
5.2. Entity Relationship Diagram:
In the analysis model, Entity Relationship Diagram is used to understand the system under
consideration with respect to entities involved and their relationships. Each entity is documented
by extracted its attributes, cardinality, and modality.
5.3. Data flow diagram (Functional Model)
DFD is all about to identify the major processes in your system and develop Data Flow Diagram up to
required level.
DFD Constructs:
=
Context Level DFD
A context diagram shows the context into which the business process fits. It also shows the overall
business process as just one process and shows all the outside entities that receive information
from or contribute information to the system.
Level 1 Diagram
This diagram shows all the processes that comprise the overall system and how information moves
from and to each process. Data stores are added to it.
Orders Order Assembled Shipping order
Suleman
Electronic
Online
System
Customer Admin
Order Detail
Product Detail
Address Information
Customer Proces
s order Warehouse
Store
Customer
Information
Publisher
ShippingDetail
Verify
Shippin
g
Assemble
d
Assemble
customer
Assemble
Requisitio
User Manual:
Index Page
This is front view of website. It will show all products and brands. Customer visit this website and select
product, search product, purchase product of his own choice. Customer can navigate to other pages
through top menu.
Product
All products are shown on this page. Customer can view products and click on “Add to Cart” button to
add items to the cart.
News
All latest and old news are shown on this page. Customer can view updated news about products and
events or offers(if any).
Register
Customer has to register first for creating account. For order placement customer has to register
first.Customer will fill form accordingly as shown in above.
Add to cart
When customer purchase product and add to cart, products added to cart are shown on this page. This
page show complete details of product customer want to purchase.
Checkout
When customer click on checkout button. This page will be shown intimating customer about details of
payment.
Forget Pass
This page helps to change password.
Change Pass successful
After successful password change successful message will be displayed.
Admin Panel
This is front page after login to admin panel. This page show all option that can navigated by admin.
Brand
Admin can manage brands. This page will display all brands in the system.
Product
Add product
News
User
Order
This page shows complete order received in system. Admin can click on any order to delete.
Sale Report
This page shows sale report entered in system.
References
[1] Bonjour Electronics, Bonjour Repair Centre
Available: http://www.bayelectronic.com/
[2] Micro Center, Computer and Electronics
Available: http://www.microcenter.com/site/products/electronics.aspx
[3] New Egg, Marketplace
Available: http://www.newegg.com/Clearance/Store
[4] Shop Rex, Super market
Available: http://metropk.shoprex.com/
[5] Best Buy Outlet,
Available: http://www.bestbuy.com/site/electronics/outlet-refurbished-
clearance/pcmcat142300050026.c?id=pcmcat142300050026
