A Senior Project Documentation Submitted to Adama Science and

Technology University

In Partial Fulfillment of the Requirement for the

Degree of Bachelor of Science in Software Engineering

By

Computer S

School of Engineering, Department of Computing

Adama Science and Technology University, Adama, Ethiopia
January 2014
 ADAMA SCIENCE AND
TECHNOLOGY UNIVERSITY

SCHOOL OF ENGINEERING
DEPARTMENT OF COMPUTING
ASSIGNMENT FOR software engineering
NAME ID

SUBMITTED TO

SUBMISSION DATE: AUG/ 28/2014

 Chapter One

Introduction
1.1. Background

History of ASTU:-

Adama Science and Technology University (ASTU) was first established in 1993G.C as Nazareth Technical College
(NTC), offering degree and diploma level education in technology fields. Later, the institution was renamed as
Nazareth College of Technical Teacher Education (NCTTE), a self-explanatory label that describes what the institution
used to train back then: candidates who would become technical teachers for TVET colleges/Schools across the
country.

In 2003G.C, a new addition to NCTTE came about—introduction of business education. Nonetheless, the new entries
were solely meant for similar purposes: these graduates were also expected to help overcome the existing dearth of
educators in vocational institutions.

Although it is an institution with a history of only two decades, ASTU is known for its dynamic past. It has always
been responsive to the realization of national policies: training of technologists at its infant stage, and later shifting
to training of technical trainers, as well as business educators, to fill the gap in TVETs.

Following its inauguration in May 2006 as Adama University, the full-fledged university started opening other
academic programs in other areas—an extension to its original mission. However, it was not until it was nominated
by the Ministry of Education as Center of Excellence in Technology in 2008 that it opened various programs in
applied engineering and technology. For its realization, it became a university modeled after the German paradigm:
it not only became the only technical university in the nation, but also the only one led by a German professor.

Notwithstanding closure of some disciplines as per the new vision and mission, the ensuing three years saw
flourishing of graduate programs, of which some (like a few in the undergraduate program) were exceptional to our
university. The same period saw pioneering of the university in introducing PhD by Research and MA/MSC by
Research programs.

Before 2008, the university was stratified into faculties, and ASTU’s reach was limited to its only campus in Adama
town. The university has now extended its reach to Asella, where two of the total seven schools are located. The
faculties at the main campus include: School of Business, School of Engineering and Information Technologies,
School of Humanities and Law, School of Natural Sciences, and School of Educational Science and Technology
Teachers Education. On the other hand, the two schools in Asella are the School of Agriculture and School of Health
and Hospital.

In addition to its main concern (academics), ASTU is also host of research Institutes and enterprises. In the main
campus, apart from the Institute of Continuing and Distance Education (ICDE), there exist two others: the Further
Training Institute (better known as FTI) and Adama Institute of Sustainable Energy. The sister town where the two
schools are located, Asella, is also host to the Artificial Insemination Institute and Asella model Agricultural
Enterprise.

Following its renaming by the Council of Ministers as Adama Science and Technology University in May 2011, the
university has started working towards the attainment of becoming a center of excellence in science and technology,
thereby allowing for the realization of goals set in the Growth and Transformation Plan (GTP). To this end, a South
Korean has been appointed as President of the University. Currently, ASTU is setting up a Research Park, in
collaboration with stakeholders and other concerned bodies: one of a kind in the Ethiopian context. The university is
also venturing out to the wider community and is currently engaged in various joint undertakings.

Vision

ASTU aspires to be the first choice in Ethiopia and the premier center of excellence in applied science and
technology in Africa by 2030.

Mission

The mission of ASTU is to provide ethical and competent graduates in applied science and technology
through quality education, demand driven research and community service. ASTU also provides innovative
knowledge to support the socio-economic development of the nation.

Core Values

 Originality and Innovativeness

 Academic freedom and integrity

 Sense of belongingness and ownership

 Nurturing diversity

 Transparency and accountability

 Professional ethics

 Responsiveness

Our Motto
“We are Dedicated to Innovative Knowledge “

Registrar Office

This section administers, registers, documents and archives all phases and steps associated with study applications,
enrollment, issue of students identification badges, placement in dormitories, internships, enrollment termination,
registration of study achievement, preparation of attestations, record of marks and record of study achievements,
official graduation documents, student and graduation statistics, general student's guidance, internship support
service. School's internship commissioner, alumni tracking and the like.

The Registrar office provides advisory services for enrolled students, study applicants and freshmen. Advisory
services include social and psychological counseling.
The major responsibilities are:-

Provide leadership to plan, organize and manage all of the activities related to the records and Registration
Department, including serving as the official authorized keeper of the university's student records.
Hire, supervise and evaluates the Records, registration staff.
Organize and administer the records, registration and graduation functions, including transcript evaluations,
certification process in order to provide maximum services to students while ensuring efficient and effective
workflow.
Supervise the coordination, evaluation and certification of all graduation applications, while overseeing the
complete graduation process to include all elements of the rehearsal and ceremony.
Responsible for collecting, recording, maintaining and reporting of student records within the prepared guidelines
e.g., grades, registration data, transcripts, mid-term verification.
Provide leadership and develop appropriate recommendations for the implementation of related technology
application in support of enhanced services offered through Registration and Records.
Develop and administer the Departmental budget.
Problem solve the research, analysis and resolution of student disputes as they relate to records and registration
Collaborate with Administrators, Deans of Faculty, and counselors to facilitate and improve services to students,
including catalogue and registration/records policy questions.
This job description is not intended to be all inclusive and the employee will also perform other reasonable related
duties as assigned by the Head of Administration.
Participate in professional development activities and serve on university committees that support the goals and
objectives of the university.
Provide back-up for records and registration services, including registering students, issuing transcripts, answering
phones, scanning, reporting grades and working special events.
Plan and organize alumni tracking of graduates.

Curriculum Reform
Adama Science and Technology University (ASTU) is undergoing a far reaching transformation process towards a
model technical university for Ethiopia. This includes revision of the portfolio of programs and its continuous
improvement.

This page provides ASTU internal access to working documents.

Undergraduate Study Regulations for Engineering Programs PreRelease V0.7
Undergraduate Study Regulations for Engineering Programs PreRelease V0.8Undergraduate Study Regulations for
Engineering Programs PreRelease V0.9

Adama science and technology university registrar office uses the old fashion access and excel database
system almost old and semi –manual system that manly used access database more pepper and many
data recorder workers there are assigned for registration time. Current database system and student
registration time there are so many problems this are
Many data recorders, more peppers, a large numbers of student queue on registration time, it is easy to error
cored, it is difficult to manage a system

Our project solve the problems that we have mentioned before to developed new automation system and
to prove online student registration system

1.2. Project Overview

This project focuses on solving the problem of ASTU’s registration system to help their student
registration. This system provides an interactive and attractive way of student online registration using
web based automation. The system mainly includes student registration and select course, observe
student status, and easly manage student information.

1.3. Statement of the problem

Astu registrar office is currently facing various problems, such problems are very much related with the lack of
technological tools such as a well-designed information technology system for its major duty of student registration
as well as other related supporting activities.
We believe that our automation system can solve the problems that currently achieved, astu registrar office system
have many problems that come with the use of semi-manual system. These can be solved by automating the system.
The major problem of the existing system is:
  Security matters: When we talk about REGISTRAR system, the security must be in the first
place. The current system of ASTU REGISTRAR the student registered manually, it is easy to
breakthrough and it is a challenge to improvise it
• Consume of time : it takes more time to student registration. The students are fully consuming
more their time in the case of registration and also registrar workers most of them working manually
with paper registration.

 Managing and usage of papers and the probability of human error in the registration process is a
problem in in the current system, and needs more human power to accomplish the registration.

 It is too difficult modify information easily

1.4. Purpose of the project

