Ambo University

Institute of Technology
Department of Computer Science

OES

Online Examination for

Ambo university
 CHAPTER FIVE
System DesignChapter
Using Five
Object-
Oriented Paradigm
 Outline
 Overview of Phase I
Design modeling Class Diagram
Class Diagram
Deployment Diagram
Persistence Modeling
State chart
User interfaces
Testing
 Review of phase one (I)
Chapter one: Introduction
Chapter two: current system.
Chapter three: proposed system.
Chapter four: system modeling using OO (object oriented)
paradigm.
 
Review of phase Two(II)
Chapter 5: Object-oriented design.
Chapter 6: System implementation.
 Class modeling

 Is design level
 introduces changes to analysis class model
 It focuses on the solution domain
 Design modeling Class Diagram

Three contents of Class:

 The name of the class.
 The attributes of the class.

 The operation of the class.

CLASS DIAGRAM USER
Manages -Name : string
-IDNo : string
* -password : string
1 -username : string
Member of * -department : string
Admnistrator +Create Acct()
-Name : string +Delete Acct()
-ID : int +Change Acct()
-username : string
1 -password : string
+Update Admin Acct() Contains
+Delete Admin Acct()

1
Manages * *
*
E_Committee Student
* 1 Instructor +Course : string
+Course : string -
*
Faculty 1 *
-Faculty_id : string *
-Faculty_name : string 1 * *
+Add_Faculty() 1 1
+Edit_Faculty() manages
+Delete_Faculty() Department

Takes
-Deptno : string
-Dept_Name : string
1 Has *
Check
-Faculty : string *
* +Add_Dept()
+Edit_Dept() Exam
+Delete_Dept() *
-ExamNo : int
-ExamType : string
1 * -Question : string
* -Course : string
Has +Add_Exam() See
Course +Edit_Exam()
Has +Delete_Exam()
-CourseNo : int
+Check_Exam()
-CourseTitle : string
-Credit_hr : int 1 *
+Add_Course()
* +Edit_Course() Calculates
+Delete_Course() *
* +Take_Course()
Result
See
-Result_Id
-Total *
-Courseno
* -StudentID
+See_Result()
+Calculate()
 Deployment Diagram
shows physical view of system
takes software into real world
 shows how software gets assigned to hardware and how
communicates.
Client Machine

:Chrome TCP/IP
Web Server Admin

:E xp l o r e r
:XAMPP

:Mozilla

PHP

Central Data Base

:MYSQL
 Architecture of the system is client server.

Clients are responsible for:-

Receiving inputs from user
Checking range of performance
Server responsible for:-
Transaction performance
Guaranteeing the integrity of data.
Putting backup of database
Persistence Modeling

It describes the persistent data aspect of

software system.
 State chart
 Is used to describe the behavior of an individual object
 Transition is used as a progression from one state to another.
 
open

Home Page opened

invalid
Enter account and role, press login

Authenticate user account and role

Valid

press logout
Page of user Home Page

Press Close

State chart Diagram of user login

State chart Diagram of user management on admin page

Select User

User Management Page

create,edit,delete account and press ok

invalid

Authenticate account

Valid

press logout
useraccount affected Home Page

Press Close
State chart Diagram of exam management on instructor page

Click Exam menu

Exam Management Page

Select Department and course

invalid

Authenticate Selection
Valid

Question area displayed

Add question and answer,submit

Question added
State chart Diagram of exam management on Exam Committee page

Click Exam menu

Exam Checking Page

Select Department and course invalid

Authenticate Selection
Valid

Question Page displayed

Read question and check, comment

Question Checked
State chart Diagram of exam page for student

Click Exam menu

Exam Page Displayed

Select Department and course

invalid

Authenticate Selection
Valid

Question Page displayed

Take question and submit answer

Question added and closed

State chart Diagram of result page for student and instructor

Click Result Menu

Result Page Displayed

Select Department and course

invalid

Authenticate Selection

Valid

Respective Result displayed

 User interfaces

User interface design is the specification of the

interaction between the system users and a system.
 Navigation mechanism is part of user interface that
takes the user form one part of the system to the other user
system.
 Input design is about designing a form and its controls
for GUI system.
 Output design is about designing reports like detailed,
summarized,and etc.
Home Page of the System
Home Page for admin of the System
Faculty Management Page of the System
Schedule adding page of the system
Exam adding page of the system
 Chapter Six

System Implementation and Testing

 System Conversion

 Parallel Conversion
 Channel Conversion
 Straight Conversion

Testing Techniques Methodologies

Unit testing
System testing
Volume testing
 
Testing User Interface
Admin page to add user to the system (missing Values) testing:
Admin page to add user to the system (correct value) testing:
 U!
YO
N K
HA
T