Final Project: DCS&IT-SUGC-Project Coordination Office Final Project Deliverable Guide Date: October 10, 2017

DCS&IT- SUGC-Project Coordination Office Version: 1.
0
Final Project Deliverable Guide Date: October 10, 2017
Final Project
1
DCS&IT- SUGC-Project Coordination Office Version: 1.0
Session: BSCS 2019

Submitted By
Prof. Mr. Bilal
Submitted By
Hamza Mushtaq BSCS-043
Mubeen Ali BSSE-015
Usman Asghar BSCS-013
Department of Computer Science & Information Technology

Superior University, Gujranwala Campus
2
This project will give us the information about railway reservation. This
system is basically concerned with the reservation and cancellation of
railway tickets to the passengers. To be more specific, our system is
limited in such a way that a
Train starting from a particular source will have a single destination.
The basic functions being performed by our system are reservation and
cancellation.
Customers can find the proper and correct information about the railway
and shows the
 It reserves and cancels seats for the passenger.

 It contains information about the trains.
 It contains information about the Seat Availability
 Railway time table
 Reservation Possibilities.
 Train Ticket booking,
 Booked Railway Ticket Status,
 Train between stations
Objective
The purpose of this source is to be describing the railway reservation

system which provides the train timing details reservation billing and
cancelation on several of reservation namely.
 Conform reservation for confirm seat.

 Reservation against can collation.
 Waiting list reservation.
 Online reservation.
 Tikal reservation.
The origin of most software system is in the need of a client. Who other
wants to out?
3
The objective of railway reservation system is to give structural design

to railway system.
The project provides functionality and flexibility to railway system such
that one can operate that system easily and efficiently.
This project also provides a complete set of solutions for some common
and specific areas of work in the railway.
Another important purpose of developing and SRS is helping the client
and understanding their own needs. An SRS establishes the client and
the supplier on want the software product will do.
An SRS provides a reference for validation of the final product. A high
quality SRS is a perquisite to high quality software and it also reduces
the development cost.
A few factors that direct us to develop a now system are given below.
Faster system.
Accuracy.
Reliability.
Reservation and cancelations form any place.
Scope
Railway reservation system is an attempt to simulate the basic
concepts of an online reservation system enables to perform the
following functions.
 Search of a selected flight

 Payment
 Booking of a selected flight
 Freight reservation enhancement
 Improved and optimized service
Overview
The remaining section of this document provided a general description

inclining characteristic of the user of this project the product hardware
and the functional and date requirement of the product general
description of the project is discussed in section 2 of this document
4
section. 3 give the function requirement date and constraints and

assumptions made while designing the E-store. It also gives user view
point of product. Section 3 also gives the specific requirement of the
product. Section 3 also discusses the external interface requirement and
gives detailed description of functional requirement section 4 is far
supporting information.
Functional Requirements
 User satisfaction
 Response time
 Safety and robustness
 Portable
Non- Functional Requirement
 Security
 Reliability
 Availability
 Maintainability
 Supportability
User Requirements
 To do the reservation transaction user must have the unique user

name and password.
 Users should be able to view a train detail according to their

requirements.
 For reservation booking user has to fill all the information that is
given in the form.
 User can cancel the reservation by giving the unique passenger id
and other necessary details.
5
 User can get the distance between two cities by giving the name of
cities.
System Analysis
 We have gathered all information by visiting a main office and

analyze the working of the government railway reservation system.
How they maintain details of passengers.
 Today all reservation systems in real time are computerized. All

transactions of railway reservation can be done through software
related to railway reservation.
 Today user wants to do transactions fastly so they can use software

or system for store information access the information. So we have
developed such a software, they can help them.
 According to analysis of many sites and reservation system we put

all the facilities that can help the users to get reservation.
 Facilities like reservation, cancellation of tickets, get the distance

between cities and etc.
6
Feasibility
The feasibility study is the important step in any system development

process. Because it makes analysis of different aspects like cost required
for developing and executing the system, the time required for each
stage of the system.
If these important factors are not analyzed then definitely it would be a
total failure. So for running the application and the organization
successfully this step is a very important step in a software development
lifecycle process.
There are three types of feasibility analysis:
i. Operational feasibility
ii. Technical feasibility
iii. Economical/financial feasibility
Operational Feasibility
 Operational feasibility measures how well the solution will work