The main purpose of this project is to develop computer based registrar system for ASTU, by changing
semi-manual student registration method into computerized system. The system allows the student can
access and online register themselves within on the web browser.

world is changing and changing every day dramatically through information technology. The use of
computer is affected our day to day activities because of information technology our world becomes like
one small village we call it globallaization.in our world all ideas without the support of information
technology it almost impossible to done. Different organization they need the acquirer of information
technology like business organization, university, college, hospitals, bank, individuals all are they need
the \acquire of it
Advantages:-
 Speed (fast service for customer)
 Accuracy and reliability
 Efficiency and effectiveness
 Minimizing routine work load
 Easily of handling data
 Minimize risk and errors

 Decrease wastage of recourse like paper…

 Increase the way of organizing data
 Providing better services
 Cost minimizing
 Providing online access for the student registration
 Minimize time by providing online registration
 1.5. Team composition
Project ASTU STUDENT ONLINE REGISTRATION
Title
No Name ID E-MAIL Responsibility
1 Addis endale Designing,
Prepared Team
by coordination
2 Henok meskele Analyzing
3 Misrak begashaw Analyzing
4 Tesfaye bigale Requirement
gathering
5 Engdasew hailu Requirement
gathering
Advisor

Table 1.1. Team composition

1.4.1. Team member’s activity and responsibility

The successful completion of the project requires the truly corporation of the team members. Each
team member has advantageous contribution in each phases of the project and responsible for the
overall activity. The team members also have the responsibility of discussing with the instructor
endale, and incorporate the points raised and agreed up on by the members and the instructor. Also, it
is the team members task to regularly report their work to him.

1.6. Objective

1.6.1. General objective

The general objective of this project work is to develop a software to automate for astu online student
registration system. so that the student can easily online reegister and access the web.

The general objective of this project is to minimize the current problem by developing an automated
system for ASTU registrar’s student on-line registration that we have observed in the operation of
registrar office. We choose the way of achievements of the objectives we use computer based system. We
believe that the automated system will successfully perform the mission and vision of the organization.

The system will facilitate the for registrar concerning to student on-line registration by providing for
permanent and suitable system, and it increased the university performance of on-line student registration
and also a daily activity will be done within a little time and number of workers.

1.6.2. Specific objectives

The specific objectives of the project are;

=> Enables ASTU registrar workers to record data effectively and efficiently
- Student’s background (in detail) information
- Student on-line registration
- Course and department information
- Withdrawal, readmission, add and drop students information
- Students states
=> Enables for ASTU registrar workers to retrieve the required data
- Students request information
- On-line student registration request
- Course and department selection request information
- Withdrawal, readmission, add and drop students request information
- Students status request
=> Enables for ASTU registrar workers to approve the request
- Student’s request
- On-line student registration request
- Course and department request
- Withdrawal, readmission, add and drop students request
- Student’s status request
 => Enables for ASTU registrar workers to easily prepare reports, status and basic student
background information.
=> Enables to update, delete, insert and modify the student information with in spot-time
* in general the objective of this project is to develop web-based database application software it gives
for the Registrar Office will have a complete control over all ASTU student’s status.
1.7. Feasibility study

The major purpose of this project to describe a proposed system can achieved for astu online student
registration system in three different types of feasibility test

1.6.1. Technical feasibility

Technical Feasibility study is deals about testing if the existing technology have a compatible to new system
and develop the proposed system. Implementation of the proposed system will use windows operating
system, sql server and visual studio 2010 .Assuming required hardware and software resources are available
for the development and implementation of proposed system. Therefore it is technically feasible.

1.6.2. Economic Feasibility

Economic feasibility of the project is determined by comparing costs and benefits of the proposed system
provide. Here, the project is economically feasible if and only if the benefits of the project have a higher
importance in spite of cost. Tools that the proposed system requires are inexpensive.

Benefits:

¹ It possible to online student registration.

¹ The students can select, drop and add courses online access.
¹ Reduce resource wastage of papers, large number of worker, student queue etc.
¹ Reduce student queue for registration time.

1.6.3. Operational feasibility

Operational feasibility test is making sure if the system works with properly when developed and use. The
student know how to access the proposed system and registered online. Therefore it is operational feasible.
1.8. Scope and limitation
1.8.1. Scope

The system we are proposing is mainly focused on ASTU online student registrar system (including
registration and getting information about the students on the web.) and the system will include the
following features:

 This project is designed for based on web based automation for ASTU online student
registrar system. this system will have created web-based database to record, insert, edit, delete,
update and search about student information, On this proposed system the activities can be done
through the following actors:

Administrator:
-can be read, insert, edit and delete student information in the side of admin
-and also create user account for student and update their accounts if necessary
Student/user:

-be able to log in into his/her accounts for access their data

-And ability to register online

-able to change his/her passkey

1.8.2. Limitation of the project

We face some challenges that we get gathering while performance the requirement and identifying the
basic things those are necessary for our system. Some of the constraints are:- There are some
limitations for this project. These are:
 When we has our system doesn’t consider the way of instructor to submitting the registrar
office student grade report and other issue/things.
 Shortage of time
 Work loading

1.9. Significance of the project

The project mainly helps to simplify the astu online student registration mechanisms followed student
online registration. So, it benefits both the university and the student in the following way:
 The project to facilitate the ASTU student online registration system. So, it benefits both the the registrar
workers and for the student of astu in the following way:

 Able to record student background information.

 Make the students registered online.

 Reduce resource wastage of time, paper, number of workers etc. Reduce non-

1.10. Operating environment

¹ Hardware environment

 32/64 bit operating system.

 RAM: 2GB and above.

 Hard-disk: 300GB and above.

¹ Software environment

 Operating system: Windows XP/7/8.

 Sql server 2008

 Visual studio 2010

 Enterprise architecture

Development tools
The following tools are used for studying existing designing and to help us developing new system
for astu registrar office management system.

unified modeling language (uml) tools

These tools have highly standardize notation and increased user involvement, so we can described
the existing system and the new system to be developing using essential use case model, ui(usr
interface),flow diagram, activity diagram, deployment modelling and class type architecture for
object oriented analysis phase.

Enterprise architecture:-
we can use for designing the above mentioned models and diagrams
 visual studio 2010:-
For user interface and student online registration system we can use some logical codes .asp.vb.net
is one of the high level languages which are easy to develop and integrated with sql server 2008.in
addition to this visual studio has full object oriented features we can construct different class code
fully implementation of inheritance, incapsulation, polymorphism structure handling provides a
global error.
sql server 2008:-

For the behind end one of the most preferable database management system tools when it stored
or handle large amount of data.
 Multiple views of data:-using sql we create the database can give different tables/users of
the database in different views of its structure and control.

 Complete database language:-sql provides a complete, consistent language for creating

database, managing its security, updating its content, inserting, deleting, selecting, retrieving data
and sharing data among many concurrent users.

 Dynamic data definition:-by using sql the structure of the database can be changed and
expanding dynamically even while users are accessing the database.

1.11. Methodology
1.11.1. Data Source

The primary source of data is obtained from astu registrar office and from the web site of astu.edu.et, which
are found in Adama town.

This section administers, registers, documents and archives all phases and steps associated with study applications,
enrollment, issue of students identification badges, placement in dormitories, internships, enrollment termination,
registration of study achievement, preparation of attestations, record of marks and record of study achievements,
official graduation documents, student and graduation statistics, general student's guidance, internship support
service. School's internship commissioner, alumni tracking and the like.

The Registrar office provides advisory services for enrolled students, study applicants and freshmen. Advisory
services include social and psychological counseling.
1.11.2. Data gathering methodology

To gather information and requirements that are used for our project we use the following methods: We used
different Methodology to collect data

 Interview
 Sample project
 Web site
 observation

¹ Observation

