FYP Documentation

[PUBLIC HEALTH SURVEILLANCE]
Qarshi University
Department of Computer Science
Final Year Project Documentation Format

Guidelines
1
Qarshi University, Lahore
PHS APP
Session: BSCS Fall 2016
Project Advisor: UMER AYUB
Submitted By
Aniqa Rouf Bscs-f-17-

Arooj Khalid Bscs-f-17-57
Hafiza zahra Bscs-f-17-57

Department of Computer Science
2
DECLARATION
We hereby declare that this project report is based on our original work and has not been
copied. We also declare that it has not been previously and concurrently submitted for
any other degree or award at Qarshi University, Lahore or other institutions.
Ibraheem Bakhtyar Khilji

Bscs-f-16-81
Makhdoom Ali Minhas

Bscs-f-16-08
3
STATEMENT OF SUBMISSION
This is to certify that Aniqa Rouf Roll No. , Arooj Khalid Roll No. BScs-17-57 and
Hafiza Zahra Roll No. BScs-16-08 have successfully completed the final project named
as: “MI Shopper” at the Qarshi University, Lahore, to fulfill the partial requirement of
the degree of Bachelors of Science in Computer Science.
___________________
_____________________
Project Advisor
Chairman, Department of Computer Science
Sir Umer Ayub
Dr. Syed Muhammad Ahsan
Lecturer, Department of Computer Science
Associate Professor
4
Acknowledgement
With many thanks to our supervisor Mr. Umer Ayub for his leadership and knowledge
which made the completion of this thesis possible. We would not have been able to do
our final year project without his excellent guidance in every step of our project work.
We would also like to express our sincere gratitude to lecturer, Department of Computer
Science, Qarshi University, who has been a source of inspiration and motivation for us.
Finally, to all of the women who sacrificed their time, and the support of these well-
known companies for their participation.
Aniqa Rouf
Bscs-f-16-81
Arooj khalid
Bscs-f-17-57
Hafiza Zahra
Bscs-f-17-57
5
Contents
STATEMENT OF SUBMISSION................................................................................2
Acknowledgement...........................................................................................................3
1.5 Project/Product Feasibility Report.............................................................................9
1.5.1 Technical Feasibility.........................................................................................9
1.5.2 Operational Feasibility.....................................................................................9
1.5.3 Economic Feasibility.........................................................................................9
1.5.4 Schedule Feasibility........................................................................................10
1.5.5 Specification Feasibility..................................................................................10
1.5.6 Information Feasibility...................................................................................11
1.5.7 Motivational Feasibility...........................111.5.8 Legal & Ethical Feasibility
...................................................................................................................................11
1.6 Project/Product Scope..............................................................................................11
1.7 CPM - Critical Path Method....................................................................................12
1.7.1 Gantt chart............................................................................................................13
1.8 Introduction to Team Members and Their Skill Sets:.............................................14
2. Design.............................................................................................................16
2.1 Systems Specifications.......................................................................................16
2.2 Context Level Data Flow Diagram...................................................................18
BACK-END PROCESSING......................................18
2.3 Use case Description................................................................................................19
2.4 Use case Diagram (refined and updated).................................................................20
BACK-END PROCESSING......................................21
2.5 Domain Model.........................................................................................................22
1.6 Sequence Diagram..............................................................................................23
6
Defining a Sequence diagram....................................................................................24