in the organization and how will end-user & management feels
about the system. Proposed system is helpful for all the users
associated with the organization.
 It will allow the administrator to have up-to-date information

regarding all the aspects of their users, the decision-making
7
process will also become faster with the use of data integration,
consolidation. So it is feasible to implement the system.
Technical feasibility
 This involves questions such as whether the technology

needed for the system exists, how difficult it will be to build,
and whether the firm has enough experience using that
technology.
 This system required minimum hardware equipment to run

efficiently.
Economic feasibility
 Economically to find out whether this project is economically

feasible or not for that used feasibility analyses.
 In this stage list direct costs or indirect costs associated with

the project.
Data Flow Diagram
A data flow diagram is a graphical representation of the flow of data

through an information system, modeling its process aspects. A DFD is
often used as a preliminary step to create an overview of the system
without going into great detail, which can later be elaborated.
8
Data flow Diagram(Zero)
Booking management
Train Management Ticket management

Railway
Reservation
System
Route Management System user

9 management
Login management
1 level DFD
Train
User enquiry Train
detail
Return total Rs
Book
Register Tickets
Login Enter PNR
Return Tickets
Enter PNR
PNR
status Tick Detail
User Details
10
2 level DFD
Use case diagram
11
Actor Define
A person who perform some action are called actor.
12
Admin User
Other
13
1. Introduction:
Information technology is the use of computers to store, retrieve, transmit and manipulate data or
information, often in the context of a business or other enterprise. IT is considered to be a subset
of information and communication technology (ICT).With the help of Information Technology
the instant messaging, emails, voice and video calls become quicker, cheaper and much efficient.
By implementing information systems we can bring down the linguistic, geographical and some
cultural bounders. Sharing the information, knowledge communication and relationships
between different countries, languages and cultures becomes easier. Information systems has
made it possible for business to be open 24 × 7 all over the globe. One of the best advantage of
information systems is the creation of new and interesting jobs. Computer programmers, system
analyzers, Hardware and Software developers and Web designers are just some of the many new
employment opportunities created with the help of IT. The advancement of IT sector has resulted
in automated:
 Administration of entire system
 Production and manipulation of sensitive information
 Culture development and communication
 Streaming if business processes and timely upgrades.
This is a proposal for a game. This game is based on the latest action, survival, action, and
classic racing games. The main problem is to provide the realistic environment and also
providing a real-time 3D experience. Most of the games have high graphics but not supported on
general computer due to large size and hardware requirements.
But, this game will have high graphic as well as can be played on any platform because we shall
use the latest compression and coding techniques and also sort our data in such a way that our
game will use low memory but high performance. The latest games have very legalistic graphics
but the problem is this that if we talk about racing games approximately they have same features
but this game is differ due to lots of features, discussed later.
2. Existing System
There are lots of games have made but they don’t have combined feature like us. For example, if
we talk about survival games they have lots of features but they are of only one category. As a
user while playing a game we feel too much irritate if we can’t complete a task/mission of a
game due to difficulty level, which is same for all users. To entertain the player to the peek is our
one of the goals.
3. Game’s System Chart
Sign Up/ Player

Login
14
Player select category
Surviv Action Racing

al
Choose game
difficulty
o Normal
o Hard
o Ultra Hard
Level &
Equipment
Selection
Game
4. Scope of the System Start
This game can be played offline but user can purchase goods or cheats for game online (In App
Purchase.). Game is only for a single user (Not multiplayer) but we will work on it to make it
multiplayer and online.
5. Summary of Requirements: (Initial Requirements)

o User create an account or login first.
o A user friendly Dashboard (Main menu)
o Racing Game category
o Select a car and a level for race
o Minimum two laps at initial stage and 4 to 5 opponent cars.
o Cars have a system to damage other cars and destroy them (Bullet guns, rocket launcher
etc.)
6. Identifying External Entities

The external entities include main player enemies (Zombies, Cars having AI, Bosses, ) character
that help our player to complete a mission (partner, guider, helper etc.).
15
7. Capture “Shall” Statements.