During our registration season we had a chance to visit astu registrar office which are found in Adama
town. For instance, adama branch of Astu University. At that time we have observed the student
registration process and its problems.

In addition we had an awareness of how the astu university student registration process going on in our
hometown.

¹ Interview

As we have mentioned above our primary source of data is astu university registrar office which are
found in Adama town. We gathered requirements by interviewing registrar office workers, data
recorder, team leader, astu registrar head (dr.gelana), Teachers and Students which are found on the
main campass. And also they give us some registrar guidance book, broachers, as a sample.

¹ Sample project

From computing department we have a chance to access the sample project related to astu student
online registration system, senior student thay make this project as senior project and mini project
.so that easly we collect some information from tose project and as an input for our automated
system

¹ Web site
 Astu have a web site to access people information about the university. The ame of the web site is
astu.edu.et.we browse from internet this web site and get more information about astu history,
registrar office and related issue.

1.11.3. System analysis and design

In the system analysis and design phase of a project we will use the object oriented approach that
examines requirements from the perspective of the class and objects found in the problem domain.

The reasons that we use the object oriented approach are:

¹ We can inherit properties of the class that are defined in the super class.

¹ We can reuse methods for avoiding redundancy.

¹ The data and functions are encapsulated in the objects that help us for easily
debugging purpose.

¹ It enables us to comprehensively model a system before we develop it.

¹ Modification of the object implementation is easy because objects are loosely coupled.

¹ Understanding of the structure is easy because object oriented modeling represents real
world entities.
1.11.4. Implementation methodology
 Activities Tools/ Programs

Platform MS Windows XP, 7/8

Database server SQL sever 2008

Development environment MS Visual Studio 2012

Programming language C#/vb/.net

Documentation MS Word, MS Excel

Diagram tools Visio or Enterprise architect

Table 1.2. Development Tools

1.12. Testing procedures

1.12.1. Unit testing
In this phase of testing we will try to eliminate faults in procedure and functions point of view by using
black box and white box testing.

Tasks that we will be perform under this phase

¹ Prepare unit test plans.

¹ Identify the unit test objectives.

¹ Prepare test cases that includes information such as set of test inputs, execution condition and
expected output.

¹ Perform the tests according to our plan

¹ Analyze the test results

¹ Document the test results.

1.12.2. Integration testing

In this phase we focus on how individual software modules are integrated and tested as a group. It occurs after unit
testing.

Tasks that we will be perform under this phase

¹ Prepare integration test plans.

¹ Identify integration test objectives.

¹ Identify integration test acceptance criteria.

¹ Perform the tests according to our plan

¹ Document the test results.

1.12.3. System testing

In this phase of testing we will focus on testing how properly the subsystem work together to achieve the
desired goals

Tasks that we will be perform under this phase

¹ Prepare system test plans.

¹ Identify system test objectives.

¹ Perform the tests according to our plan

¹ Document the test results.

1.12.4. Acceptance testing

In this phase of testing we will focus on testing a set of requirements to ensure that they meet user
expectation.

Tasks that we will be perform under this phase

 ¹ Prepare acceptance test plans.

¹ Identify acceptance test objectives.

¹ Perform the tests according to our plan

¹ Document the test results.

1.13. Constraints and Assumption

1.13.1. Constraints
¹ Scarcity of finance: because of we are students and we don’t have any source of income.

¹ Scarcity of work load: because of we are students and workers we don’t have any free time to make
best and shortage of source of income.

¹ Shortage of time: because of we are learning other courses beside this project, we couldn’t pay our
effort freely and effectively.\

1.13.2. Assumptions
¹ All computers operating system is Windows XP and above.

¹ All computers have sql sever 2008,visual studio 2010, web browser.

¹ Students have a knowledge of basic computer skills.

1.14. Project plan

1.14.1. Schedule

Months

Phases Nov11/2013- Dec 21/2013- Feb 1/2014- Jun2/2014- Jun 13/2014-

Dec 20/2013 Jan 20/2014 Jun 1/2014 Jun12/2014 Jun 25/2014
Requirement gathering and
Analysis

Design

Implementation

Testing

Maintenance

Table 1.3.Schedule

1.14.2. Budget

Materials Amount Unit price per birr Total price per birr

computer 1 computer 5000 5000

Win7/8 1 dvd 50 50

Visual studio 2010 1 dvd 50 50

Sql server 2008 1 dvd 50 50

Enterprise 1 dvd 50 50
architechture

Interner access Many times 500 500

transportation 30 days 300 300

printing 2 100 200

Paper 1 package 100 100

Pen 20 5 100

Total

Table 1.4. Budget

1.15. Definition, Acronyms and Abbreviations

Definition

¹ astu: - adama science and technology university .School for higher educational institution ,
usually directly they join after 12 grade completed formal education.
¹ Online student registration: - A way of accessing and online student registration on the web
based automation.

¹ Manage student data:- A way of keeping, recording, searching and managing student
information.

¹ Registrar office worker: - the way that is clear and easy working on astu registrar office
workers to understand to the user/student data & information.

¹ User/ student: - already the user of this system are astu active student now they are going to
learning proess.

Acronyms

¹ astu- adama science and technology university.

¹ Online student registration- the student regidtered online where ever they are physically

¹ automation-computer based system

Abbreviations
 ¹ ASTU- Adama Science and Technology University.

¹ UML- Unified Modeling Language.

1.16. References
¹ Bibliography

 Website for astu and registrar documentation.

 ASTU online registration system documentation from sample project.

 How to program c#.

¹ Webliography

 www.astu.edu.et.com

Chapter Two

Description of the Existing System

2.1. Major function of the current system

Registrar Office

This section administers, registers, documents and archives all phases and steps associated with study
applications, enrollment, issue of students identification badges, placement in dormitories, internships,
enrollment termination, registration of study achievement, preparation of attestations, record of marks and
record of study achievements, official graduation documents, student and graduation statistics, general
student's guidance, internship support service. School's internship commissioner, alumni tracking and the
like.

The Registrar office provides advisory services for enrolled students, study applicants and freshmen.
Advisory services include social and psychological counseling.

The major responsibilities are:-

 Provide leadership to plan, organize and manage all of the activities related to the records and
Registration Department, including serving as the official authorized keeper of the university's student
records.

 Hire, supervise and evaluates the Records, registration staff.

 Organize and administer the records, registration and graduation functions, including transcript
evaluations, certification process in order to provide maximum services to students while ensuring efficient
and effective workflow.

 Supervise the coordination, evaluation and certification of all graduation applications, while
overseeing the complete graduation process to include all elements of the rehearsal and ceremony.

 Responsible for collecting, recording, maintaining and reporting of student records within the
prepared guidelines e.g., grades, registration data, transcripts, mid-term verification.

 Provide leadership and develop appropriate recommendations for the implementation of related
technology application in support of enhanced services offered through Registration and Records.

 Develop and administer the Departmental budget.

 Problem solve the research, analysis and resolution of student disputes as they relate to records and
registration

 Collaborate with Administrators, Deans of Faculty, and counselors to facilitate and improve services
to students, including catalogue and registration/records policy questions.

 This job description is not intended to be all inclusive and the employee will also perform other
reasonable related duties as assigned by the Head of Administration.

 Participate in professional development activities and serve on university committees that support
the goals and objectives of the university.
 Provide back-up for records and registration services, including registering students, issuing
transcripts, answering phones, scanning, reporting grades and working special events.

 Plan and organize alumni tracking of graduates.

Curriculum Reform

Adama Science and Technology University (ASTU) is undergoing a far reaching transformation process
towards a model technical university for Ethiopia. This includes revision of the portfolio of programs and its
continuous improvement.

This page provides ASTU internal access to working documents.

Undergraduate Study Regulations for Engineering Programs PreRelease V0.7

