user requirement:

 

updates occurring on the scheduale  should be taken care off in the best way.

 

 system requirements :

 

1.1)if either the student or the staff member had to change the previous date arranged , the new date is entered to the system with the new preferences and exclusions.

 

1.2)old appointment ( date & time ) is deleted.

 

1.3)add the new appointment as a new entry going through all the steps of adding a new entry with taking the  new preferences and/or exclusions in consideration.

 

 

User requirement :

 

the software should keep all changes in a history file  

 

system requirements :

 

1.1)create a history file for tracking the changes done.

 

1.2)all entries are kept in the history file to facilitate undoing previous steps with no need of re-entering the dates again.

 

1.3)use this history file as a backup copy incase of any crash of the system

 

user requirement :

Search time for suitable slots should be fast.

 

system requirements :

 

1.1)The system is ought to have its own database as a storage for the personal information related to the project presentations.

 

1.2)we shall use oracle database management system for storing the records.

 

1.3)The system has to run on a reliable server with enough memory

 

1.4)recompile the kernel and set the High Memory Support to 64 GB.

 

1.5)The system should have a big enough secondary storage

 

1.6)we shall use 999 gigabytes hard disk, which Windows xp can recognize.

 

 

 

 user requirements :

 

The system should find sutible slot for staff & students.

 

 system Requirements :

 

1.1)The system should find a presentation slot(date & time ) in a given date range and this slot should belong  to none of the exclusion sets and to as many preference sets as possible. 

 

1.2)If suitable  presentation slot found then allocated for the specified project . 

 

1.3)If no date can be found within the specified date range and outside all exclusion sets or  no date can be found within the specified date range and outside all exclusion sets but no date can be found at the intersection of all preference sets, the date conflict occur and then the system should solve it 

 

 1.4)If a date conflict occur the system can resolve it in several ways either the coordinator extends the date range or some participations should remove or add date & times from/to their exclusion/preferences sets, then the coordinator enters this new sets into the system to  find a suitable presentation slot and then allocates it for the specific project .

 

1.5) the committee staff and students must inform the coordinator if there are any changes on their agendas ,then the coordinator enters the new dates into the system  to  find a suitable  presentation slot and then allocates it for the their  project .

 

 1.6)Once all presentations are scheduled, the schedule is posted on the graduation project webpage and e-mailed to all staff.

 

user requirement:

The presentation software must be finished after two months

 

 

system requirements :

 

1.1 The feasibility study should be done in the time that was determined to it.

 

1.1.1 If the system is not worthwhile,we must  stop it.

 

1.1.2 if the system is worthwhile,we will complete the next steps.

 

1.2 The requirements elicitation must be done in the time that was determined to it to choose the  suitable system model.

 

1.3 The requirements specification should be done in the time that was determined to it to collect the user and the system requirement.

 

1.4 The requirements validation should be done in the time that was determined to it.

 

1.5 All the afore-going steps must be done within 2 months.

 

user requirement:

 The system mut be provide securty

 system requirements :

 

1.1 the sytem must be enable user to enter name and passowrd.

 

1.1.1 if the user enter wrong name and passowrd the system mut be no accept.

 

1.1.2 if the user enter  right name and passowrd the system mut be accept.

 

1.2  if system accpet the user the user can enter the schedules  and commncate whith system

 

system model:

 

after the votes we choose the DFD model because it's the approprite model of our project it provide and shows the different operations and the attributes which we input it or the system give it to the users... 

 

 

 

 

 

bibliography:

 

Bibliography is just a list of references used in gathering information for the SRS document, references could be books, webpages, external slides...etc.

 

 1-Slides of Sommerville, the author.

 

2- modern system analysis and design

by Jeffry A.Hoffer, JoenyF,George, Joesephs valacich    

 

3-  http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html

this site about Writing Software Requirements Specifications , What is a Software Requirements Specification? ,Why Should Technical Writers be Involved with Software Requirements Specifications?

 

4-http://www.yourwindow.to/information-security/gl_userrequirementsspecificationurs.htm

this site about user requirement

 

5-http://en.wikipedia.org/wiki/System_requirements

 

this site about system requirements

 

 

appendix:

 

supplementary material that is collected and appended at the back of the books or reports or it's Something appended or added; an appendage, adjunct, or concomitant, some books define it  like Any literary matter added to a book, but not necessarily essential to its completeness, and thus distinguished from supplement, which is intended to supply deficiencies and correct inaccuracies.

 

 

 

we must define somthings  in our report like:

 

•  first off all the requirement we use in our report like:

   

   

  *The system should be compatible with the main known browsers..

   

  *The system should support good interface such as buttons, text boxes to enter data, navigational links and so on...

   

  note: it's from Slides of Sommerville, the author.

   

 

• the second is  the DFD as follows:

 

this is a process:

 

 

 and the previous picture is the interface..

 

 

 

this is the data flow:

 

 

 

 

 

 

this is the data store: