Srs Classes Time Table

srs (software requirments specifications)

SRS Classes Time Table

In conventional HEIs, a classes’ time table is made at the start of each semester. The time table gives a schedule of lectures of the various offered courses – precisely the time table gives the Instructor, the classroom and the weekday and time slot for each offered course in the academic department. The classes’ time table is usually display in a week’s format.
This project intends to make a classes’ time table from the given input. The application will i) take as input: courses’ enrollment, faculty members’ course preferences, available classrooms and labs,and ii) produce a classes’ time table.

The application will:
 take as input, through Web: courses to be offered, students enrolled in offered courses,
details about faculty members and their courses’ and day preferences, classrooms and labs
available their capacities, and
 output a classes time table
 also cater the following requirements:


Scope of Project Classes Time Table:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Classes Time Table:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Classes Time Table:

1. Faculty member may:

i) login, ii) give his/her preferences in the offered courses once, view
his/her time table of class(es) (if calculated).

2. Student may:

i) login, ii) view his/her time table (if calculated)

3. Admin may create accounts of:

faculty members, students, class coordinator
4. Class coordinator may:

i) enter data about available rooms and labs their respective
capacities, slots and the availability of multimedia ii) view all the details of available rooms
and labs, iii) enter preferences of faculty members, iv) view all preferences of all faculty
members, v) enter course information (i.e. information about the offered course, its
student strength its requirements like multimedia), vi) view all the offered courses and
their details (student strength and requirements), vii) calculate classes time table, viii) view
the time table, ix) view the unscheduled faculty members, x) view the unscheduled courses,
xi) view the unscheduled classrooms/labs slots, xii) manually schedule unscheduled courses.
5. Furthermore:
a. If a course is preferred by two or more faculty members then the system should select
the faculty member of higher post (e.g. select Associate Professor over Assistant
Professor or Lecturer etc.). If the contending faculty members have equal rank then
select on the basis of who chose earlier than others.
b. Each course will be 03 credit hours having two lectures of 90 minutes each to be
scheduled per week. Both the lectures cannot be on the same day. Lectures can be
scheduled in classrooms/labs from 08:00AM to 04:30PM having slots: 08:00AM –
09:30AM, 09:30AM – 11:00AM, 11:00AM – 12:30PM, 01:30PM – 03:00PM, 03:00PM –

c. Each faculty member should give at least five preferences. A faculty member may be
assigned at least two and at most three courses.


  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes


Use Case Diagram of Classes Time Table

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



Usage Scenarios Classes Time Table:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.


ADOPTED METHODOLOGY forClasses Time Table:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.


Work Plan of Classes Time Table:

Work plan

for complete srs contact us

watsapp: 03469806607