The Islamia University of Bahawalpur

Department of Computer Science & IT

<Project Title>

By

<Student Name>

<Roll #>

BACHELOR

IN

INFROMATION TECHNOLOGY

2015-2019
 <Project Title>
By

<Student Name>

<Roll #>

PROJECT

Presented to the Department of Computer Science & IT

The Islamia University of Bahawalpur

In partial fulfillment of

The requirements for

The Degree of

BACHELOR

IN

INFROMATION TECHNOLOGY

2015-2019

Department of Computer Science & IT

The Islamia University of Bahawalpur

 <Project Title>
By

<Student Name>

A project documentation submitted to faculty of Computer Science, in partial fulfillment of

the requirements for the degree of

BACHELOR
IN
INFROMATION TECHNOLOGY

Project Documentation Committee:

External Examiner _______________________

Internal Supervisor _______________________

Mr. Muzammil ul Rehman,
Lecturer,
DCSIT, IUB.

HOD , _______________________
Dr. Dost Muhamad Khan,
Assistant Professor,
DCSIT, IUB.
 PROJECT COMPLETION CERTIFICATE

It is certified that the work contained in the project entitled topic “<Project Title>” has been

carried out and completed by “<Student Name>” under my supervision of his/her Bachelor

in Information Technology (BSIT) program.

Signature: ____________________

Supervisor: Mr. Muzammil Ul Rehman_

 DECLARATION OF ORIGINALITY

I hereby declare that the work contained in this project and the intellectual contents of this

report are product of my own work, this report as previously published in any form nor does it

contain any verbatim of the published resources which could be treated as infringement of the

international copyright law, except where due reference is made in the text of this project.

I also declare that I do understand the terms 'copyright' and 'plagiarism' and in case of any

copyright violation or plagiarism found in this work, I will be held fully responsible of the

consequences of any such violation.

Signature: __________________________

Author's Name: <Student Name>____________

Roll No.: <Roll #>___________________

I
 DEDICATION

My parents and friends.

II
 ACKNOWLEDGEMENTS

Special thanks to Mr. Muzamil Rehman, my supervisor and Dr. Waqar Aslam course

coordinator, for their guidance and continued support in completion of this project

documentation.

III
 ABSTRACT
An abstract contains the summary of the overall work presented. It should be of three
paragraphs at-least, but not more than one page. First paragraph should build the interest of
reader towards your idea and provide some brief introduction and relate it to the work
presented.

Second Paragraph should summarize your work presented and at the end of the paragraph it
should reflect the benefits of your work. You can highlight the benefits in a bullet list.

Third paragraph should briefly conclude importance of the work done and future work (if any).

IV
 TABLE OF CONTENTS
DECLARATION OF ORIGINALITY ........................................................................................................................I

DEDICATION ....................................................................................................................................................II

ACKNOWLEDGEMENTS ...................................................................................................................................III

ABSTRACT ...................................................................................................................................................... IV

CHAPTER NO. 1 ................................................................................................................................................ 1

1 INTRODUCTION ...................................................................................................................................... 1

1.1 SCOPE ......................................................................................................................................................... 1

1.2 ACRONYMS, AND ABBREVIATIONS .................................................................................................................... 1
1.3 ASSUMPTIONS AND DEPENDENCIES................................................................................................................... 1
1.4 OBJECTIVES .................................................................................................................................................. 1
1.5 PROJECT BRIEF.............................................................................................................................................. 2
1.6 SOFTWARE PROCESS MODEL ........................................................................................................................... 2
1.7 PROJECT STRUCTURE...................................................................................................................................... 2

CHAPTER NO. 2 ................................................................................................................................................ 3

2 LITERATURE REVIEW ............................................................................................................................... 3

2.1 BACKGROUND .............................................................................................................................................. 3

2.2 DEFINITIONS & TERMS ................................................................................................................................... 3
2.3 SOFTWARE & TOOLS ...................................................................................................................................... 3
2.4 RELATED RESEARCH ....................................................................................................................................... 4

CHAPTER NO. 3 ................................................................................................................................................ 5

3 ANALYSIS AND DESIGN ........................................................................................................................... 5

3.1 SOFTWARE REQUIREMENT SPECIFICATIONS ........................................................................................................ 5