Undergraduate Study Regulations for Engineering Programs PreRelease V0.8

Undergraduate Study Regulations for Engineering Programs PreRelease V0.9

The Registrar Office

The Office of the Registrar is a unit of the University responsible for all
Operational matters pertaining to student admissions, student selection and placement,
Follow up overall student registration, scheduling of courses, manage academic records of all the Schools
from enrollment to graduation. Major duties and responsibilities of the office: (Should be linked to the
following points)
Prepare the academic calendar of the University
Ensure that University directives and guidelines on students (admission, registration, Graduation, etc.)
And curricula (courses, credit requirements, etc.) are equitably, uniformly and consistently interpreted and
implemented
Maintain up-to-date records and documents on all academic matters pertaining to students and programs
of study of the University Create and maintain up-to-date, confidential, private, safe, and permanent
records of all students, including drop-outs, dismissals, withdrawals, and alumni of undergraduate
programs.
Create and maintain up-to-date, confidential, private, safe, and permanent records of all students,
including drop-outs, dismissals, withdrawals, and alumni of undergraduate programs.
Create and maintain up-to-date and accurate information on student admissions, placement, registration,
and academic performance, and attrition, graduation by level of instruction and delivery mode (regular,
extension, summer in-service, etc.) and of classroom utilization.
 Rules and Regulations
Academic Rules and Regulations
Academic Calendar
One Academic Year (usually, between September and end of June or the beginning of July) consists of two
semesters, each 16 weeks within which mid-semester exam will be administered. There may be additional
week (s) for final examinations of each semester
.Academic Calendar includes important dates as registration period, class start and end period, exam
period, add and drop period, application periods for readmission, make up exams and re-grading, inter-
Semester break, period of students stay in the University and graduation day.
Academic Calendar is issued three months before the start of the Academic Year after it will be
Endorsed by University Senate. It is issued and posted before students leave the campus for
Summer vacation. It is posted throughout the year on the Notice Board. Registration Students in all
programs must be in a good health appropriate for the field of study. Each student must be register at the
beginning of each semester after completing all requirements like producing clearance, grade report,
receipts etc.
Courses & Credits Requirements
All courses are semester courses. 1 credit hour is equal to 1 lecture hour or 2-3 hours. Of laboratory. The
maximum load shall not be exceeding 19 credit hours unless otherwise stated in the course catalogue. A
student who has justifiable reasons for deviation from the normal load has to secure a special permission,
not exceeding 22, from SB/DC if he is in his year of graduation; or has completed an equivalent course
work corresponding to one academic year and has a CGPA of 2.75,A degree student is required to
complete senior project as a partial fulfillment for his/her degree. Any deviation from these requires the
permission of the Senate (DAC). A maximum of 22 credit hours may be allowed for a graduating student if
his/her CGPA is 2.75 or above.
Letter grading system
is used ( A, B, C, D, F, NG, DO, W ) in which A= 4, B = 3, C =
2, D = 1, and F = 0, NG = No Grade, W= Withdrawal, DO= Drop Out.
In order to score a grade student must attend at least 90% of the classes and all assignments and exams
must be completed, otherwise NG (No Grade) will be assigned. Students with NG shall submit their
evidences to the head of his academic department up to one week after the start of the subsequent
semester.
The School Board finds that the student did not have valid reasons for not sitting for final examination, the
"I" grade on the student's record shall be changed automatically to "F", GPAs shall be calculated and the
status of the student shall be determined accordingly.
Repeating Courses
A student may repeat a course for which an "F" grade is scored until the "F" is cleared.
Students dismissed for academic reasons may be readmitted to repeat courses in which the scored "F" or
"D" grades up to five scheduled courses ( Less than 15cr. hrs.)A grade on repeated course shall be
recorded as follows a newgrade of “B” and below shall be recorded as it is. And a new grade of “A” shall be
recorded as “B”.Grade ComplainStudent may apply for re-grading within the time frame on the Academic
calendar if he/she is not satisfied with the grade A student can complain for re-grading only for a maximum
of one courseper semesterA student is allowed to apply for re-grading fora maximum of two timesduring his
entire stay in a program of study.If the re-grading results are a grade lower than the one previously
obtained, the lower grade shall be recorded.AcademicAchievementsA First Year student who obtains SGPA
less than 1.5at the end of the first semester is subjected to Academic Dismissal.
A first year student who scores SGPA of 1.5 up to 1.75 shall continue his studies, but be warned.
Any student who scores SGPA below 1.5 or CGPA below 1.75 will be dismissed, irrespectiveof his/her
CGPA or SGPA, respectively.A student who fails to achieve a SGPA of 1.00 at any semester issubject to
dismissalfor goodAcademic Probation is a suspension of penalty of dismissal because of scholastic failure.
It is not a right but a privilege given by the Senate (DAC). However, a student who for two consecutive
semester scores a SGPA of grater than or equal to 2.00 and if his CGPA is grater or equal to l.90, up on the
decision of the respective SMC may be considered for as a probation student but not pass student.Make-
up ExaminationsMake-up examination is allowed only for a student who is unable to sit for a final
examination forreasons beyond his/her control (hospitalization or accidents.) It is never allowed for more
than two timesthroughout the study period nor to raise grade point average. A student is allowed to sit for
make-up exam only if he can produce valid and documented reasons for not having sat on final
examination a weak after the start of the next semester.If a student does not have valid and documented
reasons for not sitting for final examination the “I” grade on students’ record will be changed automatically
to “F”.A student who has less than three (one or two) “I” grades in a semester and who is allowed to take a
make-up examination may continue his studies in subsequent semester if he is in good academic standing.
A student who has three or more “I” grades in a semester shall withdraw from the university, and apply for
make-up exam.GPAs shall not be calculated and no academic status shall be determined until the results
of the make-up examination are known.
Withdrawals
Candidates in good academic standing wishing to discontinue their studies must fill in an official
withdrawal form.Students who intend to drop or withdraw from the University for a semester or a year must
discuss the matter thoroughly with their academic advisor.Application for withdrawal must be made within
six weeks after registration for the semester and present to the respective department or School head.
When approved, submit to Registrar.Reasons for withdrawal must be supported by reliable and irrefutable
document (s)
Readmission
Readmission is not a right but a privilege given to the student by the academic commission
(AC). A student, who has been dismissed or withdrew for reasons beyond his/her control, may
have the privilege to be readmitted. Readmission application is processed on the time set on the
academic calendar
Graduation
All required courses and minimum credit hours shall be satisfied. A CGPA of 2.00 and MGPS
2.00 is required There should be no F grade. Graduates shall collect their temporary degree/diploma from
the Office of the Registrar within three month time after graduation day.Role of Academic AdvisorsEach
Student shall immediately contact his/her academic advisor in case of any academic problem. Detail and
supportive advises are given by the advisor. Advisors are responsible for students’ academic matters.
Fees: Tuition and accommodation fees for regular
Ethiopian students are based on the cost sharing
Regulation. There are charges for various services rendered by the office. No
.
Services Fee (in Birr)
1. Issuance of Original Degree/Diploma..................................... 100.00
2. Issuance of Official Copy-
Domestic Destination (per page).................................................. 40.00
-International Destination (per page)........................................... 100.00
3. Issuance of Student Copy (Per page).......................................... 20.00
4. Late Registration with Penalty....................................................... 30.00
5. Readmission application ...............................................................20.00
6. ID Lost.......................................................................................... 120.00
7. ID due to Name Change by Court.............................................. 60.00
8. Renew ID......................................................................................15.00
9. Authentication of Documents per page……………………………........ 50.00
10. To whom it may concern letter......................................................... 15.00
11. Lots of Clearance paper to Look from file......................................... 40.00
12. Loss of graduation clearance & any document copy from the file ...................40.00

2.2. Problems of the current system

