SCHOOL OF COMPUTING SCIENCE DEPARTMENT OF ...mameamin.6te.net/.../11/dormitory-system-documentation.docx · Web viewRisk identification and management During the development of our

Chapter one

System proposal

1.1 Introduction As we are graduating class students, it is expected from us to develop a

project. So we have selected our project title intended to do on Dormitory

System. Office of Housing and Students Service has numerous roles in Debre

Birhan University (DBU) for the achievement of students’ service. From such

service, dormitory system, recreation service, café service, health service.

Among those services, dormitory service is one types of service that need for the

students. So our project concerned about this dormitory service. Basically, our

university gives dormitory service both female and male students separately.

During giving this service there is a lot of problems occur in assigning dorm

manually. Because of this, we are initiating to develop our project on dormitory

system in order to minimize the problem by using computerized system.

Dormitory system web site Page 1

1.2 Background Debre Bran University is situated in Amhara Regional State which is 130 km far

from Addis Ababa. It was established by Ministry of Education (MOE) in 1997

E.C, and has begun to give services for the students in 1998 E.C. And also

Office of Housing and Students Service was established, because dormitory

service is one of the important services for students. It gives dormitory services

for both regular and summer students. During gives this service, the proctor

assign the females and males students separately. Not only based on sex but

also the students is assigned in their dorm by their department. Currently, the

dormitory system was working 7550 bed rooms and have 50 staff

employees .the staff contain both females and males employees, the females

control the females students dormitory and the males control the males

dormitory. All of the activities are performed manually. The student’s dormitory

and their name lists are stamped on the block building. If it is so, it wastes the

time and cost of the university and less secure.

1.3 Statement of the problemThe dormitory system is one of the university student’s services that have so

many problems. Currently, all activities are performed full manual system (paper

based). This process of working procedure creates many problems these are:

Mixing of file each other (misplaced) which create difficult to searching and

time consuming

Losing of student’s files when transfer manual file place to place

Assigning the students in their dormitory manually is very tedious for the

assigner.

Mixing of different sex in same dorm when the time of assigning

Lack of file security

Lack of data integrity and leads to information redundancy

Lack of unavailability of accurate and up to date information and therefore

right decision could not be taken at the right time

Requires more labor to manage the data


Cross referencing is difficult and sometimes might get wrong decision

Physical damage of file due to dust, moisture and other cause.

1.4 Objective of the Project

1.4 .1General Objective

The general objective of this project is to develop dynamic web based

application for DBU Dormitory system. The newly developed web-based system

will improve the services rendered for students by the university.

1.4.2 Specific Objective

The specific objective of our project is that:

To improve the efficiency of assigning and distributing of the dorm

To minimizing the work load of the employees

To make suitable condition for the student and the employee

To announce the result of assigning dorm on time

To apply the best possible security technique to achieve security service

To minimize problem of human error during at the time of assigning dorm

To develop effective and efficient file management system(database)

1.5 Feasibility Analysis of the project A feasibility study is a preliminary study undertaken to determine and

document a project's practicality. We can say our project which is web based

application development for DBU dormitory system is feasible because it can

fulfill all the requirement of good software which are economical,

technical ,political, and operational feasible.

1.5.1. Operational Feasibility

Operational feasibility is the process of examining the possibility of the project

will achieve its desired objective. In our case, as we are the project team

members, the project that we are developing is to be operational feasible and the

project will be:

Any user can operate the system


User friendly

The proposed website will be easy and navigate the pages.

1.5.2. Technical Feasibility

Our project is technically feasible. Because everyone can access if the

access privilege is given .It is also compatible with modern technology. This

system is to be implemented in website by website users or students.

1.5.3. Economic Feasibility

After developing this project, it has its own benefit for the university members.

Since this project is going to dynamic web site, there is reduction cost for

material that used for manual operation, save time and make comfortable

working environment for the user.

1.5.4 Political feasibility

The political feasibility of our project in the university, it is acceptable for all

university employees or after developing the project there is no conflicts between

the employees and the university.

1.6 Scope of the project

Dormitory system has numerous roles, but it very difficult to cover all activities

in our project due to shortage of time and resource. So that our web based

application project only focused on the following features:

Accept and record students data

Accept and record the block data

Accept and record dormitory data

Accept and record proctors information

Assign student into their dormitory

Announce online for assignee students

Generate report

1.7. Limitation of the project

There are some limitations for this project. These are:


The users must have an internet connection when using this system

The page may not be effective in some browsers, as they may not support

the tools used.

The developed system needs educated manpower

The system is not functional if there is no light

1.8 Methodology

1.8.1System analysis and Design Methodology

We decide to use object-oriented methodology instead of structured approach,

object oriented approach is used for the project because it is more acceptable

due to its great advantage of Polymorphism, Abstraction, Encapsulation,

Modularity, inheritance, Hierarchy, Concurrency, Persistence, etc in terms of its:

Increased Extensibility

Increased Reusability

Improved Quality

Lesser maintenance cost and burden

Less complexity and application backlog

Increased chance of project success.

1 .8.2 Method of data collection

In our project, we have use two of data collection method. They are:

Primary data collection and Secondary data collection

