Table of Contents

Abbreviation ......................................................................................................................................
Summary............................................................................................................................................
CHAPTER ONE ..............................................................................................................................
1.1 Introduction.............................................................................................................................
1.2 Background of the organization..............................................................................................
1.3 Statement of the problem........................................................................................................
1.4 Objective of the project...........................................................................................................
1.4.1 General objective .............................................................................................................
1.4.2 Specific objectives.........................................................................................................
1.5 Scope of the project ................................................................................................................
1.6 Significance of the project ......................................................................................................
1.6.1 Target beneficiaries of the system ...................................................................................
1.7. Methodology of the project....................................................................................................
1.7.1 Data Collection Methodology.....................................................................................
1.7.2. Software process model ......................................................................................................
1.7.2.1 System Analysis and Design (Approach)................................................................
1.7.3. Tools and Techniques........................................................................................................
1.8. Limitation of the project ........................................................................................................
1.9. Risks and Contingencies........................................................................................................
1.10 Assumptions and Constraints................................................................................................
1.11 Scheduling.............................................................................................................................
CHAPTER TWO .............................................................................................................................
2.1 Existing System
2.1.1 Players in the existing system..............................................................................................
2.1.2. Functions/activities in the existing system .........................................................................
2.1.3 Business rules.......................................................................................................................
2.1.4 Report Generated in the Existing System ........................................................................
2.1.5 Bottlenecks of the existing system...................................................................................
2.1.5.1 Performance (Response time) ..............................................................................
2.1.5.2 Input (Inaccurate/redundant/flexible) and Output ...............................................
2.1.5.3 Access Control and Security................................................................................
2.1.5.4 Efficiency.............................................................................................................
2.2 Proposed System: (solution for the new system) ....................................................................
2.3 Feasibility Analysis..................................................................................................................
2.3.1 Operational Feasibility: .....................................................................................................
2.3.2 Technical Feasibility.........................................................................................................
2.3.3 Economic Feasibility ........................................................................................................
2.3.4 Political Feasibility ...........................................................................................................
2.3.5 Schedule & Legal Feasibility............................................................................................
2.4 Requirements of the proposed system ....................................................................................
2.4.1 Functional Requirement................................................................................................
2.4.2 Non Functional Requirement.......................................................................................
2.5. Hardware and Software Requirement.........................................................................................
2.5.1 Hardware Interfaces.........................................................................................................
2.5.2 Software Interfaces ..........................................................................................................
2.5.3 Security and Access Permissions Plan.............................................................................
 2.6 Cost budgeting ............................................................................................................................
CHAPTER THREE.........................................................................................................................
System Analysis and Modeling .......................................................................................................
3.1 Introduction.............................................................................................................................
3.2. System Requirement Specification (SRS) .............................................................................
3.3 Product Functions ...................................................................................................................
3.4 User Characteristics................................................................................................................
3.5 General Constraints.................................................................................................................
3.5.1. Communication Interface................................................................................................
3.6 Use Cases................................................................................................................................
3.6.1 Actors...............................................................................................................................
3.6.2. Use-case Diagram ...........................................................................................................
3.6.3 Description of Use Case Diagram....................................................................................
3.8. Object Diagram......................................................................................................................
3.8.1. Class Diagram.................................................................................................................
3.8.1.1. Class Diagram description ...........................................................................................
3.9. Sequence Diagram……………………………………………………………………….
3.10. Activity Diagram……………………………………………………………………….
3.11. State Chart Diagram…………………………………………………………………….
3.12 Analysis Models....................................................................................................................
3.12.1. Sequence Diagrams.......................................................................................................
3.12.2 Activity Diagrams..........................................................................................................
Reference ..........................................................................................................................................
 CHAPTER ONE
1.2. Intoduction
Student Management System is software which is helpful for students as well as the school authorities. In
the current system all the activities are done manually. It is very time consuming and costly.
Our Student Management System deals with the various activities related to the students.
There are mainly 3 modules in this software
 Administrator Module
 Faculty Module
 Student Module.