Sr. No Actors Initial Requirements
1 User Create an account
1.1 Shall Login
1.2 Shall choose a game category
1.3 Shall select a round/Environment
1.4 Shall select equipment
1.5 Shall view player's his health
1.6 Shall use things for player's recovery
1.7 Shall view his current position of player on map
1.8 Shall online purchase things
1.9 Shall cancel order
1.10 Shall modify order
1.11 Shall view online things
1.12 Shall filter order in categories
1.13 Shall select a car
2 Player Shall Punch enemies
2.1 Shall shoot enemies
2.2 Shall get required things from enemies
2.3 Shall grab enemies
2.4 Shall destroy objects to get things
2.5 Shall jump over obstacles
2.6 Shall swim
3 Enemies Shall hurt the player
3.1 Shall hurt the helpers of player
3.3 Shall attack on player Knife
3.4 Shall attack on player Gun etc.
8. Allocate Requirements
Sr. No Actor Initial Requirements Use Case Name

1 User Create an account UC_createAcc
Shall Login UC_logIn
Shall choose a game category UC_category
Shall choose game dificulty UC_dificulty
Shall select a car UC_carSelection
UC_EnvironmentSelectio
Shall select a round/Environment n
Shall select equipment UC_selelectHealth
16
Shall view player's his health UC_health

Shall use things for player's recovery UC_recovery
Shall view his current position of player on
map UC_map
Shall online purchase things UC_purchaseTinghs
Shall cancel order UC_cancelOrder
Shall modify order UC_ModifyOrder
Shall view online things UC_OnlineDashboard
Shall filter order in categories UC_categoriesFilter
2 Player Shall Punch enemies UC_plyPunchEnemy
Shall shoot enemies UC_plyShootEnemy
Shall get required things from enemies UC_playerGetTinghs
Shall grab enemies UC_plygrabEnemy
Shall destroy objects to get things UC_plythingsDestroy
Shall jump over obstacles UC_plyjumpObst
Shall swim UC_playerSwim
Enemie
3 s Shall hurt the player UC_enmhurtPlayer
Shall hurt the helpers of player UC_enmhurtHelpers
Shall attack on player Knife UC_enmknifeAttack
Shall attack on player Gun etc. UC_enmgunAttack
9. Priorities Requirements
Sr. Use Case

Rank Initial Requirements Use Case Name
No ID
1 Highest User “Shall” Create an account UC_1 UC_createAcc
2 Highest User “Shall” Login UC_2 UC_logIn
User “Shall” choose a game
category UC_3 UC_category
3 Highest User “Shall” choose game dificulty UC_DD UC_dificulty
4 Highest User “Shall” select equipment UC_4 UC_selelectHealth
User “Shall” view player's his
5 Highest health UC_5 UC_health
User “Shall” use things for player's
6 Highest recovery UC_6 UC_recovery
User “Shall” view his current
7 Highest position of player on map UC_7 UC_map
8 Highest Player “Shall” Punch enemies UC_8 UC_plyPunchEnemy
9 Highest Player “Shall” shoot enemies UC_9 UC_plyShootEnemy
Player “Shall” get required things
10 Highest from enemies UC_10 UC_playerGetTinghs
17
11 Highest Player “Shall” grab enemies UC_11 UC_plygrabEnemy

