Beruflich Dokumente
Kultur Dokumente
SPECIFICATION
For
TIMETABLE MANAGEMENT
SYSTEM
1.1 Purpose
The purpose of Software Requirements Specification (SRS) document
is to describe the external behavior of the Timetable Management System.
Requirements Specification defines and describes the operations,
interfaces, performance, and quality assurance requirements of the
Timetable Management System. The document also describes the
nonfunctional requirements such as the user interfaces. It also describes
the design constraints that are to be considered when the system is to be
designed, and other factors necessary to provide a complete and
comprehensive description of the requirements for the software. The
Software Requirements Specification (SRS) captures the complete software
requirements for the system, or a portion of the system. Requirements
described in this document are derived from the Vision Document prepared
for Timetable Management System.
2. Selection for Number of working days of the week (ex. Saturday off)
Software Requirements Specification for TIMETABLE MANAGEMENT SYSTEM 3
4. Periods per day selection .This selection is day wise ex. Can be made
4 periods on Saturday etc.)
1.4 References
The rest of this document contains the following in the mentioned order:
1- Overall description of the project and its requirements.
2- Specific requirements for the project including the functionality,
usability, reliability, performance, security, safety, design constraints,
and copy right and intellectual properties.
Software Requirements Specification for TIMETABLE MANAGEMENT SYSTEM 4
2. Environmental Characteristic
1 Hardware
1.1 Processor P IV & Above
1.2 RAM 256
1.3 O.S. Window Xp & Above
2 People
2.1 Contractor
The Contractor is responsible for developing, updating, and obtaining
approval for the SRS, if it is included as a requirement in the contract.
2.2 Project Manager
The Project Manager is responsible for coordinating the efforts of those
involved in the SRS development, review, and approval.
2.3 Contract Manager
The Contract Manager verifies that the SRS deliverable is provided,
reviewed, and approved.
3. Goods of Implementation
STRATEGIC BENEFITS:
BENEFITS TO MANAGEMENT:
• Helps to get a global outlook and exposure for the institute for being Tech
Savvy
BENEFITS TO TEACHERS:
4.2Revision History
Provide a revision history table with column titles: Revision Number, Date of Release,
Owner and Summary of Changes.
4.3Table of Contents
Provide a table of contents with a list of the document sections and the pages on which
they begin.
4.5.3 Constraints
Describe factors that limit the scope and functionality of the
software. Constraints are requirements that are imposed on the
software solution.
4.6 Functional Requirements
The functional requirements sections should be customized to
contain the information necessary to define the fundamental actions that
must take place within the software to process inputs and to process and
generate outputs. Functional requirements should include specific
requirements for business rules, which describe and document the steps
in a business process.
In the functional requirement subsections, specify all software
requirements to a level of detail sufficient to enable the developer to
build the software application. Each functional requirement documented
in the requirements sections must have a unique identifier for
requirements traceability and should be ranked for importance and/or
stability.
4.6.1 Business Requirements
Describe all requirements from a business perspective. Business
requirements are the parts of the fully defined business process that
will be automated by the software.