¹ The student registration it takes more time and large number of workers are involved.

¹ The application which are used for recording student data and student registration are not
effective and efficient (semi-manual .like word, excel and access).

¹ Students must have a queue for registration

¹ Consume of more time and resource for student registration time.

 Chapter three

Proposed system

3.1. Overview

On this section we describes the proposed system for astu online student registration system and define the
functionality and functionality of the proposed system.

3.2. Functional Requirements

Major function of the existing system is astu online student’s registration,

Functional requirements are basically an action of the system and features of the project that must be
included into our automation system, to satisfy the astu online student registration need and to be acceptable
to the user.it contains the functions into our proposed system is going to fulfill.
The following activities are the functional of new system:-

 Recording student information

The system records all the necessary information about student (detail information like name, sex, age, dept,
birth date, wereda, zone, region, nationality…etc.)

 Online student registration:-the student is going to registered online and access the
database
 Retrieving student information:-The new system provides simple retrieving mechanism to
get the student request and accept if it is fulfill the rule and regulations or the registrar office.
 Sending approval (confirmation):-The system sends different approval to accomplish the
student request
Searching for student information:-The new system provides simple search for the student
to see their registration and course information already they are selected.
Update student information:-The administrator / student will be update his/her background
information when it is necessary.
Block the use account:-If the administrator want to terminate the student account by
different reasons the system provides a way of blocking the student’s account (inactive) from the
database of the registrar office.
report generating:-The registrar worker can prepared different reports such as:-Grade report
New student come and registered
o Temporary degree
o Check list
o student status

o all student background information

o when the student terminate getting service from the university

3.3. Non Functional Requirements

Listed below are some major non-functional requirements

A. Usability

Astu online student registration system is going to developed in a highly usable and user friendly way. Since
the users of astu registrar office are student’s., the system will be easy to use and it is possible to access and
student register online.

B. Reliability

The system is highly minimize wastage of time and resources that may occur unexpectedly. So having these
properties the system is going to be highly reliable.

C. Performance

The performance of Astu online student registration system will depend on the hardware performance of the
computer on which it is running. To be specific, the system would run or perform much faster on a computer
which has 2GB or more RAM capacity, 300GB or more HDD, Dual core or more processor capacity.

D. Supportability

Astu online student registration system will be supportable and compatible on windows platform.

E. Accessibility
The system will be a web based application it is going to be accessible on the web browser. But The other
case will be if the system is easily attacked by virus, hackers and cracker’s.

F. Error Handling And Extreme Conditions

Each error that may occur in Astu online student registration system is going to be handled accordingly in
order to reduce the amount of failure.

Since users of our system are Astu student, they make mistakes when the registration time, each and every
input boxes are going to be handled according to their type.

G. Documentation

At the end of the project, every activity of the entire system, design, coding and other process will be
documented for future reference. There will be a documentation of implementation for testing and
maintenance during application failure.

H. Security

Security issue is major attention in our system, because our goal is to make the way of Astu online student
registration system, the system is not accept online grade submission from instructor, sensitive data that
needs to be secured.

I. Back up

We will take a backup in our system database. In order to enable the administrator and the student/ the user
to access the data from our system.

3.4. System Model

13. Software processing model

We select the following processing model, due to:-
13.1evolutionary models: prototyping
 When to use: Customer defines a set of general objectives but does not identify detailed requirements for
functions and features. Or Developer may be unsure of the efficiency of an algorithm, the form that human
computer interaction should take.
• What step: Begins with communication by meeting with stakeholders to define the objective, identify
whatever requirements are known, outline areas where further definition is mandatory. A quick plan for prototyping
and modeling (quick design) occur. Quick design focuses on a representation of those aspects the software that will
be visible to end users. ( interface and output). Design leads to the construction of a prototype which will be
deployed and evaluated. Stakeholder’s comments will be used to refine requirements.

• Both stakeholders and software engineers like the prototyping paradigm. Users get a feel for the actual
system, and developers get to build something immediately. However, engineers may make compromises in order to
get a prototype working quickly. The less-than-ideal choice may be adopted forever after you get used to it.

Quick
communication plan
Modeling
Quick design

Deployment
delivery & Construction
feedback of prototype
 The Waterfall Model

It is the oldest paradigm for SE. When requirements are well defined and reasonably stable, it leads to a
linear fashion. (problems: 1. rarely linear, iteration needed. 2. hard to state all requirements explicitly.
Blocking state. 3. code will not be released until very late.)The classic life cycle suggests a systematic,
sequential approach to software development.

3.4.1. Scenarios

Scenario: 1

Name of use case: student Registration

Participating instance actor: student

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The student must be registered

Flow of events:
 1. He clicks on the new semester registration form to register.

2. The system display the registration form.

3. He fill the form and click register button.

Alternate conditions:

3 a. If he fills the form incorrectly then the system will generate an error message.
3 b. If he selects out of class level (i.e.id,name,sex,age Department, course code) during the
registration then he will be given a chance he got the correct information to make sure that he is
trying to register for the system properly.

Exit condition: The system saves the entered data into database.

Special requirement: sql server 2008,visual studio 2010,web browser must be installed on the computer
before accessing and installing the online astu student registration system.

Scenario: 2

Name of use case: student select the course

Participating instance actor: student

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The student must be registered.

Flow of events:

1.He select his name, id no,COURSE CODE, COURSE TITTLE , CRDHRS ,SEMESTER ,ACADAMIC YEAR ,PRERECUIST.
DEPT CODE from the list and click ok button.

1. The system displays the wel come to course selection window.

2. He select a course that he want to take from the list.

 3. He clicks on taken course and click on a registered course button.

4. The system displays you have registered for These Courses which holds list of course selection
windows.

Alternate conditions:

5 a. If he made a mistake in selecting the course , he can click a back button to back to the previous
window.
5.b. If he selects out of class level (i.e.id,name,, course code) during the registration then he will be
given a chance he got the correct information to make sure that he is trying to register for the system
properly.

Exit condition: The system saves his course selecton.

Special requirement: Special requirement: sql server 2008,visual studio 2010,web browser must be
installed on the computer before accessing and installing the online astu student registration system.

Scenario: 3

Name of use case: administrator add department

Participating instance actor:admin

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The student must be registered.

Flow of events:

1.He select DEPT CODE , DEPT NAME ,DEPT HEAD, SECRETERY from the department information list and click
registere button.

5. The system displays the wel come to add new department window.

6. He select a department that he want to add from the list.

 7. He clicks on taken department and click on a registered button from add new department window.

8. The system displays you have registered for these new department which holds list of new
department selection windows.

Alternate conditions:

5 a. If he made a mistake in selecting the new department, he can click a back button to back to the
previous window.
5.b. If he selects out of class level (i.e.id,name,, course code) during the registration then he will be
given a chance he got the correct information to make sure that he is trying to register for the system
properly.

Exit condition: The system saves his course selecton.

Special requirement: Special requirement: sql server 2008,visual studio 2010,web browser must be
installed on the computer before accessing and installing the online astu student registration system.

Scenario: 4

Name of use case: administrator add course

Participating instance actor:admin

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The student must be registered.

Flow of events:

1.He select COURSE CODE ,COURSE TITTLE , CRDHRS ,SEMESTER ,ACADAMIC YEAR ,PRERECUIST ,DEPT CODE
from the course information list and click add or remove button.
9. The system displays the wel come to add new course window.

10. He select a course that he want to add from the list.

11. He clicks on taken course and click on a registered button from add new course window.
 12. The system displays you have registered for These new department which holds list of new course
selection windows.

Alternate conditions:

5 a. If he made a mistake in selecting the new course , he can click a back button to back to the
previous window.
5.b. If he selects out of class level (i.e.id,name,, course code) during the registration then he will be
given a chance he got the correct information to make sure that he is trying to register for the system
properly.