Player “Shall” destroy objects to
12 Highest get things UC_12 UC_plythingsDestroy
13 Highest Player “Shall” jump over obstacles UC_13 UC_plyjumpObst
14 Highest Enemies “Shall” hurt the player UC_14 UC_enmhurtPlayer
Enemies “Shall” hurt the helpers of
15 Highest player UC_15 UC_enmhurtHelpers
Enemies “Shall” attack on player
16 Highest Knife UC_16 UC_enmknifeAttack
Enemies “Shall” attack on player
17 Highest Knife UC_17 UC_enmgunAttack
18 Medium User “Shall” select a car UC_18 UC_carSelection
User “Shall” select a
19 Medium round/Environment UC_19 UC_EnvironmentSelection
User “Shall” online purchase
20 Medium things UC_20 UC_purchaseTinghs
21 Medium User “Shall” “Shall”cel order UC_21 UC_”Shall”celOrder
22 Medium User “Shall” modify order UC_22 UC_ModifyOrder
23 Medium User “Shall” view online things UC_23 UC_OnlineDashboard
User “Shall” filter order in
24 Lowest categories UC_24 UC_categoriesFilter
25 Lowest Player “Shall” swim UC_25 UC_playerSwim
10. High Level Use Case Diagram
18
Sign up Difficult
y
selectio
login n
recover
puch
shoot
Category
select
Attac
k View
Health Run
Heal
Destro
y Jump
Cancel
order
Online
purchase
Butto
ns
Sent a
request Get
Equipment
19
11.Analysis Level Use Case Diagrams
11.1 UC_1 Register
Name
Password
User
Gender
Confirm
Password
Email
11.2.UC_2 Login
Password
User
Email
20
11.3. UC_3 Category Selection/Game Mode
Action
User
Racing
Survivall
11.4. UC_DD Selection of Difficulty of Game (How Hard the game be)
Normal
User
Hard
Ultra
Hard
21
11.5. UC_4 Select Health Equipment
Injections
User
Capsules
First Aid
Box
11.6. UC_6 player’s recovery items
Instant
Help
User
Instant
Boster
Hint
22
11.7. UC_5 Health Status Bar
User
Health Bar
11.8. UC_8+9+10 Player’s Attack on Enemies
Shoot
Playe Punch
r
Grab
23
11.9. UC_14+15+16+17 Enemies Attack on Player
Shoot
Enemy Punch
Grab
11.UC_20+21+22+23 User Can Purchase Goods online
cars
Levels
Enemy Guns
Equipment
Knife
24
12. Use Case Description
12.i.
UC_1 UC_createAcc
Actor/Actress Users(player,admin)
UC_ID UC_1
Feature User will create an account
Pre-Condition System/game should be available
User Scenarios
Sr. No Actor Action System Action
Member will request for signup
01 System will display signup page
page
System will upload details and
02 User will enter signup details
register user
System will display code
validation form
User should enter validation System will validate account and
03
code sent to email accaount show login page
System will upload and verify
04 Member will enter login details login details and display main
menu of game.
Alternate Scenarios
1.a System may not be available
2.a Error messege will displayed if user submit for without filling all or a single field
2.b error message displaye if user enter wrong data in the form
3.a user can request to resend code if not received
3.b error message displayed if user enter wrong validation code
4.a Form may not available
5.a User may not registered successfully(Not Confirm his account/Not entered validation
code)
5.b User may enter wrong details
5.c error message displaye if user enter wrong data in the form
Post Conditions Member will registered successfully
Cross Reference UC_2
25
12.ii.
UC_3 UC_category
Actor/Actress Users
UC_ID UC_3
Feature Choose game mode (e.g racing, survival)
Pre-Condition User must registered and logged into his account
User Scenarios

System select racing and move
01 User choose difficulty(Racing)
forward
User choose System select survival and move
02
difficulty(Survival) forward
System select action and move
03 User choose difficulty(Action)
forward
Alternate Scenarios
1.a User may not logged in successfully
Post Conditions Game mode selected successfully
Cross Reference UC_DD
26
12.iii.
UC_4 UC_selectHealth
Actor/Actress Users
UC_ID UC_4
User can select player’s Health
Feature
equipments(Injections,capsules,antidodes)
User should choose game category and difficulty level + have
Pre-Condition
sufficient balance in his violet to purchase an item
User Scenarios
System will check amount in
User may select an player’s
01 account and add items to the
Health items
bucket of player
Alternate Scenarios
1.a User’s balance may be insufficient.
Post Conditions Health items added to player’s bucket successfully
Actor/Actress User
UC_ID UC_
User can see player’s health bar and in percentage too + health
Feature
equipments
Pre-Condition User must selected game category
User Scenarios
01 User can see player’s health Not action just an interface
Alternate Scenarios
1.a User’s balance may be insufficient.
Post Conditions User can view player’s details successfully
Cross Reference Null
27
12.iv.
UC_7 UC_map
Actor/Actress User
UC_ID UC_7
Feature User can see player’s current position on map

Pre-Condition Game should be started
User Scenarios

