WELCOME TO THE PRESENTATION OF OUR FINAL PROJECT!.

WELCOME TO WELCOME TO THE THE

PRESENTATION PRESENTATION OF OUROF OUR

FINAL PROJECT!FINAL PROJECT!

DEC REGISTRAR OFFICEDATABDEC REGISTRAR OFFICEDATABASE SYSTEMASE SYSTEM

Developed By:Developed By:

• Hailemariam Abera RDEG/037/95Hailemariam Abera RDEG/037/95• Markos Borena RDEG/040/95 Markos Borena RDEG/040/95 • Yeshimebet Hagos RDEG/074/97Yeshimebet Hagos RDEG/074/97• Yirgalem Hailu RDEG/084/95Yirgalem Hailu RDEG/084/95

In Fulfillment for the Award of Bachelor of Technology in In Fulfillment for the Award of Bachelor of Technology in Computer ScienceComputer Science

Under the guidance of:Under the guidance of:• Kalechristos Abebe(2nd Cpl)Kalechristos Abebe(2nd Cpl)

DEFENCE UNIVERSITY COLLEGEDEFENCE UNIVERSITY COLLEGE COLLEGE OF ENGINNERINGCOLLEGE OF ENGINNERING

October 2009October 2009

1. INTRODUCTION1. INTRODUCTION

1.1. Back Ground1.1. Back Ground Defence Engineering College shall normally Defence Engineering College shall normally

operate on a two-semester basis. operate on a two-semester basis. The main function of the registrar office is The main function of the registrar office is

To keep records or registers for all students. To keep records or registers for all students.

To manage all the activities being processed To manage all the activities being processed in the registrar office in each semester, in the registrar office in each semester, manually, is a tough work and mostly prone to manually, is a tough work and mostly prone to errors. errors.

Thus, our main objective is to help the registrar Thus, our main objective is to help the registrar office by converting the former system into office by converting the former system into automated ones.automated ones.

1.2.1.2. Statement of the ProblemStatement of the Problem

In response to our motive to analyze the In response to our motive to analyze the registrar system practices, this project will registrar system practices, this project will answer the following questions:answer the following questions:

How the system was being performed?How the system was being performed? What difficulties or problems were observed?What difficulties or problems were observed? How to reveal all the problem and former How to reveal all the problem and former

system?system? What makes our project effective?What makes our project effective?

1.3.1.3. Purpose of the SystemPurpose of the System The new system provides handling and The new system provides handling and

registering of student records in an efficient and registering of student records in an efficient and effective manner.effective manner.

Computerizing the system basically has Computerizing the system basically has positive impact in: positive impact in:

time consumption, time consumption, resource and material utilization and resource and material utilization and error minimizationerror minimization..

1.4. Objectives of the Project1.4. Objectives of the Project1.4.1. 1.4.1. General ObjectiveGeneral Objective

Analyzing the existing system and replacing it Analyzing the existing system and replacing it with an automated system.with an automated system.

1.4.2. 1.4.2. Specific ObjectivesSpecific Objectives Obtain understanding about the existing Obtain understanding about the existing

information system.information system. Identify potential users and their information Identify potential users and their information

needs.needs. Increase profitability by improving controlling Increase profitability by improving controlling

system of the registrar.system of the registrar. Convert the manual system to an automated one.Convert the manual system to an automated one.

1.5.1.5. MethodologyMethodology

A methodology is a formalized approach to A methodology is a formalized approach to implementing the system development life implementing the system development life cycle (SDLC). cycle (SDLC).

In this project we use In this project we use object-oriented system analysis and design methodologies.

The most advantage of object-oriented The most advantage of object-oriented system analysis is that; system analysis is that; it is simple for representation of real world object it is simple for representation of real world object

and it is flexible. and it is flexible.

Fact Finding MethodsFact Finding Methods InterviewInterview QuestionerQuestioner ObservationObservation Document AnalysisDocument Analysis

1.6.1.6. Scope of the ProjectScope of the Project The scope of this project is focused or limited The scope of this project is focused or limited

to the registrar office activities.to the registrar office activities.

2. REQUIREMENT SPECIFICATION2. REQUIREMENT SPECIFICATION Is to cover analysis of existing activities in registrar Is to cover analysis of existing activities in registrar

(work flow) and its boundary in detail.(work flow) and its boundary in detail.

2.1. 2.1. Business System Analysis of registrarBusiness System Analysis of registrar The business area analysis will enable the team to The business area analysis will enable the team to

investigate the business in which the software we will investigate the business in which the software we will develop and operate. develop and operate.

2.2. 2.2. Current SystemCurrent System One of the reasons for studying and documenting the One of the reasons for studying and documenting the

existing system is that: existing system is that: it will be helpful for understanding of current business with its it will be helpful for understanding of current business with its

problems and requirements built in.problems and requirements built in.

2.3. 2.3. Proposed SystemProposed System2.3.1. 2.3.1. Overview:Overview:

The new system will introduce simple, easy and The new system will introduce simple, easy and efficient method of the database system. efficient method of the database system.

2.3.2. 2.3.2. Requirement DefinitionRequirement Definition The important goal of requirement modeling is The important goal of requirement modeling is

to come to an understanding of the business to come to an understanding of the business problem.problem.

3. OBJECT ORIENTED ANALYSIS3. OBJECT ORIENTED ANALYSISAnalysis is a process of separating a Analysis is a process of separating a

whole into its component parts. whole into its component parts. The goal of analysis is:The goal of analysis is:

To understand the problem or problems To understand the problem or problems To prompt relevant questions To prompt relevant questions To provide a basis for answering To provide a basis for answering

questions questions To decide what the system should do.To decide what the system should do.To decide what the system should not do.To decide what the system should not do.etc..etc..

3.1. System Models3.1. System Models System modeling abstracts the overall system System modeling abstracts the overall system

under consideration.under consideration. Hence, we are trying to present the Hence, we are trying to present the

actor, , use case,use case, scenarios, scenarios, sequence diagram and also sequence diagram and also the class diagram of the proposed system.the class diagram of the proposed system.

3.2. Actor’s Identification3.2. Actor’s Identification An actor represents anything or anyone that interfaces with An actor represents anything or anyone that interfaces with

the system.the system.

3.3. Use Case Definition3.3. Use Case Definition A use case describes a sequence of actions that provides a A use case describes a sequence of actions that provides a

measurable value to an actor. measurable value to an actor.

3.3.1. 3.3.1. List of Use CasesList of Use CasesRegister student Register student Fill in semester grade Fill in semester grade Generate ReportsGenerate ReportsPrepare student copyPrepare student copyPrepare grade reportPrepare grade report

3.4. Scenarios3.4. Scenarios It is “a narrative description of what people do and It is “a narrative description of what people do and

experience as they try to make use of computer experience as they try to make use of computer system and application”. system and application”.

We described the scenario by listing the main We described the scenario by listing the main activities that is carried out in the system.activities that is carried out in the system.

Scenario name: - Scenario name: - Register StudentRegister Student Participating actor instance: Markos (Registrar Clerk)Participating actor instance: Markos (Registrar Clerk) Pre Condition:Pre Condition:

Markos wants to register students.Markos wants to register students. Markos login to the system. [alternative flow of event:[RLE] ]Markos login to the system. [alternative flow of event:[RLE] ] System displays the main menu.System displays the main menu. Markos selects Register Students Menu.Markos selects Register Students Menu. System displays formats to register students menu.System displays formats to register students menu. Markos enters to the system Student details.[RFE] Markos enters to the system Student details.[RFE] The system updates the database.The system updates the database.

Post Condition: Post Condition:

Student Registered.Student Registered. Alternative Flow of Event:Alternative Flow of Event:

RLERLE Markos provides wrong login information and the Markos provides wrong login information and the

system notifies Timer to re-enter login information for system notifies Timer to re-enter login information for 3 times.3 times.

RFERFE Markos provided wrong entry data and the system Markos provided wrong entry data and the system

notifies Timer to re-enter data. End of register Good notifies Timer to re-enter data. End of register Good Receiving Notes.Receiving Notes.

3.5.3.5. Conceptual DiagramsConceptual Diagrams 3.5.1. Class Diagram3.5.1. Class Diagram Class modeling is the main stage of objectClass modeling is the main stage of object

oriented analyses and design.oriented analyses and design.

3.5.2.3.5.2. Sequence DiagramSequence Diagram Sequence diagram is used to model the logic of Sequence diagram is used to model the logic of

usage scenarios.usage scenarios. The following sequential diagrams are stated The following sequential diagrams are stated

for each use case to help the user to for each use case to help the user to understand the elements clearly: understand the elements clearly:

4. OBJECT OREINTED DESIGN4. OBJECT OREINTED DESIGN

This section describes This section describes design goals of the project, design goals of the project, subsystem decomposition,subsystem decomposition, hardware or software platforms on which hardware or software platforms on which

the system will run, the system will run, the persistent data management, the persistent data management, access control, access control, control flow mechanisms, andcontrol flow mechanisms, and boundary conditions. boundary conditions.

4.14.1.. Purpose of the system We have selected strategies for building the system, We have selected strategies for building the system,

such as,such as, hardware/software platform on which the system will hardware/software platform on which the system will

run, run, the persistent data management strategy, the persistent data management strategy, the global control flow, the global control flow, the access control policy, and the handling of boundary the access control policy, and the handling of boundary

conditions.conditions.

The result of this design is a The result of this design is a modelmodel that includes that includes a clear description of each of these strategies, a clear description of each of these strategies, subsystem decomposition, and subsystem decomposition, and a deployment diagram representing the a deployment diagram representing the

software/hardware mapping of the system.software/hardware mapping of the system.

4.2. Design Goals The design goals are explained as follows:The design goals are explained as follows: Performance Criteria

describes the speed and space requirements of describes the speed and space requirements of our system.our system.

Response time: - : - once the Registrar System is once the Registrar System is started all requests should be responded.started all requests should be responded.

Memory: -: - not less than 120 MB of memory is not less than 120 MB of memory is required to run the system. required to run the system.

Dependability CriteriaDependability Criteria Security: - : - Registrar System should be secured.Registrar System should be secured.

Maintenance CriteriaMaintenance Criteria Extensibility: - : - As we are using Object Oriented Design, it is As we are using Object Oriented Design, it is

possible to add new functionality or new classes at any stage of possible to add new functionality or new classes at any stage of developmentdevelopment..

Modifiability: - : - If it is needed to change the functionality of If it is needed to change the functionality of the system, it should be accomplished without the need of rewriting the system, it should be accomplished without the need of rewriting the whole system. the whole system.

Readability:- :- The code has to be documented well so that it The code has to be documented well so that it will be easily understandable in time of maintenance.will be easily understandable in time of maintenance.

End User CriteriaEnd User Criteria Usability:- :- There will be a help menu for users of the system if There will be a help menu for users of the system if

they come across some difficultiesthey come across some difficulties. .

4.3. Proposed Software Architecture4.3. Proposed Software Architecture The proposed software architecture is a repository The proposed software architecture is a repository

architecture where subsystems access and modify architecture where subsystems access and modify data from a single data structure. data from a single data structure.

Subsystem DecompositionSubsystem Decomposition

Login This subsystem checks whether the user is valid or not. This subsystem checks whether the user is valid or not.

RegistrationThe Registration subsystem consists of functionalities of The Registration subsystem consists of functionalities of

registering students registering students

Prepare ReportThe Report subsystem consist all functionalities of the system The Report subsystem consist all functionalities of the system

that produce report concerning the students . that produce report concerning the students .

Data ManagementThe Data Management subsystem connects the overall system The Data Management subsystem connects the overall system

to the database and serves as a facilitator between them. to the database and serves as a facilitator between them.

4.4. Hardware/software Mapping4.4. Hardware/software Mapping

The system is going to be implemented on a The system is going to be implemented on a server having greater than 2 GHz of CPU server having greater than 2 GHz of CPU speed.speed.

The hard disc capacity is greater than 40 GB The hard disc capacity is greater than 40 GB which is enough to handle the data of the which is enough to handle the data of the registrar, and registrar, and

the memory is 256 MB in capacity. the memory is 256 MB in capacity.

4.5.4.5. Access Control and SecurityAccess Control and Security

During system design, we modeled access During system design, we modeled access by examining the object model and by examining the object model and determining which objects are shared determining which objects are shared among actors, and by defining how actors among actors, and by defining how actors can control access.can control access.

The access control is regulated by the user The access control is regulated by the user Administrator which has an unbounded Administrator which has an unbounded access to the SYSTEM. access to the SYSTEM.

Every user of the SYSTEM will have Every user of the SYSTEM will have username and password with different username and password with different privileges given by the user Administrator. privileges given by the user Administrator.

4.6. Boundary Conditions4.6. Boundary Conditions System Star

The starting condition of the system is when the user double The starting condition of the system is when the user double clicks the icon of the SYSTEM.clicks the icon of the SYSTEM.

Initialization Initialization will happen when the user tries to Initialization will happen when the user tries to

execute one of the system’s classes.execute one of the system’s classes. Shutdown i. When the session expires without the user doing i. When the session expires without the user doing

any action on the system. any action on the system. ii. When the user selects the Exist Command which is ii. When the user selects the Exist Command which is the appropriate way to shut down the system on the the appropriate way to shut down the system on the user’s end.user’s end.

Exception Handling Exception handling is the mechanism by whichException handling is the mechanism by which

the treats an exception.the treats an exception.

4.7. 4.7. Conclusion The developer team strongly believes that, this The developer team strongly believes that, this

project has paved a way towards the project has paved a way towards the understanding object oriented analysis and understanding object oriented analysis and design. design.

As it is the one the motivations behind project As it is the one the motivations behind project work, we have tried our best to study new work, we have tried our best to study new system development techniques.system development techniques.

Due to the limitation of time, we can not Due to the limitation of time, we can not accomplish all what we intend to do.accomplish all what we intend to do.