Exit condition: The system saves his course selecton.

Special requirement: Special requirement: sql server 2008,visual studio 2010,web browser must be
installed on the computer before accessing and installing the online astu student registration system.

Scenario: 5

Name of use case: search student data

Participating instance actor: admin/student

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The admin/student must be registered.

Flow of events:

1. He select his id no from the list and click search button.

2. The system displays the seaarch window.

3. The system displays search window which holds list of the id no and selected course .

4. The system display the selected id no and selected course.

5. He clicks close button

6. The system displays selected id no and selected course information.

Alternate conditions:

7 a. If he decides to ignore the search , then he can click the back button to back to the previous window.

Exit condition: The system saves his information and exit.

Special requirement: Special requirement: sql server 2008,visual studio 2010,web browser must be
installed on the computer before accessing and installing the online astu student registration system.

Scenario: 6

Name of use case: log in /user information

Participating instance actor: admin/student

Entry condition:

 Student must be open the web site of ASTU online registration system on the computer.

 ASTU online registration system must be opened.

 The admin/student must be registered.

Flow of events:

1. He select his user name,user type,password from the list and click log in button.

2. The system displays the log in window.

3. The system displays log in window which holds list of the his user name,user type,password.

4. The system display the selected user name,user type,password.

5. He clicks close button

6. The system displays selected user name,user type,password and selected log in information.

Alternate conditions:

5 a. If he want to leave as it is, he can always undo his previous settings by repeating the same process.
Exit condition: The system saves the log in information ,it helps to access the system and exit.

Special requirement: Special requirement: sql server 2008,visual studio 2010,web browser must be
installed on the computer before accessing and installing the online astu student registration system.

3.4.2. Use case Model

A use-case model is a model of how different types of users interact with the system to solve a problem. As
such, it describes the goals of the users, the interactions between the users and the system, and the required
behavior of the system in satisfying these goals.

A use-case model consists of a number of model elements. The most important model elements are: use
cases, actors and the relationships between them.

3.4.2.1. Actor identification

An Actor is something that performs use cases upon a system. It is just an entity, meaning it can be a
Human or other system that directly play an external role in the system.

Name: student
Description: the students who are learning in the astu. Perform different tasks in this system: take a course,
take online registration, explore ASTU registrar information and history.

Name: admin
Description: It can be a system admin or a data recorder who guides and manage the student every
information.
Task: view student current status.
3.4.2.2. Use case identification

In our project we identified the following use cases:-

¹ Student online Register.

 ¹ Student Take a course.
¹ Student Take a user account and password.
¹ Admin add and remove course
¹ Admin add and remove department
¹ Admin/student search information about any active student information
¹ explore ASTU registrar information and history

¹ Admin/student View student current status.

3.4.2.3. Use case diagram

A use case diagram illustrates a set of use cases for a system, the actors of these use cases, the relations
between the actors and these use cases, and the relations among the use cases. The UML notation for a use
case diagram is shown on the figure, in which

¹ An oval represents a use case,

¹ A stick figure represents an actor,

¹ A line between an actor and a use case represents that the actor initiates and/or participates in the
process.
 Use case diagram
Astu online student registration system

Select course View student

status
Registered

Explore the
Update Log in
system
student
information

Log in

Student Add course

Search

Admin/data recorder

View status Contact Add new

department department
Fig 3.1. Use case diagram

3.4.3. Description of Use case Model

Description 1

Use case name Student online Register

Use case number 1

Use case description Allow the student to register and select their current course

Participating actor ASTU active student.

Pre-condition The student must open the browser and the site.

1. The student click on the add new student button to

Flow-of events
register.
2. The system display the registration form.
3. The student fill the form and click register button.
Post-condition The student successfully registered.

Alternative flow-of events If the student make mistake, the system displays error message and
allow making correction.
 Description 2

Use case name Student Take / select a course

Use case number 2

Use case description Allow the student to take course of the subjects which are provided
by the system.

Participating actor ASTU active student.

Pre-condition The student have to be registered.

Flow-of events
1. The student select their id no, course code, crdhrs from the
list and click course register button.
2. The system displays the course selection window.
3. The student click on take a course selection button.
4. The system displays course selection window which holds
list of course of the system.
5. The student select a course that they want to take from the
list.
6. The system displays the course at the position of where
their current semester, year and status.
7. The student continue taking / selecting course from they
stopped till up to the permission .

Post-condition The system saves the student position of course selection.

Alternative flow-of events If the student make mistake, the system displays error message and
allow making correction.
 Description 3

Use case name Take a Self-Test

Use case number 3

Use case description Allow the kid to test their performance.

Participating actor Kids.

Pre-condition The kids have to be registered.

Flow-of events
1. The kids select their name from the list and click ok button.
2. The system displays the Home window.
3. The kids click on Self-Test button.
4. The system displays Self-test window which holds list of
the three subjects.
5. The kids select the subject that they want to take self-test.
6. The system display the test of the selected subject.
7. The kids take the test.
8. The kids click finish button

9. The system displays self-test result.

Post-condition The system saves the kids result.

Alternative flow-of events If the kids make mistake, the system displays error message and allow
making correction.
 Description 4

Use case name Customize background setting

Use case number 4

Use case description Allow the kids to customize background of CBTSEK

(I.e. background music, background color).

Participating actor Kids, Guider.

Pre-condition The kids have to be registered.

Flow-of events
1. The kids/guider select their name from the list and click ok
button.
2. The system displays the Home window.
3. The kids/guider click on edit from the menu bar and select
setting.
4. The system displays the setting window.
Description 5
5. The kids/guider customize the background and click ok
Use case name Play games
button.
Use case number
Post-condition 5The system saves the customized setting.

Use case description

Alternative flow-of events Allow
If the the
kidskids
maketo play different
mistake, educational
the system games.
displays error message and allow

Participating actor making correction.

Kids.

Pre-condition The kids have to be registered.

Flow-of events
1. The kids select their name from the list and click ok button.
2. The system displays the Home window.
3. The kids click on play games button.
4. The system display the list of educational games.
5. The kids select game from the list and play.
6. The system shows result when the game is over.
Post-condition The system saves the kids status.

Alternative flow-of events If the kids make mistake, the system displays error message and
allow making correction.
 Description 6

Use case name Explore Ethiopian history

Use case number 6

Use case description Allow the kids to know about Ethiopia.

Participating actor Kids.

Pre-condition The kids have to be registered.

Flow-of events
1. The kids select their name from the list and click ok button.
Description 7
2. The system displays the Home window.
Use case name View
3. kids
Thestatus
kids click on Explore Ethiopian History button.
Use case number 7 4. The system display a window which holds categories of
Ethiopian history.
Use case description Allow the guider to check kids status.
5. The kids select from the list of categories and start reading
Participating actor Guider.
about Ethiopia.
Pre-condition
Post-condition The kids
guider must open read.
successfully the CBTSEK.
1. The guider click on student status link.
Flow-of events
Alternative flow-of events If the kids make mistake, the system displays error message and
2. The system checks whether the kids status exists or not.
allow making correction.
3. The system display a window that enable the guider to
select the class level.
4. The guider select the class level.
5. The system displays the kids status window.
Post-condition The guider successfully view kids status.

Alternative flow-of events If the guider insert wrong information the system displays an error
message.

3.5. Object Model

Object model is a description of an object-oriented architecture, including the details of the object structure,
interfaces between objects and other object-oriented features and functions.

3.5.1. Data Dictionary

¹ Lessons: - A collection of subject portion which is given per a day. Each subjects are
divided into lessons in the way that is easy to provide.
¹ Supportive Self-tests: - Self tests to help kids to evaluate their knowledge and
performance using speech recognition and text to speech method.
¹ Status: An indicator by which the guider can know the kids performance.

¹ Games: A collection of games which are educational based in order to increase the kids
remembrance.