Systm will dis[lay map’s
01 User click on map icon
window/interface
Alternate Scenarios
1.a Level may be loading when user click in map.

Post Conditions Player’s position identified successfully
Cross Reference Null
28
12.v.
UC_8 UC_plyPunchEnemy
Actor/Actress Player
UC_ID UC_8
Feature Player can punch enemy when user press punch button
Pre-Condition Punch button must be pressed
User Scenarios

System reduce the health lecel of
01 Player punch the enemy enemy according to logic
percentage
Alternate Scenarios
1.a enemy may not be in the rage or may player punched in other direction
Post Conditions Enemy died successfully
Cross Reference UC_9 + UC_10 + UC_11+UC_12
12.vi.
UC_13 UC_plyjumpObst
Actor/Actress Player
UC_ID UC_13
Feature Player can jump over obstacles
Pre-Condition Jump button must be pressed
User Scenarios
29
Move player vertically and

01 Hit jumoed bitton horizontally farward into
existing direction
Alternate Scenarios
1.player may not have a stemna
Post Conditions Player Jumped successfully
30
4.2. Domain Model:
4.3. System Sequence Diagram:
Admin:
Shopkeeper:
31
Coustmer:
32
Visitor:
4.4. Sequence Diagram:
1) Login:
2) View Profile:
33
3) Update Profile:
4) Add Floor:
5) Update Floor:
34
6) Add Shops:
7) Stocks Reports:
35
8) Place Order:
9) Change Order:
10) Logout:
11) Update Categories:
36
12) Add Products:
13) Update Products:
14) Confirm Order:
37
15) Generate Invoice:
16) Register:
17) Update Shops:
18) Carry Out Payment:
38
19) Order Status:
4.5. Collaboration Diagram

1) Login:
2) View Profile:
3) Update Profile:
4) Add Floor:
39
5) Update Floor:
6) Add Shops:
7) Stocks Reports:
8) Place Order:
9) Change Order:
40
10) Add Categories:
11) Logout:
13) Add Products:
14) Update Products:
15) Confirm Order:
41
17) Register:
18) Update Floors:
19) Carry Out Payment:
20) Order Status:
4.6. Operation Contracts:

1) Login:
Name: Login (Username: nVarChar, Password: nVarChar)
Responsibilities: Logged into the system.
Cross References: UC-3.12.1.1: Login
42
Exceptions: None
Preconditions: Internet Facility or Availability
Post conditions: Dashboard will be appeared
2) Logout:
Name: Logout ()
Responsibilities: Logout from the system.
Cross References: UC-3.12.1.19: Logout.
Exceptions: None
Preconditions: Member should have logged in to the system.
Post conditions: Logged Out.
3) Add Products:
Name: Add Products (Product ID: Id, Quantity: Integer)
Responsibilities: Add Products in the system.
Cross References: UC-3.12.2.3: Add Products
Exceptions: None
Preconditions: Must be login in the system.
Post conditions: New products will be added.
4) Update Products:
Name: Update Products (Product ID: Id, Quantity: Integer)
Responsibilities: Update Products in the system.
Cross References: UC-3.12.2.4: Update Products
Exceptions: None
43
Preconditions: Products should be added first.
Post conditions: Products will be updated and dashboard will be appeared.
5) Stock Reports:
Name: Stock Reports (Sale Ratio: float, Purchase Ratio: float)
Responsibilities: Maintain all the stock reports.
Cross References: UC-3.12.2.22: Stock Reports
Exceptions: None
Preconditions: Member should have all sales and purchase records.
Post conditions: Stock Report is generated.
6) Add Categories:
Name: Add Categories (Categories ID: Id , Product ID: Id)
Responsibilities: Add Categories in the system.
Cross References: UC-3.12.2.1: Add Categories
Exceptions: None
Preconditions: Must be login in the system.
Post conditions: Categories will be added.
Name: Update Categories (Categories ID: Id, Product ID: Id)
Responsibilities: Update Categories in the system.
Cross References: UC-3.12.2.2: Update Categories
Exceptions: None
44
Preconditions: Categories must be added
Post conditions: Categories will be updated and dashboard will be appeared.
8) Registration:
Name: Registration (Username: nVarChar, Password: nVarChar)
Responsibilities: Costumer will register.
Cross References: UC-3.12.3.1: Registration.
Exceptions: None
Preconditions: Must visit the website or open the E-Mall.
Post conditions: Login form will be appeared.
9) Place Order:
Name: Place Order (Order Id: Id, Description: nVarChar)
Responsibilities: Order will be placed.
Cross References: UC-3.12.3.2: Place Order.
Exceptions: None
Preconditions: Costumer should be registered first.
Post conditions: Confirm order page will be appeared.
10) Confirm Order:
Name: Confirm Order (Order Id: Id, Description: nVarChar)
Responsibilities: Costumer will register.
Cross References: UC-3.12.3.1: Registration.
Exceptions: None
Preconditions: Costumer order for something.
45
Post conditions: Pending order list must be cleared.
4.7. Design Class Diagram:
4.8. State chart diagram

