Software Requirements

Specification
for

SCHEDULER

(Online software for university students)

Prepared by <Nabiha Faisal>

<B20102130>

<Sec: A>

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 1

Table of Contents
Table of Contents....................................................................................................................... 1
1. Introduction.......................................................................................................................... 2
1.1 Purpose...................................................................................................................................... 2
1.4 Project Scope..............................................................................................................................2
2. Overall Description.............................................................................................................. 2
2.1 Product Perspective....................................................................................................................2
2.2 Product Features.........................................................................................................................2
2.3 User Classes and Characteristics.................................................................................................3
2.5 Design and Implementation Constraints......................................................................................3
3. System Features................................................................................................................... 3
4. External Interface Requirements........................................................................................ 4
4.1 User Interfaces............................................................................................................................4
4.2 Hardware Interfaces....................................................................................................................4
4.4 Communications Interfaces.........................................................................................................4
5. Other Nonfunctional Requirements.................................................................................... 5
5.1 Security......................................................................................Error! Bookmark not defined.
5.2 Reliability..................................................................................................................................5
5.3 maintainabiliy.............................................................................................................................5
6. Other Requirements............................................................................................................. 5
7. Refrences............................................................................................................................. 5

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 2

1. Introduction
This document defines the requirements and goals of an electronic Scheduler Tool-particularly
for university timetables. Instructors and administrators at University's leverage this tool to
determine classroom and course assignments for each academic quarter. Students use Scheduler
Tool to view instructor details of courses in advance, which enables them to prepare accordingly.

1.1 Purpose

The purpose of this document is to provide a detailed description about the requirements needed
to successfully complete the Scheduler application for the benefit of the project management,
client, and development team. Throughout this document, Nabiha Faisal will provide a general
description of the project, the functional, interface, and performance requirements for the
application, a list of other relevant application attributes as well as an updated schedule

1.2 Project Scope

This requirements effort intends to define the requirements for the scheduler. The requirements
elicitation team includes Nabiha Faisal. The team will spend the period between of two months
identifying and documenting functional, interface, performance, and other requirements for the
Scheduler software system. Actual time spent on requirements elicitation during that period will
be considerably less than the total 23 days.

2. Overall Description

2.1 Product Perspective

The primary functionality for the Scheduler system is for the creation and viewing of course
schedules.

2.2 Product Features

The scheduler will have different functionality for three types of users, administrators,
instructors, and students. Administrators will be the primary users, with the ability to generate
new schedules, view past schedules, and modify the various databases included in the tool.
Instructors have the ability to go into the tool and enter time and class preferences so that their
preferences can be taken into account when schedules are being generated. Finally, students
have the ability to view generated schedules and provide what classes they want to take in the
future in order to give administrators a sense of what classes are needed most in upcoming
terms.

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 3

2.3 User Classes and Characteristics

The Scheduller application is intended to be used by university students. A typical user should
have some experience using web applications and mobile operating systems. A basic
knowledge of the iOS or Android operating system on a mobile device as well as the ability to
authenticate to University’s online student services will be sufficient to use the application
effectively.

2.4 Design and Implementation Constraints

The application shall be written in C++. The interfaces of the application shall be implemented
using the QT Non-Commercial application. The application shall store its files using XML tags.
The application will be platform independent.

3. System Features
The main functional requirements of the Scheduler are the following:
1. The Scheduler shall provide a means for entering and storing:
a. college information;
b. department information;
c. professor information;
d. class information;
e. building information;
f. classroom information.
2. The Scheduler shall schedule, if possible, the classes into classrooms.
3. The Scheduler shall take into consideration for generating the schedule the following
parameters: classroom size, classroom type, and distance from the department. These
parameters shall be selected by the user from a list of pre-defined values.
4. The Scheduler shall save the schedule in a format that can be used to generate a University
Semester Catalog that is readable by humans.
5. The Scheduler shall notify the user if no valid schedule can be generated and shall indicated
the causes that prevent the generation of a valid schedule.
6. The Scheduler shall write the schedule containing class and classroom information to a file
that can be read by supplied web pages so that these can be posted onto the university web
server.

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 4

4. External Interface Requirements

4.1 User Interfaces

The Scheduler has three separate interfaces, each for a different user of the application. The
Scheduler consists of a desktop application, which will be accessible only by administrators of
the Scheduler, as well as an online web application that is accessible by administrators,
instructors, and students. Instructors and students will be able to enter preferences on this web
application and view schedules generated by administrators. The initial user interfaces for each
account are described in the following sections:
 Administrator Interface
The initial administrator interface does not require a login. It allows an administrator to view
schedules, generate schedules, and edit the Scheduler's databases.

 Instructor Interface
The initial instructor interface is accessible after an instructor logs in to the Scheduler web
application. This interface allows an instructor to enter their course preferences.

 Student Interface
The initial student interface is accessible after a student logs in to the Scheduler web
application. This interface allows a student to enter their future schedules (for course demand
preferences) and view generated schedules.
The Instructor and Student interfaces are only accessible when a user logs in to the Scheduler.

4.2 Hardware Interfaces

The app is designed for the Android phone and web.

4.3 Communications Interfaces

The application will utilize the networking hardware of the user’s device through network
communications services provided by the Android operating system. Network communications
capability will be used to connect to remote databases and/or web services for authentication
and importing the user’s class schedule information.

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page 5

5. Other Nonfunctional Requirements

5.1.1 Security
Users must be a university student in order to access the automatic class schedule and
assignment sharing features of this application Users can authenticate by logging in using their
university username and password.

5.1.2 Reliability
Most functionality will not require network connectivity. System components that require
authentication through university and network connectivity will function as long as the systems
maintained by the University are available.

5.1.3 Maintainability
The development team will follow best practices for clean code and software modularity in
order to make the application as maintainable as possible.

6. Other Requirements
None.

7. References
http://users.csc.calpoly.edu/~gfisher/classes/309/specs/Liinct/requirements/file_edit/file-
database.html

https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.980.5249&rep=rep1&type=pdf

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.