Ministry of Education Database System. By- Abdirashid Jeeni

8/7/2019 Ministry of Education Database System. By- Abdirashid Jeeni

1/82

Admas University College

Hargeisa Main Campus

Moe (ministry of Education)

Database system

Prepared By: Abdirashid JeeniICT Department

Email: [email protected]

Web: www.facebook.com/ajeeni

Admas University College

Hargeisa Main Campuswww.admashmc.com
mailto:[email protected]://www.facebook.com/ajeenihttp://www.admashmc.com/http://www.facebook.com/ajeenihttp://www.admashmc.com/mailto:[email protected]


2/82


3/82

Introduction


4/82

MINISTERY OF EDUCATION AUTOMATED SYSTEM

(MOEAS)

To develop a software application that support the application specific to the

ministry of Education automation in specific activity to an organization there

by allowing the integration of all the Students, Teachers, and schools of the

country pertaining to their performance. To keep track of all the other

departments related to that organization such as regional process, Exam

Board and etc.

To allow the Registration department of MOE to update the teachers,

students, and schools details whenever there is a change in their profile

concerning to the organization. To bring onto correct data in specific

suggestions and make them free to post their requirements to the

Registration department thus bringing the organization more specific

regarding the efficiency and the reliability of the ministry.

Moreover, the registration department of MOE should have the ability to

manipulate the data which is collected from the regions during the survey

then it will register, update/edit, Delete, search and print reports by using

this new system.

Finally, this system will facilitate more rigid works to simple way and it is easy

to use.


5/82

Abstract

This thesis concerned with the system of Minister of Education.

This software will support the officials to maintain a computerized database

management system to promote legal maintenance of managing the

students, Teachers and schools. This software solved many problems. In this

world there are many software of student registration to keeping records of

students, teachers and schools that manage it but this software is my little

struggle for betterment. This system provides information with accuracy,

reliability and high speed.

This is heavy database that should solve the daily routine of the ministrywhich may avoid the uncontrollable time that may loss manually management

activities, also the system has ability to correct errors from the user and

automatically handle duplicate records by using try and catch error exceptions

and primary key techniques respectively.


6/82

Ministry of Education

Organizational Profile

In Somaliland since Education is recognized as a fundamental tool that will

not only facilitate long term economic gains, but build the necessary human

resource to achieve this goal. The Ministry of Education in Somaliland is

branch is charged with overseeing public educational institutions in the

country it is the department which controls National Education Policy andsupports achievement of primary education for all children.

The political ahead of this department is the Minister of Education

Currently, Somaliland has over 450 primary schools with total enrollment of

108,995 students, (36% girls and 64% boys). In the years 1996/1997 there

were only 163 primary schools with a total enrollment of 33,000 students.

Somaliland has 5 universities and 3 colleges that provide higher education in

different fields of specialization including medicine

Though progress has been made in education the issues of access, equity and

quality of education continue to be a key challenge to education in

Somaliland, and the lack of International recognition contributes to

inadequate international funding to support policy implementation. The UN

and INGOs have minimally continued to supplement government and

communities in Education.


7/82

System Analysis

PURPOSE OF THE STUDY:


8/82

The MOE1 is a powerful application designed to allow ministry to streamline

their manipulation tasks and manage their students, teachers and schools

more efficiently.

Student Information

Teacher Information

School Information

The MOE complete guide application includes a comprehensive student

information database, teacher information, school information, and school

and teacher Assessment. It comes standard with those three to access

allowing them to be updated their personal information, request time off or

input their yearly assessment entries. It also has role based access level

control that is functionally based on whether a user is a student, a teacher, or

a ministry Employee. With MOE database managers and ministry

Administrators can manage and track

1) MOE: Ministry of Education


9/82

1.1.4 OBJECTIVE OF THE STUDY:

To develop a software application that supports Specifics of the MOE

Automation in a network of the ministry there by allowing the interaction of

all the above mentioned entities appertaining to that organization. To keep

track of all the other departments related to that organization like regional

processes, Exam Board etc.

To allow the Reg. department of an ministry to update the students details

whenever there is a new change in the student profile referring to that

organization.

SCOPE OF THE STUDY:

Allow for the creation of an application specification to the registration

department that maintain the technology automation of the MOEAS4 software

i.e., which contains the data related to the Students.

PROJECT OVERVIEW AND LIMITTIONS:

This project can be used to identify the three entities in the MOE1. The

project maintains the details of the entire Entities2. Each Entity is given with

different special unique Id.

In this I can use the vb.net language. Back end is MS-Access. Duration of this

project was 4 months. I was discussed the total modules of REG3 department.

Limits are more. In this project I was taken only REG department from MOE

2) Entities: Student, Teachers, School

3) REG: Registration Department4) MOEAS: Ministry of Education


10/82

EXISTING SYSTEM

Ministry of Education Registers Students, Teacher, and Schools in all regions in

the country as Region wise but this system is manual and it is time consuming

and very lazy, this system is more prostrate to errors and sometimes the

approach to various problems is unstructured.

The MOE Administration falls short of controlling the students data during the

