Download Sample requirements document. - Department of Computer Science

Legal Practice System Authors – David Adams, Terry Carter, Andrew Cubbon
Functional Requirements
Listed below are the functional requirements of the system that we are to create. In the
table, the following shorthands are used:
M – a mandatory requirement (something the system must do).
D – a desirable requirement (something the system preferably
should do).
O – an optional requirement (something the system may do).
For ease of reading, the requirements have been split according to which of the four
main parts of the system they relate to.
Recording details of students and topics:
Req. ID
Description
Priority
1
Lecturers can add topics.
M
2
Lecturers can remove topics.
D
3
Lecturers can edit details of a topic.
M
4
Lecturers can view details of a topic.
M
5
Lecturers can add a student.
M
6
Lecturers can remove a student.
M
7
Lecturers can edit details of a student.
M
8
Lecturers can view details of a student
M
9
Lecturers can easily remove all students from the system at the end of each
year.
D
10
The system stores which topics each student is studying, which are entered by
the lecturer.
M
11
The compulsory topics are automatically entered into each student’s record.
D
12
Lecturers can add topics to a student’s record.
M
13
Lecturers can remove a topic from a student’s record.
D
Entering details of exercises:
Req. ID
Description
Priority
14
Lecturers can add exercises to a topic.
M
15
Lecturers can edit exercises.
M
16
Lecturers can remove exercises.
M
17
Lecturers can view the questions in an exercise.
D
18
Lecturers can add questions to an exercise.
M
19
Lecturers can edit questions.
D
20
Lecturers can remove questions.
D
21
Lecturers can enter a comment to be displayed for each answer to a multiplechoice question.
D
Version 2.1 1/3/02
7