i) Primary data collection

In primary data collection, we collect the data by the following methods, such as

interviews and Participatory observation.

a) Interview

This is one of the methods used for the collection of data in which the project

developers have the chance of asking different questions. We will conduct the

interview at work by going to the manager of Office of Housing and Student

service.


b) Participatory observation

This is another type of method for collecting data and information and also it is

the simplest way of gathering data in which we can witness the actual events

which will happen in the dorm services.

ii) Secondary data collection

From secondary data collection method, we use document analysis.

a) Document analysis

This method of data collecting is analyzing the document prepared in the

existing system. We analyzed different documents like forms and report samples

in the existing system.

1.8.3 Case tools

In our project, we use php programming language for front end development

environment. Because our project concerned with web based application and

php is more advisable to develop web based application. In case of back end

development environment, we use phpMYADMIN

1.8.4 Requirement structuring tools

Those are instruments which used for designing different figures and designs

VB SUITE 5.1: To design different diagrams like

Use case diagram

Activity diagram

Sequence diagram

Class diagram

Microsoft Office 2007: For documentation as word processor

1.9 Significance of the project

DBU dormitory system is one of the university student’s service systems. After

developing our project that has great significance:


1.9.1 for the university

This project has ultimate significance for the university and the employees of the

Office of Housing and Student Service by reducing:

Work load

Time and

Cost

1.9.2 for the students

After developing this project, the students will know where they are to be

assigned their dorm through online. So they get quality service from the university.

1.9.3 for the developers

We are developers of this project, so that from this project, we get enough

knowledge and experience how to develop such types of projects.

1.10 Motivation of the project

The reason that initiates us to develop this project is that we understand the

problem of our university dormitory services and in order to simplify the existing

problem. Besides of this as graduating students this kind project which requires

the implication of many course we studied which will helps us to know more

about the course and how they are practiced in the real world

1.11 Cost of the projectIn order to perform our project, we are estimated the following cost budget of

expenditure


1.11.1 Software development cost

For this particular project we will be using different software but the softwares

are getting from the university.

Software costs

Software Description Price

Microsoft office word 2007 Get from DBU

Microsoft power point 2007 Get from DBU

Microsoft SQL server Get from DBU

Microsoft /php Get from DBU

Avast !free antivirus Get from DBU

Vb suite 5.1 Get from DBU

xampp Get from DBU

Total 0 Birr

Table 1.1 Software cost


1.11.2 Hardware development cost

Hardware cost

No Name

Quantity

Unit price

in birr Total

1 Purchase of flash disk (4GB) 1 400.00 400.00

2 Purchase of floppy disk 4 8.00 32.00

3 Purchase of stationary

Paper

Pen

Pencil

Printing Cost

Photocopy

1pack

12

3

130page

390 pages

80.00

3.00

1.25

3.00

0.35

80.00

36.00

3.75

390.00

136.05

4 Purchase of CD-RW 2 20.00 40.00

5Purchase food 800.00

6 Purchase of CD-R 3 5.00 15.00

7 Miscellaneous expense 200.00

8 Total 2132.80

Table 1.2 cost budget of the project


1.12 Time schedule of the project For the time scheduling purpose, the Gant chart is being used in order to show a simple

indication for the project’s progress in each and every phase.

Activity November December January February March April may June

proposal

Require

ment

Analysis

System

design

Impleme

ntation

Present

ation

and final

submissi

on date

Table 1.3 Working plan of the project

1.13 Risk identification and management During the development of our project there may be accidents and problems that

may create a negative side effect in our progress those are:

There may a problem of light in the lab this cause not to finish the project in

the estimated schedules.

Our files and documents may be affecting by a virus and worms.


There may be accidents and diseases to one of our project mate this also

has a negative impact to our project

In general there may be problems that cause a negative influence during the

development of our project

1.14 Risk mitigation

In our project will may occur some problem, but we have to take immediate action

when the problem will occur like:

Take precondition for the problem

To protect our project from malicious thing like viruses, worms by loading

antivirus software on our computer system

Take backup this project in order to handle accidental problem

Chapter two Current system analysis

2.1. INTRODUCTION

This chapter deals with analyzing the purpose, goals, objectives and function of the

existing system. It produces a broad outline of the proposed system that identifies

the function to be performed and the technical aspects that the system must fulfill

and briefly describe the existing system functionality, problem of the existing

system. It also deals with the functional and non- functional requirements of the

proposed system. During this phase, the analysis must become full aware of the

root problems and must develop enough knowledge about the existing system to

enable an effective solution to be proposed. The first activity is assembling of the

formal requirement for the proposed system.

The second activity is logical modeling that allows the analysis to view the current

system by focusing on what is does instead of how it does.


2.2 Major Function Existing System

DBU dormitory system service has its own power and functions are:-

Accept the list of students from the registrar and record them

Distinguish the sex of students and recorded the name separately to assign

the dorm

Preparing and providing dorm for the student as they receive the list of the

student from the registrar.

Preparing reports for the students’ dean about general observable fact of

dormitory services.

Giving property clearing form for the students

2.3 Problems of the Existing system

Proctors perform their activities by using fully manual based system. The proctor