1) Login:
2) Add Categories:
46
3) Add Products:
4) Carry out Payment:
47
6) Place Order:
8) Update order:
9) Update Product:
48
10) Logout:
11) View Profile:
12) Update Profile:
13) Add Floor:
49
14) Update Floor:
15) Add Shops:
16) Stocks Reports:
50
17) Confirm Order:
18) Register:
19) Cancel Order:
51
20) Order Status:
52
4.9. Data Model:

1. Costumer:
1.1. Order Status:
1. Order Status
Sr. No Attribute Data Type Size Description Constraints
Name
1 ID Int Max It will be a Primary key
primary key
and has an auto
increment of
“1”
2 Order Detail nVarchar Max It will be used Can be consist
to know about of characters,
the order and integers or
its special
specifications character
3 Order Price Int 50 It will be the Only contain
price of Integers
selected
products that
are present in
the order
4 Date, Time DATETIME 50 It will be the Only contain
Date and Time Date and Time
when order is
placed
5 Customer ID Int Max It will be the It consist of
foreign key of Integers only.
the customer
table which
will identify
the customer
who places the
order
6 Shop No Int Max It will be the It consist of
the Shop table
which will
identify the
Shop from
where the
order is placed
7 Product ID Int Max It will be the It consist of
the Product
table which
53
will identify
Update Order the products
Sr. No Attribute Data Type Size present in the
Description Constraints
Name order
1.2. Update Order:
54

primary key
and has an auto
increment of
“1”
2 Order Detail nVarchar Max It will be used Can be consist
to know about of characters,
the order and integers or
its special
specifications character
3 Order Price Int 50 It will be the Only contain
price of Integers
selected
products that
are present in
the order
4 Date, Time DATETIME 50 It will be the Only contain
Date and Time Date and Time
when order is
placed
5 Customer ID Int Max It will be the It consist of
the customer
table which
will identify
the customer
who places the
order
the Shop table
which will
identify the
Shop from
where the
order is placed
the Product
table which
will identify
the products
present in the
order
8 Previous Order Int Max It will be the It consist of
ID foreign key Integers only.
55
that will
identify the
previous order
1.3. Costumer:
Customer
Name
1 ID Int max It will be a Primary key
primary key
and has an
auto
increment of
“1”
2 User Name nVarchar 50 User name Can be
can be consist of
consist of characters,
characters, integers or
integers or special
special character
character and
it will be
used for
logging in to
the system
3 First Name Char 50 It will be the Only contain
first name of characters
the user
4 Last Name Char 50 It will be the Only contain
last name of characters
the user
5 Password nVarchar 50 It will be Can be
used for consist of
logging in to characters,
the system by integers or
the user special
character
6 Contact No Int 50 Contact no is Only integer
used for values are
contacting to accepted
the user by
other users
7 Email nVarchar 50 Email is used Should be
for contacting consist of
56
to the user by “@” sign.

other users
and it will
also be used
as logging in
the system
8 Date of Birth Date 50 From it we Should be
can evaluate valid
the age of the according to
user data type
1.4. Place Order:
2. Place Order
Name
primary key
and has an
auto
increment of
“1”
2 Order nVarchar Max It will be Can be
Detail used to know consist of
about the characters,
order and its integers or
specifications special
character
3 Order Price Int 50 It will be the It consist of
price of Integers
selected only.
products that
are present in
the order
4 Date, Time DATETIME 50 It will be the It consist of
Date and Date and
Time when Time only.
order is
placed
5 Customer Int Max It will be the It consist of
ID foreign key Integers
of the only.
customer
table which
will identify
the customer
57
who places
the order

foreign key Integers
of the Shop only.
table which
will identify
the Shop
from where
the order is
placed
foreign key Integers
of the only.
Product
table which
will identify
the products
present in the
order
2 . Mall Admin
2.1 . Contact Others
Contact Others
Name
1 Sender’s nVarchar 50 It will be Can be
Email used to consist of
identify that characters,
who the integers or
sender is special
through his character but
email it must be
address. consist of
“@”
2 Sender’s Char 50 It will be Can be
Name used to consist of
identify that characters
who the only.
sender is
through his
name.
58
3 Receiver’s nVarchar 50 It will be Can be