3.5.2. Class Diagram

Class models show the classes of the system, their interrelationship (associations and multiplicity) among
classes, the operations and attributes of the classes.

A class diagram is typically modeled rectangles with three-section:

 The top one indicates the name of the class

 The middle one lists the attributes of the class and

 The third one lists the methods.

class Dynamic View

Registration

+ Age: int
+ classLevel: String
- isTestNeeded: boolean
+ kidFname: String
CustomizeSetting
+ kidLname: String
PlayGame + sex: String + bgColor: String
+ bgMusicType: String
+ startTime: datetime + get_age() : String
+ stopTime: datetime + get_classlevel() : String + get_bgColor() : String
+ get_kidFname() : String + get_bgMusic() : String
+ calculateTimeTaken() : datetime + get_kidLname() : String
+allow +allow + set_bgColor(String) : void
+ countErrors() : int + get_sex() : String + set_bgMusic(string) : void
+ calculateResultPercentage() : string + register() : void
+ displayResult() : void + requestTest() : void
+ set_age(int) : void
+ set_classLevel(String) : void
+ set_kidFname(String) : void
+ set_kidLname(String) : void
+ set_sex(String) : void

+allow

Lessons

+ classLevel: String
+ lastStop: String
+ subjectName: String

+ getLastStop() : String
+ get_classLevel() : String
+ get_subjectName() : String
+ resumeLesson() : void
+ setLastStop(String) : void

Test ViewStatus

+ classLevel: String + KidFName: String

+ isPassed: boolean + kidLName: String
+ lastStop: String + classLevel: String
+ result: int + SubjectName: String
+ subjectName: String - laststop: String

+ get_classLevel() : String + getKidFname() : String

+ get_lastStop() : String + getKidLname() : String
+ get_subjectName() : String + get_classLevel() : String
+ ProvideTest() : void + get_subjectName() : String
+ displayResult() : void + get_laststop() : string
+ search(String, String) : String
+ Show status() : void

Fig 3.2. Class diagram

3.6. Dynamic Model

3.6.1. Sequence Diagram

A sequence diagram in a UML is a kind of interaction diagram that shows how processes operate with one
another and in what order. A sequence diagram shows object interactions arranged in time sequence. It
depicts the objects and classes involved in the scenario and the sequence of messages exchanged between
the objects needed to carry out the functionality of the scenario. It shows, as parallel vertical lines (lifelines),
different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of simple runtime scenarios in
a graphical manner.

sd Registration

Kids CBTSEK Screen Registration Registration Kids Table

Window Controller

start()

display()

Click on New Button()

display registration form()

fill the form()

click Ok Button()

activate()

check duplication of name()

validate()

save()

confrim()

successfully registered()

Fig 3.3. Sequence diagram for Registration

sd take a lesson

Kids CBTSEK Screen Home Window subject Lesson lesson controller lesson table

Start()

Display()

Select Name()

Click Ok Button()

Click Take a Lesson Button()

Select()

Lesson has been Resumed ()

take()

click finish Button()

activate()

save()

Fig 3.4. Sequence diagram for Take a lesson

 sd Self_test

kids CBTSEK Screen Home window Subject Test Self test Controller status table

start()

display()

select name()

click Ok button()

click self test Button()

Select()

display self test()

take self test()

click Finish Button()

activate()

save result()

request result()

confirm()

show result()

Fig 3.5. Sequence diagram for Take a Self-test

sd Customize background setting

Kids/Guider CBTSEK Screen Home window menu bar Setting controller Setting table

Start()

Display()

Select name()

Click OK button()

Click edit()

Click setting()

Setting window displayed()

Customize()

Click save button()

Activate()

Save()

Fig 3.6. Sequence diagram for Customize Background Setting.

sd Play Games

Kids CBTSEK Screen Home window Game Game controller game result table

Start()

Display()

Select name()

Click OK button()

Click Play Games button()

List of games displayed()

Select game()

Selected game displayed()

play()

Click finish button()

activate()

save result()

request result()

confirm()

Show result()

Fig 3.7. Sequence diagram for Play Games

 sd Ethiopaian History

kids CBTSEK Screen Home Window History categories

start()

display()

select name()

click Ok button()
click explore Ethiopian
history button()

display list of history()

select()

display history()

read()

Fig 3.8. Sequence diagram for Explore Ethiopian history

sd view kids status

Guider CBTSEK Screen classLevel kids status status controller status table

start()

display()

click kids status hyperlink()

select class level()

activate()

check existance()

validate()

retrieve()

confrim()

display kids status()

Fig 3.9. Sequence diagram for view kids status

3.6.2. Activity Diagram

An activity diagram describes a system in terms of activities. Activities are states that represent the
execution of a set of operations. The completion of these operations triggers a transition to another
activity. Activity diagrams are similar to flowchart diagrams in that they can be used to represent control
flow (i.e., the order in which operations occur) and data flow (i.e., the objects that are exchanged among
operations).

act Register

CBTSEK

[ Start ]

Entry Window

[ Click new button ]

Registration Form

[ Fill form ]

[ Click Cancel button ]

Close Registration Option?

[ Click Ok button ]

[ Valid ] [ Inv alid ]

Registration successfull Validatation?
Message

Fig 3.10. Activity diagram for Registor

 act Take a lesson

CBTSEK

[ Start ]

Entry Window

[ Select name and Click Ok button

]

Home

[ Click Take a lesson button

]

Lessons

[ select ]

[ Amharic ] [ English ] English lessons list

Amharic lessons list Subj ect?

[ Maths ]

Maths lessons list

Resume lesson

Take the lesson

Fig 3.11. Activity diagram for take a lesson

 act Take a self-test

CBTSEK

[ Start ]

Entry w indow

[ Select name and Click Ok button

]
Home

[ Click Self-test button ]

Self-test

[ select ]

[ Amharic ] [ English ] English Test

Amharic Test Subj ect?

[ Maths ]

Maths Test

Take self-test

[ Click Finish button ]

v iew result

Fig 3.12. Activity diagram for take a self-test

 act Customize background Setting

CBTSEK

[ Start ]

Entry Window

[ Sel ect nam e and Cl i ck Ok button ]

Home

M enu bar

[ Cl i ck edi t and sel ect setti ng ]

Setting

[ customize and click sav e button ]

setting has been changed

Fig 3.13. Activity diagram for customize background setting

 act Play games

CBTSEK

[ Start ]

Entry w indow

[ Select name and click Ok button ]

Home

[ click play game button ]

Games

[ select ]

[ Finish ]
play v iew result

Fig 3.14. Activity diagram for Play games

 act Explore Ethiopian History

CBTSEK

[ Start ]

Entry w indow

[ Sel ect name and cl ick OK button ]

Home

[ Cl i ck Explore Ethiopi an history button]

History Categories

[ sel ect ]

read

Fig 3.15. Activity diagram for Explore Ethiopian History

 act View kids status

CBTSEK

[ start ]

Entry Window

[ ki ds statu s hyperl i nk ]

clas s lev el

[ Sel ect ]

View kids status

[ Cl ose button ]

Close v iew status

Fig 3.16. Activity diagram for view kids status

3.6.3. State diagram

 State diagrams are used to give an abstract description of the behavior of a system. This behavior is analyzed and
represented in series of events, that could occur in one or more possible states

stm Registration

Opening CBTSEK

Display entry window

Display registration
form

[Fill form]

registration [valid] [invalid]

validating?
successful message

Figure 3.17. Registration State diagram

 stm Taking A lesson

Opening CBTSEK

Display entry w indow

Display home w indow

Display subj ects

Display lessons

Display lesson resume lesson

start/resume?

Figure 3.18. Taking a lesson state diagram

stm Taking a self-test

Opening CBTSEK

Display entry w indow

Display home w indow

