SUPERIOR UNIVERSITY LAHORE

Faculty of Computer Science & IT

Final Year Project

PROJECT REPORT

[Title of Project]

Project ID: [write ID here Issued by FYP Manager]

Project Team
Student Name Student ID Program Contact Number Email Address

[Project Supervisor]
([Designation])
 Project Report: < write Project title here>

Project Report
[Title of Project]

Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>

Faculty of CS&IT, Superior University Lahore, Pakistan ii

 Project Report: < write Project title here>

APPROVAL

PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________

Name:______________________________
Date:_______________________________ Signature:__________________________

PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________

Date:_______________________________ Signature:__________________________

HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________
_____________________________________________________________________________

Date:_______________________________ Signature:__________________________

Faculty of CS&IT, Superior University Lahore, Pakistan iii

 Project Report: < write Project title here>

Dedication

This work is dedicated to my family, friends and everyone who showered me with
their love and support. I am especially thankful to those who presented challenges
to my work and I pray for them because without their resistance I would never
have been able to achieve what I did.

Faculty of CS&IT, Superior University Lahore, Pakistan iv

 Project Report: < write Project title here>

Acknowledgements

I am really thankful to my supervisor who has guided us well throughout the semester. As well
as the people that provided us with their honest opinions and reviews. Who made time for us
for conducting their interview from their busy schedules, I would also like to thank my friends
and family that provided us with the opportunity and support for developing this project.

Faculty of CS&IT, Superior University Lahore, Pakistan v

 Project Report: < write Project title here>

Executive Summary

This project is for the automation of manual sale purchase of a Grocery, Vegetables and
Fruits with the name of Shopper`s Mart E-Store. E-Commerce plays an important role in
today’s online marketing and therefore I have selected to work on this project for the
sake of automating the online E-Store. The basic theme is that the work which is
currently being done manually through sale purchase of Grocery, Vegetables and Fruits,
is now being done with the help of e-commerce. This will bring efficiency in the system
and also better facilitate the users i.e., Shopper`s Mart E-Store. This project is for the
automation of manual sale purchase of a Grocery, Vegetables and Fruits with the name
of Shopper`s Mart E-Store. E-Commerce plays an important role in today’s online
marketing and therefore I have selected to work on this project for the sake of
automating the online E-Store.

Faculty of CS&IT, Superior University Lahore, Pakistan vi

 Project Report: < write Project title here>

Table of Contents
Dedication .......................................................................................................................................iv
Acknowledgements..........................................................................................................................v
Executive Summary.........................................................................................................................vi
Table of Contents ........................................................................................................................... vii
List of Figures ................................................................................... Error! Bookmark not defined.
List of Tables .................................................................................... Error! Bookmark not defined.
Chapter 1......................................................................................................................................... 1
Introduction .................................................................................................................................... 1
1.1. Background....................................................................................................................... 2
1.2. Motivations and Challenges ............................................................................................. 2
1.3. Goals and Objectives ........................................................................................................ 3
1.4. Literature Review/Existing Solutions ............................................................................... 3
1.5. Gap Analysis ..................................................................................................................... 3
1.6. Proposed Solution ............................................................................................................ 4
1.7. Project Plan ...................................................................................................................... 4
1.7.1. Work Breakdown Structure .......................................................................................... 5
1.7.2. Roles & Responsibility Matrix ....................................................................................... 5
1.7.3. Gantt Chart ................................................................................................................... 5
1.8. Report Outline .................................................................................................................. 5
Chapter 2......................................................................................................................................... 7
Software Requirement Specifications ............................................................................................ 7
2.1. Introduction...................................................................................................................... 8

Faculty of CS&IT, Superior University Lahore, Pakistan vii

 Project Report: < write Project title here>

2.1.1. Purpose ......................................................................................................................... 8

2.1.2. Document Conventions ................................................................................................ 8
2.1.3. Intended Audience and Reading Suggestions .............................................................. 8
2.1.4. Product Scope ............................................................................................................... 8
2.1.5. References .................................................................................................................... 9
2.2. Overall Description ........................................................................................................... 9
2.2.1. Product Perspective...................................................................................................... 9
2.2.2. Product Functions ......................................................................................................... 9
2.2.3. User Classes and Characteristics .................................................................................. 9
2.2.4. Operating Environment .............................................................................................. 10
2.2.5. Design and Implementation Constraints .................................................................... 10
2.2.6. User Documentation .................................................................................................. 10
2.2.7. Assumptions and Dependencies ................................................................................ 10
2.3. External Interface Requirements ................................................................................... 11
2.3.1. User Interfaces............................................................................................................ 11
2.3.2. Hardware Interfaces ................................................................................................... 11
2.3.3. Software Interfaces .................................................................................................... 11
2.3.4. Communications Interfaces ........................................................................................ 12
2.4. System Features ............................................................................................................. 12
2.4.1. System Feature 1 ........................................................................................................ 12
2.4.1.1. Description and Priority .......................................................................................... 12
2.4.1.2. Stimulus/Response Sequences ............................................................................... 12
2.4.1.3. Functional Requirements ........................................................................................ 12
2.4.2. System Feature 2 ........................................................................................................ 13
2.4.2.1. Description and Priority .......................................................................................... 13
2.4.2.2. Stimulus/Response Sequences ............................................................................... 13
2.4.2.3. Functional Requirements ........................................................................................ 13
2.4.3. System Feature 3 (and so on) ..................................................................................... 14
2.5. Other Nonfunctional Requirements .............................................................................. 14
2.5.1. Performance Requirements ....................................................................................... 14
2.5.2. Safety Requirements .................................................................................................. 14
2.5.3. Security Requirements ............................................................................................... 15
2.5.4. Software Quality Attributes ........................................................................................ 15
2.5.5. Business Rules............................................................................................................. 15
2.6. Other Requirements....................................................................................................... 15
Chapter 3....................................................................................................................................... 16
Use Case Analysis .......................................................................................................................... 16
3.1. Use Case Model .............................................................................................................. 17
3.2. Use Case Descriptions .................................................................................................... 17
Chapter 4....................................................................................................................................... 18
System Design ............................................................................................................................... 18
4.1. Architecture Diagram ..................................................................................................... 19
4.2. Domain Model ................................................................................................................ 19
4.3. Entity Relationship Diagram with data dictionary ......................................................... 19

Faculty of CS&IT, Superior University Lahore, Pakistan viii

 Project Report: < write Project title here>

4.4. Class Diagram ................................................................................................................. 20

4.5. Sequence / Collaboration Diagram ................................................................................ 20
4.6. Operation contracts ....................................................................................................... 20
4.7. Activity Diagram ............................................................................................................. 21
4.8. State Transition Diagram................................................................................................ 21
4.9. Component Diagram ...................................................................................................... 21
4.10. Deployment Diagram.................................................................................................. 22
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1] .................. 22
Chapter 5....................................................................................................................................... 23
Implementation ............................................................................................................................ 23
5.1. Important Flow Control/Pseudo codes .......................................................................... 24
5.2. Components, Libraries, Web Services and stubs ........................................................... 24
5.3. Deployment Environment .............................................................................................. 24
5.4. Tools and Techniques ..................................................................................................... 25
5.5. Best Practices / Coding Standards.................................................................................. 25
5.6. Version Control .............................................................................................................. 25
Chapter 6....................................................................................................................................... 26
Testing and Evaluation .................................................................................................................. 26
6.1. Use Case Testing............................................................................................................. 27
6.2. Equivalence partitioning ................................................................................................ 27
6.3. Boundary value analysis ................................................................................................. 27
6.4. Data flow testing ............................................................................................................ 27
6.5. Unit testing ..................................................................................................................... 28
6.6. Integration testing .......................................................................................................... 28
6.7. Performance testing ....................................................................................................... 28
6.8. Stress Testing ................................................................................................................. 28
Chapter 7....................................................................................................................................... 29
Summary, Conclusion and Future Enhancements ........................................................................ 29
7.1. Project Summary ............................................................................................................ 30
7.2. Achievements and Improvements ................................................................................. 30
7.3. Critical Review ................................................................................................................ 30
7.4. Lessons Learnt ................................................................................................................ 30
7.5. Future Enhancements/Recommendations .................................................................... 31
Appendices.................................................................................................................................... 32
Appendix A: User Manual ............................................................................................................. 33
Appendix B: Administrator Manual .............................................................................................. 34
Appendix C: Information / Promotional Material ........................................................................ 35
Reference and Bibliography .......................................................................................................... 38
Index.............................................................................................................................................. 40

Faculty of CS&IT, Superior University Lahore, Pakistan ix

 Project Report: < write Project title here>

List of Figures

1.1 Caption of first figure of first chapter 6

1.2 Caption of second figure of first chapter 7
2.1 Caption of first figure of second chapter 14
2.2 Caption of second figure of second chapter 22
2.3 Caption of third figure of second chapter 26
5.1 Caption of first figure of fifth chapter 49
5.2 Caption of second figure of fifth chapter 49

Faculty of CS&IT, Superior University Lahore, Pakistan x

 Project Report: < write Project title here>

List of Tables

1.1 label of first table of first chapter 6

1.2 label of second table of first chapter 7
2.1 label of first table of second chapter 14
2.2 label of second table of second chapter 22
2.3 label of third table of second chapter 26
5.1 label of first table of fifth chapter 49
5.2 label of second table of fifth chapter 49

Faculty of CS&IT, Superior University Lahore, Pakistan xi

 Project Report: < write Project title here>

Faculty of CS&IT, Superior University Lahore, Pakistan xii

Chapter 1
Introduction
 Project Report: < write Project title here>

Chapter 1: Introduction
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
Currently purpose of this project is sell/purchase Grocery, Vegetables and Fruits online,
so there is no scope with respect to organization purpose. The project can be used for
individual, small group and can be enhance for use in organization level. This project is
for the automation of manual sale purchase of a Grocery, Vegetables and Fruits with the
name of Shopper`s Mart E-Store. E-Commerce plays an important role in today’s online
marketing and therefore I have selected to work on this project for the sake of
automating the online E-Store.