2.7 Collaboration Diagram............................................................................................28
Contents:....................................................................................................................28
2.9 Data Model..............................................................................................................30
3 USER INTERFACE:....................................................................................................33
3.1 Log In..................................................................................................................34
3.2Verification Phase:....................................................................................................35
3.3Sign Up.....................................................................................................................36
3.4Chatting Panel...........................................................................................................37
3.5Help Desk.................................................................................................................38
3.6User Profile...............................................................................................................39
3.7Setting Menu.............................................................................................................40
3.8Account Settings.......................................................................................................41
3.9Find Friends..............................................................................................................42
3.10 Remove Contacts...................................................................................................43
3.11 Chatting………………………………………………………………………….44
7
CHAPTER 1
INTRODUCTION
8
1. Introduction
The internet has changed many aspects of society, from business to recreation, from culture to
communication and technology, as well as shopping and travelling. This new form of
communication has provided new ways of doing business with the help of technological
development. E-commerce is the new way of shopping and doing business. Technology has
allowed companies to promote and sell their products on new markets, overcoming
geographical borders as never before. Consumers have access to a wider market of products
when they use wireless and internet technologies. Mobile devices with wide access to the
Internet have allowed companies to reach consumers in more diverse ways, thus ensuring deep
market penetration. Our project is an e-commerce android app . It is a mobile commerce system
which run under Android platform that used for promotion and selling your product with single
application. With powerful Admin Panel can manage the order, create category and product
menu. You can add, update, update or change that product menu, category, currency and
change admin password with generate password, etc.
1.1 Problem Statement and Justification
This project is to create an e-commerce android application with a server and users to
enable the users to buy products. To develop an instant trading solution to enable users to
seamlessly buy products. The project should be very easy to use enabling even a novice
person to use it.
1.2 Application Architecture
The e-commerce application works in two forms.
o User form:
In this form, all the users can view products of different categories and then
buy them.
9
o Admin form:
In this form the admin can add new products for the users to buy.
Here is the structure of our Chat Application.
1.3 Hardware and Software Specification
Before starting our project we focused on what kind of software and

hardware will be need for this application. Our sources should be limited because
we do not need more equipment for our project and software we are using is also
open source so we just spend cost for hardware purchase. Specification for
hardware and software are:
 HARDWARE:
Personal Computer with good processor and Android Studio.
 SOFTWARE:
Updated Version of Android Studio installed in.
SDK tools.
Java script Support.
1.4 Tools and technologies used with reasoning
Our technical team master a comprehensive set of tools and technologies

during project development. A topic-oriented structure is provided below.
1. Java
2. Xml
3. Firebase
4. Android SDK
5. Google play services
 Java:
10
Our source code is Java in android. It is used for system

stability. It is most important when programs compile code for
virtual machine, they do not need to recompile.java language
is used to code the apps.
 Xml:
In Android we use xml for designing our layouts because xml is
lightweight language so it doesn't make our layout heavy
.
 Firebase:
Firebase provides a real time database and backend as a service. In our app
firebase is used as API that allows application data to be synchronized
across users and stored on Firebase’s cloud
.
 Android SDK:
Android studio is a software used to develop Android apps and to emulate
them. It is the main tool for our application development.
 Google play services:

Google play services gives us the freedom to use the newest APIs for
popular Google services without worrying about device support. Updates
to Google Play services are distributed automatically by the Google Play
store and new versions of the client library are delivered through the
Android SDK manager.
1.5 Project/Product Feasibility Report
1.5.1 Technical Feasibility

We are using some Extra-Ordinary functionality for the betterment of the end
user. The team members have comprehensive knowledge of the domain, Desktop
environment tools and game engine environment and technology.
1.5.2 Operational Feasibility

MI Shopper is a e-commerce application. Which provide a comfortable
environment where everyone can easily browse catalog and order stuff easily.
They can easily access the app no matter where they are.
11
1.5.3 Economic Feasibility

Mostly, most of the applications are costly and does not fit to every android
version. As our e-commerce application is suitable for mostly many versions of
android. It does not cost much. As it does need any online or extra purchases. And
it is available for almost many versions of android. We are using the play Store
for our application availability for the intended users. There is zero cost for
development, hardware and Software.
1.5.3.1 Development Feasibility

There is zero development cost because Android Studio is an open source application
software. It is easily available at android site. As Justification for the benefit/cost analysis
relative to the project is to be measured in economic feasibility. As we are developer as
well so there’s no need for development cost.
1.5.3.2 Hardware Feasibility

Cost to purchase hardware for the development of this website is one time
because every group member owns his/her machine (Personal computer).
1.5.3.3 Software Feasibility

Android Studio is an android development software that helps to develop an
android application. Android Studio used Java Script as backend language. As
android studio does not cost anything because it’s an open source software easily
available on internet (free of cost), so software for this project will cost us
nothing.
1.5.4 Schedule Feasibility