In the Software we can register as a faculty as well as a student for every student the authentication code
and the roll no is provided by the head of the department faculty and for the registration of a faculty the
Registration ID and the authentication code is provided by the administrator the institute.
In this project an admin can manage the faculty and take decision about the students like deletion of any
student admin is authorized to create the token for the registration of the faculty as same as a faculty is
authorized for creating token for the registration of a student.
1.2 Background
Ambo university is established in 1939 E.C at western Shewa .It starts giving different service to
students. .Now a days the service gives access around 10,000 students, 20 blocks and 32 dormitories.
Manual system creates complex & complicated system when entering and clearing student to university.
The problems that are identified are discussed on the next tittles.
1.3 Statement of the problem
This Student management system currently uses manual system which creates the following major
problems.
 It is difficult to find students result one by one.
 Data recording system is not centralized or not in the modern system which is difficult to
search.
 It creates wastages of time
 Data redundancy &lose:-as mentioned above ,the manual searching system of a required
information is very time consuming and sometimes may lead to inability to find the
information that already exists . This results in storing the same information again and again.
And also the data may disappear because of some real world problems since it is stored on
papers manually.
 Space reservation problems: - the manual system is using papers for storing information. As the
number of users is increasing and information is stored redundantly, the space reserved for
storing this information is more than required.
 Security:-since students grade and exam result was kept manually with paper it may lost.

 Lack of online registration system

 The office consumes manpower, time and resources because of manual service of
student registration system.
 students also consume time and resources for registration
 Lack of organized data for screening student’s service documents and relevant information.
 Inaccuracy of information (loss of data)
 Reports are not processed on time.
  Redundant flow of student information.
1.3 Objective of the Projects
1.3.1 General objectives
The main objective of this project is to convert or change the manual system to computerized system to
solve the above stated problems.
1.3.2 Specific objectives
The system should provide the following:
 Enables students to view their exam result and other services in easiest way.
 Make the system automatic.
 Minimize human work effort.
 Efficient use of time.
 Fast data processing.
 Less cost.
 Designing the system architecture of the system
 Designing friendly user interface
 Designing database to the system that can hold all the information
 To improve the communication between the student with the registrar.
 Ensures students information security.

 Assigning department and registering for fresh students

 Enabling students to view their grade and CGPAsecretly.

 Enabling all department heads to send students mark to registrar.
 Accelerating user requirement and benefits.
 Supplies timely information for the students.
 Minimizing data redundancy.
 Minimizing loose of data.
 Secured means of storing files.
 Improved planning and management.

1.5 Scope of the project

 The scope of our project is providing the access for information about student management system
to students in AmboU. The scope of the project is that every student will know their user name
and password to see their grade and other details.

 Allowing the AmboU student to use the online system anywhere they are.

 Our system used for undergraduate students.

 The System contains all the recorded information that can be handled by registrar office.
  For new students who access the system for the first time, the DMS allow privilege to access by
their Name and Registration number.

1.6 Significance of the project

This project has great significance in different direction as listed below:-

For user:-
 To get timely information.
 To save their time and money.
 To access accurate and fast information
For HUR office:-
 To easily retrieve user information.

 To improve management system

 To solve problem of manual work.

 To save time and money and manpower
For developers
 Requirement for the partial fulfillment of the Bachelor degree in computer science.

 To be familiar on solving real life problems.

 To expand knowledge gained from lessons.

1.6.1 Target beneficiaries of the system

This system is vital for students and registrar office of Ambo university.

This project provides many benefits for:-

 Students:-by providing fast access to the view grade system by reducing time,like waiting in the
queue and going to different offices. The students access the system anytime when they need to
check their grade and other services.
 Instructor:-it will save the the time for instructors .
 University:-in manual there is loss of materials like paper, pen which is cost and more man power,
the system reduces loss of costly materials and man power.
 Officers:-The project reduces the time and work load for officers for serving the students and
teachers who need services.
 Developers of the project:-It increases our knowledge and we get mental satisfaction from the
project we developed.
 1.7. Methodology of the project