exam, teachers data during the Salary payment and Schools Data in analyzing

time for their strengths and weakness. The decision for appraisal of assigning

next project to the Ministry or to train them to enhance the skills where lies

with proper projection. They are not provided with the detailed projectinformation done or to be assigned based on Application / Verticals.

DRAWBACKS IN EXISTING SYSTEM:

Need of extra manual effort.

It used to take much time to find any Student, Teacher or School data

Not much accurate.

Danger of losing the files in some cases.

Un reliable and non efficient

PROPOSED SYSTEM

With the advent of latest technology if we do not update our system then our

business results in losses gradually with time. The technical systems contains

the tools of latest trend i.e. computers printers, which are almost available in

there but not used as needed. The systems with this technology will be very

fast, accurate, user-friendly and reliable.


11/82

Decision in assigning proper skillful hands for the project is an important issue

in MOE Module. The MOE Administrator should report with the student holding

the necessary data required for the project assignment. The decision in

making analysis about the students data, schools and teachers skills are a

prime important before booting in.

The proposed system of MOE Module is the right software to be incorporated

into the Automation of MOE Software for helping the ministry needs with

respect to skilful of Management Resource.

The proposed system provides detailed general information about the three

mentioned entities along with Educational, Certification, Skill and Assessment

details. It enhances the MOE Management in adding, viewing and updatingthe entities details and generates various reports regarding Students Data,

teachers skills and experiences and schools Assessments.

ADVANTAGES OF PROPOSED SYSTEM:

Very fast and accurate.

No need of any extra manual effort.

No fever of data loss.

Just need a little knowledge to operate the system.

Doesnt require any extra hardware device.

At last very easy to find any Student, Teacher or School data.

Data Entry and report retrieving from anywhere to any place


12/82

Project Requirement Specification:The project requirement specification is comprised of the entire requirement

which we needed to develop our client server application.

Following specifications are included.

Hardware specification

Software specification H

Software Specification:

Language : VB.NET, ADO.NET.

Database : MS ACESS

Operating System : WindowsNT/95/98/2000

RAM : 256MB

Hard ware Specification:

Processor : Intel P-III based system

Processor Speed : 250 MHz to 833MHz

RAM : 64MB to 256MB

Hard Disk : 2GB to 30GB

Key Board : 104 keys

Mouse : SP2/USB


13/82

FEASIBILITY STUDY

Once the problem is clearly understood, the next step is to conduct

feasibility study, which is high-level capsule version of the entered systems

and design process. The objective is to determine whether or not the

proposed system is feasible. The Four tests of feasibility have been carried

out.

Technical Feasibility

Economical Feasibility

Operational Feasibility

Challenge Feasibility

TECHNICAL FEASIBILITY

In Technical Feasibility study, one has to test whether the proposed

system can be developed using existing technology or not. It is planned to

implement the proposed system using VB.NET technology. It is evident that

the necessary hardware and software are available for development and

implementation of the proposed system. Hence, the solution is technically

feasible.

ECONOMICAL FEASIBILITY

According to now the manual scheme of system operates much cost of the

system this cost comprises Salary of much Staff, stationary, including (huge

shelves), building etc. But the new system will Get rid of much about those

As part of this, the costs and benefits associated with the proposed system

compared and the project is economically feasible only if tangible or

intangible benefits outweigh costs. The system development costs will be

significant. So the proposed system is economically feasible.


14/82

OPERATION FEASIBILITY

It is a standard that ensures interoperability

The new solution is feasible in all sense but operationally it is not. The new

system may demand the expulsion of much staff from the MOE. It creates an

environment of joblessness and fear among the employees. It can lead to an

indefinite strike in the organization also. So the management must take

corrective actions prior in advance in order to start the further proceedings.

In another way, without stifling competition and innovation among users, to

the benefit of the public both in terms of cost and service quality. The

proposed system is acceptable to users. So the proposed system is

operationally feasible.

CHALLENGE FEASIBILITY

As we aware of the developed countys such important organizations doesnt

use this ambiguity bulky and ridicules system cause of retrieving data from

such system is hard and getting harder and harder day after day, thus the

new system is bravely Challengeable and feasible.


15/82

Special Features Language

Front End

MicrosoftVisual Basic .NET

The Microsoft Visual Basic .NET programming language is a high-level

programming language for the Microsoft .NET Framework. Although it is

designed to be an approachable and easy-to-learn language, it is alsopowerful enough to satisfy the needs of experienced programmers. The Visual

Basic .NET programming language is closely related to the Visual Basic

programming language but the two languages are not the same. A discussion

of the differences between Visual Basic .NET and Visual Basic 6.0 is beyond

the scope of this document.

The Visual Basic .NET programming language has a syntax that is similar to

English, which promotes the clarity and readability of Visual Basic .NET code.

Wherever possible, meaningful words or phrases are used instead of

abbreviations, acronyms, or special characters. Extraneous or unneeded

syntax is generally allowed but not required.

The Visual Basic .NET programming language can be either a strongly typed

or a loosely typed language. Loose typing defers much of the burden of type

checking until a program is already running. This includes not only type