Time is an important factor. Team Members are working according to time and
activity plan. The first phase is “requirement gathering” and it has reserved 2
weeks to complete. Second phase is “design” and in this phase mockups and the
GUI within 4 weeks. The third phase is “implementation” and it has taken 8- 11
weeks. The fourth phase is “testing and changes” it has taken 3 weeks to
complete. The last phase is “documentation” and it is in parallel with other tasks
and takes 8-10 weeks to complete. Project took work around twenty weeks (4
months almost) while our whole team was working 8 hours daily.
12
1.5.5 Specification Feasibility

Requirements are the features that the system must have or a constraint that must
be accepted for the User.
SPECIFICATIONS CONSTRAINTS FEASIBILITY RECOMMENDED

SOLUTIONS.
Sign-in Correct and Yes User name & password
standard user require or phone
name & password number & Email
already Exist.
Efficient and fast. Small size app Yes Module-shifting.
Multi-language Efficiently less storage
chat space is used.
Availability Fast and secure Yes User must sign apple
installation store or app store to
download this game.
1.5.6 Information Feasibility

“MI Shopping app” is an android application, developed by Android Studio with
the backend language of java and xml. Backend development is being done in xml
language. It’s an e-commerce application that helps to secure the user account
from random users. It protect the privacy of every user.
1.5.7 Motivational Feasibility

User’s order history will be available until user deletes them. The user’s database
will be updated on firebase.
1.5.8 Legal & Ethical Feasibility

This is highly secure and is being developed under strict supervision. The data of
every user will be secure. No one can access to others personal data.
13
1.6 Project/Product Scope

 Selling can be centered around the Global client.
 Pre-deals, subcontracts, and supply.
 Financing and protection.
 Commercial exchanges, requesting, conveyance installment.
 Product administration and support.
 Cooperative item improvement.
 Distributive co-employable working.
1.7 CPM - Critical Path Method
Activity Activity Name Duration

Days
1 Requirement Gathering 14
2 Primary Investigation 10
3 Design 25
4 Development 20
5 User panel 10
6 Admin panel 8
14
7 Testing 15
8 Internal Testing 10
9 External Testing 8
Documentation 7
10
1.7.1 Gantt chart
15
1.8 Introduction to Team Members and Their Skill Sets:
There are three team members working on this project. We divided project evenly
onto three of us.
1. Ibraheem Bakhtyar Khilji (BSCSF-16-81)
● .net framework
● Java Script.
● C#.
● Android development..
● Database.
● MS office.
● Marketing Experience
2. Makhdoom Ali Minhas (BSCSF-16-08)

● Marketing Experience.
● Database.
● Design Document.
● Module level Documentation.
● Java script.
● MS office.
● Wordpress
● HTML
● CSS
16
CHAPTER 2
DESIGN
17
2. Design
The design phase of this project started early in September and we worked on the
following aspects which are as following :
2.1 Systems Specifications

The following are the clauses that must be included while describing the system
specifications.
Introduction
Android studio is a platform for mobile application development. It is a
development tool to develop android application. It’s an open source software
available on the internet. Our shopping application provide a easy to use shopping
app for buying of products.
Following are the main steps we have followed in making the shopping
application
Existing System
As there are a lot of e-commerce applications. We made a simple and
elegant android application with an interactive user interface.
Organizational Chart
Organizational chart will be very much supportive to get a better overview
of the e-commerce application. As it defines the perspective of the trading.
Scope of the System

 Selling can be centered around the Global client.
 Pre-deals, subcontracts, and supply.
 Financing and protection.
 Commercial exchanges, requesting, conveyance installment.
 Product administration and support.
 Cooperative item improvement.
 Distributive co-employable working.
User friendly application:
18
Application with a friendly environment would provide a comfortable

situation. In which we can communicate in a friendly manner and we can
easily communicate with our customers.
● User experience:
This application will give user a free environment to communicate
comfortably. Users will have a good experience. And will give a strong
review about our application. It allows users to communicate with seller in
an elegant manner.
Summary of Requirements (Initial Requirements)
● Download Application
● Sign Up
● Sign In
● Rate us option (feedback is necessary)
● Admin Panel
● User Panel
● Delete Account
● Log Out
19
2.2 Context Level Data Flow Diagram
Sales
History
Management Generate
Store Sales
Management
Report
Generate
User User Sale
Management
Report
User MI Generate
Profile Shopper User Profile
Management App Report
Login Generate
Management Sales
History
Report
System Check user