1.7.1 Data Collection Methodology

Before implementation and design requirement analysis is the first step. So, this data collection
method is a precondition for requirement analysis. Knowing this fact we have collected
information from the existing system and used it for proposed system. There are many methods
used to collect data. Among them we have used two methods:

1. Interview
2. Observation
Interview:

We have used this method to gather information by asking the head and employers of the
registrar some basic questions.

Some questions that we asked the registrar are:

How registration process is going on?

During registration time what are there any problems?
If there are what are they?
What requirements are needed for the process?
Observation:

This is by observing:

Written documents and procedural manuals

Registration form,
Add and drop form
Grade recording mechanism and
Other activities.
Withdrawal form

1.7.2. Software process model

1.7.2.1 System Analysis and Design (Approach)

1.7.3. Tools and Techniques

1.8. Limitation of the project

The project we are developing has limitation on fields like:

 Our system works when a server control services is available.

  It works for the one who understand English language (we have not used other language).

 It serves only students who are Undergraduates in AmboU.

 Our system does not serve the students who are not able to see (blind people).

 Our system doesn’t give a service where there are no internet access.

1.9. Risks and Contingencies

1.10 Assumptions and Constraints

1.11 Scheduling

CHAPTER TWO
2.1 Existing System
Suppose the current student management system of the university is a manual System. This makes the
system so tedious and time consuming. This process takes some days to be completed and possess a lot of
stress to all the users and workers who provide registration and other service system. In the manual
system, the grade and transcript of all the students are documented in a file cabinet. Each time it is
needed, a search operation is conducted on the file cabinets to locate a particular students document.
2.1.1 Players in the existing system
Instructor
 He/she is responsible for checking student exam paper in proper way and give grade
 After he /she gives the grade then report the grade to the registrar in manual (paper based).

Registrar office
 It is responsible to register new students and promote regular students to the next batch based
on some criteria.
 Store students grade and other information in manual way.

Students
 They are end users who get service from university.
 They check their results from their instructor before it reported to the registrar.\

2.1.2. Functions/activities in the existing system

The main function of the existing system is:-
 Register student who assigned to this university in manual way.
 Store student’s information in document form.

2.1.3 Business rules

The main business rules or principles of the existing system are:-
  Anyone who registered must be the member of the university.

 Every student must register at the beginning of each semester.

 Students and teachers must fulfill their prerequisites before he/she get registration service.
 Students must know their username and password to access the system.
 Teachers of the university must submit the grade to the registrar.
2.1.4 Report Generated in the Existing System

The forms generated in the existing system are in the forms of forms and files.
Forms: - are the reports generated in the existing system that contains all information filled by the
University students and Teachers.
Files:-are the collection of information about the students grade and other detail documentation.
These all reports kept in offices of the university to store information about the University students.
2.7 Bottlenecks of the Existing System
Due to the manual means of the management system a lot of problem are encountered in order to keeping
information about student’s grade.
2.7.1 Performance
The performance of existing system is less, because teachers show all the student their grade one by one.
2.7.2 Input (Inaccurate/Redundant/Flexible) and Output (Inaccurate)
During filling of the registration form the user may fill inaccurate or incorrect information and may miss
necessary information this show the system is inaccurate. And the system is not flexible because if user
wants to erase the form he/she must only change another form.
2.7.3 Security and Control
Since all the student document form in the manual system is stored manually, the security that the system
provides is not good. The system shouldn’t provide sufficient protection for accessing and manipulation of
the view grade and registration form in the system. Therefore, it is not easily protected and control. b/c
grade and other student related information may be corrupted.
2.7.4 Efficiency
Due to the manual activities of the system wastage of resources are occurred like stationary materials, man
power, time etc. This makes the current system is inefficient while utilizing resources.
2.2. Proposed System: (solution for the new system)

After observing and identifying the current (existing) system, it is mandatory to develop
proposed system. This proposed system should solve the problem of the existing system and
must be advanced. So, the key solution to avoid all the problems mentioned previously is to find
 a unified way to solve the problems mentioned earlier. The only unified way is by