checking of conversions but also of method calls, meaning that the binding of

a method call can be deferred until run-time. This is useful when building

prototypes or other programs in which speed of development is more

important than execution speed. The Visual Basic .NET programming

language also provides strongly typed semantics that performs all type

checking at compile-time and disallows run-time binding of method calls. This


16/82

guarantees maximum performance and helps ensure that type conversions

are correct.

This is useful when building production applications in which speed of

execution and execution correctness is important.

This document describes the Visual Basic .NET language. It is meant to be a

complete language description rather than a language tutorial or a user's

reference manual.

What is .NET?

This is a loaded question, but what it really comes down to is that .NET

means different things to different people. Much of what Microsoft is now

offering has the .NET name somewhere in its title, but what .NET means

really depends on whom you ask. The official one-line answer is that .NET is

Microsofts platform for XML Web services.

Microsofts .NET Framework is a new computing platform built with the

Internet in mind, but without sacrificing the traditional desktop application

platform.

The Internet has been around for a number of years now, and Microsoft has

been busy developing technologies and tools that are totally focused on it.

These earlier technologies, however, were built on Windows DNA (Distributed

internet Applications Architecture), which was based on COM (Component

Object Model). Microsofts COM was in development many years before the

Internet became the force that we know today. Consequently, the COM model


17/82

has been built upon and added to in order to adapt it to the changes brought

about by the Internet.

With the .NET Framework, Microsoft built everything from the ground up with

Internet integration as the goal. Building a platform from the ground up also

allowed the .NET Framework developers to look at the problems and

limitations that inhibited application development in the past and to provide

the solutions that were needed to quickly speed past these barriers.

ACTIVE X DATA OBJECTS

In Visual Basic .Net, three data access interfaces are available: Active

X Data Objects (ADO), Remote Data Objects (RDO) and Data Access Objects

(DAO). These access interfaces are used to access the data from database.

Why use ADO?

Consistently accessing data within the enterprise is a challenge for

today's business applications. ODBC provides the first step toward

overcoming this challenge by enabling applications to access relational

databases. However, as developers and system architects want to include no

relational data sources and to work in environments such as the Internet,

they encounter the dilemma of either developing their own data-access

paradigms or working with application program interfaces (APIs) that are

incompatible in the new environments. Microsoft ActiveX Data Objects

(ADO) along with OLEDB solves this dilemma by providing a single model that

works with all data sources in a variety of environments.

ADO provides consistent, high-performance access to data, whether

you're creating a front-end database client or middle-tier business object


18/82

using an application, tool, language, or even an Internet browser. ADO is the

single data interface you need for developing 1- to n-tier client/server and

Web-based, data-driven solutions.

This paper introduces ADO and the ADO programming model for

application developers who are targeting Microsoft SQL Server. Particular

attention is given to taking advantage of SQL Server features with ADO, such

as stored procedures and server cursors. The concepts presented in the sections

titled "The ADO Object Model" and "Using ADO with Visual Basic, VBScript, Visual C+

+, and Java" are applicable to all ADO programmers.

ADO Overview

ADO was first introduced as the data access interface in Microsoft

Internet Information Server (IIS). ADO is easy to use because it is called

using a familiar metaphor: the Automation interface, available from just

about any tool and language on the market today. Because of its popularity

as an easy-to-use, lightweight interface to all kinds of data, and the growing

need for an interface spanning many tools and languages, ADO is being

enhanced to combine the best features of, and eventually replace, RDO and

DAO, the data access interfaces in widest use today. ADO is in many ways

similar to RDO and DAO. For example, it uses similar language conventions.

ADO provides simpler semantics, which makes it easy to learn for today's

developers.

ADO is designed to be the application-level interface to OLEDB,

Microsoft's newest and most powerful data access paradigm. OLEDB provides

high-performance access to any data source. Together ADO and OLEDB form

the foundation of the Universal Data Access strategy. OLEDB enables

universal access to any data. ADO makes it easy for developers to program.

Because ADO is built on top of OLEDB, it benefits from the rich universal data

access infrastructure that OLEDB provides.


19/82

OLEDB Overview

OLEDB is an open specification designed to build on the success of ODBC

by providing an open standard for accessing all kinds of data throughout

the enterprise. OLEDB is a core technology supporting universal data

access. Whereas ODBC was created to access relational databases, OLEDB

is designed for the relational and non relational information sources, such

as mail stores, text and graphical data for the Web, directory services, and

IMS and VSAM data stored in the mainframe. OLEDB components consist

of data providers, which expose data; data consumers, which use data;

and service components, which process and transport data (for example,

query processors and cursor engines). These components are designed to

integrate smoothly to help OLEDB component vendors quickly bring high-

quality OLEDB components to market. OLEDB includes a bridge to ODBC to

enable continued support for the broad range of ODBC relational database

drivers available today.

OLEDB Providers

There are two types of OLEDB applications: consumers and providers. A

consumer can be any application that uses or consumes OLEDB interfaces.

For example, a Microsoft Visual C++ application that uses OLEDB interfaces

to connect to a database server is an OLEDB consumer. The ADO object

