support, refunds and other real time fixes.
 Confirm Reservation for confirm Seat.
railway reservation office and waiting in the queue for your turn.
to be built, its functions, its users, its constraints and its dependencies.
Contents, the Appendices, and the Index.
requirements. Such all details are provided in section 3.
inconsistency and inaccuracy in the maintenance of data.
destroyed due to any natural calamity of fire or water.
etc. causing inconvenience to customers and staff.
paperwork and hence load on the staff of admin department.
 Machine does all the calculations. Hence, chances of error are low.
updation can easily be performed.
displays a list of trains available with different classes.
 Date, Time and place of departure.
should be comfortable with English Language.
using general-purpose applications on the computer system.
operating system with At least Internet Explorer 8 installed.
knowledge of railway reservation system and its working.
application, it is necessary to have internet access.
processor, RAM etc. those are required for software to run.
with a working LAN connection to be mandatory.
and having minimum of 512 kbps working LAN compulsorily.
of any train and its expected arrival/departure at any given station.
After reserving the required amount of tickets, the customer paid the amount.
It is available during all 24 hours.
system functions are performed for which actor. Roles of the actors in the system can be depicted.
actor and is drawn as a horizontal ellipse.
or more interactions with the system.
interactions in the application, and the classes to be programmed.
and the first letter is capitalized.
and the first letter is lowercase.
left-aligned and the first letter is lowercase.
modelling, the classes of the conceptual design are often split into a number of subclasses.
complemented by a state diagram or UML state machine.
be restarted. It means 24x7 availability.
SSL in all transactions that include any confidential customer information.
modularity in mind so that maintainability can be done efficiently.
prefix "un," such as: The system shall reject unauthorized users.
is deleting "booking," which is an extraneous word.
Design constraints can be imposed by other standards, hardware limitations, etc.
software to trace processing activity.
example which shows how the data shall be stored and presented.
*Note: the file format and type may vary when the system is being developed.
modify any of the data files.
Categories such as those below.
 Note: This is sometimes specified as part of the User Interfaces section.
a given site, mission, or operational mode, for example, safety limits.
2. Specify features that should be modified to adapt the software to an installation.
to depict the structures and the relationships in a complex system.
o System : A set of elements organized to achieve certain objectives form a system.
Systems are often divided into subsystems and described by a set of models.
created for better understanding of the system.
o View : A view is a projection of a system’s model from a specific perspective.
another and in what order. It is a construct of a message sequence chart.
runtime scenarios in a graphical manner.
be used for the visualization of data processing (structured design).
operate in sequence or in parallel (which is shown on a flowchart).
between the various parts of the system.
reservation and cancellation in between.
Reservation/ Cancellation management, Admin’s Report Generation Tasks etc.
diagrams exist, which differ slightly and have different semantics.
on a service as whole.
RFC are triggered for a wide variety of reasons and from a wide variety of sources.
raise an RFC in the e-helpline tool.
appropriate individuals receive adequate notice of changes.
i. Product or service change.
implementation duration or not and so on.
e. Impractical, inadequate RFCs without necessary budgetary approval.
g. Executor and evaluator details.
the change executed needs to be evidenced to declare successful closure.
If the type of change is an emergency change, then invoke Emergency change procedure.
Emergency or urgent changes have over-riding priority over scheduled changes.
be executed in the shortest possible time.
not be as exhaustive as other changes.
Implementing untested system should be avoided to the maximum extent.
technical team on hand while deploying emergency changes.
costs shall be updated, wherever required.
Request. Details of risks associated with the Change should be updated in RFC.
 Who RAISED the Change?
 What is the REASON for the Change?
 What is the RETURN required from the Change?
 What RESOURCES are required to deliver the Change?
 Who is RESPONSIBLE for the build, test and implementation of the Change?
All Changes recorded as Minor (C1) and Major (C3) changes shall be approved by CAB.
CAB meetings should be held as per CAB Meeting Guidelines.
Major (C3) and Minor (C1) changes.
 Executors - Domain Engineers.
PIR Discussion: Every Monday, Wednesday and Friday between 3:00 PM to 4:00 PM.
CAB Meeting: Every Monday, Wednesday and Friday 4:00 PM to 6:00 PM.
The issue of risk to business has to be considered prior to approval of the Change Request.
Details of risks associated with the Change should be updated in RFC.
Authority could be the customer engagement manager.
all the above two functions.
not change should be pursued. CAB meetings should follow CAB Guidelines.
communicated to all relevant stakeholders with proper reason and justification.
necessary lead time required for the normal RFC process.
from all aspects before the Change request is closed.
meetings maybe via a bridge line opened by the Change manager.
and either approve or do not give approval.
built, it is mandatory to attach an email approval to the RFC.
Change Owner coordinates the change with the Release Manager.
process and not extensive tests..
information and will be closed post validation of PIR by Change manager.
 Reports status and present findings to the CAB.
 Produce regular and accurate management reports.
 Document RFC for PIR, minutes of meetings (for e.g.