computerization. The various entities that interact with the system are identified. In addition to
this, the work flows, functional, non-functional requirement, activities performed by man and by
machine and procedure within the system are being examined to understand and visualize the
system.

2.3 Feasibility Analysis

Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we
undertake. Feasibility is the study of impact, which happens in the organization by the development
of a system. The impact can be either positive or negative. When the positives nominate the
negatives, then the system is considered feasible. Here the feasibility study can be performed in
four ways such as operational feasibility technical feasibility , Economical Feasibility and Political
feasibility.

2.3.1 Operational Feasibility

The project is easy to maintain and use. So there is no need of special training for the maintenance staff.
There will be no resistance from the user side.

2.3.2 Technical Feasibility

Points in concern with the technical feasibility of our proposed system-

 The technology i.e. hardware and software which we have used is normally available. It is easy
to implement.

 Our system is capable for up gradation account to users demand within the budget.

 Since our system proposes all the necessary technical resources so it is technically feasible.

 The system is easy to maintain and very attractive for user.

We can strongly says that it is technically feasible, since there will not be much difficulty in getting
required resources for the development and maintaining the system as well. All the resources needed
 for the development of the software as well as the maintenance of the same is available in the
organization here we are utilizing the resources which are available already.

2.3.3 Economic Feasibility

Development of this application is highly economically feasible .The organization needed not spend
much money for the development of the system already available. The only thing is to be done is
making an environment for the development with an effective supervision. If we are doing so, we can
attain the maximum usability of the corresponding resources .Even after the development, the
organization will not be in condition to invest more in the organization .Therefore, the system is
economically feasible.

2.3.4 Behavioural/ Political Feasibility

The proposed system is behaviorally feasible and cannot cause any harm in the environments. The project
would be beneficial because it satisfies the need of the customer. The system will be developed to be user
friendly, needless training and improves the working environment. Our system is behaviorally feasible,
because the staff of AU was open minded towards the acceptance of this new system.

2.3.5 Schedule & Legal Feasibility

The proposed system can be implemented in an acceptable timeframe given below. Project manager is also
responsible for monitoring & controlling the project development based on the schedule shown below.

2.4 Requirements of the proposed system

2.4.1 Functional Requirement

The functional requirements of the system are to the implement the solution for finding the train details
and route information in the large existing rail system.

1. Input / Output:
The user selects the type of train and enter the source and destination codes with which finds
the trains details and route information.
2. Processing:
The information regarding train details are retrieved from the database.
 3. Storage Requirements:
The information will be retrieved from the database.
4. Control Requirements:
Alerts when any errors are there and when any of the field is not selected.
2.4.2.Non Functional Requirements

Speed and Performance

 The system should quickly display option for students as soon as the students enter their name
and id number.

Error Handling
When user makes some error:
 The system must have capacity for error handling.

 The system should display error message if the user input invalid character.

Response time
 The system connects to personal computer within minimum period of time.
 The users have to get services from the system rapidly.
 The system should meet what the user expects.

Robustness:
 The system should be tolerable of fault in case of SW and HW failure.

Availability:
 The system should available for further use while needed.
2.5. Hardware and Software Requirement

2.5.1 Hardware Interfaces

2.5.2 Software Interfaces
2.5.3 Security and Access Permissions Plan
 Our system is secured; means unauthorized body cannot access the system and system resources.
 The system shall permit the admin to manage user’s information.
 Since students can access the system by their unique username and password.
2.6 Cost budgeting

CHAPTER THREE
System Analysis and Modeling
3.1 Introduction
The project development in a team use an object oriented system development methodology. Because the
Object oriented system development approach gives easier and natural way to break down problems into
simple, small and manageable components so that it reduces the vague appearance of the big problem.
Moreover, it is predominately used and popular method in present software development trend.
The major activities described in this chapter are Constructing a use case model ,Documenting the use case
course of events, constructing sequence and activity diagram analysis level class diagram and user proto
type about the proposed system.
3.2. System Requirement Specification (SRS)
3.3 Product Functions
There are three different users who will be using this product:
 Administrator who can view and edit the details of any students & faculty.
 Faculty who can view and edit the details of students.
 Students who can view their details as well as they can edit their details.