officer has no modern database management system. This process of working

procedure creates problems. These are:-

Performance Response time

Delay in producing different reports

Take too much time to find the students record

Information Input

Inaccurate capture of data – Data is handled in a way that is not

efficient for retrieval or processing purpose

Output Inaccuracy in updating important information because of manual

processing

Inconsistent result obtained from existing system

The student cannot make a direct online communications with the university through the website.


Less flow of information among several employees To provide information, it may take inevitably long time by

searching the necessary facts to which it is intended for.

Stored data Data is stored repeatedly in different files – The same information

is stored in many copies repeatedly in different forms.

Data is not secured. Due to this, some secret information is

opened for unauthorized users or agents.

File mixed each other (misplaced): Lose of students files during file transfer or data must be

inconsistency.

Economics Manual handling of data is expensive as compared to automated

system. In general, cost in terms of time is very high.

As the number of student increases, the existing manual system

will incur cost to handle those requirements.

As the number of employees to handle the task of manual

processing increases, the organization will spend a lot of money for

its staff.

Control High probability of losing important students documents due to

manual system

Data is highly exposed to unauthorized access and update.

Since data is stored in different places, it leads to data

inconsistency

Efficiency Time wastage

Employees waste time due to manual:-

Data processing.

Data entry

Report generation.

Preparation of different forms.

Communication between employees


Material wastage The organization wastes many materials especially concerning

stationery materials, and file cabinets

Services Inaccurate result of the existing system – If what the system takes

as an input generates an error, then this error can affect all levels

of divisions.

Inconsistent result of the existing system – Inconsistency in

decision-making with regard to dorm related matters of the

employees

Being a manual system, the existing system is not easy to use, and

rigid for new situations and changes.

2.4 Practices to be preserved from the existing systemThis project will come up with a solution that can minimize the above listed problems of the system in the organization and enable the file management system (FMS) to be effective and efficient by considering the limited resources and by considering the strengths of the existing system.

2.4.1Strength The whole employee is very cooperative or eager for their duties

performed even if it is a tiresome work The existing system gives all the facilities that are provided by the

dormitory services

2.4.2 Weaknesses High inconsistency of data during registration Lack of data integrity High exposure to record error Difficulty in managing data and poorly filing system difficulty to get dormitory data easily as fast as possible mixing of record and difficult to search lose of available file from the file cabinet


2.5 Players in the existing system Players (actors) represents anyone participates in the system.

The actors in the existing system are:-

Students: - people who are getting services from the system.

High level manager: - the person who is responsible for managing and coordinating the university

Registrar: one of the system that can associate with dormitory system

Employees:- they have main role in the system in order to accomplished their tasks regarding to this system

2.6 Alternative solutions

We have an alternative solution in order to solve problems that exist in the

existing system .The website, that we are going to develop, is a dynamic website

that will provide the university with an online assign, which will improve the problem

of the existing manual system. This proposed system which is a technology through

which any students sitting at a long distance they will see their dorm.


Chapter three

Proposed system

3.1 Overview of the Proposed SystemThe general overview of our proposed system is designed to address the

problems of the existing manual system of dormitory services. The proposed

system solves those entire problems in the existing system. Because the system

is very integrated; it control all the data input and error which happen during data

registration. It will provide online dorm announcement for the student. The new

system will be able to access and retrieve different data effectively and

efficiently.

The proposed system will be able to:

Bring operational efficiency and effective manner

Minimize the burden of proctors

Increase state of satisfaction by alleviating tiredness

Reduce time wastage

Facilitate response time

Give data availability ,confidentiality and integrity

Achieve quality service delivery

Generate report

Assign students in their respective dorms

Retrieve the data from the database

Update and manipulate the database

Give easy access for the students and dormitory employees

Bring data security

Reduce data inconsistency


It is easy to use (user friendly)

Fast and reliable

Reduces wastage of copier ink

Reduces wastage of man power

Reduces wastage of paper

3.2 Functional requirementThe functional requirements focus on the main functions that the new application

system will provide. The major functional requirements of our proposed system are

the following:

The system should accept and record the student data

The system should assign the students in their dorm

The system should accept student id and view student information

The system should accept and record the block information

The system should allow to update the necessary information

The system should retrieve the students and the blocks information

The system should check availability of block and dorm

The system should allow the administrator to control the site

The system should retrieve students data

The system accept comment from user

The system should generate report

The system should Provides Online dorm show

3.3 Non functional requirement The non functional requirements focus on the quality of the application

systems needed to be developed from different evaluations point of view. The

non functional requirements of our proposed system includes:-

User friendlily/ system interface: the system interface that will be

developed must be interactive and easily understandable.

Response time: during the time accessing, the system response time will be

short.

Updating: we can update students and blocks information in the system:


there will know any kinds of problem during updating.

System modification: whenever modification necessary, the system

should support such process.

Physical environment: it is implemented using internet and store

information on the central database resides under the server.

Maintenance: the parts of the system answer the question that raised due to

some kinds of the problem.

Portable: It become portable for different platform

Providing error handling methods: Enable the user to confirm that

details are correct before creation, deletion or modification

Security issue: Access control for data which require user authentication

and authorization