model that uses OLEDB interfaces is an OLEDB consumer. Any application

that uses the ADO object model uses OLEDB interfaces indirectly through the

ADO objects. An OLEDB provider implements OLEDB interfaces; therefore, anOLEDB provider allows consumers to access data in a uniform way through a

known set of documented interfaces. In a sense, an OLEDB provider is similar

to an ODBC driver that provides a uniform mechanism for accessing relational

data.


20/82

OLEDB providers not only provide a mechanism for relational data but

also for non relational types of data. Furthermore, OLEDB providers are built

on top of Component Object Model (COM) interfaces that allow more

flexibility; whereas ODBC drivers build on top of a C API specification.

Microsoft OLEDB SDK version 1.1 shipped two OLEDB providers: the ODBC

Provider and sample text provider. The sample text provider is an example

that demonstrates the implementation detail of an OLEDB provider. The

ODBC Provider is an OLEDB provider for ODBC drivers. This provider enables

consumers to use the existing ODBC drivers without having to implement new

OLEDB providers to replace existing ODBC drivers. With OLEDB version 2.0,

providers for SQL Server, Oracle data, and Microsoft Jet databases were

added to the SDK. For more information about OLEDB and OLEDB providers,

see the OLEDB section of the Microsoft Data Access

Crystal Reports

Crystal Reports for Visual Basic .NET is the standard reporting tool for Visual

Basic.NET; it brings the ability to create interactive, presentation-quality

content which has been the strength of Crystal Reports for years to

the .NET platform.

With Crystal Reports for Visual Basic.NET, you can host reports on Web and

Windows platforms and publish Crystal reports as Report Web Services on a

Web server.

To present data to users, you could write code to loop through record-sets

and print them inside your Windows or Web application. However, any work

beyond basic formatting can be complicated: consolidations, multiple level

totals, charting, and conditional formatting are difficult to program.


21/82

With Crystal Reports for Visual Studio .NET, you can quickly create complex

and professional-looking reports. Instead of coding, you use the Crystal

Report Designer interface to create and format the report you need. The

powerful Report Engine processes the formatting, grouping, and chartingcriteria you specify.

Report Experts

Using the Crystal Report Experts, you can quickly create reports based on

your development needs:

Choose from report layout options ranging from standard reports to

form letters, or build your own report from scratch.

Display charts that users can drill down on to view detailed report data.

Calculate summaries, subtotals, and percentages on grouped data.

Show Top or Bottom results of data.

Conditionally format text and rotate text objects.


22/82

Back End

Microsoft Access

Access is an interactive, relational database management system. A database

is an organized collection of data stored in categories that are accessible in a

logical or practical manner.

Relational databases enable data to be stored in multiple tables linked

together via data indexes. This makes working with the data faster and

easier. Once entered into the database, the data may be manipulated or

viewed in various ways such as by sorting or by specially set-up queries and

reports.

A full-featured procedural programming language essentially a subset of

Visual Basic,

A simplified procedural macro language unique to Access;

A rapid application development environment complete with visual form

and report development tools;

A sprinkling of objected-oriented extensions; various wizards and

builders to make development easier.

For new users, these multiple personalities can be a source of

enormous frustration. The problem is that each personality is based on

a different set of assumptions and a different view of computing. For

instance,

The relational database personality expects you to view your application

as sets of data;


23/82

SYSTEM DESIGN


24/82

Introduction

Introduction of system design

Systems design is the process or art of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements.

One could see it as the application of systems theory to product development.

There is some overlap with the disciplines of systems analysis, systems

architecture and systems engineering.

Based on the user requirements and the detailed analysis of a new system,the new system must be designed. This is the phase of system designing. It is

a most crucial phase in the development of a system. Normally, the design

proceeds in two stages :

preliminary or general design

Structure or detailed design

Preliminary or general design: In the preliminary or general design, the

features of the new system are specified. The costs of implementing thesefeatures and the benefits to be derived are estimated. If the project is still

considered to be feasible, we move to the detailed design stage.

Structure or Detailed design: In the detailed design stage, computer oriented

work begins in earnest. At this stage, the design of the system becomes more

structured. Structure design is a blue print of a computer system solution to a

given problem having the same components and inter-relationship among the

same components as the original problem.


25/82

Input, output and processing specifications are drawn up in detail. In the

design stage, the programming language and the platform in which the new

system will run are also decided.

There are several tools and techniques used for designing. These tools andtechniques are:

Flowchart

Data flow diagram (DFDs)

Data dictionary

Structured English

Decision table

Decision tree

DATA BASE DESGIN

A database is an integrated collection of logically related records or files which

consolidates records into a common pool of data records that provides data

for many applications. A database is a collection of information that is

organized so that it can easily be accessed, managed, and updated.

In one view, databases can be classified according to types of content:

bibliographic, full-text, numeric, and images.

The data in a database is organized the data according to a database model.

The model that is most commonly used today is the relational model.

Other models such as the hierarchical model and the network model use a