3.1.1 Problem Statement ......................................................................................................................... 5
3.1.2 Constraints and Limitation .............................................................................................................. 5
3.1.3 Functional Requirements ................................................................................................................ 7
3.1.4 Non-Functional Requirements ........................................................................................................ 8
3.2 UML DIAGRAMS........................................................................................................................................... 9
3.2.1 Use Case Diagrams ......................................................................................................................... 9
3.2.2 Use Case Descriptions ................................................................................................................... 10
3.2.3 Activity Diagrams .......................................................................................................................... 11
3.2.4 Sequence Diagrams ...................................................................................................................... 12
3.2.5 State-Transition Diagrams ............................................................................................................ 13
3.2.6 Class Diagrams .............................................................................................................................. 14

V
 3.2.7 Component Diagram ..................................................................................................................... 15
3.2.8 Deployment Diagram .................................................................................................................... 16

CHAPTER NO. 4 .............................................................................................................................................. 17

4 DATABASE ANALYSIS AND DESIGN ....................................................................................................... 17

4.1 DATABASE OVERVIEW .................................................................................................................................. 17

4.1.1 Tools used ..................................................................................................................................... 17
4.1.2 Data Dictionary ............................................................................................................................. 17
4.2 UML DIAGRAMS......................................................................................................................................... 18
4.2.1 Data Flow Diagrams ..................................................................................................................... 18
4.2.2 Entity-Relationship Diagram ......................................................................................................... 20
4.3 NORMALIZATION ......................................................................................................................................... 21
4.4 DATABASE SNAPSHOTS ................................................................................................................................. 22

CHAPTER NO. 5 .............................................................................................................................................. 23

5 GRAPHICAL USER INTERFACE SNAPSHOTS ............................................................................................ 23

5.1 ADMINISTRATOR SIDE .................................................................................................................................. 23

5.1.1 Snapshot #01 ................................................................................................................................ 23
5.1.2 Snapshot #02 ................................................................................................................................ 24
5.1.3 Snapshot #03 ................................................................................................................................ 25
5.2 USER SIDE.................................................................................................................................................. 26
5.2.1 Snapshot #01 ................................................................................................................................ 26
5.2.2 Snapshot #02 ................................................................................................................................ 27
5.2.3 Snapshot #03 ................................................................................................................................ 28

REFERENCES................................................................................................................................................... 29

VI
 LIST OF FIGURES

Figure 3-1: Use Case Diagram of Online Shopping System ..................................................... 9

Figure 3-2: Activity Diagram for Online Shopping System .................................................... 11
Figure 3-2: Activity Diagram for Online Shopping System .................................................... 12

VII
 LIST OF TABLES
Table 3-1: Functional Requirements .......................................................................................... 7

VIII
 CHAPTER NO. 1

1 INTRODUCTION
Paragraph 1.
Paragraph 2.
Paragraph 3.

1.1 SCOPE
Paragraph 1.
Paragraph 2.
Paragraph 3.

1.2 ACRONYMS, AND ABBREVIATIONS

Paragraph 1.
Paragraph 2.
Paragraph 3.

1.3 ASSUMPTIONS AND DEPENDENCIES

Paragraph 1.
Paragraph 2.
Paragraph 3.

1.4 OBJECTIVES
The main objectives work are:
1. Objective #1.
2. Objective #2.
3. Objective #3.
4. Objective #4.
5. Objective #5.
You can add as many objectives, and Note: Remove this line.

Page |1
1.5 PROJECT BRIEF
A brief description of hardware and software required/used in this project.
Paragraph 1.
Paragraph 2.
Paragraph 3.

1.6 SOFTWARE PROCESS MODEL

This section represents the software process model used to develop the project. Water fall /
Spiral / Incremental / RAD / Agile. Present its diagram, and convince why you used it by
explaining its benefits.
Paragraph 1.
Paragraph 2.
Paragraph 3.

1.7 PROJECT STRUCTURE