User Login
Management Generate Detail
System User
Report
20
2.3 Use case Description

Use case “Sign Up” which is the first use case in which a user have to enter
his/her required details to create an account. After account creation the user will be
redirected to “Log In” the Second use case. The third use case will be “Browse Catalog”
in which user can browse products. The fourth one is “add to cart” the user can add
products to cart which he wants to buy. The fifth is “Remove Product” in which a user
can easily remove unwanted products from the cart. The last one is “Log Out” in which
user can log out at any time.
Use case Name: Sign Up
Use case Name Sign Up
Actor User
Precondition User should have successfully downloaded
the app and have an active connection
Success scenario Start the app
(Basic flow)  First download the app from play
store
 User install app on his/her required
details
 User click on sign up
 The user will receive (user created
successfully) message
Extension Name already exist , resembles or similar
(alternate flow) Password is too short
Phone format is not incorrect
Email address format is not valid
Post condition user successfully installed the app

user created account successfully
UCD
21
Use case Name: Log In
Use case Name Login

Actor User
Precondition User should have successfully downloaded
the app and have an active connection
Success scenario
(Basic flow)  Have an account
 Enter his/her email id and password
according to the sign up info
 User click on login
Extension In correct email id password
(alternate flow) Have no connection or connection lost
App crash while starting app
Case sensitive password
Forgotten user name or password
Post condition User successfully login to their account
On home view of the app
UCD
Use case Name: browse catalog
Use case Name Browse Catalog

Actor User
Precondition User should be logged
Success scenario  User can successfully browse all the
(Basic flow) products
 User can successfully see the
product names, price and
description
Extension User cannot see all the products in which
(alternate flow) case restart the app
Post condition User should be able to click on products
and add them to cart
UCD
Sign Up
22
Log In
Catalog
Use case Name: Add to cart
Use case Name Add to cart

Actor User
Precondition User can add products to cart
Success scenario  Add a product to cart
(Basic flow)
Extension Log out
(alternate flow)
Post condition Add payment method
UCD
Sign Up
Log In
Catalog
23
Use case Name: remove products
Use case Name Remove products

Actor User
Precondition Users cart should have products
Success scenario  User are free to remove product at
(Basic flow) any time
 User are free to remove unwanted
product
Extension Connection lost
(alternate flow)
Post condition User successfully remove product
UCD
Cart
Remove Product
24
Use case Name: log out
Use case Name Log out

Actor User agent
Precondition User should have successfully login to their
account
Success scenario Login
(Basic flow)  Home screen
 Active connection
 User willing wants to logout from
app
Extension Connection lost app crash

(alternate flow) App crash
Post condition user successfully log out from app
On main screen to login or sign up
UCD
Now we discuss these artifacts one by one as follows:
25
Brief description
Use case is something that describe the overall functionality of app. There are many
conditions must be met before starting the app. First, user must have download app in
his/her mobile. Second, we should provide a sensible and easy environment that helps
user to develop interest in our app and that helps us to keep long term relationship. Third,
the code is easy going and error proof that gives user a quick response .
Preconditions
 User must have internet connection to download the app.
 Install the app.
Basic flow
As our motive is to provide a relaxing platform to a user so after starting the app our
success scenario will be accomplished if user give us a good review.
Post conditions
The conditions should necessary met. When we successfully achieved all the above
describe goals and there are positive influence of our app in people life and don’t leave
any bad impact on their mind.
26
2.4 Use case Diagram (refined and updated)
Use case diagram are as following
Catalog
Cart
Ship
27
2.5 Domain Model

Domain models represent the set of requirements that are common to systems
and that can be represented relationship with each other. The requirements
represented in a domain model include:
 App and user relationship

 User communication interaction
2.6 Sequence Diagram

A sequence diagram shows object interaction arranged in time sequence.
It depicts the object and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of
the scenario
Following are objects that are use in our project
 Sign In
 Verification Phase
 Sign Up
 Catalog Panel
 Adding to Cart
 Removing from Cart
 Remember Me
 Categories
 View profile
 Update profile
 Update status
 Account setting
 Setting menu
28
Defining a Sequence diagram

Following is a simplest form of sequence diagram of few panels:
Figure 1: startup menu:
Browse Catalog
Add to Cart
Log Out
A sequence diagram is made up of objects and messages. Objects can be

taken in different sense like an object can be consider a person who request or
send a message to perform a specific task. Above diagram shows the little
description ,it shows all the required connections.
2.7 Collaboration Diagram

The collaboration diagrams are also interaction diagrams it convay the
same message as sequence diagram , but focus on object role instead of the time that
message are sent .in a sequence diagram , object role are the vertices and messages
are the connecting link.
Contents:
describing how they are related and how they interact
29
Collaboration diagram
Users Products
Description
Orders
30
CHAPTER 3
USER INTERFACES
3 User Interface:
User interface is something that need to be as clean as you may preserve it. In
growing era of era as the whole thing in its growing level emerge as higher but complex
so, it’s the obligation of maker/developer to at the same time as offering desirable cloth to
consumer he/she ought to take into account that person is a simple person and understand
the easy matters without difficulty. While designing our app we tried our excellent to
31
offer consumer friendly environment to person so he/she need to first take knowledge
about the app.
3.1 Main Panel

This is our Main Page
32
3.2 Sign Up Panel

This is the Sign-Up Page
33
3.3 Log in Panel

This is the Log in Page
34
3.4 Admin Panel Categories

This is the page in admin panel that selects in which category do you want the
new product to be in.
35
3.5 Admin Add Product Details

This is the page in which admin add details of product.
36
3.6 User Panel Catalog

This is the catalog page
37
3.7 User Side Panel
38
This is the user side panel
39
3.8 User Profile Settings

This is the settings page
40

FYP Documentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FYP Documentation

Uploaded by

Copyright:

Available Formats

[PUBLIC HEALTH SURVEILLANCE]

Final Year Project Documentation Format

Session: BSCS Fall 2016

Project Advisor: UMER AYUB

Aniqa Rouf Bscs-f-17-

Qarshi University, Lahore

Ibraheem Bakhtyar Khilji

Makhdoom Ali Minhas

Defining a Sequence diagram....................................................................................24

1.1 Problem Statement and Justification

1.2 Application Architecture

The e-commerce application works in two forms.

Here is the structure of our Chat Application.

1.3 Hardware and Software Specification

Before starting our project we focused on what kind of software and

1.4 Tools and technologies used with reasoning

Our technical team master a comprehensive set of tools and technologies

5. Google play services

Our source code is Java in android. It is used for system

 Google play services:

1.5 Project/Product Feasibility Report

1.5.1 Technical Feasibility

1.5.2 Operational Feasibility

1.5.3 Economic Feasibility

1.5.3.1 Development Feasibility

1.5.3.2 Hardware Feasibility

1.5.3.3 Software Feasibility

1.5.4 Schedule Feasibility

1.5.5 Specification Feasibility

SPECIFICATIONS CONSTRAINTS FEASIBILITY RECOMMENDED

1.5.6 Information Feasibility

1.5.7 Motivational Feasibility

1.5.8 Legal & Ethical Feasibility

1.6 Project/Product Scope

1.7 CPM - Critical Path Method

Activity Activity Name Duration

1.7.1 Gantt chart

1.8 Introduction to Team Members and Their Skill Sets:

2. Makhdoom Ali Minhas (BSCSF-16-08)

2.1 Systems Specifications

Scope of the System

User friendly application:

Application with a friendly environment would provide a comfortable

2.2 Context Level Data Flow Diagram

System Check user

2.3 Use case Description

Post condition user successfully installed the app

Use case Name: Log In

Use case Name Login

Use case Name: browse catalog

Use case Name Browse Catalog

Use case Name: Add to cart

Use case Name Add to cart

Use case Name: remove products

Use case Name Remove products

Use case Name: log out

Use case Name Log out

Extension Connection lost app crash

Now we discuss these artifacts one by one as follows:

2.4 Use case Diagram (refined and updated)

Use case diagram are as following

2.5 Domain Model

 App and user relationship

2.6 Sequence Diagram