3.4 User Characteristics

There are mainly three kinds of users for the product. The users include:
 Administrator
 Faculty
 Student.

3.5 General Constraints

Every user must be comfortable using computer.
All operations are in English so user must have basic knowledge of English.
3.5.1. Communication Interface
3.6 Use Cases
Essential use cases that the proposed system consists are:-

1) Login
2) Registration
3) Registration slip
4) Placement
5) Exam result
6) Send grade
7) Grade error
8) Application form
9) Registration report
10) Download course
 11) Upload files
12) Update news

3.6.1 Actors

The proposed system consists of three major actors for the accomplishment of the system.
These are:-
1) Students
2) Registrar
3) Department head

3.6.2. Use-case Diagram

Figure 2.1 Essential use case of proposed system
Use case and actor description

Login Use Case

Use case name Login

Use case identifier UC#1
Actor(s) Students, department head and registrar
Description Students, department head and registrar want to use the webpage
Precondition Students, department head and registrar should create account
Post condition Students, department head and registrar use the webpage

Basic course of Actions

1. Students, department head and registrar want to use the site

2. They have an account
3. They enter their user name, password and security key
4. Press login button
5. The entered fields are correct
6. They logged into the site
7. Use case ends

Alternate of courses of Action

Alternative course A: 2) If they have no an account
2.1) click create account button
2.2) fill all fields
2.3) get your security key
2.4) go to step 3
 Registration Use Case

Use case name Registration

Use case identifier UC#2
Actor(s) Students
Description Students register for course
Precondition The students have an account and security key to login
Post condition Student registration is success full.
Basic course of Actions

1. Students want to be registered for courses

2. Students login to the page
3. Fill all required field on the page
4. Students previous mark is above or equal to the passing mark
5. Registration is successful
6. Students get registration message
7. Use case ends

Alternate of courses of Action

Alternative course A: 3) If the students do not fill each fields correctly
3.1) Message (re fill the information) will be displayed.

3.2) Use case loops to itself

Alternative course B: 4) If students previous mark is less than passing mark
4.1) Use case ends.
 Registration slip Use Case

Use case name Registration slip

Use case identifier UC#3
Actor(s) Student
Description The registered students want to take registration slip
Precondition The student must be registered
Post condition Both of them get and print registration slip.
Basic course of Actions

1. Students want to get registration slip

2. Student registration is success
3. Print registration slip tag will appear
4. Students click on print button
5. Registration slip is printed
6. Use case ends

Alternate of courses of Action

Alternative course A: 3) If the students registration is not success
3.1) use case ends

Department placement Use Case

Use case name Placement

Use case identifier UC#4
Actor(s) Student and registrar
Description Every students are assigned to their department
Precondition The students should have entrance point
Post condition Every students with entrance point are assigned to their
department
 Basic course of Actions

1. Fresh students want to assign to their department

2. Students fill all their information
3. Students enter their entrance point
4. Student select each department orderly
5. Registrar enter number of students for each of departments
6. The system compare every students’ point and check their first choice
7. Students’ point and first choice is ok
8. Assign students to their department
9. Students click show me department button to see their department
10. Use case ends

Alternate of courses of Action

Alternative course A: 7) If the students’ point and first choice is not ok
7.1) the students’ point and second choice is ok
7.2) go to step 8
Alternative course B: 7.1) If the students’ point and second choice is not ok
7.1.1) the students’ point and third choice is ok
7.1.2) go to step 8
Alternative course C: 7.1.1) If the students’ point and third choice is not ok
7.1.1) assign department randomly
7.1.2) go to step 9
 Exam result Use Case

Use case name Exam result

Use case identifier UC#5
Actor(s) Student
Description Every students are able to see their exam result, grade and CGPA
Precondition The students should have to took exam
Post condition Every students can correct error if any
Basic course of Actions
1. Students want to see their exam result
2. They enter their ID No, course code and security key
3. They click show button
4. The entered values are correct
5. Display their exam result
6. Students print their result
7. Use case ends

