Sunteți pe pagina 1din 14

Addis ababa

science and technology


university
Department of Software Engineering
Object Oriented System Analysis and Modeling Project

Name ID Number
Fraol Ahmed ETS0502/07
Abdurahman Ali ETS0019/07
Ekram Beharu ETS0406/07
Bezawit Tolosa ETS0257/07
Nardos Israel ETS0836/07
Biruk Feleke ETS0289/07
Functional and nonfunctional requirements of the system
I) Functional Requirement: The functional requirements for the student clearance system are:
Administration of Users: The system shall record a database of user accounts. There are
three types of users. The unit clearance officer (users) use the student clearance system for
either posting the students status or making the enquiries/printing reports. The other user is
the student users who request the system for a printed copy of a clearance paper. The third
classes of users are technical users like the system administrator who will have full access to
the system and are able to create new, edit, and delete a user.
User Authorization: The student clearance system shall allow the user administrator to
approve the registration of a new user by authorizing his user account.

II) Non-Functional Requirements: These kinds of requirements are sometimes called constraints of
the system. Non-functional requirements denote limits of the system and its expected behavior. They
do not impact the system directly in terms of functionality:
Usability: The system must be errorless in the most common web browsers such as Chrome,
IE 8 and 9, Firefox, Opera, and Safari. The system shall inform the user about its current
state (loading, item created, item updated, etc.)
Reliability: The system must not contain errors making

1
A basic use-case for Clearance request

Use case: RequestClearance


Primary actor: Student
Goal in context: To request a copy of clearance paper and send a copy to the office
of registrar.
Preconditions: System will check for valid student ID number and clearance status
in all responsible offices.
Triggers: The student decides to request a copy clearance paper and submit a
copy to the office of registrar.
Scenario:

1. Student: opens clearance request page in a web browser by entering the Url.
2. Student: enters his/hers Id number into the input field provided
3. Student: presses request button.
4. Student: Observes his/hers clearance status in all sectors

Exceptions:

1. Entered Id number is not valid (System displays message saying Please Enter a valid Id
number): Student reenters a valid Id number.
2. Student hasnt cleared in all responsible sectors: The system will in indicate in which sectors
student need to clear.
3. Student has cleared in all responsible sectors: The system will provide a print option and sends
a copy to the office of registrar.
4. Student selects print option: The system will provide a printed document.

Priority: Essential, must be implemented


When available: Second Increment
Frequency of use: anytime when necessary
Channel to actor: via web browser and Network connection
Secondary actors: system administrators
Channels to secondary actors: web browser.
Open issues:

1. Should there be a way to request a clearance copy without knowing Id number?


2. Should a student navigate to other pages?
3. Should the system be accessible any any time in the year?

2
A basic use-case for Login
Use-case: Login
Primary actors: Responsible sectors
Goal in context: Login to Add, Edit or delete student records
Precondition: System will check for valid login details (username and password of
officer)

Triggers: The officer wants to login to maintain student records


Scenario:

1. Officer: opens login page by clicking the button from the navigation bar.
2. Officer: Enters his/hers login credentials.
3. Officer: selects from options Adding, Editing or Deleting student records.

Exceptions:

1. Entered login credentials are incorrect: System displays a message saying Please enter valid
credentials
Priority: Essential, must be implemented
When available: First increment
Frequency of use: anytime when necessary
Channel to actors: via web browser and Network connection
Secondary actors: System administrators
Channels to secondary actors: web-browser
Open issues:

1. Should the system specifically tell whether the password or the username is incorrect?
2. Should the login page be accessible simply by typing the url?
3. Are system administrators use the same logins with other officers?

3
A basic use-case for Adding student records
Use case: AddRecords
Primary actor: Officers of responsible sectors
Goal in context: To add records of students with issues that wont allow the student
to have clearance paper.
Precondition: The system checks if full information of the student to be recorded
is provided
Triggers: The student receives or borrows a service or an item
Scenario:

1. Officer: selects Add Records option from options listed.


2. Officer: enters details of student which will recorded.
3. Officer: enters the issue that the student is being recorded of.
4. Officer: clicks save button at the end of form.
5. System: displays result of operation.

Exceptions:

1. Officer hasnt filled all the required fields: The system tells the user to fill out all the required
fields.

Priority: Essential, must be implemented


When available: First increment
Frequency of use: at any time when necessary
Channel of actor: via web browser and Network connection
Secondary actors: System administrators
Channels to secondary actors: via web browser and Network connection
Open issues:
1. Can a student be recorded without any issue?
2. Should an officer be able to record a student for an issue that the officer is not
responsible to?

4
A basic use-case for Editing student records
Use case: EditingRecords
Primary actors: Officer of responsible sectors
Goal in context: To Edit records of students with issues that wont allow the student
to have clearance paper.
Preconditions: The system will check if the student record to edited already exists
in the system
Triggers: Changes occur in service or an item student received or borrowed
Scenario:

1. Officer: selects Edit records option from list of options provided


2. Officer: searches for student record by entering student Id number
3. Officer: selects student whose record is to be edited
4. System: displays editable information of student which is previously recorded
5. Officer: Edits information he/she wants
6. Officer: clicks save button
7. System: displays result of operation

Exceptions:

1. Entered student Id number does not exist: System displays message saying No student
record with entered Id number
2. Officer hasnt filled all the required fields: The system tells the user to fill out all the required
fields.

Priority: Moderate priority, to be implemented after basic requirements