Chapter 1 of this project documentation highlight the importance of the selected problem
carried out in this project work, its introduction, necessary guidelines and motivational factor
etc. Chapter 2 comprises on background related work and literature survey. Chapter 3 which is
the foundation of this project work, presents the complete System Analysis and Design in the
form of Software Requirement Specifications (Functional and Non-Functional Requirements)
and various UML diagrams (Use Case, Activity, Sequence, State-Transition, Architecture).
Also, a detailed discussion on Database Analysis Design in the form of Data Description and
various UML diagrams (Data Flow, Entity-Relationship) and at the end Normalization and
Database Snapshot are provided in Chapter 4. The pictorial evidence of the work done in the
form of Graphical User Interface snapshots is provided in Chapter 5 of this project
documentation. Finally, at the end of this project documentation future work (if any) and
references are furnished.

Page |2
 CHAPTER NO. 2

2 LITERATURE REVIEW
2.1 BACKGROUND
Paragraph 1.
Paragraph 2.
Paragraph 3.

2.2 DEFINITIONS & TERMS

Paragraph 1.
Paragraph 2.
Paragraph 3.

2.3 SOFTWARE & TOOLS

Paragraph 1.
Paragraph 2.
Paragraph 3.

Page |3
2.4 RELATED RESEARCH
This section should only be used in research related projects or if any research paper or book
is used to complete this project. Two example of citations is provided below using APA
reference style. This page is optional and you can remove it to avoid confusion.

(Batool et al., 2013) “have clearly differentiated between Traditional RE and Agile RE
techniques. They conducted a literature study and then presented a case study and concluded
that Agile RE resulted in better success rate in large organisations where changes evolve
througout the software development process”.

(Verma, Kaur, & Arora, 2016) “have discussed that software crisis arised as technology and
web connectivity has increased the need for development of software and traditional
approaches failed to meet the pace. This paved the way for Agile techniques to overcome the
gap”.

Page |4
 CHAPTER NO. 3

3 ANALYSIS AND DESIGN

The analysis section is presented by Software Requirement Specifications and the design
section is presented by UML Diagrams.

3.1 SOFTWARE REQUIREMENT SPECIFICATIONS

3.1.1 Problem Statement
Paragraph 1.
Paragraph 2.
Paragraph 3.

3.1.2 Constraints and Limitation

Paragraph 1.
Paragraph 2.
Paragraph 3.

Page |5
Note: Remove this page after reading:
Each functional requirement in this section should be:
 Correct
 Traceable (both forward and backward to prior/future artifacts)
 Unambiguous
 Verifiable (i.e., testable)
 Prioritized (with respect to importance and/or stability)
 Complete
 Consistent
 Uniquely identifiable (usually via numbering like FR-01)
Attention should be paid to the carefully organize the requirements presented in this section so
that they may easily accessed and understood.

Page |6
3.1.3 Functional Requirements
The table given below list all functional requirements.
Table 3-1: Functional Requirements

Req. No Description
FR-01 Functional requirement #01 goes here.
FR-02 Functional requirement #02 goes here.
FR-03 Functional requirement #03 goes here.
FR-04 Functional requirement #04 goes here.
FR-05 Functional requirement #05 goes here.
FR-06 Functional requirement #06 goes here.
FR-07 Functional requirement #07 goes here.
FR-08 Functional requirement #08 goes here.
FR-09 Functional requirement #09 goes here.
FR-10 Functional requirement #10 goes here.

Page |7
3.1.4 Non-Functional Requirements
Here is a list of non-functional requirements.

3.1.4.1 Performance

3.1.4.2 Reliability

3.1.4.3 Availability

3.1.4.4 Security

3.1.4.5 Maintainability

3.1.4.6 3.5.6 Portability

Page |8
3.2 UML DIAGRAMS
This section represents various UML diagrams. For Behavioral models Use Case, Activity,
Sequence, State-Transition diagrams are presented. For Structural models Class, Component,
Deployment diagrams are presented.

3.2.1 Use Case Diagrams

An example use case diagram for online shopping system is provided here. Note: Remove
this line.
Replace this diagram with your Use Case Diagram. Note: Remove this line.

Figure 3-1: Use Case Diagram of Online Shopping System

Page |9
3.2.2 Use Case Descriptions

3.2.2.1 UC-01 Description

