‡ Software Requirements Specification ‡
Version 1.0
April 9, 2008
Project Scheduling System (PSS)
Arwa Al.Zaban
Fida'a Al.Oumar
Hawra Al.Rabaan
Haya Al.Mirshed
May Al.Suhaibany
Nouf Al.Sayary
Noura Al.Sudairy
Reem Al.Duweesh
Sarah Al.Ajlaan
Sarah Al.Najraan
Submitted in partial fulfillment
Of the requirements of
CSC 312 Software Engineering
Bibliography
Bibliography…………………………………………………………………………………………………………………2
1.0. Introduction…………………………………………………………………………………………………… 3
1.1. Purpose
1.2. Scope of Project
2.0. User Requirements………………………………………………………………………………………4
3.0. System Requirements…………………………………………………………………………………5
3.1. User Requirement definition (1)
3.2. System Requirements specification (1)
3.3. User Requirement definition (2)
3.4. System Requirements specification (2)
3.5. User Requirement definition (3)
3.6. System Requirements specification (3)
4.0. System Models…………………………………………………………………………………………… 8
4.1. Context Diagram
4.2. Level 0 Diagram (DFD)
5.0. Appendix……………………………………………………………………………………………………
List of figures ……………………………………………………………………………………………………………2
Figure 1.1 ……………………………………………………………………………………………………………………8
Figure 1.2 ……………………………………………………………………………………………………………………9
1.0. Introduction
1.1. Purpose
The purpose of this document is to present a detailed description of the Project Scheduling System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system and will be proposed to the Regional Historical Society for its approval.
1.2 Scope of Project
After finishing part I, the main work in part II is to discover the requirements for the PSS software.
Then, we generated an SRS “software requirements specification” document.
Some information about the system:
The coordinator asks all potential attendees based on their
· Personal agendas within a certain date range.
· Presentation slot is defined by a pair.
· Presentation slot should belong to none of the exclusion sets & to as many preference sets as possible.
2.0. User Requirements
2.1. The system shall collect the exclusions and preferences dates and times for graduation committee staff and graduation students
2.2 The system shall find the certain time for presentation slot and resolve a date conflict when occur
2.3 The system shall reflect changes of date and time immediately on presentation scheduling
3.0. System Requirements
|
User Requirement definition
|
1. The system shall collect the exclusions and preferences dates and times for graduation committee staff and graduation students
|
System Requirements specification
|
1.1
1.1 The user should log in with his/her email and password to grant the access on their schedule. If it’s his/her first time, he/she should sign up and fill in the registration form.
1.2 In the registration form, the system asks for the user’s status (graduation student or staff member). Basic information is required also (i.e. name, ID , date of birth, project group name.
1.1 The user should enter one of these initials in each slot of the table :
“P” for : preferences
“E” for exclusions.
“S” for subject.
Leaving the slot with a “null” value indicates Free time. (A1)
(A1
1.4 Facilities are provided for the “submit” & “edit” buttons for the user to choose from.
1.5 The user’s information is sent to a database that includes all the other users' information.
|
User Requirement definition
|
2. The system shall find the certain time for presentation slot and resolve a date conflict when occur
|
System Requirements specification
|
2.1 The system then gathers the information from the database to find a presentation slot.
2.2 The system should compare all the preferences and exclusions and returns the ideal slot, where there’s no exclusions & as much preferences as possible.
2.3 The system shall sense if a conflict occurs and determine whether the conflict is strong or weak. (A2)
2.4 If no conflict occurs the system shall organize the information of all users (students and staff) and display the appropriate presentation schedule for all users to see.
|
User Requirement definition
|
3. The system shall reflect changes of date and time immediately on presentation scheduling
|
System Requirements specification
|
3.1 The system shall give three options to resolve the occurrence of conflict. Either, extending the date range.
3.2 The system might also ask the participants to remove dates/times from their exclusion set, 0r to add some new dates/times from their preference set, by using the "edit" button.
3.3 The system then shall gather the information and try to find another appropriate time slot.
3.4 The system shall reorganize the information of all users (students and staff) and display the appropriate presentation schedule for all users to see.
4.0. System Models
4.1. Context Diagram
Figure (1.1)
4.2. Level 0 Diagram (DFD)
Figure (1.2)
5.0. Appendix
Ø Project Scheduling System: split project into tasks and estimate time & resources required for each task.
Ø Preferences and Exclusions:
Preferences: preferred times to attend.
Exclusions: the times he’s not able to attend in a table.
Ø Strong Conflict: when no other date is found where no exclusions occur and all users’ preferences occur within the date range
Ø Weak conflict: when another date’s found but not all users prefer it
Comments (0)
You don't have permission to comment on this page.