Email used to consist of
identify that characters,
to whom the integers or
email is sent special
through his character but
email it must be
address. consist of
“@”
4 Receiver’s Char 50 It will be Only contain
Name used to characters
identify that
to whom the
email is sent
through his
name.
2.2. Floors:
Floors
Name
primary key
and has an
auto
increment of
“1”
2 Name nVarchar max User name Can be
can be consist of
integers or special
special character
character and
it will be
used for
logging in to
the system
3 Image URL nVarChar max It will be the Only contain
last name of characters
the user
2.3. Mall Admin:
59
Mall Admin
Name
primary key
and has an
auto
increment of
“1”
2 User Name nVarchar 50 User name Can be
can be consist of
integers or special
special character
character and
it will be
used for
logging in to
the system
60
5.1 Analysis & Design Model for structured approach must contain following artifacts:
1. Entity Relationship Diagram

2. Data Flow Diagram (Functional Model)
3. State Transition Diagram (Behavioral Model)
4. Architecture Design
5. Component Level Design
5.2. Entity Relationship Diagram:

In the analysis model, Entity Relationship Diagram is used to understand the system under
consideration with respect to entities involved and their relationships. Each entity is documented
by extracted its attributes, cardinality, and modality.
Example:
61
Cardinality
From the description of the problem we see that:
Each department has exactly one supervisor.
A supervisor is in charge of one and only one department.
Each department is assigned at least one employee.
Each employee works for at least one department.
Each project has at least one employee working on it.
An employee is assigned to 0 or more projects.
Identify Attributes
The only attributes indicated are the names of the departments, projects, supervisors and
employees, as well as the supervisor and employee NUMBER and a unique project number.
Fully Dressed ERD:
62
5.3. Data flow diagram (Functional Model)

DFD is all about to identify the major processes in your system and develop Data Flow Diagram
up to required level.
63
DFD Constructs:
Context Level DFD
A context diagram shows the context into which the business process fits. It also shows the
overall business process as just one process and shows all the outside entities that receive
information from or contribute information to the system.
Level 1 Diagram
This diagram shows all the processes that comprise the overall system and how information
moves from and to each process. Data stores are added to it.
Level 2 Diagram
This diagram shows all the processes that comprise a single process on the level 1 diagram and
how information moves from and to each of these processes. It also shows in more detail the
content of higher-level process. Level 2 diagrams may not be needed for all level 1 processes.
Level 3 Diagram
This diagram shows all processes that comprise a single process on the level 2 diagram and how
information moves from and to each of these processes. Level 3 diagrams may not be needed for
all level 2 processes. Correctly numbering each process helps the user understand where the
process fits into the overall system.
Integrating Scenario Descriptions

DFDs generally integrate scenario descriptions
Names of use cases become processes
Names of inputs and outputs become data flows
Combining “small” data inputs and outputs into a single flow
Steps in Building DFDs
 Build the context level DFD

 Create DFD fragments for each scenario
 Organize DFD fragments into level 1
 Decompose level 1 DFDs as needed
 Validate DFDs with user
DFD Fragment Tips

 All process names must be verb phrases
 Maintain organization’s viewpoint in naming processes
 Layouts often place
 Processes in the center
 Inputs from the left
 Outputs to the right
 Stores beneath the processes
64
A DFD Fragment Example
Level 1 Diagram
65
Illegal Data Flows:
66
5.4. State Transition Diagram

State Transition Diagram is developed to represent the behavior of the system under
consideration. The constructs of STD are as follows:
State
A set of observable circum-stances that characterizes the behavior of a system at a given time
State transition
The movement from one state to another
Event
An occurrence that causes the system to exhibit some predictable form of behavior
Action
Process that occurs as a consequence of making a transition
Guidelines for developing a state transition diagram

 Make a list of the different states of a system (How does the system behave?)
 Indicate how the system makes a transition from one state to another (How does the system
change state?)
 Indicate event
 Indicate action
 Draw a state transition diagram
67
Example
5.5. Architectural design

The Focus of architecture design is the Mapping of Requirements into Software Architecture.
DFD prepared in analysis model is analyzed to do it.
Two major structural patterns or two major alternatives are Transform (Flow) Analysis and
Transaction (Flow) Analysis.
Beginning the Design Process

 Review the fundamental system model i.e. DFD and Software Requirement Specification
document.
 Review and refine data flow diagrams for the software
 Determine whether DFD exhibits transform or transaction characteristics
Example
 There is a string conversion system.
 It has the ability to reverse strings, count number of characters, and append new strings
with an old string.
 A user would be using this system and would be providing the string to it. The string
would be validated. If approved the system would be displaying different choices
including reversal of string, character counting and appending of strings.
 The user would select a choice and enter the appropriate selection. According to the
selected choice the system would perform the required action.
 If “Reverse String” is selected the valid string is attained and reversed.
68
 If “Count Characters” is selected the valid string is attained and the number of characters
are counted.
 If “Append String” is selected the valid string is attained and the user also enters a new
string. Both the strings are appended together and the result produced.
 Whatever the choice selected the result is displayed.
Level 1 Diagram
Level 2 Diagram
69
Program Structure/Design Architecture
70
71
5.6. Component Level Design

Every component, which is appearing in program structure/design architecture, is logically
analyzed and pseudo code or flow chart is prepared for each module. This flow chart is then
given to programmer who translates it into a machine-readable code. The options available for
component level design are:
 Flow chart
 Box Diagram
 Decision Table
 Psuedocode
Psuedocode
72

Final Project: DCS&IT-SUGC-Project Coordination Office Final Project Deliverable Guide Date: October 10, 2017

Uploaded by

Document Information

Original Description:

Original Title

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

Final Project: DCS&IT-SUGC-Project Coordination Office Final Project Deliverable Guide Date: October 10, 2017

Uploaded by

Copyright:

Available Formats

DCS&IT- SUGC-Project Coordination Office Version: 1.

Session: BSCS 2019

Hamza Mushtaq BSCS-043

Mubeen Ali BSSE-015

Usman Asghar BSCS-013

Department of Computer Science & Information Technology

 It reserves and cancels seats for the passenger.

The purpose of this source is to be describing the railway reservation

 Conform reservation for confirm seat.

The objective of railway reservation system is to give structural design

 Search of a selected flight

The remaining section of this document provided a general description

section. 3 give the function requirement date and constraints and

Non- Functional Requirement

 To do the reservation transaction user must have the unique user

 Users should be able to view a train detail according to their

 We have gathered all information by visiting a main office and

 Today all reservation systems in real time are computerized. All

 Today user wants to do transactions fastly so they can use software

 According to analysis of many sites and reservation system we put

 Facilities like reservation, cancellation of tickets, get the distance

The feasibility study is the important step in any system development

 Operational feasibility measures how well the solution will work

 It will allow the administrator to have up-to-date information

 This involves questions such as whether the technology

 This system required minimum hardware equipment to run

 Economically to find out whether this project is economically

 In this stage list direct costs or indirect costs associated with

A data flow diagram is a graphical representation of the flow of data

Data flow Diagram(Zero)

Train Management Ticket management

Route Management System user

Use case diagram

3. Game’s System Chart

Sign Up/ Player

Player select category

Surviv Action Racing

5. Summary of Requirements: (Initial Requirements)

6. Identifying External Entities

7. Capture “Shall” Statements.

Sr. No Actor Initial Requirements Use Case Name

Shall view player's his health UC_health

Sr. Use Case

11 Highest Player “Shall” grab enemies UC_11 UC_plygrabEnemy

10. High Level Use Case Diagram

11.Analysis Level Use Case Diagrams

11.1 UC_1 Register

11.3. UC_3 Category Selection/Game Mode

11.5. UC_4 Select Health Equipment

11.6. UC_6 player’s recovery items

11.7. UC_5 Health Status Bar

11.8. UC_8+9+10 Player’s Attack on Enemies

11.9. UC_14+15+16+17 Enemies Attack on Player

11.UC_20+21+22+23 User Can Purchase Goods online

12. Use Case Description

Sr. No Actor Action System Action

Feature User can see player’s current position on map

Sr. No Actor Action System Action

1.a Level may be loading when user click in map.

Sr. No Actor Action System Action

Feature Player can jump over obstacles

Pre-Condition Jump button must be pressed