Robustness: The system shall validate data entry and prompt the user when

the invalid data is entered

Documentation: At the completion of the project, every activity in the

development process will be documented for future reference.

3.4 Business RulesA business rule is effectively an operating principle or policy the software must

satisfy. It often concerns to access control issues, and operating polices and

principles of the new developing system. Therefore, our new developing

system has the following business rules.

BR1: Authorize to the system.

Users must have a valid user name and password.

BR2: The system administrator should administer the system and give

accesses (views) to those employees as per their priority to the system and

update the password.

BR3: Correct Information.


The user checks the filled students’ information and the entered information are

correct.

BR4: Validate students and dormitory Information

The authorized user registers the student’s information and the system validates.

The user’s password must be renewed in every month to make the system

secured.

BR5: The users should fulfill the following requirements

Education

Experience

Other Skills

BR6: Approve Information

The site manager approves every information that is entered to the system and

generated report from the system.

3.5 User InterfaceThe user interface of software is the portion that the user directly interacts with

including the screens, reports, documentation, and software support.

The following are user interfaces of DBU dormitory system

User Interface

ID

User Interface Name

UI- 01 Homepage UI

UI- 02 System Login UI

UI-03 Admin homepage UI

UI- 03 Student record UI

UI- 04 Dorm record UI

UI- 05 Block Record UI


UI-06 Department record UI

UI-07 Country record UI

UI-08 Faculity record UI

UI-09 Proctor record UI

UI-10 Assign student UI

UI-11 View dorm online UI

UI-12 Update UI

UI-13 Search UI

UI-14 Delete UI

UI-15 Comment UI

UI- 16 Generate Report UI

Table 3.1 user interfaces and their identification name

3.6 Hardware and Software required

3.6.1 Hard ware requirements

For the system soft ware installation a Pentium 4 desktop with:

80 GB hard disk (HDD)

512 MB memory (RAM)

3.2 GHz processor

Good resolution monitor

Compact disks (CDs)

Network Interface Cards (NIC)

Uninterrupted power supply (UPS)

Flash

Key board

Mouse


Server

Printer

Digital camera

Computer with internet connection

3.6.2 Soft ware requirements

The following software requirements will be needed to make the new system.

Windows 2007/XP

Xampp Software

Vb suite 5.1

Notepad software

Firefox

Microsoft office Power point 2007

Microsoft office word 2007

Internet Explorer

Notepad++

Nightly

3.7 Security MechanismsAccess control of data requires user authentication and user authorization.

The following commands specify access control identifies and they are typically

used to authorize and authenticate the user.

3.7.1 Username

The user identification is required to the server for access to its file system. This

command will normally be the first command transmitted by the user after the

control connections are made.


3.7.2 Password

The command must be immediately preceded by the user name command, and,

for some sites complete the user’s identification for access control.Since

password information is quite sensitive, it is desirable in general to “mask “it or

suppress type out.

Chapter four

System Modeling

4.1. IntroductionThis chapter deals with analyzing the proposed system. It includes the system

use case diagrams, the use case descriptions (scenarios), sequence

diagrams, and activity diagrams.

After identifying the actors and use cases, the use cases are developed and

textual descriptions (scenarios) are stated. The Sequence diagram id depicted

based on the use cases which are developed for the proposed system.

Activities will be represented by the activity diagrams.

4.2 Actor IdentificationActors are external factors that interact with the system. This may include

people, external system, and other organization. An actor initiates a use case

and receives something of value from the use case. Actors are always

external to the system being modeled i.e. they are not parts of the system.

One can use the following criteria to find actors: Who is using the system; who

is affected by & affects the system; what other system infract with this system;

where does then system get information; who install the system; who obtain

information from this system the like. Based on these criteria the following

actors are identified.

- Proctor

- Students


Actors Description

1.Proctors He/she registers students, blocks, and assign the

student in their dorm

2. Students Person who get service from the system.

Table 4.1.Actors and their description

4.3. System Use Case DiagramUse case diagrams are diagrams used for capturing for functional

requirements of the system. The notation of use case diagrams is developed

to build an external view of a system. Each use case diagram describes a

behaviorally related sequence of transaction in a dialogue between the user

and the system. It captures the goal of the users and the responsibility the

system to its users. It is the functionality of the system or the service provided

by the system. The following are use cases used in the system:

- Login

- Record students

- Record blocks

- Assign student

- Update record

- search record

- Record proctor

- Send comment

- Read comment

- Generate report

- View dorm on line


Fig 4.1 Use case diagram


Use case Name: Login

Description: Validates the user to enter to the system

Actors involved: proctors, students

Precondition: The user must have valid user name and password.

Basic course of action:

1. The proctor wants to enter to the system.

2. The system displays the login

3. The proctor fills and submits the username and password.

4. The system checks the login information.

5. The system displays homepage.

6. Use case ends.

Alternate course A: The entered username and/or password are not correct.

A.3 The system determines the invalidity of username and/or password

A.4 The system informs the user to reenter username and/or password

A.5 The user resumes at step 3 of basic course of action.

A.6 Use case ends.

Post condition: The users logs in to the home page.

Use case name: assign student

Description: The proctors accept the student information from

the registrar and assigned them by using

assignee student UI.

Actor: proctor

Precondition: From the homepage, the proctor click on

“assign student hyperlink”.

.


Post condition: the proctor assigned the students into the dorm

Include: login


1. The proctor wants to assign students

2. The proctor browses the website of the university.

3. The system display the homepage

4. The proctor click on “assign dorm ”from the homepage

5. The system displays login form

6. The proctor enter his/her user name and password

7. The system displays the assign dorm form

8. The proctor filling the student information

9. The system checked the inserted data or information

10.The system response the availability of information

11.The proctor submit the information

12.The end use case

Use case Name: Generate report

Description: Generate a report specified.

Actors: proctor

Precondition: Request general report

Include: login


1. The proctor browse/select website


3. The proctor select general report submenu on homepage.

4. The system display login form

5. The proctor enter his/her username and password

6. The system display general report form

7. The proctor selects report type: monthly report, weekly report, annual

report

8. The system display report type form


9. The proctor fill the necessary information

10. The system check filled information

11. The system displays (generates) report.

12. The proctor submit to concerned body

13. End of use case.

Post condition: Report is generated.

Use case name: view the dorm on line

Actor: student

Description: The student can get available information from the view data

form and they know their dormitory where they assigned.

Precondition: The students want to see their dormitory online.


1. The students enter into DBU web site

2. The system display the home page

3. the students click “view dorm menu” on homepage

4. The system display login form

5. For archive students fill their id and name, for fresh students fill

their admission card and name to view their dormitory where they

assigned

6. The system display the information from the database table

7. Use case end

Post condition: The students will see their dormitory online

Use case name: update data

Actor: proctor

Description: The proctor updates the students’ information during the

following time:

1. When the students assigned wrongly

2. When the students are dismissed by academic and discipline case

3. When the students fill withdrawal


Precondition: proctor select and identify the updated information

Include: login


1. The proctor browse/select the web site


3. The proctor click update data on the homepage

4. The system display the login form

5. The proctor fill his/her user name and passwords

6. The system validate the filled user name and password

7. The system display the update data form

8. The proctor fill the data that he/she wants to update

9. The proctor click the search button

10.The system display the data that is going to update

11.They proctor updated the necessary data

12.The proctor click update

13.The system display successfully updated message

14.Use case end

4.4Sequence diagram

Sequence diagrams are used to model the logic of usage scenarios or the

description of the potential way the system used. Sequence diagrams are a great

way to validate and flesh out the logic of use case scenarios and to document the

design of the system.

Dormitory system has the following sequence diagrams.


Fig 4.2 basic course of action sequence diagram for login


Fig4.3 Alternative course of action sequence diagram for login


Fig 4.4 Basic course of action sequence diagram for view dorm


Fig 4.5 basic course of action sequence diagram for block registration


Fig. 4.6 Basic course of action sequence diagram for update


4.5 Activity diagram

Uml activity diagram used to document logic of single operation or method, a

single use case or the flow of business process and show the how those

activities depend on one another the field circle represent the starting point of

the activity diagram and the field circle with border represent the end point.

The diamond represent decision point called branch the arrow represent the

transition between two activity and the text on the arrow represent condition

that must be fulfilled to process of the transition.

Fig 4.6 activity diagram login



Fig 4 .8 activity diagram for view data


Fig 4.9 activity diagram for block registration


Fig 4.10 Activity diagram for update record


CHAPTER FIVE

System design

5.1. Introduction

The analysis model describes the system completely from the actors’ point of

view and serves as the basis of communication between the client and the

developers. The analysis model, however, does not contain information about

the internal structure of the system, its hardware configuration, or, more

generally, how the system should be realized.But the purpose of designing is to

show the direction how the webpage is built and to obtain clear and enough

information needed to drive the actual implementation of the webpage. It is

based on understanding of the model the webpage built on.

5.2 Design Goals

The objectives of designing are to model a system with high quality. The ability

of the programmers to implement a high-quality, error-free system depends very

much on the nature of the design created by the designer; also, the ability of the

maintenance programmers to make changes to the system after it has been put

into operation and to the expanded system depends on the quality of the system

design.

The field of structured design contains a number of guidelines that help designer

determine which modules, and which interconnections between the modules will

best implement the requirements specified in the system analysis /Requirement

gathering phase.

The first step in designing a process is to map the essential model of user

requirements onto a configuration of process. Then, within each process, the

designer must decide how to allocate processes and data to different tasks.

Finally, we must organize the processes within each task into a hierarchy of

modules, using modeling tool.


5.3 Class Modeling

The design level of class model introduces changes to analysis class model

based on implementation technology. Regarding on this we have tried to identify

and design UML class diagram that are the major design issue in object oriented

analysis, these class diagram show the class of the system as well as the

interrelationship among each classes and further more it identify the static nature

of how the software is built.

Class Diagrams

The purpose of a class diagram is to depict the classes within a model. In an

object oriented application, Classes have attributes (member variables),

operations (member functions) and relation-ships with other classes

Fig 5.1 class diagram


Software Mapping

In this part, we described the overall system software and organization. We try to

see list of computer language (with a description of the function).

Fig 5.2 software mapping diagram

HTML: is visually rice and widely supported, but html forums are primitive and

they have not automatically validated on the client.

CSS: is cascading style sheet used for deigning the pages.

JavaScript: permit some client side programming (for example validation in

HTML forms).

Apache is software used to support mysql, and php by using wamp ser


Web browser -Html

-CSS

-Java script

Web server

-Mysql

-Apache

-Php HTTP

Fig 5.3 home page user interface


Fig 5.4 login user interface


Fig 5.5 student registration user interface


Fig 5.6 country registration user interface


Fig 5.7 block registration user interface


Fig 5.8 dorm registration user interface


Fig 5.9 proctor registration user interface


Logical Database Design

This deals with process of translating the conceptual representation to the logical

structure of the database and designing the relations. It also includes refining

mapping the conceptual data models to logical data models and then to derive a

set of relations.

Proctor control block 1:M

Block has student 1:M

dorm has student 1:M

Department found in faculty1:M

Student has department 1:M

Student has faculty 1:M

Fig 5.10 physical design model for database


Fig 5.11 physical design model for dorm


Fig 5.12 physical design model for student


Fig 5.13 physical design model for login


CHAPTER SIX

Implementation

6.1 Introduction

Implementation in the system includes implementing the attributes and methods

of each object and integrating all the objects in the system, to function as a

single system. The implementation activity spans the gap between the detailed

object design model and a complete set of source code files that can be

compiled together. This chapter presents Algorithm design & coding.

6.2 Algorithm Design

For controller class member function algorithm are designed. This design

enables to see every steps and flow of logic in each function. This design part is

important in the coding part of implementation. Some of the algorithms are:

Algorithm for log in to the admin home page

Display login page

Fill user name and password in the appropriate interface

If the filled input is valid

Display admin home page

Else

Display Error Message and return to login page

End if

Algorithm for student registration

Display login page

Fill user name and password in the appropriate interface


Display admin home page


If user selection is student registration

Display student registration

Fill the necessary input in the appropriate interface


Insert the data into database ()

Else

Display Error message ()

End if

6.3 Coding

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<title>student Registration</title>

<style type="text/css">



</style>

<script type='text/javascript'>