more explicit representation of relationships.
http://en.wikipedia.org/wiki/Database_modelhttp://en.wikipedia.org/wiki/Relational_modelhttp://en.wikipedia.org/wiki/Hierarchical_modelhttp://en.wikipedia.org/wiki/Network_modelhttp://en.wikipedia.org/wiki/Database_modelhttp://en.wikipedia.org/wiki/Relational_modelhttp://en.wikipedia.org/wiki/Hierarchical_modelhttp://en.wikipedia.org/wiki/Network_model


26/82

DBA (DATABASE ADMINISTRATOR)

The DBA is the person responsible for the operation,

configuration and performance of the database. The DBA is charged with

keeping the database operating smoothly, ensuring that backups are done on

regular basis (and that backups work), and installing new software. Other

responsibilities might include planning for future expansion and disk space

needs, creating databases and table spaces, adding users and maintaining

security, and monitoring the database and retuning it as necessary. Large

installations might have teams of DBAs to keep the system running

smoothly; alternatively, the task might be segmented among the DBAs.

UML DIAGRAMS

UNIFIED MODELING LANGUAGE

UML is the international standard notation for object-oriented analysis and

design. The Object Management Group defines it. The heart of object-

oriented problem solving is the construction of a model. The model abstracts

the essential details of the underlying problem from its usually complicated

real world. Several modeling tools are wrapped under the heading of the

UML, which stands for Unified Modeling Language.


27/82

AN OVERVIEW OF UML:

The UML is a language for

Visualizing Specifying

Constructing

Documenting

These are the artifacts of a software-intensive system. The three major

elements of UML are

The UMLs basic building blocks

The rules that dictate how those building blocks may be put together.

Some common mechanisms that apply throughout the UML.

BASIC BUILDING BLOCKS OF THE UML:

The vocabulary of UML encompasses three kinds of building blocks:

Things

Relationships Diagrams

Things are the abstractions that are first-class citizens in a model.

Relationships tie these things together.

Diagrams group the interesting collection of things.


28/82

THINGS IN THE UML:

They are the abstractions that are first-class citizens in a model. There are

four kinds of things in the UML1. Structural things

2. Behavioral things.

3. Grouping things.

4. Notational things.

These things are the basic object oriented building blocks of the UML. They

are used to write well-formed models.

STRUCTURAL THINGS:

Structural things are the nouns of the UML models. These are mostly static

parts of the model, representing elements that are either conceptual or

physical. In all, there are seven kinds of Structural things.

CLASS:A class is a description of a set of objects that share the same attributes,

operations, relationships, and semantics. A class implements one or more

interfaces. Graphically a class is rendered as a rectangle, usually including its

name, attributes and operations, as shown below.


29/82

INTERFACE:

An interface is a collection of operations that specify a service of a class or

component. An interface describes the externally visible behavior of that

element.

Graphically the interface is rendered as a circle together with its name.

ISpelling

COLLABORATION:

Collaboration defines an interaction and is a society of roles and other

elements that work together to provide some cooperative behavior thats

bigger than the sum of all the elements. Graphically, collaboration is rendered

as an ellipse with dashed lines, usually including only its name as shown

below.

Chain

Chain of Responsibility


30/82

USE CASE:

Use case is a description of a set of sequence of actions that a system performs that

yields an observable result of value to a particular thing in a model. Graphically, Use

Case is rendered as an ellipse with dashed lines, usually including only its name as

shown below.

ACTIVE CLASS:

An active class is a class whose objects own one or more processes or

threads and therefore can initiate control activity. Graphically, an active class

is rendered just like a class, but with heavy lines usually including its name,

attributes and operations as shown below.

Place Order

HRMS

EMPLOYEE

DEATILS


31/82

orderform.java

server

COMPONENT:

Component is a physical and replaceable part of a system that conforms to

and provides the realization of a set of interfaces. Graphically, a component is

rendered as a rectangle with tabs, usually including only its name, as shown

below.

NODE:

A Node is a physical element that exists at run time and represents a computational

resource, generally having at least some memory and often, processing capability.

Graphically, a node is rendered as a cube, usually including only its name, as shown

below.

BEHAVIORAL THINGS:

Behavioral Things are the dynamic parts of UML models. These are the verbs of a

model, representing behavior over time and space.


32/82

INTERACTION:

An interaction is a behavior that comprises a set of messages exchanged

among a set of objects within a particular context to accomplish a specific

purpose. Graphically, a message is rendered as a direct line, almost always

including the name if its operation, as shown below.

Display

STATE MACHINE:

A state machine is a behavior that specifies the sequence of states an object are an

interaction goes through during its lifetime on response to events, together with its

responses to those events. Graphically, a state is rendered as a rounded rectangle

usually including its name and its sub-states, if any, as shown below.

GROUPING THINGS:

Grouping things are the organizational parts of the UML models. These are the boxes

into which a model can be decomposed.

Waiting


33/82

PACKAGE:

A package is a general-purpose mechanism for organizing elements into

groups.

ANNOTATIONAL THINGS:

Annotational things are the explanatory parts of the UML models.

Note:

A note is simply a symbol for rendering constraints and comments attached to

an element or a collection of elements.

