- Information
- AI Chat
Vdocuments - SRS Document for time table management
Computer application (BCA404)
KLE University
Recommended for you
Preview text
SOFTWARE REQUIREMENT
SPECIFICATION
For
TIMETABLE MANAGEMENT
SYSTEM
Version 1 Approved
PREPARED BY : Minali Chourasia (0611CS081008) Namrata Jain (0611CS081010) Namrata Patel(0611CS081011) Mohini Pathak (0611CS081009) Pragya Chourasiya (0611CS081015) [ BE(CS) VI Sem. ]
- DATE : 18/03/
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.
1 Background Details
The Software Requirements Specification captures all the requirements in a single document. The Timetable Management System that is to be developed provides the members of the College and Student of the College with Student information, System Provide all Classes Time Table details of the college, and it provide many facilities. The Timetable Management System is supposed to have the following features.
1 Overall Description
In few minutes, the program generates a complete timetable that fulfills all your requirements. The program follows all psycho hygienic and organizational requirements such as:
Selection for Number of working days of the week (ex. Saturday off)
Zero (attendance) period insertion
Periods per day selection .This selection is day wise ex. Can be made 4 periods on Saturday etc.)
Subjects could be entered considering
Hard subjects in first 4 or 5 periods
Subject in which classroom
Single or double duration consecutively
Periods per week per subject
Type of subject ( Hard, easy...)
Subjects distributed evenly for entire week
1 References
SRS template, 2010-05-10, Computer Engineering department, Kuwait University.
1 Product Perspective
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.
BENEFITS TO MANAGEMENT:
Helps to get a global outlook and exposure for the institute for being Tech Savvy Reduces paper work leads to saves cost and paper Increased Productivity by savings in man hrs in managing information with automation Information required for Decision making is instantly available Single suite of Education Management software handing everything saves on additional investment in different software and management issues Removes bottleneck in the process of getting information out of pile of data and further reduces piles of files
BENEFITS TO STAFF & ADMINISTRATION:
Easy monitoring of individual modules leads to quick error detection Quick & automated report generation Centralized data repository for easy data access Authenticated profile based data access User friendly interface requiring minimal learning and IT skills High level data security Design for easy Scalability Elimination of processes those are people dependent Minimal data redundancy
BENEFITS TO TEACHERS:
Saves time as Student attendance is automated Marks and Grades generation is computerized this adds to time efficiency Timetable creation before hand Assignments to students can be given and tracked Availability of more time for teaching to students Improved interaction with parents Access to own and students' attendance Various school activities are better organized
- Software Requirements Specification Outline
This outline specifies the minimum content elements for the SRS document. Document formatting is not defined; all formats are acceptable, if the content elements are complete. 4 Page Provide a cover page with the necessary content, such as the name of the document, date, and the Office of Systems Integration logo and footer. 4 History Provide a revision history table with column titles: Revision Number, Date of Release, Owner and Summary of Changes. 4 of Contents Provide a table of contents with a list of the document sections and the pages on which they begin. 4 Description In the Behavioral description subsections, provide a view of the entire SRS. This section should describe how the SRS is organized.
4.5 Constraints Describe factors that limit the scope and functionality of the software. Constraints are requirements that are imposed on the software solution. 4 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 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. 4.6 Non Functional Requirements The Non 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 and generate its result. Non Functional requirements should include specific requirements for business rules, which describe and document the steps in a business process. 4.6 Logical Data Requirements Describe the logical data requirements for the system.
4.6 User Requirements Describe the user requirements; these should capture the intended behavior of the human interface of the application.
4.6 Requirements
4.6.5 Requirements Describe the performance conditions and their associated capabilities. These requirements should be stated in measurable terms.
4.6.5 Requirements Describe requirements for the quality characteristics of the application, such as usability, reliability, and maintainability. These requirements should be stated in measurable and verifiable terms. 4.6 Interfaces Describe the characteristic of each interface between the software and other hardware or software, such as communication protocols and purpose of the interface. 4.6 Other Requirements Identify any additional requirements that could not be appropriately categorized into the preceding requirements sections. 4 References Provide any references used in the creation of the document. 4 Provide an alphabetized list of definitions for special terms and acronyms used in the document. 4 The appendices should contain material that is too detailed or large to be included in the main body of the document. Refer to each appendix in the main body of the text where the information applies.
Vdocuments - SRS Document for time table management
Course: Computer application (BCA404)
University: KLE University
- Discover more from: