SHREE JAYACHAMARAJENDRA COLLEGE OF

ENGINEERING
DEPARTMENT OF COMPUTER SCIENCE AND
ENGINEERING
Project on
“Railway coach information management system”
Team members
NAME ROLL NO USN
ARJUN M.R 10 4JC07CS014
ESHWARA C 19 4JC07CS032
HARIPRASAD 21 4JC07CS038
K.B
RAVIKUMARA 44 4JC07CS087
 SOFTWARE DESIGN SPECIFICATION(SDS)
1.1 INTRODUCTION:
The design phase begins when the requirement specification documents for
the software to be developed is available. While the requirement specification
activity is entirely problem domain, design is the first step to move from the
problem domain. Design is essentially the bridge between requirement specification
and the final solution for satisfying the requirement.
The design of a system is essentially a blueprint or a plan for a solutions for
the system. The design process for software system often has two levels. At the first
level the focus is on deciding which modules, and how the modules are needed for
the system, the specification of these modules, and how modules should be
interconnected. This is called design or top level design. In the second level, the
internal design of the modules or how the specification of the modules can be
design. Detailed design essentially expands the system design to contain more
detailed description of the processing logic and data structure such that the system
is sufficiently complete for coding.

1.2 ARCHITECTURAL DESIGN:

The architectural design phase identifies the multiple components of the
interaction among them. It provides enough detail on the components to write detail
designs. During this phase, top level designs are all forms, reports, data structures.
Program modules, files formats and human interfaces based on the information
contained in the system specification documents. It also identifies the design criteria
and design constraint. Applicable to the various modules or system.

1.2.1 PROBLEM SPECIFICATION:

The railway management systems computerise all activities involved in the
railway. This project aims at improving the overall efficiency of the activities and
provides total information documents available. The railway management system
will relieve the railway personnel from routine documentation work.
 In the railway management system the main modules identified are:
➢ Details
➢ Stock and maintenance
➢ Service
➢ Report Generation catalogue
➢ Access control and security

1.2.2 FUNCTION DESIGN

Details
This module maintains the information related to the condition of the arrived
and sent out railway coaches.

Service
This module involves the activities of the information storing related to the
incoming condition and the outgoing condition, and in also includes the activities of
checking the status of the coaches.

Stock and maintenance

This module maintains the information related to the details of providing the
survey sheet to the coaches and stores the status.

Report Generation and Catalogue

This module maintains the information related to the queries and includes the
various report generating activity.

Access control and Security

This module maintains the information related to the user password and
denying the unauthorized entry to the database.
1.2.3 USER INTERFACE DESIGN
The main menu of the system has the following options:
 Details
 Stock and Maintenance
 Service
 Report Generation and Catalogue
 Access control and Security
1.3 MODULE SPECIFICATION
1.3.1 DETAILS
MODULE AND SUBMODULE DESCRIPTION
NAME : Details
FUNCTION : Store the details about the condition of the
arrived and sent out railway coaches.
INPUT : Arrival and departure details
OUTPUT : None
SUBMODULES USED: Arrival. Departure
NAME : Arrival
FUNCTION : Stores the arrival details of the incoming
Coaches.
INPUT : Coach number, Coach code, Date shop in,
Base/div, Year built, volts.
OUTPUT : None
SUBMODULES : None
NAME : Departure
FUNCTION : Stores the sent out details of the outgoing
Coaches.
INPUT : Coach code, Coach number, Date shop out,
Base/div, Year built, volts, Date electrical fit.
OUTPUT : None
SUBMODULES : None
DATA BASE DESIGN
The tables used in the modules are Coach, entcoach.
INTERFACE ACROSS MODULES
This module interacts with the sub modules of service module.
CONSTRAINTS
The splitting of the details into arrival and departure is to done manually.

1.3.2 SERVICE:
MODULE AND SUBMODULE DESCRIPTION
NAME : Service
FUNCTION : Stores the details about the documents of
all items.
INPUT : Documentation details
OUTPUT : None
SUBMODULES : Incoming documentation, Checking Status,
Outgoing documentation.
NAME : Incoming documentation
FUNCTION : Storing of the conditions the components of the
Incoming coach.
INPUT : Number of components arrived and their
Conditions.
OUTPUT : None
SUBMODULES : Fault/missed components, Total components.
NAME : Fault/ missed components
 FUNCTION : Stores the various details of the missed
Components viz., make, capacity, lug dates etc.
INPUT : Fault/ missing details
OUTPUT : None
SUBMODULES USED: None
NAME : Total components
FUNCTION : Stores the total incoming components
INPUT : Total no. of arrived components and their status
OUTPUT : None

SUBMODULES USED: None