Graphically a note is rendered as a rectangle with dog-eared corner together,

with a textual or graphical comment, as shown below.

Business Rules


34/82

RELATIONSHIPS IN THE UML:

There are four kinds of relationships in the UML:

1. Dependency

2. Association

3. Generalization

4. Realization

1. DEPENDENCY:

This is relationship between two classes whenever one class is completely

dependent on the other class. Graphically the dashed line represents it with arrow

pointing to the class that it is being depended on.

2. ASSOCIATION: It is a relationship between instances of the twoclasses. There is an association between two classes if an instance of one class

must know about the other in order to perform its work. In a diagram, an

association is a link connecting two classes. Graphically it is represented by line

as shown.


35/82

3. GENERALIZATION:

An inheritance is a link indicating one class is a super class of the other. A

generalization has a triangle pointing to the super class. Graphically it is

represented by line with a triangle at end as shown.

5. REALIZATION:

DIAGRAMS IN UML:

Diagrams play a very important role in the UML. There are nine kind of modeling

diagrams as follows:

Use Case Diagram

Class Diagram

Object Diagram

Sequence Diagram

Collaboration Diagram

State Chart Diagram

Activity Diagram

Component Diagram

Deployment Diagram

CLASS DIAGRAM:

Class diagrams are the most common diagrams found in modeling object-

oriented systems. A class diagram shows a set of classes, interfaces, and

collaborations and their relationships. Graphically, a class diagram is a

collection of vertices and arcs.


36/82

Contents:

Class Diagrams commonly contain the following things:

Classes

Interfaces

Collaborations

Dependency, generalization and association relationships

USE CASES DIAGRAM:

Use Case diagrams are one of the five diagrams in the UML for modeling the

dynamic aspects of systems(activity diagrams, sequence diagrams, state

chart diagrams and collaboration diagrams are the four other kinds of

diagrams in the UML for modeling the dynamic aspects of systems). Use Case

diagrams are central to modeling the behavior of the system, a sub-system,

or a class. Each one shows a set of use cases and actors and relationships.

COMMON PROPERTIES:

A Use Case diagram is just a special kind of diagram and shares the same common

properties, as do all other diagrams- a name and graphical contents that are a

projection into the model. What distinguishes a use case diagram from all other

kinds of diagrams is its particular content.


37/82

ContentsUse Case diagrams commonly contain:

Use Cases

Actors

Dependency, generalization, and association relationships

Like all other diagrams, use case diagrams may contain notes and constraints. Use

Case diagrams may also contain packages, which are used to group elements of your

model into larger chunks. Occasionally, you will want to place instances of use cases

in your diagrams, as well, especially when you want to visualize a specific executing

system.INTERACTION DIAGRAMS

An Interaction diagram shows an interaction, consisting of a set of objects and their

relationships, including the messages that may be dispatched among them.

Interaction diagrams are used for modeling the dynamic aspects of the system.

A sequence diagram is an interaction diagram that emphasizes the time

ordering of the messages. Graphically, a sequence diagram is a table that

shows objects arranged along the X-axis and messages, ordered in increasing

time, along the Y-axis and messages, ordered in increasing time, along the Y-

axis.

Contents

Interaction diagrams commonly contain:

Objects

LinksMessages

Like all other diagrams, interaction diagrams may contain notes and

constraints.


38/82

LOGIN FORMUSERNAME

PASSWORD

STUDENT-REGFirst NameLast Name

School NameClassYear

MAIN FORMSTUDENT REGTEACHER-REG

TEACHER-ASSESSCHOOL-REGSCHOOL -ASSES

TEACHER-REGFirst NameLast Name

SubjectRegionSchool Name

SCHOOLASSESS

School NameRegionYearRegion

SCHOOL-REGSchool name

RegionSchool TypeSchool LangLocation

DATA BASE DESIGN

CLASS DIAGRAM

TEACHER-Assess

FirstName

LastName


39/82

OBJECT DIAGRAM

USE CASE DIAGRAM

Logi


40/82

Activity Diagrams

MOE Staff MOEAS Operator

UserAdd

Add Teacher

Add School Teacher

Add School


41/82

GetsData

Begin the DataEntry

Add all the data toDatabase

GetsInformation

CollectsInformation

Submits To Operators

DATA FLOW DIAGRAMS:

A graphical tool used to describe and analyze the moment of data through a system

manual or automated including the process, stores of data, and delays in the

system. Data Flow Diagrams are the central tool and the basis from which other

components are developed. The transformation of data from input to output,

through processes, may be described logically and independently of the physical

components associated with the system. The DFD is also know as a data flow graph

or a bubble chart.

CONTEXT DIAGRAM:

The top-level diagram is often called a context diagram. It contains a single

process, but it plays a very important role in studying the current system. The

context diagram defines the system that will be studied in the sense that it

determines the boundaries. Anything that is not inside the process identified in the

context diagram will not be part of the system study. It represents the entire

software element as a single bubble with input and output data indicated by

incoming and outgoing arrows respectively.

TYPES OF DATA FLOW DIAGRAMS:

Data Flow Diagrams are of two types as follows:

(a)Physical DFD

(b)Logical DFD


42/82

PHYSICAL DFD:

Structured analysis states that the current system should be first

understand correctly. The physical DFD is the model of the current system and is

used to ensure that the current system has been clearly understood. Physical

DFDs shows actual devices, departments, and people etc., involved in the current

system

2. LOGICAL DFD:

Logical DFDs are the model of the proposed system. They clearly should

show the requirements on which the new system should be built. Later during

design activity this is taken as the basis for drawing the systems structure

charts.

BASIC NOTATION:

The Basic Notation used to create a DFDs are as follows:

DATAFLOW:

Data move in a specific direction from an origin to a destination.

PROCESS

People, procedures, or devices that use or produce (Transform) Data. The physicalcomponent is not identified.


43/82

SOURCE:

External sources or destination of data, which may be People,

programs, organizations or other entities.

DATA STORE:

Here data are stored or referenced by a process in

theSystem

DESIGN:

Design is the first step in moving from problem domain to the solution domain.

Design is essentially the bridge between requirements specification and the final

solution.

The goal of design process is to produce a model or

representation of a system, which can be used later to build that

system. The produced model is called the Design of the System. It is a plan for a

solution for the system.


44/82

Operator/UserEmployeeMOEAS

Process Flow Diagram

Is anManages


45/82

LOGINPROC

ESS

ERROR ININPUT

SCREEN

CONTEXT FLOW DIAGRAM

Description:

Context Flow Diagram gives us the complete details about the inputs and outputs for

a given system. In the above system the main task is to identify a criminal face. So,

the operator and eyewitness are the inputs to our system and criminal face is

desired output.

User id

Creates

Creates

Creates Details

Creates

Creates

Student Reg

Teacher Reg

Teacher

Assessment

School

Registration

School

Assessment


46/82

Password

Description:

The inputs to the process are User Id and Password given by the developer to allow

the software available for the Admin environment. After giving the inputs the details,

checks whether the entered ones are valid are not. It displays screen if match occurs

otherwise error message if they are not matched.


47/82

MAINSCREEN

ADMIN Studetn RegTeacherRegistration

TeacherAssessments

SchoolRegistration

SchoolAssessment

MAIN SCREEN PROCESS

Description:

This process mainly explains the different screens that are available for the admin.

Here the selection of the screen depends on the admin and he can select whatever

screen he wants. The different screens that are available are Student Registration,

Teacher Registration, Teacher Assessment, School Registration and School

Assessment


48/82

Operator/UserTeachers Report

Add Teacher Details

Description:

Create


49/82

This process clearly illustrates adding the details of the teacher such as full name,

gender, school name, and address along with his teacher Id. These details are being

added to the database, if any error is generated then it will be prompted to the

admin otherwise we get message data is successfully added.

Add Student Report


50/82

Add StudentReport

AdminDATABASEDATA IS ADDED


51/82

Description:

This process clearly illustrates adding the details of the student Report such as full

name, gender, class, year, and etc with his student Id. These details are being added

to the database, if any error is generated then it will be prompted to the admin

otherwise we get message data is successfully added.

Add School Report


52/82


53/82

Description:

This process clearly examples adding the details of the schools such as school name,

region, school type, school language and location. These details are being added to

the database, if any error is generated then it will be prompted to the admin

otherwise we get message data is successfully added.


54/82

Add Teacher Assessment


55/82

Admin AddTeacherAssessment

DATA UPDATEDDATABASE


56/82

Description:

This process clearly exemplifies adding the details of the Teacher Assessment such

as full name, gender, level, qualification, Institute, Year, Number of teaching

subjects, Major, Manor, classes he/she teaches, Region and School name and along

with his/her Teacher Id. These details are being added to the database, if any fault is

generated then it will be prompted to the admin otherwise we get message data is

successfully added


57/82


58/82

Types of Normalization:

First Normal Form (1NF)

Second Normal Form (2NF)

Third Normal Form (3NF)

Boyce-Codd normal form (BCNF)

Fourth Normal Form (4NF)

Fifth Normal Form (5NF)

Domain/Key Normal Form (DKNF) Sixth Normal Form (5NF)

Used Normal Forms:First Normal Form: is a normal form used in database normalization. A

relational database table that adheres to 1NF is one that meets a

certain minimum set of criteria. These criteria are basically concerned

with ensuring that the table is a faithful representation of a relation

Why I selected First Normal Form is:I have selected 1NF because I need there shouldnt be duplicate records

in the project tables due to the data integrity and 1NF supports these:

1. There's no top-to-bottom ordering to the rows.

2. There's no left-to-right ordering to the columns.

3. There are no duplicate rows.

4. Every row-and-column intersection contains exactly one value from

the applicable domain (and nothing else).