function formValidator(){

// Make quick references to our fields

var stud_id = document.getElementById('stud_id');

var fname = document.getElementById('fname');

var mname=document.getElementById('mname');

var lname=document.getElementById('lname');

var sex = document.getElementById('sex');

var age = document.getElementById('age');

// Check each input in the order that it appears in the form!

if(notEmpty(stud_id, "Please Create and Enter stud_id")){

if(isAlphanumeric(stud_id, " Please Enter Numbers and Letters Only

stud_id")){

if(lengthRestriction(stud_id, 1, 10)){

if(notEmpty(fname, "Please Enter Your First Name")){

if(isAlphabet(fname, "Please enter only letters for your First Name")){

if(lengthRestriction(fname, 1, 30)){

if(notEmpty(mname, "Please enter your Midle name")){

if(isAlphanumeric(mname, "Please enter only letters for your Middle Name")){

if(lengthRestriction(mname, 1, 30)){Dormitory system web site Page 55

if(notEmpty(lname, "Please enter your Last Name")){

if(isAlphanumeric(lname, "Please enter only letters for your Last Name")){

if(lengthRestriction(lname, 1, 30)){

if(madeSelection(sex, "You Do Not select Sex")){

if(notEmpty(age, "Please enter your age")){

if(isAlphanumeric(age, "Please enter only letters for your age")){

if(lengthRestriction(age, 1, 2)){

return true;

}}}} }}}}

}}}} }}}}

return false;

}

function notEmpty(elem, helperMsg){

if(elem.value.length == 0){

alert(helperMsg);

elem.focus(); // set the focus to this input

return false;

}

return true;

}

function isNumeric(elem, helperMsg){

var numericExpression = /^[0-9]+$/;

if(elem.value.match(numericExpression)){

return true;

}else{

alert(helperMsg);


elem.focus();

return false;

}

}

function isAlphabet(elem, helperMsg){

var alphaExp = /^[a-zA-Z]+$/;

if(elem.value.match(alphaExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

}

}

function isAlphanumeric(elem, helperMsg){

var alphaExp = /^[0-9a-zA-Z]+$/;

if(elem.value.match(alphaExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

}

}

function lengthRestriction(elem, min, max){

var uInput = elem.value;


if(uInput.length >= min && uInput.length <= max){

return true;

}else{

alert("Please enter between " +min+ " and " +max+ " characters ");

elem.focus();

return false;

}

}

function madeSelection(elem, helperMsg){

if(elem.value == "Select Sex"){

alert(helperMsg);

elem.focus();

return false;

}else{

return true;

}

}

function emailValidator(elem, helperMsg){

var emailExp = /^[\w\-\.\+]+\@[a-zA-Z0-9\.\-]+\.[a-zA-z0-9]{2,4}$/;

if(elem.value.match(emailExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

}


}

</script>

</head>

<body>

<table width="986" height="53" cellpadding="0" cellspacing="0">

<tr>

<th width="1" height="51" scope="col"></th>

<th width="96" height="51" scope="col"><img src="image/dbu1.JPG"

width="100" height="98" /></th>

<th width="730" bordercolor="#ECE9D8" bgcolor="#1E3F6A"

background="images/backgroud pic00.jpg">

<p align="center" class="style4"> Debre Berhan university dormitory website

</p>

</tr>

</table>

<table width="991" height="25" cellpadding="0" cellspacing="0">

<tr>

<th>

<td><input type="button" Value="Home" class="style6"

onclick="window.location.href='phome.php'"></td>

<td><input type="button" Value="Administrator" class="style6"

onclick="window.location.href='adminhome.php'"></td>

<td><input type="button" Value="student" class="style6"

onclick="window.location.href='studentform.php'"></td>

<td><input type="button" Value="faculity" class="style6"

onclick="window.location.href='faculityform.php'"></td>

<td><input type="button" Value="dorm" class="style6"

onclick="window.location.href='dormform.php'"></td>


<td><input type="button" Value="proctor" class="style6"

onclick="window.location.href='proctor3.php'"></td>

<td><input type="button" Value="country" class="style6"

onclick="window.location.href='countryform.php'"></td>

<td><input type="button" Value="block" class="style6"

onclick="window.location.href='blockform.php'"></td>

<td><input type="button" Value="department" class="style6"

onclick="window.location.href='departmentform.php'"></td>

<td><input type="button" Value="submenu" class="style6"

onclick="window.location.href='submenu.php'"></td>

<td><input type="button" Value="signout" class="style6"

onclick="window.location.href='Aboutus.html'"></td>

</th>

</tr></table>

<fieldset><legend><h3><i>Fill the student information here</i></h3> </legend>

<form id="form1" name="form1" method="post" action="<?php echo

htmlspecialchars($_SERVER

['PHP_SELF']); ?>" onsubmit='return formValidator()'>

<table width="526" border="" align="center">

<tr>

<td colspan="2"><div align="center">

<b><h1 class="style2">Student registration form</h1></b>

</div></td>

</tr>

<tr>

<td width="179" align="right" class="style1">Stud_Id</td>

<td width="331"><label>


<input type="text" Id="stud_id" name="stud_id">

</label></td>

</tr>

<tr>

<td align="right" class="style1">First Name </td>

<td ><label>

<input type="text" name="fname" Id="fname">

</label></td>

</tr>

<tr>

<td align="right" class="style1">Middle Name </td>

<td><label>

<input type="text" name="mname" Id="mname">

</label></td>

</tr>

<tr>

<td align="right" class="style1">Last Name </td>

<td><label>

<input type="text" name="lname" Id="lname">

</label></td>

</tr>

<tr>

<td align="right" class="style1" >Sex</td>

<td><label>

<select Id="sex" name="sex">

<option value="Select Sex">Select Sex</option>


<option value="Male">Male</option>

<option value="Female">Female</option>

</select>

</label></td>

</tr>

<tr>

<td align="right"class="style1" >Age</td>

<td ><label>

<input type="text" name="age" Id="age" >

</label></td>

</tr>

<tr>

<td align="right"class="style1" >Status</td>

<td><label>

<select Id="status" name="status">

<option disabled="disabled"value="Select status">Select status</option>

<option value="Regular">Regular</option>

<option value="Summer">Summer</option>

</select>

</label></td>

</tr>

<tr>

<td align="right" class="style1">Year</td>

<td><label>

<select Id="year" name="year">

<option disabled="disabled"value="Select Year">Select Year</option>


<option value="1st">1st</option>

<option value="2nd">2nd</option>

<option value="3rd">3rd</option>

<option value="4th">4th</option>





</select></label></td></tr>

<tr>

<th>

<label> <align="right" class="style1">department_code

</label></th>

<td>

<?php

$con=mysql_connect("localhost","root","");

if(!$con)

{

die("does not connect:".mysql.error());

}

mysql_select_db("dormitory_system",$con);

$sql="select department_code from department";

$result=mysql_query($sql,$con);

echo "<select name='department_code' id='department_code' >";

echo "<option size=80> select department_code </option>";

if(mysql_num_rows($result))


{

while($row = mysql_fetch_array($result))

{

echo "<option value='$row[department_code]'>".

$row['department_code']."</option>\n";

}

}

else

{

echo "<option> No department_code present</option>";

}

echo"</select>";

?>

</td>

</tr>

</tr>

<tr>

<th>

<label><align="right" class="style1">Country_code</label></th>

<td>

<?php


if(!$con)

{


}Dormitory system web site Page 64


$sql="select country_code from country";


echo "<select name='country_code' id='country_code' >";

echo "<option size =80 > select country_code </option>";


{


{

echo "<option

value='$row[country_code]'>".$row['country_code']."</option>\n";

}

}

else

{

echo "<option> No country_code present</option>";

}

echo"</select>";

?>

</td>

</tr>

</tr>

<tr>

<th>

<label><align="right" class="style1">Dorm_Number</label></th>

<td>Dormitory system web site Page 65

<?php


if(!$con)

{


}


$sql="select dorm_no from dorm";


echo "<select name='dorm_no' id='dorm_no' >";

echo "<option size =80 > select dorm_no </option>";


{


{

echo "<option value='$row[dorm_no]'>".$row['dorm_no']."</option>\n";

}

}

else

{

echo "<option> No dorm_no present</option>";

}

echo"</select>";

?>

</td>


</tr>

</tr>

<tr>

<td colspan="2" align="center" ><label>

&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp<input name="register" type="submit"

id="register" value="Register" class="style1" >

</label></td>

</tr>

<?php

if(isset($_POST['register']))

{

include('config.php');

$stud_id=$_POST['stud_id'];

$fname=$_POST['fname'];

$mname=$_POST['mname'];

$lname=$_POST['lname'];

$sex=$_POST['sex'];

$age=$_POST['age'];

$status=$_POST['status'];

$year=$_POST['year'];

$department_code=$_POST['department_code'];

$country_code=$_POST['country_code'];

$dorm_no=$_POST['dorm_no'];

$sql="INSERTINTO

student(stud_id,fname,mname,lname,sex,age,status,year,department_code,cou

ntry_code,dorm_no)


VALUES('$stud_id','$fname','$mname','$lname','$sex','$age','$status','$year','$de

partment_code','$country_code','$dorm_no')";

if(mysql_query($sql))

{

?>

<script type="text/javascript">

alert("Inserted Succesfully");

</script>

<?php

}

else {

?>

<script type="text/javascript">

alert("Error on table student primary key duplication")

</script><?php.mysql_error();

?>

<?php

}

//or die('Error,query failed');

mysql_close($conn);

}

?>

</table>

</form>

</fieldset>

</body>

</html>Dormitory system web site Page 68

CHAPTER SEVEN

CONCLUSION AND RECOMMENDATION

7.1 Conclusion

The project is partitioned into five chapters and each chapter has a specific

deliverable which is essential and base for the next chapter.

The first chapter is the proposal (Introduction), in this part the major infuses are:

describing about background where the new system is intended to be build on,

the problems in the system have been identified, the feasibility part studies

building a new system is possible or not from different perspectives, after the

scope of the proposed system has been defined the selected programming tools

and methods are stated and finally the project’s phases with their respective

deliverables are stated, each phase and its perspective work is scheduled.

The second chapter is conducted based on the first chapter. The first part in this

section is analyzing the different activities of the current dormitory system, then

the problems which encountered doing these activities are analyzed and also the

strengths which must be preserved in the new system are identified. Then the

next step is developing alternative options to address the problems, and after

different alternative evaluations the one which is developing the new web based

dormitory system is selected based on the actual evaluation and the challenges

of the alternative.

The third and the fourth chapters deal with describing and modeling the

proposed system. The functional as well as the non-functional requirements are


also studied together with the Hardware and Software requirements of the

system.

An effort has been made to study dormitory system as partial fulfillment of BSc

degree in information technology. In doing the study the team has tried to follow

object oriented system analysis and design methodology.

Since the success and failure of any system depends on gathering the right

information through different fact-finding techniques and user involvements, the

team has made the best effort to gather requirements. After a detail review and

study of the existing system of dormitory system models have been designed to

reflect the new system that are suppose to solve problems.

In order to solve different problems existed, the team has tried to propose a

solution that at least reduce the existed problems and model the proposed

system using different tools and methodologies. The team believe the different

tools and techniques has helped us a lot in capturing real user requirements and

model the right system for the users for their day to day transactions. Thus it

should have the precedence in know-how and experience in collecting,

processing and utilizing information.

7.2. Recommendation

Nowadays, the world is highly becoming a competitive world. Organizations have

to divert their attention on using the recent technology to be on the first line and

competitive. This can be real if they are able to use information communication

technology (ICT) to successfully achieve their objective. As we describe in this

document, almost all activities of the organization is done on manual basis. From

the various facts that constitute the project, the following recommendations have

come to light:

Attention should be given to the existing practice in the design, development and

utilization of the new system.

Serious consideration should be given for the introduction of the new system.

The staffing division should have adequate computer facilities for the introduction

of the new system.


Behavioral chance of the users of the system to adapt the new system.

There should be a network infrastructure in order to connect the different user

computers in that live in different place.

Budget should be allocated to take specific measure:

- To change the obsolete hardware instrument by the new one.

- To avoid shortage of computer hardware equipment like printer, scanner and

others.

- To have standardize database.

7.3. Acronyms/Definition of Terms

Fig -figure

LAN – Local Area Network

WAN – Wide Area Network

OO- Object Oriented

BR- Business Rules

UI- User Interface

UC- Use case

UML- Unified Modeling Language

SQL- Structural Query Language

NIC- Network Interface Cards

UPS- Uninterruptible power supply

PC- Personal Computer

Admin -Administrator


GB - Giga bite

GHz- Giga hertz

HDD - Hard Disk Drive

ID- Identification

MB - Mega bite

PC- Personal Computer

RAM- Random Access Memory

PHP- Hypertext preprocessor

Documents

SCHOOL OF COMPUTING SCIENCE DEPARTMENT OF ...mameamin.6te.net/.../11/dormitory-system-documentation.docx · Web viewRisk identification and management During the development of our