When available: Second Increment
Frequency of use: at any time when needed
Channel of actor: via web browser and Network connection
Secondary actors: System administrators
Channels to secondary actors: via web browser and Network connection
Open issues:

1. Should there be a way to search a record without using Id number.?


2. Can an Id number of a student record be changed?

5
A basic use-case for Deleting student records
Use case: DeleteRecords
Primary actor: Officers of responsible sectors
Goal in context: To delete student records from existing records
Preconditions: The system will check if the student record to deleted already exists
in the system.
Triggers: Student disengages from service being received or returns
borrowed item
Scenario:

1. Officer: selects Delete records option from list of options provided


2. Officer: Searches for a student record by entering student Id number.
3. Officer: selects student record whose record is to be deleted
4. Officer: presses delete button to delete student record
5. System: displays result of operation

Exception:

1. Entered student Id number does not exist: System displays message saying No student
record with entered Id number
2. Officer hasnt filled all the required fields: The system tell the user to fill out all the required
fields.

Priority: Essential, must implemented


When available: First increment
Frequency of use: at any time when needed
Channel of actor: via web browser and Network connection
Secondary actors: System administrator
Channel to secondary actors: via web browser and Network connection
Open issues:

1. Should there be a way to search a record without using an Id number?

6
A basic use-case for System Administrator login
Use case: AdministratorLogin
Primary actor: System administrator
Goal in context: Login as system administrator to gain full access of the
system
Preconditions: System will check for valid login credentials (username and
password) of System administrator

Triggers: System administrator wants to gain full access of the system


Scenario:

1. System administrator: opens administrator login page by typing the url in the address bar
2. System administrator: enters login credentials
3. System administrator: selects where to go from the navigation bar.

Exception:

1. Entered login credentials are incorrect: System displays a message saying Please enter valid
credentials

Priority: Essential, must be implemented


When available: First increment
Frequency of use: any time when necessary
Channel to actor: via web browser and Network connection
Secondary actors:
Channels to secondary actors:
Open issues:

1. Should the system administrator login page be accessible from the navigation bar?

7
A basic use-case for Adding user accounts
Use case: AddAccounts
Primary actors: System Administrators
Goal in context: Create user accounts for responsible sectors
Precondition: The system checks if all fields are filled correctly
Triggers: System administrator decides to create an account for a
responsible officer
Scenario:

1. Officer: selects Add new accounts option from the options listed.
2. Officer: enters details of officer whos going to use the new account
3. Officer: clicks save button after filling the form.
4. System: displays result of operation.

Exception:

1. System administrator hasnt filled all the required fields: The system displays a message
saying Please fill out all required fields.

Priority: Essential, must be implemented


When available: First increment
Frequency of use: By the time when system gets implemented
Channel to actors: via web browser and Network connection
Secondary actors:
Channels to secondary:
Open issues:

1. Should the system auto generate a user name and password for given officer details?

8
A basic use-case for Editing user accounts
Use case: EditAccounts
Primary actor: System administrator
Goal in context: Edit details of existing user accounts
Preconditions: System will check if the user account to be edited exists
Triggers: There will be a need to change user account details
Scenario:

1. System administrator: selects Edit user accounts option from list of options
2. System administrator: searches for user account by entering username.
3. System administrator: selects user account to be edited
4. System: displays editable information of user account to be edited
5. System administrator: updates information of the user account
6. System administrator: clicks save button
7. System: displays result of operation

Exceptions:

1. Entered username does not exist: System displays message saying No user account found with
entered username
2. System administrator hasnt filled all the required fields: System tells the system administrator
to fill out all the required fields.

Priority: Moderate priority, to be implemented after basic functions


When available: Second increment
Frequency of use: anytime when necessary
Channel to actor: via web browser and Network connection
Secondary actor:
Channels to secondary actors:
Open issues:

1. Should there be a way to search a user account with a user name?


2. Can a user name of an account be changed?

9
A basic use-case for Deleting user accounts
Use case: DeleteAccounts
Primary actors: System administrator
Goal in context: delete existing user accounts
Preconditions: The system checks if the user account to be deleted
exists in the system
Triggers: System administrator wants to delete unnecessary
user accounts
Scenario:

1. System administrator: selects the option Delete user accounts from the list of options.
2. System administrator: searches for user account to be deleted by entering username.
3. System administrator: selects user account to be deleted.
4. System administrator: presses delete button.
5. System: displays result of operation.

Exceptions:

1. Entered username does not exist: System displays message saying No user account found.

Priority: Essential, must be implemented


When available: First increment
Frequency of use: any time when necessary
Channel to actor: via web browser and Network connection
Secondary actors:
Channel to secondary actors:
Open issues:

1. Should there be a way to search a user account without a username?


2. Can deleted user accounts be recovered?

10
A basic use-case for viewing student statistics
Use case: ViewStatistics
Primary actors: System administrators
Goal in context: To view the number of students cleared and yet to
clear
Preconditions:
Triggers: System administrator chooses to view statistics of
students
Scenario:

1. System administrator: clicks on the view stats link.


2. System: displays a categorized view of students who have cleared and students who are yet
to clear.

Exception:

Priority: Least priority, to be implemented after all


functionalities
When available: Third increment
Frequency of use: few times a year
Channel to actor: via web browser and Network connection
Secondary actors:
Channel to secondary actors:
Open issues:

1. Should the system display results according to times selected by the user?
2. Should viewing statistics be allowed to all other user accounts?

11
A use-case diagram for AASTU Student Clearance System

12
An Activity Diagram for Requesting a clearance paper

13