Software Requirements Specification for TMS

Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii 1. Introduction ..............................................................................................................................1
1.1 1.2 1.3 1.4 1.5 Purpose............................................................................................................................................. 1 Document Conventions .................................................................................................................... 1 Intended Audience and Reading Suggestions .................................................................................. 1 Project Scope ................................................................................................................................... 1 References ........................................................................................................................................ 1 2.1.1 Developers View.2. 2.1.1.1 Front End.2 2.1.1.2 Back End..2 2.1.2 Users View...3

2. Feasibility study.2 2.1 Technical Feasibility..2

2.2 Economical Feasibility.......3 2.3 Operational Feasibility...3 3. Overall Description ..................................................................................................................4

3.1 Product Perspective.......................................................................................................................... 4 3.2 Operating Environment .................................................................................................................... 4

3.3 Assumptions and Dependencies ...4

3.4 Software Requirements.4 3.5 User Classes and Characteristics ..................................................................................................... 4

3. System Features .......................................................................................................................5

3.1 Functional Requirements ............................................................................................................. .5-6 4.1 Performance,Security and other Requirements................................................................................ 6

4. Other Nonfunctional Requirements .......................................................................................6

Software Requirements Specification for TMS

Page ii

Chapter # 2

1. Introduction
1.1 Purpose
Time table management is a difficult task in any educational institute management system and it is done manually. Goal of this project is to try to automate the process of Time Table Management. Automated Time Table Management System can be very effective in any educational management system. Another Goal of this project is to try to make it intelligent so it know a little about time table based upon user input and help the user in making the correct decision. Time Table Management System will be multi agent meaning that different entities will exist independently and Time Table Management System will only provide a way for them to interact.

1.2 Document Conventions

The document has used underlined words to highlight the user requirements. It also uses capital lettered words to highlight key words. The document has tried to maintain a priority of requirements.

1.3 Intended Audience and Reading Suggestions

The document is intended to be a guide for developers, users and testers. The goal of this document is to identify the requirements of application TMS 1.0. A developer may directly want to know the requirements by reading the section of USER REQUIREMENTS and skipping other sections if required.

1.4 Project Scope

Another important aspect would be the scope of the system i.e. the scope/area where the current system is to be implemented / deployed after the system is been developed; the current scope of the system developed by us is assumed for Computer Science and Software Engineering departments of UPR , University of Poonch Rawalakot.

1.5 References
For gathering the requirements as per defined scope in previous sections, we arranged meetings with teachers of CS(dep) and from following sites. Wikipedia.org Systemflowchat.com Google.com

Software Requirements Specification for TMS

Page 1

Chapter # 2

2. Feasibility Study:
Feasibility study is one of the most important step of the system development life cycle. The main purpose to carry out feasibility study is to understand the effectiveness and the usefulness of newly developed system to the organization. Three types of the feasibility has been carried out by us they are: Technical Feasibility Economical Feasibility Operational Feasibility

2.1 Technical Feasibility:

Technical Feasibility deals with availability and effectiveness of the technology required to develop and use the system. Our system Time Table Management System is been technically feasible because it is a web based application and so no additional tools are needed to run the software Now we may see the technical feasibility from the users as well as developers point of view. 2.1.1 Developers View:
Front End: ASP .net 4.1:

ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language.
Back End: SQL Server 2008:

Microsoft SQL Server is a relational model database server produced by Microsoft. Its primary query languages like ANSI SQL. SQL Server 2008 introduced "MARS" (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes.

Software Requirements Specification for TMS

Page 2

Chapter # 2

SQL Server 2008 introduced DMVs (Dynamic Management Views), which are specialized views and functions that return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance. Tools: Microsoft Visual Studio 2012 Microsoft Visual Studio 2012 is an Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, .NET Framework 4.1, .NET Compact Framework. Visual Studio supports languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any programming language, provided a languagespecific service exists. Built-in languages include: C/C++ (via Visual C++), VB.NET (via Visual Basic .NET), and C# (via Visual C#). Support for other languages such as F#, M, Python, and Ruby among others is available via language services installed separately. 2.1.2 Users View: Supports all the leading browsers like internet explorer, fire fox, and Google chrome etc The technical requirements specified above are feasible for most of the developers and user so we can say that the system is technically feasible.

2.2 Economical Feasibility:

This system as specified doesnt require any extra costly systems and softwares so it can be developed in any of the circumstances and is considered to be economically feasible too.

2.3 Operational Feasibility:

Time Table Management System is been analyzed by keeping two important aspects in mind that are User Convenience which can be achieved as this system is intended to generate time tables automatically for the institute and reduce the tedious amount of jobs done by the faculties. We also have analyzed it in a manner that it covers all the fundamental objectives/requirements of the system and due to this reason there will be no/minimal user resistance and so we can say that system is operationally feasible too.

Software Requirements Specification for TMS

Page 3

Chapter # 2

3. Overall Description
3.1 Product Perspective
Time Table Management System is been analyzed by keeping two important aspects in mind that are User Convenience which can be achieved as this system is intended to generate time tables automatically for the institute and reduce the tedious amount of jobs done by the faculties. We also have analyzed it in a manner that it covers all the fundamental objectives/requirements of the system and due to this reason there will be no/minimal user resistance and so we can say that system is operationally feasible too.

3.2 Operating Environment

OS: HD: RAM: Processor: Win XP, Win7, Win Vista, Mac 80 GB 512 MB or Above Pentium 1.0 GHZ

3.3 Assumptions and Dependencies

This document is subject to following assumptions.
The developed document contain the requirements within well-defined scope mentioned above it contains all the basic needed requirements. The major source of the requirements gathering is the sessions been conducted with teachers therefore their reviews and experience were takes as potential requirements to be included in the project.

3.4 Software Requirement

SQL Server 2008 Visual Studio 2012 Asp.net Adobe Photoshop C# HTML5

3.5 User Classes and Characteristics

Administrator: Responsible with over all functionality of the system.

Software Requirements Specification for TMS

Page 4

Chapter # 2

Teacher: To enter his/her preferred time into the system to generate time table. And to view information. Student: To view time table information.

4. System Features
4.1 Functional Requirements
This document describes the functionalities or services that the system is expected to provide .All the current requirements and expected near future requirements. The requirements are gathered at higher perspective level and drawn below in tabular form.

Time Table Management System ID

REQ-1

Requirements
View Time Table

Justification
Student and teachers will select the department and can view the time table. Admin will ADD, EDIT, VIEW, DELETE the Departments.

REQ-2

Manage Department

REQ-3 REQ-4

Manage Courses Manage Resources

Admin will ADD, EDIT, VIEW, DELETE the subjects. Admin will ADD,EDIT ,VIEW,DELETE the Resources like rooms, Labs etc.

REQ-5

Manage Time Slots

Admin will set the time slots for the subjects

REQ-6

Manage Semester

Admin will ADD,EDIT ,VIEW,DELETE the semesters

Software Requirements Specification for TMS

Page 5

Chapter # 2

REQ-7

Manage Clashes

System will handle the student and teachers clashes.

REQ-8

Assign courses

Admin will assign the different courses to different teachers.

REQ-9

Set Availability

Teacher will set his availability timing.

REQ-10 Manage Admin Admin will ADD, EDIT, VIEW, DELETE the admin record.

REQ-11

Change setting

account Admin will change account setting

REQ-12 REQ-13

Change Password Login to Application

Admin and teacher can change password for their accounts To provide user an easy way to login application database application database will be consist of buttons lables,text fields etc. System will generates the time table in the form of tables. The application provides easy way to view the reports of whole Time table.

REQ-14

Generate time Table

Software Requirements Specification for TMS

Page 6

Chapter # 2

5. Other Nonfunctional Requirements

5.1 Separate account for users with access types. As many people will be accessing the system simultaneously or separately, so it is necessary to maintain different account and access rights for the users. 5.2 Security implemented through account and login. The system need to be very secure apart from the automation, so it do not allow the users to make unwanted changes in any part of the system and it should not allow the unwanted users. 5.3 Report for available slot. Members shall have the able to view report about the available rooms and time slots. 5.4 Reports room, time and subject. Members shall be able to view time table in different ways, i.e. room wise, subject wise or time wise. 5.5 Information sent to teachers for any update in time table. If time table is updated by the admin due to any reason then a notification is to be sent to the concerned teachers. 5.6 Distributed application. The application shall be distributed and shall be available for access from different areas. 5.7 Availability The required availability will greatly impact the design. This system will have at least 12 hour availability.

Software Requirements Specification for TMS

Page 7