5. All columns are regular [i.e. rows have no hidden components such

as row IDs, object IDs, or hidden timestamps.
http://en.wikipedia.org/wiki/Database_normalizationhttp://en.wikipedia.org/wiki/Relational_databasehttp://en.wikipedia.org/wiki/Table_(database)http://en.wikipedia.org/wiki/Relation_(mathematics)http://en.wikipedia.org/wiki/Database_normalizationhttp://en.wikipedia.org/wiki/Relational_databasehttp://en.wikipedia.org/wiki/Table_(database)http://en.wikipedia.org/wiki/Relation_(mathematics)


59/82


60/82

RDBMS:Database Tables:

Login Table

In computer security, login is the process by which the users should pass the

Authentication security or access the system it should be controlled by

identification of the user using credentials provided by the Administrators. A

user can log in to a system to obtain access, It should match together the left

party usernames and their parallel passwords then the Authentication should

be correct if only they are correctly matched other wiser it should appear the

below message.
http://en.wikipedia.org/wiki/Computer_securityhttp://en.wikipedia.org/wiki/Accesshttp://en.wikipedia.org/wiki/Computer_systemhttp://en.wikipedia.org/wiki/User_(computing)http://en.wikipedia.org/wiki/Credentialhttp://en.wikipedia.org/wiki/Computer_securityhttp://en.wikipedia.org/wiki/Accesshttp://en.wikipedia.org/wiki/Computer_systemhttp://en.wikipedia.org/wiki/User_(computing)http://en.wikipedia.org/wiki/Credential


61/82

Schools Registration Table

this is the Table which is used to register all schools in the country it has

the name of SchoolReg it accepts data from a Visual Basic Form this

table consists of five important columns that are SchoolName, Region,

SchoolLanguage, Schooltype, and Location which all has text data type .


62/82


63/82

Teacher Registration TableAccording to the rules of Ministry of Education (MOE) Teachers must be registered

before they teach in public Schools.


64/82


65/82


66/82

Teacher Assessment Table


67/82

It is the mandatory process in Somaliland that all incoming students go through

Registration step before being able to attend classes. So Ministry of Education

Department of High school registration registers all high school students.

This table is where MOE Automation registers the students; it has various important

columns which are used to keep information of the students which is important to

known in order to identify certain information about student

Column name Data Type Description

ID Text The unique identity of the teacher

FirstName Text

MiddleName Text

LastNAme TextGender Text

Region Text

SchoolName Text

Class Text

Year Number
http://en.wikipedia.org/wiki/Studentshttp://en.wikipedia.org/wiki/Class_(education)http://en.wikipedia.org/wiki/Studentshttp://en.wikipedia.org/wiki/Class_(education)


68/82

nterface design

The first step in the software designing is the Interface design. We

have lot of problems that should be in the interface howto design

a user friendly interface finally we have some idea from the other

softwares t how to develop it. Control and Design of Interface of

theApplication Forms. The forms are the classes that hold many

objects they can besaid the containers that hold deferent controls

form is the key element in thesystem. Administrator form Simple

Form MDI Form Menu. Menu is the drop down listof elements auser can easily access it. File Menu Policy

Advantages of Interface Designing

The interface is the designed screen in any powerful language, to

store, manipulate, access and retrieve data easily. This part of the

system provides facilities to the users of the system. The interface

of the MOE System is designed in the most powerful language

called Microsoft Visual Basic.Net 2005. The interface is the user-

friendly environment that everyone can use easily. The importance

of good user interface design can be the difference between

product acceptance and rejection in the marketplace. If end-users

feel it is not easy to learn, not easy to use, or too cumbersome, an

otherwise excellent product could fail. Good User Interface Design

can make a product easy to understand and use, which results in

greater user acceptance.


69/82


70/82

Testing Phase


71/82

TESTING PHASE

The testing phase involves the testing of the developed system

using various kinds of data. An elaborated testing of data is prepared and a

system is tested using the test data. While testing, errors are noted and

corrections remade, the corrections are also noted for future use.

SYSTEM TESTING

Testing is a set of activities that can be planned in advance and

conducted systematically. The proposed system is tested in lonely because

there were no software consisting of its own in the analyst phase Following

are the tests conducted on the system.

UNIT TESTING

During the implementation of the system each module of the system

was tested separately to uncover errors within its boundaries. User interface

was used as a guide in the process.

MODULE TESTING

A module is composed of various programs related to that module. Module

testing is done to check the module functionality and interaction between

units within a module.


72/82

It checks the functionality of each program with relation to other programs

within the same module. It then tests the overall functionality of each

module.

INTEGRATION TESTING

Integration testing is a systematic technique for constructing the

program structure while conducting tests to uncover errors associated with

interfacing. The objective is to take unit-tested module and build a program

structure that has been dictated by design.

ACCEPTANCE TESTING

The software has been tested with the realistic data given by the client

and produced fruitful results. The client satisfying all the requirements

specified by them has also developed the software within the time limitation

specified. A demonstration has been given to the client and the end-user

giving all the operational features.


73/82

Implementation


74/82


75/82

Main Form

SCHOOL REGISTRATION FROM


76/82

TEACHERS REGERTRATION FORM


77/82

Teacher Assessment Form


78/82

Teacher Registration Form


79/82


80/82

Teacher Registration Form


81/82

Searches Reports and Skin


82/82

END

Documents

Ministry of Education Database System. By- Abdirashid Jeeni