Display subj ects

display self tests

Show result

Figure 3.19. Taking a self-test state diagram

 stm customizing background

Opening CBTSEK

stm Playing game

Display entry w indow Display home w indow

Drop dow n Edit

Opening CBTSEK

display setting

Display entry window

Display home window Display game

categories

Figure 3.20. Customizing background state diagram

Display game Show result

Figure 3.21. Playing game state diagram
 stm Exploring Ethiopian History

Opening CBTSEK

Display entry w indow

Display home w indow Display History

Display history
categories

Figure 3.22. Exploring Ethiopian History state diagram

 stm viewing kids status

Opening CBTSEK

Display entry window

Display subjects
Display kids status

Figure 3.23. Viewing kids status state diagram

Chapter Four: System Design

4.1. Overview
During system design, we define the design goals of the project and decompose the system into smaller
subsystems. We also select strategies for building the system, such as the hardware/software platform on
which the system will run, the persistent data management strategy, the global control flow, the access
control and security, and handling of boundary conditions.

The result of system design is a model that includes a clear description of each of these strategies, a
subsystem decomposition, and a UML deployment diagram representing the hardware/software mapping of
the system.

4.1.1. Purpose of the system

As we already tried to mention earlier in the previous chapters, the purpose of the proposed system is
educating and building kid’s minds in more technological way by computerizing the formal way of teaching
and learning mechanism.

Educationally cultivating kid’s minds being the main purpose of the system, there are also educational
games included by which the kids could entertain while grasping knowledge. But because of time that we
have we can’t include every subject matter like music and drawing, the system teaches only the three basic
subjects which specifically are Mathematics, English and Amharic.

4.1.2. Design Goals

Accessibility: - The system will be accessed by any user, who installs the system on computer.
Portability: - the system will work on any computer that fulfills all the requirements.
Usability: - The system will not be complex to understand and use, because it will be develop by
considering the knowledge of kids.
Performance: - The performance of CBTSEK will depend on the recommended hardware performance of
the computer on which it is running, i.e. the system would run or perform much faster on a computer which
has 2GB or more RAM capacity, 300GB or more HDD, Dual core or more processor capacity.
Maintainability: - Changes made on our system such as adding other subject and functionality shouldn’t
affect the existing functionality of the system.
Error Handling: - Since users of our system are kids, they make mistakes when we compare to adults, each
and every input boxes are going to be handled according to their type.

4.2. Proposed System Architecture

4.2.1 Overview

Architecture is the fundamental organization of a system, embodied in its components, their relationships to
each other and the environment, and the principles governing its design and evolution.
Describe the subsystem decomposition in terms of subsystem responsibility, dependence among
subsystems, subsystem mapping to hardware, and major policy decisions such as control flow,
access control, and data storage.

As an architecture for our system we choose component based software architecture. The main motivation
behind component based design is component reusability, a component encapsulates the functionality and
behaviors of a software element into a reusable and self -deployable binary unit.
A component-oriented design represents a higher level of abstraction than an equivalent object-oriented
design; the former defines components and connections between them instead of classes and connections
between classes.

Why we chose component based architecture?

¹ Since our system is a teaching system there may be many changes needed in the future during the
change in the curriculum, so with component based architecture handling the changes and
implementing updates without affecting the rest of the system is going to be easy because of the
independency and flexible connectivity of components.

¹ Productivity for current and future software development because of reusability of components.

4.2.2. Sub-System decomposition

¹ Registration subsystem: -This subsystem is responsible for registering new student to the system. It
receives all the necessary inputs that are needed for a kid to be registered and registers him/her.

¹ Lesson subsystem:-This subsystem is responsible for resuming and displaying an appropriate lesson
based on the kid’s level subject name and last stop. And aside from that it saves the kid’s last stop
when the kid leaves the system so that he/she may resume from where he/she has left off.

In this subsystem there are three classes, lesson class, Test class and view status class. They are
highly cohered.

¹ Play games Subsystem: this subsystem is responsible to allow the kids to play different educational
games which are supportive for regular class sessions.

¹ Customize setting subsystem: - This subsystem is responsible for changing the background settings
of the system based on the user’s choice. For example: the user may select black color as a
background, so the system will receive that request and change the background to black.

4.2.3. Hardware software mapping

Addressing hardware/software mapping issues often leads to the definition of

 additional subsystems dedicated to moving data from one node to another, dealing with
concurrency, and reliability issues. The system needs one computer where the CBTSEK setup is
going to be installed, and as a back end it will use SQL server.

4.2.4. Persistent data management

Persistent data represents a bottleneck in the system on many different fronts: Most
functionality in system is concerned with creating or manipulating persistent data. Often, this
leads to the selection of a database management system and of an additional subsystem dedicated to
the management of persistent data. The persistent data of the sub systems such as Registration
subsystem, Background setting subsystem and Lessons subsystem will be stored in an SQL Server
database

4.2.5. Access control and security

Starting CBTSEK will led the kids to register or to select their name from existing list to continue.

The system allow the kids and guider to customize background setting (background color and background
music) of the system.

Class Actors

Kids Guider

View status getKidFname()

getKkidLName()
search()
setKidFname()
setKidLname()

Lessons getLastStop()
retrieve()
setCurrentStop()
updateProgress()

Customize setting get_bgColor() get_bgColor()

get_bgMusic() get_bgMusic()
 set_bgColor() set_bgColor()
set_bgMusic() set_bgMusic()

Registration get_age()
get_classLevel()
get_kidFname()
get_kidLname()
get_sex()
register()
requestTest()
set_age()
set_classLevel()
set_kidFname()
set_kidLname()
set_sex()

Test getClassLevel()
getLastStop()
getSubjectName()
provideTest()
dispalyResult()

Playgames CalculateTimeTaken()
countErrors()
calculateResultPercentage()
displayResult()

4.2.6. Boundary conditions

When the system starts, first it establish a connection with the database to provide the necessary information
for starting.

When the user want to quit the system, they click on the close button of the system.
 Our system provide error handling facility to detect or handle exceptional cases. When kids make a mistake
the system will display an appropriate error message and allow the kids to correct their mistake.

4.3. Subsystem services

¹ Lessons subsystem operation:

getLastStop – Display the last stop or progress of the kids.

resume – Display the next lesson.

¹ Customize setting subsystem operation:

get_bgColor – Customize background color of the system.

get_bgMusic –Customize background music of the system.

¹ Registration subsystem operation:

get_age – Get age entered from kids.

getClassLevel – Get class level entered from the kids.
getFname – Get first name entered from the kids.
getLname – Get last name entered from the kids.
getSex – Get gender entered from the kids.
requestTest – Used to request a test from the test table.

¹ Play game subsystem operations:

countErrors- count an error which is happened during playing game

calculateTimeTaken- calculate the time take to finish the game.
Display result- show the result that is scored during playing game.
4.4. Component diagram

Component diagrams are used to model physical aspects of a system. It is a special kind of diagram in UML
that used to visualize the physical components in a system. The purpose is also different from all other
diagrams discussed so far. It does not describe the functionality of the system but it describes the
components used to make those functionalities.

cmp Component Model

Lessons Subsystem
Registration Subsystem

Lessons View status

Registration
Register()

Test
requestTest()

Play games Subsystem Background Setting Subsystem

play game Background setting

set_bgColor() set_bgMusic()
countErrors() calculatePercentage()

Figure 4.1.component diagram

4.5. Deployment diagram

A deployment diagram models the physical architecture of the hardware. It shows the
hardware for the system, the software that is installed on that hardware, and the
middleware used to connect the disparate the machines to one another.

deployment For CBTSEK

client computer

CBTSEK_App

Test

ESR

Database

View Satus
Sql Serv er

ASR

lesson

registration

Custumize Setting

Figure 4.2. Deployment diagram

Summary