NAME : Checking status
FUNCTION : Include the activities of checking of the status of
Incoming coaches.
INPUT : Coach code and number
OUTPUT : Details of the given coach
SUBMODULES USED: None
NAME : Outgoing documentation
FUNCTION : Stores the details of the serviced coach
Components.
INPUT : Serviced details
OUTPUT : None
SUBMODULES USED: Serviced/ New components, Total
components
 NAME : Serviced/New components
FUNCTION : Stores the various details of the serviced
Components viz make, capacity, lug dates etc.
INPUT : Serviced/New components details
OUTPUT : None
SUBMODULES USED: None
NAME : Total components
FUNCTION : Stores the total outgoing components
INPUT : Total no. of attached components and their
Status.
OUTPUT : None
SUBMODULES USED : None

DATA BASE DESIGN

The tables used by this modules and its sub modules are Alternator, Battery,
Regulator, Axle pulley, Belt, Battery box, Light, Fan, Switch.
INTERFACE ACORSS MODULES
This module interacts with the Details and Stock and maintenance module.
CONSTRAINTS
The priority list has to be done manually.

1.3.3 STOCK AND MAINTENANCE

MODULE AND SUBMODULE DESCRIPTION
NAME : Stock and maintenance
FUNCTION : Stores all details of coaches
 INPUT : Coach details
OUTPUT : None
SUBMODULES USED: survey number, status
NAME : Survey number
FUNCTION : Assigning the survey number to each
Coach survey
INPUT : Coach ID and survey number
OUTPUT : None
SUBMODULES USED : None
NAME : Status
FUNCTION : Keeps track of the status of the
Components of the each coach
INPUT : Survey number, Status
OUTPUT : None
SUBMODULES USED : None

DATABASE DESIGN
The tables used by this module and its submodules are Coach, Condition,
Alternator, Battery, Regulator, Deficiency, Light , Fan, Battery box, Axe pulley,
Belt.
INTERFACE ACROSS THE MODULES
This module interacts with the Service and Details modules.
CONSTRAINTS
The coach status should be decided manually.
1.3.4 REPORT GENERATION CATALOGUE
MODULE AND SUB MODULE DESCRIPTION
NAME : Report Generation Catalogue
FUNCTION : Generates Report and query result
INPUT : User query
OUTPUT : Reports and query results
SUBMODULES USED : Reports and Queries
NAME : Reports
FUNCTION : Generates Reports
INPUT : User query
OUTPUT : Reports
SUBMODULES USED : None
NAME : Query
FUNCTION : Display query answer
INPUT : User query
OUTPUT : Display query answer
SUBMODULES USED : None

DATA BASE DESIGN

The views are created for reference.

1.3.5 ACCESS CONTROL AND SECURITY

MODULES AND SUB MODULE DESCRIPTION
 NAME : Access control and security
FUNCTION : Providing entry to authorized users only.
INPUT : User name and password
OUTPUT : Checking user password and providing
entry.
SUBMODULES USED: User permission, security
NAME : User permission
FUNCTION : Checking user password and allowing
Them to use the database.
INPUT : User password
OUTPUT : Access provision
SUBMODULES USED : None
NAME : Security
FUNCTION : Securing the database from the
unauthorized entry.
INPUT : Unauthorized user password
OUTPUT : Denying Access
SUBMODULES USED : None

1.4 DETAILS DESIGN:

DETAILS MODULE
• Enter the arrival and sent out details of the coach.
• The details such as the date coach code, coach number etc are
documented.
 • The manufacturer, base/division and the last POH place is also
entered.
• The tables Coach and in-out-coach is used for this purpose.
• User is allowed to select corresponding coach record for entering
the sent out details.

SERVICE MODULE
• The user enters the incoming conditions of the coach.
• The missed/fault components are listed.
• Unique survey number is assigned automatically.
• The components details will be checked to help in servicing.
• The replaced/New components after servicing will be listed.
• The details of the coach will be updated.
STOCK AND MAINTENANCE MODULE
• User allowed to select the components.
• Select the survey number.
• Components details are displayed based on the survey number and
coach number.
• The serviced details and the components status will be stored.
• The coach attributes like make and capacity will be stored.

REPORT GENERATION CATALOGUE

• Enter the query
• Report is generated
• Select print option if hard copy is required.

ACCESS CONTROL AND SECURITY

• The user ID and password will be verified
• The provision for accessing the database will be provided if the
password matches.
• Unauthorized password will be denied from accessing the database
and reports.
1.5 DESIGN STANDARDS
Directory structure
Main directory D:/RAILWAYS
Database D:/RAILWAYS/Service
Code D:/RAILWAYS/Form
Structure is attached in
Annexure A