Alternate of courses of Action

Alternative course A: 4) If entered values are not correct

4.1) error message will be displayed
4.2) go to step 2
 Grade error Use Case

Use case name Grade error

Use case identifier UC#6
Actor(s) Student and registrar
Description Every student is able to correct their result.
Precondition The students exam result has an error
Post condition Every students get the correct result

Basic course of Actions

1. Students want to correct their grade

2. They enter their ID No, course code and security key
3. The entered values are correct
4. Select course which has error and write their idea
5. They click send error button to registrar
6. Registrar see grade error message
7. Registrar check students result
8. Registrar found error
9. Correct error and update students result
10. Sent error correction message to students
11. Use case ends

Alternate of courses of Action

Alternative course A: 4) If entered values are not correct
4.1) error message will be displayed
4.2) go to step 2
Alternative course B: 7) If registrar not found error
7.1) send no error message to students
7.2) use case ends
 Application form Use Case

Use case name Application form

Use case identifier UC#7
Actor(s) Student
Description Students fill add, drop and withdrawal forms
Precondition The students face some problems
Post condition Students can continue their lesson

Basic course of Actions

1. Students want to fill application form

2. They enter their ID No and security key
3. They click show form button
4. The entered values are correct
5. Application form will be displayed
6. Students fill the application form
7. All application form fields are filled correctly
8. Filling application form is success
9. Use case ends

Alternate of courses of Action

Alternative course A: 4) If entered values are not correct
4.1) error message will be displayed
4.2) go to step 2
Alternative course B: 7) If all application form fields are not filled correctly
7.1) fill all fields error message will be displayed
7.2) go to step 6
 Download courses Use Case

Use case name Download courses

Use case identifier UC#8
Actor(s) Student, department head and registrar
Description Student, department head and registrar download courses that the
student registered for
Precondition The students is registered for courses
Post condition Student, department head and registrar can have the courses on
their hand

Basic course of Actions

1. Student, department head and registrar want to download course

2. Students were registered for courses
3. They enter their ID No and security key
4. They click on download link
5. The entered values are correct
6. They get the downloaded courses and print it
7. Use case ends

Alternate of courses of Action

Alternative course A: 2) If student was not registered for grade
2.1) go to step 7
Alternative course B: 5 ) If entered values are not correct
5.1) error message will be displayed
5.2) go to step 3
 Registration report Use Case

Use case name Registration report

Use case identifier UC#9
Actor(s) department head and registrar
Description department head and registrar able to see report when students
register
Precondition The students is registered for courses
Post condition Department head and registrar can identify who registered, how
many students registered

Basic course of Actions

1. Department head and registrar want to get registration report

2. Students were registered for courses
3. Message was sent to department head and registrar
4. Department head and registrar login
5. They see received message symbol on the message tab
6. They click the tab and see the message
7. Use case ends

Alternate of courses of Action

Alternative course A: 2) If student were not registered
2.1) use case ends
 Send grade Use Case

Use case name Send grade

Use case identifier UC#10
Actor(s) department head and registrar
Description department head send students’ grade to registrar for CGPA
calculation
Precondition Teachers have submit students’ grade to head of department
Post condition Department head and registrar use the calculated students’ CGPA

Basic course of Actions

1. Department head wants to gate students’ CGPA
2. The department head collected students’ grade
3. Department head send student’s grade to registrar
4. The system calculate CGPA
5. The registrar receive message for the calculated CGPA
6. Print the CGPA
7. The registrar sent the grade and CGPA back to department head
8. The department head receive message for the calculated CGPA from registrar
9. Print the CGPA
10. Use case ends
Alternate of courses of Action
Alternative course A: 2) If department head not collected students’ grade
2.1) department head try to collect students’ grade
2.2) go to step 3
 Upload files Use Case

Use case name Upload files