1.1. Background
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
There are many E-commerce stores in internet. But none of them are giving that easy
interface that we are providing. It is easy and user friendly so customer will get ease in
buying from this store. The basic theme is that the work which is currently being done
manually through sale purchase of Grocery, Vegetables and Fruits, is now being done
with the help of e-commerce. This will bring efficiency in the system and also better
facilitate the users i.e., Shopper`s Mart E-Store.

1.2. Motivations and Challenges

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
There are many existing e-commerce stores in market. But some of them are not responsive
and working on old fashion complicated style. Some of them are full of errors. And have privacy
issues. We searched about some stores they are targeting only one item or some specific from

Faculty of CS&IT, Superior University Lahore, Pakistan 2

 Project Report: < write Project title here>

1 vendor, we are providing different things from different venders because we have strong
database record.

1.3. Goals and Objectives

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
This E-commerce store will help people to find groceries, vegetables and fruits. Some times it
happens when user is at home and not willing to go out for shopping or in any case of
emergency they need at once. So for these kind of issues we are providing this store so user can
order for things from their home.

1.4. Literature Review/Existing Solutions

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
This Store is user friendly. Easy to understand. Users can rate this site and can give suggestions
about this. There are no issues about privacy or security in this store. Users can locate or search
their required item and can check it on cart. It is most easy way to buy things from store. There
are many existing e-commerce stores in market. But some of them are not responsive and
working on old fashion complicated style. Some of them are full of errors. And have privacy
issues. We searched about some stores they are targeting only one item or some specific from
1 vendor, we are providing different things from different venders because we have strong
database record.

1.5. Gap Analysis

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 3

 Project Report: < write Project title here>

In the future, This Store is going to be a platform where everyone can find products they wish
to buy. But in order to move forward from the current state and achieve that desired future
state, an analysis of the gaps is required that need to be filled. They are stated as follows:
 Market the product to spread awareness of its existence.
 Develop in such a manner that the end product is better than its competitors.
 Make it user-friendly and hassle-free to make the users stay.
 Assure the consumers of reliability
 Provide the users with advanced features like discount offers.
 Use react native library to make the site user friendly and its development more
manageable.
 Develop the mobile apps with compiled UI using react instead of native app
development languages.
 Gather data about the most popular products and their brands.
 Divide product data in categories.
Test the system on multiple platforms and devices to make sure it is free of bugs and
doesn’t cause the users any problems

1.6. Proposed Solution

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
All issues like monitoring the data, checking user’s activities, secured resources information,
manage the records, communication gaps, customer enhancement and most important factor
it is secured and safe to store the information of the records. Users can add products to cart for
purchasing. We are offering store for different products, vegetables and fruits.

1.7. Project Plan

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 4

 Project Report: < write Project title here>

The objective of the project is to automate the current manual system of the Grocery,
Vegetables and Fruits sale-purchase. This includes activities:
 To facilitate add/delete/update categories and products data.
 To facilitate proper record of all information related to Grocery, Vegetables and
Fruits.
 To facilitate admin management with ease of use of proper information
management so admin can handle it easily.
 Order Log Reports
 Order list regarding purchase’ items and facility to update status.

1.7.1. Work Breakdown Structure

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

1.7.2. Roles & Responsibility Matrix

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

1.7.3. Gantt Chart

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

1.8. Report Outline

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 5

 Project Report: < write Project title here>

Faculty of CS&IT, Superior University Lahore, Pakistan 6

 Project Report: < write Project title here>

Chapter 2
Software Requirement
Specifications

Faculty of CS&IT, Superior University Lahore, Pakistan 7

 Project Report: < write Project title here>

Chapter 2: Software Requirement Specifications

2.1. Introduction
2.1.1. Purpose
<Identify the product whose software requirements are specified in this document, including
the revision or release number. Describe the scope of the product that is covered by this SRS,
particularly if this SRS describes only part of the system or a single subsystem.>

2.1.2. Document Conventions

<Describe any standards or typographical conventions that were followed when writing this
SRS, such as fonts or highlighting that have special significance. For example, state whether
priorities for higher-level requirements are assumed to be inherited by detailed requirements,
or whether every requirement statement is to have its own priority.>

2.1.3. Intended Audience and Reading Suggestions

<Describe the different types of reader that the document is intended for, such as developers,
project managers, marketing staff, users, testers, and documentation writers. Describe what
the rest of this SRS contains and how it is organized. Suggest a sequence for reading the
document, beginning with the overview sections and proceeding through the sections that are
most pertinent to each reader type.>

2.1.4. Product Scope

<Provide a short description of the software being specified and its purpose, including relevant
benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If
a separate vision and scope document is available, refer to it rather than duplicating its
contents here.>

Faculty of CS&IT, Superior University Lahore, Pakistan 8

 Project Report: < write Project title here>

2.1.5. References
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document. Provide enough information so that the reader
could access a copy of each reference, including title, author, version number, date, and source
or location.>

2.2. Overall Description

2.2.1. Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain
existing systems, or a new, self-contained product. If the SRS defines a component of a larger
system, relate the requirements of the larger system to the functionality of this software and
identify interfaces between the two. A simple diagram that shows the major components of the
overall system, subsystem interconnections, and external interfaces can be helpful.>

2.2.2. Product Functions

<Summarize the major functions the product must perform or must let the user perform.
Details will be provided in Section 3, so only a high level summary (such as a bullet list) is
needed here. Organize the functions to make them understandable to any reader of the SRS. A
picture of the major groups of related requirements and how they relate, such as a top level
data flow diagram or object class diagram, is often effective.>

2.2.3. User Classes and Characteristics

<Identify the various user classes that you anticipate will use this product. User classes may be
differentiated based on frequency of use, subset of product functions used, technical expertise,
security or privilege levels, educational level, or experience. Describe the pertinent
characteristics of each user class. Certain requirements may pertain only to certain user classes.

Faculty of CS&IT, Superior University Lahore, Pakistan 9

 Project Report: < write Project title here>

Distinguish the most important user classes for this product from those who are less important
to satisfy.>

2.2.4. Operating Environment

<Describe the environment in which the software will operate, including the hardware
platform, operating system and versions, and any other software components or applications
with which it must peacefully coexist.>

2.2.5. Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These
might include: corporate or regulatory policies; hardware limitations (timing requirements,
memory requirements); interfaces to other applications; specific technologies, tools, and
databases to be used; parallel operations; language requirements; communications protocols;
security considerations; design conventions or programming standards (for example, if the
customer’s organization will be responsible for maintaining the delivered software).>

2.2.6. User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials)
that will be delivered along with the software. Identify any known user documentation delivery
formats or standards.>

2.2.7. Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements
stated in the SRS. These could include third-party or commercial components that you plan to
use, issues around the development or operating environment, or constraints. The project
could be affected if these assumptions are incorrect, are not shared, or change. Also identify
any dependencies the project has on external factors, such as software components that you
intend to reuse from another project, unless they are already documented elsewhere (for
example, in the vision and scope document or the project plan).>

Faculty of CS&IT, Superior University Lahore, Pakistan 10

 Project Report: < write Project title here>

2.3. External Interface Requirements

2.3.1. User Interfaces

<Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style guides
that are to be followed, screen layout constraints, standard buttons and functions (e.g., help)
that will appear on every screen, keyboard shortcuts, error message display standards, and so
on. Define the software components for which a user interface is needed. Details of the user
interface design should be documented in a separate user interface specification.>

2.3.2. Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software
product and the hardware components of the system. This may include the supported device
types, the nature of the data and control interactions between the software and the hardware,
and communication protocols to be used.>

2.3.3. Software Interfaces

<Describe the connections between this product and other specific software components
(name and version), including databases, operating systems, tools, libraries, and integrated
commercial components. Identify the data items or messages coming into the system and going
out and describe the purpose of each. Describe the services needed and the nature of
communications. Refer to documents that describe detailed application programming interface
protocols. Identify data that will be shared across software components. If the data sharing
mechanism must be implemented in a specific way (for example, use of a global data area in a
multitasking operating system), specify this as an implementation constraint.>

Faculty of CS&IT, Superior University Lahore, Pakistan 11

 Project Report: < write Project title here>

2.3.4. Communications Interfaces

<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>

2.4. System Features

<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>

2.4.1. System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
2.4.1.1. Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or
Low priority. You could also include specific priority component ratings, such as benefit,
penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
2.4.1.2. Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements associated with use
cases.>
2.4.1.3. Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services
provided by the feature, or to execute the use case. Include how the product should
respond to anticipated error conditions or invalid inputs. Requirements should be

Faculty of CS&IT, Superior University Lahore, Pakistan 12

 Project Report: < write Project title here>

concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder

to indicate when necessary information is not yet available.>

<Each requirement should be uniquely identified with a sequence number or a

meaningful tag of some kind.>

REQ-SF1-1: <Write your requirement here>

REQ-SF1-2:
REQ-SF1-3:

2.4.2. System Feature 2

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
2.4.2.1. Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or
Low priority. You could also include specific priority component ratings, such as benefit,
penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
2.4.2.2. Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements associated with use
cases.>
2.4.2.3. Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services
provided by the feature, or to execute the use case. Include how the product should
respond to anticipated error conditions or invalid inputs. Requirements should be
concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder
to indicate when necessary information is not yet available.>

Faculty of CS&IT, Superior University Lahore, Pakistan 13

 Project Report: < write Project title here>

<Each requirement should be uniquely identified with a sequence number or a

meaningful tag of some kind.>

REQ-SF2-1:
REQ-SF2-2:
REQ-SF2-3:

2.4.3. System Feature 3 (and so on)

2.5. Other Nonfunctional Requirements

2.5.1. Performance Requirements
<If there are performance requirements for the product under various circumstances, state
them here and explain their rationale, to help the developers understand the intent and make
suitable design choices. Specify the timing relationships for real time systems. Make such
requirements as specific as possible. You may need to state performance requirements for
individual functional requirements or features.>

2.5.2. Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

Faculty of CS&IT, Superior University Lahore, Pakistan 14

 Project Report: < write Project title here>

2.5.3. Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product
or protection of the data used or created by the product. Define any user identity
authentication requirements. Refer to any external policies or regulations containing security
issues that affect the product. Define any security or privacy certifications that must be
satisfied.>

2.5.4. Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either
the customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness,
testability, and usability. Write these to be specific, quantitative, and verifiable when possible.
At the least, clarify the relative preferences for various attributes, such as ease of use over ease
of learning.>

2.5.5. Business Rules

<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>

2.6. Other Requirements

<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Faculty of CS&IT, Superior University Lahore, Pakistan 15

 Project Report: < write Project title here>

Chapter 3
Use Case Analysis

Faculty of CS&IT, Superior University Lahore, Pakistan 16

 Project Report: < write Project title here>

Chapter 3: System Analysis

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]

3.1. Use Case Model

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

3.2. Use Case Descriptions

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 17

 Project Report: < write Project title here>

Chapter 4
System Design

Faculty of CS&IT, Superior University Lahore, Pakistan 18

 Project Report: < write Project title here>

Chapter 4: System Design

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]

4.1. Architecture Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.2. Domain Model

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.3. Entity Relationship Diagram with data dictionary

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 19

 Project Report: < write Project title here>

4.4. Class Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.5. Sequence / Collaboration Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.6. Operation contracts

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 20

 Project Report: < write Project title here>

4.7. Activity Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.8. State Transition Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.9. Component Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 21

 Project Report: < write Project title here>

4.10. Deployment Diagram

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 22

 Project Report: < write Project title here>

Chapter 5
Implementation

Faculty of CS&IT, Superior University Lahore, Pakistan 23

 Project Report: < write Project title here>

Chapter 5: Implementation
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]

5.1. Important Flow Control/Pseudo codes

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

5.2. Components, Libraries, Web Services and stubs

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

5.3. Deployment Environment

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 24

 Project Report: < write Project title here>

5.4. Tools and Techniques

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

5.5. Best Practices / Coding Standards

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

5.6. Version Control

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 25

 Project Report: < write Project title here>

Chapter 6
Testing and Evaluation

Faculty of CS&IT, Superior University Lahore, Pakistan 26

 Project Report: < write Project title here>

Chapter 6: Testing and Evaluation

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]

6.1. Use Case Testing

6.2. Equivalence partitioning

6.3. Boundary value analysis

6.4. Data flow testing

Faculty of CS&IT, Superior University Lahore, Pakistan 27

 Project Report: < write Project title here>

6.5. Unit testing

6.6. Integration testing

6.7. Performance testing

6.8. Stress Testing

Faculty of CS&IT, Superior University Lahore, Pakistan 28

 Project Report: < write Project title here>

Chapter 7
Summary, Conclusion and
Future Enhancements

Faculty of CS&IT, Superior University Lahore, Pakistan 29

 Project Report: < write Project title here>

Chapter 7: Summary, Conclusion & Future Enhancements

7.1. Project Summary

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

7.2. Achievements and Improvements

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

7.3. Critical Review

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

7.4. Lessons Learnt

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 30

 Project Report: < write Project title here>

7.5. Future Enhancements/Recommendations

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 31

 Project Report: < write Project title here>

Appendices

Faculty of CS&IT, Superior University Lahore, Pakistan 32

 Project Report: < write Project title here>

Appendix A: User Manual

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this appendix all about]

Appendix A: Appendix Title

[Appendix Heading 1]: [20 pt, Calibri, Bold, Left aligned]
Text in 12-Point Size, Times New Roman, 1.5 Line Spacing.

A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 33

 Project Report: < write Project title here>

Appendix B: Administrator Manual

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this appendix all about]

B.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

B.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

B.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 34

 Project Report: < write Project title here>

Appendix C: Information / Promotional Material

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this appendix all about]

C.1. Broacher

C.2. Flyer

C.3. Standee

C.4. Banner

Faculty of CS&IT, Superior University Lahore, Pakistan 35

 Project Report: < write Project title here>

C.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

C.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

C.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 36

 Project Report: < write Project title here>

Appendix [no.]: Appendix Title

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
[Between 4 to 8 lines describe what is this chapter all about]

A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

C.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

Faculty of CS&IT, Superior University Lahore, Pakistan 37

 Project Report: < write Project title here>

Reference and
Bibliography

Faculty of CS&IT, Superior University Lahore, Pakistan 38

 Project Report: < write Project title here>

Reference and Bibliography

[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition,
Volume, Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……

Faculty of CS&IT, Superior University Lahore, Pakistan 39

 Project Report: < write Project title here>

Index

Faculty of CS&IT, Superior University Lahore, Pakistan 40

 Project Report: < write Project title here>

Index

[A]

[B]

[C]

Faculty of CS&IT, Superior University Lahore, Pakistan 41

 Project Report: < write Project title here>

Faculty of CS&IT, Superior University Lahore, Pakistan 42

 Project Report: < write Project title here>

Faculty of CS&IT, Superior University Lahore, Pakistan 43