Chapter Four 4. System Analysis
Chapter Four 4. System Analysis
Chapter Four 4. System Analysis
4. SYSTEM ANALYSIS
4.1. System Model
System modeling helps the analyst to understand the functionality of WKU Department
Placement system. for modeling the system, the object-oriented analysis methodology used,
which includes:
Actor specification
Use case diagram
Use case description
Sequence diagram
Class diagram
Generally, it helps the analyses to understand the functionality of the WKU Department
Placement system and it communicates the system with the user.
In this project, there are 6 actors for accessing the system. These are:
Administrator
Main Registrar
College Registrar
College Dean
Department Head
Student
Table 4.1 Actors and their specification
Actor Specification
o Post information
o Main Registrar
o Makes the placement
o disseminates the student list into the colleges
o notify student's placement result after the placement is done
o approve or reject the student Department Change request
o Views comment
o modify account
o Views comment
o Post news
Section Purpose
Use Case Name Login
Identifier UC1
Actor Administrator, Main Registrar, College Registrar, College Dean, Department
Head, Student
Description The user enters an authorized user name and password in order to access the
system.
Goal To access the system.
Pre-condition The user should have username and password.
Post-condition The user successfully login to the system.
Basic course of User action System response
action 1. user clicks the login link 2. Display the login page with login
Section Purpose
Use Case Name Create Account
Identifier UC2
Actor Administrator
Description Creating accounts for the user.
Goal To create account to the user in the system.
Pre –condition Administrator should log in Admin page
Post-condition New account will be created.
Basic course of User action System response
action 1. The admin enters to the system create 2. The System Displays create
account page account page.
3. Open account creation Form.
Section Purpose
Use Case Name Update User Account
Identifier UC3
Actor Administrator
Description Allow the administrator to Update accounts.
Goal To change user account in the system.
Pre-condition Administrator should log in to Admin page
Post-condition The account will be Updated.
Basic course of User action System response
action 1 The administrator enters Update User 2 The system displays the Update
Accounts button Account to form.
empty.
Section Purpose
Use Case Name Delete User Account
Identifier UC4
Actor Administrator
Description Allow the administrator to delete accounts.
Goal To delete user account from the system.
Pre-condition Administrator should log in to admin page.
Post-condition The account will be deleted.
Basic course of User action System response
action 1. The administrator clicks delete User 2 The system displays the Account
Accounts button page.
5 The system removes the account
3 The administrator selects the account from the list.
to be deleted.
4 The administrator presses delete
button
Section Purpose
Use Case Name Post information
Identifier UC5
Actor Administrator, Main Registrar, College Registrar, College Dean, Department
Head
Description Allows the Administrator, Main Registrar, College Registrar, College Dean and
Department Head to post news and information.
Goal To post news and information.
Pre-condition Administrator, College Dean and Department Head need to log in to the system
Post-condition The information is successfully posted.
Basic course of User action System response
action 1 User click post information 2 The system displays post information
button. page.
3 User click browse button. 4 The system displays the file location.
button.
Section Purpose
Use Case Name View orientation
Identifier UC6
Actor Student
Description Allows the student to view orientation of the departments.
Goal To View orientation.
Pre-condition Student need to log in to the system
Post-condition The information is successfully accessed.
Basic course of User action System response
action 1 User click view orientation 2 The system displays view orientation
button. page and department list
3 User select department to see 4 The system displays the orientation.
orientation.
Section Purpose
Use Case Name View date
Identifier UC7
Actor Student
Description Allows the student to view department selection date.
Goal To View date.
Pre-condition Student need to log in to the system
Post-condition The information is successfully accessed.
Basic course of User action System response
action 1, User click view date button. 2 The system displays view placement
date page and the placement date.
Section Purpose
Use Case Name Select Department
Identifier UC8
Actor Student
Description Allows the student to Select Department.
Goal To Select Department.
Pre-condition Student need to log in to the system
Post-condition The Department selection Successfully submitted .
Basic course of User action System response
action 1 User click Select Department 2 The system displays Department
button. Selection form.
3 User fills the form 5 The system displays Successfully
Section Purpose
Use Case Name View placement
Identifier UC9
Actor Administrator, Main Registrar, College Dean, College Registrar, Department
Head, Student
Description Allows the user to view department placement.
Goal To View placement.
Pre-condition user need to log in to the system
Post-condition The information is successfully accessed.
Basic course of User action System response
action 1 User click view placement button. 2 The system displays view placement
3 User enters id number to see page.
placement result. 4 The system searches and displays
department placement result.
Section Purpose
Use Case Name Add Department
Identifier UC10
Actor College Dean
Description The College Dean Add Department.
Goal To Add Department on the system.
Pre –condition College Dean should log in
Post-condition New Department will be created.
Basic course of User action System response
action
1. The College Dean enters to the 2. The System Displays Add
system and click on Add Department Department page.
button
3. Open Add Department Form.
4. The System Display Form.
5. Enter the appropriate information on
8. 7 Check the filled information.
the form.
6. Click on Save Department button 8 If the filled information is correct
the system creates the new
Department in the system database
and display successful message.
Alternative A: If the filled information is incorrect
course of action A1: the system displays error message
Section Purpose
Use Case Name Update Department
Identifier UC11
Actor College Dean
Description The College Dean Update Department.
Goal To Update Department on the system.
Pre –condition College Dean should log in
Post-condition Department will be Updated.
Basic course of User action System response
action 1. The College Dean enters to the 2. The System Displays Update
system and click on Update Department Department page and displays
button Department list.
3. The College Dean select Department.
Section Purpose
Use Case Name Delete Information
Identifier UC12
Actor Administrator, Main Registrar, College Dean, College Registrar, Department
Head
Description Allow the user to delete information.
Goal To delete information from the system.
Pre-condition user should log in
Post-condition The information will be deleted.
Basic course of User action System response
action 1. The user enters delete Information 2 The system displays the delete
button information page.
Section Purpose
Use Case Name Distribute list
Identifier UC13
Actor Main Registrar
Description Allows the Main Registrar to send student list to the colleges.
Flow of event
The user run the system and opens the home page and user clicks the login link. Then the
system displays a login form that accepts username and password from the user. The user
enters his/her username and password and user clicks on login button. The System must
validate user name and password, matches the username, password and roll from the
database and matches it with the password. After all, if the entry is correct, system take
the user to his/her page. otherwise the system will display an error message.
Flow of Event
The Administrator logs in to the system using his respective accounts and The Administrator
clicks on the Create Account button. Then The system displays the Create account form. The
administrator fills in the details of the new user and submits. The system checks the information filled and
acknowledges. Finally, the account will be created.
Object models describe the system in terms of object classes and their associations, with
common attributes and the services (operations) provided by each object. Visualizes the elements
in a software application in terms of object. It has several major functions in developing a system
like faster development of software, Reduce development risk reduction and reusability.
4.2.1. Class Diagram
We used class diagram to describe the structure of a system by showing the system's classes,
their attributes, operations (methods), and the relationships among objects.
Please fill this space
We are going to use sequence diagrams, and activity diagrams only from the dynamic parts of
UML diagrams.