Use case identifier UC#11
Actor(s) Registrar
Description The registrar upload files and information for students and
department head
Precondition Registrar wants to distribute information for students and
department head
Post condition Department head and students read the uploaded and get
information

Basic course of Actions

1. Registrar wants to upload files

2. The registrar logged into the site
3. Select the post information tag
4. Select upload button
5. Write information on the text area
6. Click upload button
7. System upload information
8. Uploaded successfully message will be displayed
9. Use case ends

Alternate of courses of Action

Alternative course A: 2) If not logged into the website
2.1) use case end
 Update news Use Case

Use case name Update news

Use case identifier UC#12
Actor(s) Registrar
Description The registrar update news and post it for users
Precondition Registrar wants to distribute information for students and
department head
Post condition Department head and students read the uploaded and get
information

Basic course of Actions

1. Registrar wants to update news for users

2. The registrar logged into the site
3. Select the post information tag
4. Select update news button
5. Write information on the text area
6. Click update button
7. System update information
8. Uploaded successfully message will be displayed
9. Use case ends

Alternate of courses of Action

Alternative course A: 2) If not logged into the website
2.1) use case end

Fig 2.2 Class Diagram

 Online Registration System

1 1 1 1

* * * *

User Interface Account Administratoin Database Management Transaction System

-interfaceType -account -adminId -transaction
-secured -dbHandle -dbAccessKey +manageTransaction()
+getInterfaceType() +isValidAccount() +isValidAccount() +isValidTransaction()
+isSecuredInterface() +manageAccount() +manageAccount()
+accessDB()
+platformSupported() +accessDB() * *
* 1 * *
* *
Login Account Execute Order
-username -accountId -userId Cancel Order
-password -accountOwner -order -userId
-securitykey -accountInfo +isValidOrder() -order
+isnewUser() * +login() +updateOrderStatus() +iscancellable()
+isLoggedin() +getAccountInfo() +notifyUser() +cancelOrder()
+forgotPassword() +updateAccount() +notifyUser(
* * *
* *
*
Interface Component Student
-ok -fullName Department Head Registrar Office
-cancel -idNo -name -name
-other -age -idNo -idNo
+isOk() -sex -position
-classYear -position
+isCancel() -age
+isOther() -nationality -age
-sex
-state -sex
-phoneNo
-region -phoneNo
-email
-woreda -email
+login()
* -fax
-fucalty +sendGrade()
+prepareSlip() +login()
-depratment
-email +getReport() +getReport()
-phoneNo +uploadFiles()
+login() * +updateNews()
* +getCourses()
+register() +setplacement()
+fillForms()
+checkGradeError() 1
 2.3.3 Sequence Diagram

Student Registrar Registration Subsystem Database

FillApplication

Determine
Classification

Open Registration
Page

Enter Data
Check Duplication

Validated

Check Old Results

Validated

Calculation

Save Data

Confirm Save
Issue Registration
Print Report
Report

Fig 2.3 Sequence Diagram for Registration

Student Registrar System Database

Fill Form
Enter Stud No for departments

perform opreration
show students'
department

accepted
save student information

Confirm Save
registration report
show students' t
departmen

print

Fig 2.4 Department selection sequence Diagram

 System Databas
ee
login
check Account

Fig 2.5 Grade View sequence Diagram

validate
display grade view page
Id,securitykey & course code
check security
validate
Request search
grade
Displaye Grade
Displaye Grade
Print
Department Head Registrar System Database

Send Grade
Enter grade & cr.hrs

calculate
Display Result

validated
Save

Confirm Save
Report

Send CGPA

Print

Fig 2.6 Calculate CGPA sequence Diagram

Student Department Registrar System

grade error
message
check grade

send
corrected Enter grade
update
grade

Updated & saved

update CGPA

Updated & saved

Update Report
Updated Grade & CGPA
Updated Grade & CGPA

Print

Fig 2.7 Grade Error sequence Diagram

 [Date]
AMBO UNIVERSITY HACHALU HUNDESSA DEPARTMENT OF COMPUTER SCIENCE 2021 G.C 33