In this phase we produce the design specification for the PSS software. The specification includes Architectural design, Data design, Component-level design and Interface design. We will discussion all them. Architectureal design: An early stage of the system design process, the suitable architectural design style is "decomposition style" because the sub-system in this project are decomposed, and the suitable model is"pipeline model" because the system is decomposed into functional modules witch transform inputs to outputs. :Data design
ER

Data base schema
Data Dictionary showing description of 7 entities
|
Occurrence |
Aliases |
Description |
Entity name |
|
Each student has an ID |
pupil |
General term describing all students of the department of information technology |
Student |
|
Each member of the staff has a number, an office and an Agenda working according to it. |
employee |
General term describing all staff of the department |
Staff |
|
Each presentation has a time to be held in |
meeting |
Time to present the project |
Project Presentation |
|
Each schedule belongs to either a student or an employee |
timetable |
A table that shows the daily routine of the student or the employee |
Schedule |
|
Each project has an ID and a supervisor |
plan |
projects required for graduation |
Project |
|
A conflict has a cause |
clash |
A time that is not suitable for a student or a member of staff |
Conflict |
|
Each coordinator has a name |
supervisor |
A person who tries to set up a suitable time between students and staff |
Coordinator |
Data Dictionary showing description of 4 relations
|
Multiplicity |
Entity name |
Relationship |
Multiplicity |
Entity name |
|
1…1 |
schedule |
has |
0...1 |
Student |
|
1…1 |
project |
enters |
0…* |
Staff |
|
1…1 |
project |
Is required by |
1…1 |
Project Presentation |
|
1…1 |
staff |
Is entered by |
0…1 |
Schedule |
|
1…1 |
project |
enters |
0…1 |
student |
|
0…1 |
conflect |
has |
0…* |
project presentation |
|
1…1 |
Project presentation |
enters |
1…* |
Coordinator |
Data Dictionary showing description of 4 attributes
|
PK |
Range |
Default value |
Multi valued |
Nulls |
Length |
Data type |
Description |
Attribute |
Entity name |
|
Y
|
1970-2008 |
|
No
No
No
No |
No
No
No
Yes |
9
10
6
9 |
Varchar
Varchar
Date
Varchar |
Uniquely identifies a student
Name of the student
Date of birth
Contacts of the student |
Student ID
name
DOB
Tel number |
Student |
|
Y |
|
|
No
No
No
No |
No
No
No
No |
9
10
6
2 |
Varchar
Varchar
float
float |
Uniquely identifies a staff
Name of staff
Money a staff gets for his/her work
Hours of free time |
Staff num
name
salary
office hour |
Staff
|
|
Y |
|
|
No
No
No
No |
No
No
No
No |
6
6
9
2 |
date
date
Integer
integer |
The time when students can start present their projects
The time when projects can't be presented anymore
The number of the coordinator
The number of the project |
Start date
End date
Cor num
Project number |
Project presentation |
|
Y |
|
|
No
No
No
No |
No
No
No
No |
10
6
6
9 |
Varchar
Varchar
Varchar
Varchar |
A timetable that a student or a staff have to follow
A time that is not suitable for a student or a member of staff
The preferred time
A number that identifies a schedule |
Personal agenda
Exclusion set
Preference set
ID |
Schedule |
|
Y |
|
|
No
No
No
No |
No
No
No
No |
9
15
9
9 |
Integer
Varchar
Varchar
Varchar |
Uniquely identifies a project
The name of the project
The person who observes all of the project
The number of staff |
Project number
Project name
Supervisor
Staff num |
Project |
|
Y |
|
|
No
No
No |
No
No
No |
15
15
6 |
Varchar
Varchar
date
|
The name of the conflict
What caused the conflict
When did the conflict happen |
Conflict name
Cause
Start date |
Conflict |
|
Y |
|
|
No
No
No |
No
No
No |
9
9
2 |
Varchar
Varchar
Float
|
Uniquely identifies a coordinator
Name of the person
Times of free time |
Number
Name
Office hours |
Coordinator |
:Component-level design