Title Description
Use Case ID UC-01
Use Case Name Login
Actors Administrator, High Authority
Description This use case describes the process of login verification for the
users of the system
Pre-Condition Database should be connected.
Primary Scenario Step 1. The user will provide username and password
Step 2. Then user will click login.
Step 3. The system will validate the login information.
Step 4. The system will show the success message.
Step 5. The system will open the main application.
Secondary Scenario 1. The administrator can click exit to close the application.
Exceptions Step 2. Username/Password not supplied.
Step 3. Username/Password is not valid.
Post-Condition The system shall apply the proper access rights defined for the
current user.

This is an example use case description. All bubbles in the use case diagram must be described
individually. Note: Remove this line.

P a g e | 10
3.2.3 Activity Diagrams
An example activity diagram for online shopping system is provided here. Note: Remove this
line.
Replace this diagram with your Activity Diagram. Note: Remove this line.

Figure 3-2: Activity Diagram for Online Shopping System

P a g e | 11
3.2.4 Sequence Diagrams
An example sequence diagram for online shopping system is provided here. Note: Remove
this line.
Replace this diagram with your Sequence Diagram. Note: Remove this line.

Figure 3-3: Sequence Diagram for Online Shopping System

P a g e | 12
3.2.5 State-Transition Diagrams

Figure 3-4: State Transition Diagram for ATM System

P a g e | 13
3.2.6 Class Diagrams

Figure 3-5: Class Diagram for Online Shopping System

P a g e | 14
3.2.7 Component Diagram

Figure 3-6: Component Diagram of Online Shopping System

P a g e | 15
3.2.8 Deployment Diagram

Figure 3-7: Deployement Diagram of Library Management System

P a g e | 16
 CHAPTER NO. 4

4 DATABASE ANALYSIS AND DESIGN

The analysis section is presented by database overview and the design section is presented by
UML Diagrams. At the end, normalization and database snapshots are presented.

4.1 DATABASE OVERVIEW

Paragraph 1.
Paragraph 2.
Paragraph 3.

4.1.1 Tools used

Paragraph 1.
Paragraph 2.
Paragraph 3.

4.1.2 Data Dictionary

Paragraph 1.
Paragraph 2.
Paragraph 3.

P a g e | 17
4.2 UML DIAGRAMS
4.2.1 Data Flow Diagrams

4.2.1.1 Context Diagram

Figure 4-1: Context Diagram of Library Management System

P a g e | 18
4.2.1.2 Level-Zero Diagram

Figure 4-2: Level Zero Diagram for Payroll System

P a g e | 19
4.2.2 Entity-Relationship Diagram

Figure 4-3: Entity-Relationship Diagram of Football Coaching System

P a g e | 20
4.3 NORMALIZATION
This section should provide the transition of raw data into normalized tables (1st Normal form
to 3rd Normal form). For simplicity purposes, you can represent your Normalized tables in 3rd
Normal form only.

P a g e | 21
4.4 DATABASE SNAPSHOTS
The snapshots of the normalized tables after implementing them in your selected database
management system (SQL Server / MySQL / SQLite / Oracle etc.).

P a g e | 22
 CHAPTER NO. 5

5 GRAPHICAL USER INTERFACE SNAPSHOTS

This section provides the pictorial proof of the software implemented.

5.1 ADMINISTRATOR SIDE

This section provides the snapshots of the administrator side.

5.1.1 Snapshot #01

P a g e | 23
5.1.2 Snapshot #02

P a g e | 24
5.1.3 Snapshot #03

Add all snapshots of the admin side here one by one. Note: Remove this line.

P a g e | 25
5.2 USER SIDE
This section provides the snapshots of the user side.

5.2.1 Snapshot #01

P a g e | 26
5.2.2 Snapshot #02

P a g e | 27
5.2.3 Snapshot #03

Add all snapshots of the user side here one by one. Note: Remove this line.

P a g e | 28
 REFERENCES

Batool, A., Motla, Y. H., Hamid, B., Asghar, S., Riaz, M., Mukhtar, M., & Ahmed, M. (2013).
Comparative Study of Traditional Requirement Engineering and Agile Requirement
Engineering. Paper presented at the 15th International Conference on Advanced
Communication Technology (ICACT).
Verma, A., Kaur, I., & Arora, N. (2016). Comparative analysis of software engineering
paradigms. Paper presented at the 3rd International Conference on Computing for
Sustainable Global Development (INDIACom), New Dehli, India.

P a g e | 29