Naga Ass A A Documentation

Mizan-Tepi University
School of Computing and Informatics

Department of Information Technology
Project report on
MTU_Teaching and Learning Support System for
School of Computing and Informatics in
Tepi Campus.
Submitted in the Partial Fulfillments of the Requirements for the
Degree of Bachelor of Science in
Information Technology
By
Group member’s name---------ID
1 .Negessa……….Wayessa ETR/600/04
2. Natenael ……… Mekonen ETR/594/04
3. Merob …………….. Tegene ETR/528/04
4. Dechasa ……… …Asratu ETR/237/04
5. Abdurahman ………….Abay ETR/521/04
ADVISOR: prof.ephraim uy. Basal

Submission date: 05/10/2007

Project report on
MTU_Teaching and Learning Support System
For
Tepi Campus
Submitted in the Partial Fulfillments of the Requirements for the
Degree of Bachelor of Science in
Information Technology
Project Advisor: Head of the Department
Prof.Ephraim uy. Basal Mr.Admasu
Name and signature of Members of the Examining Board

Chairman Name__________________________ Signature________________________
Name Signature Date
___________________________ ____________ ___________
___________________________ ____________ ___________
___________________________ ____________ ___________
___________________________ ____________ ___________
___________________________ ____________ ___________
___________________________ ____________ ___________
___________________________ ____________ ___________
Name______________________ Signature_______________ Date__________

Declaration
We declare that the Project Report is our original work and has not been presented for a degree
in any other university.
Group Members:
1. NEGESSA WAYESSA Signature_______________ Date__________
2. NATENAEL MEKONEN Signature_______________ Date__________
3. MEROB TEGENE Signature_______________ Date__________
4. DECHASA ASRATU Signature_______________ Date__________
5. ABDURAHMAN ABAY Signature_______________ Date__________
This Project document has been submitted for examination with my approval as university
advisor.
_________________ ________________ _________________
Advisor Name Signature Date
MTU_Teaching and Learning Support System for SCI IT 2015 Page i

ACKNOWLEDGEMENT
First of all we would like to introduce great thanks for our God that has helped us in every
difficult condition. And then we would like to express our deep thanks and gratitude to our
advisors prof.Ephraimuy. Basal for their day to day encouraging support and guidance in
carrying out the project. The other person we kindly says to thank are our Instructor for
that we are voluntarily help us to provide some information what can help us to develop
this project.
Lastly we would like to say thanks to all of our group members for their actively
participation, for the completion of this document and their good behavior and attitude.
MTU_Teaching and Learning Support System for SCI IT 2015 Page ii

Abstract
This project is done by Mizan Tepi University‟s Department of Information Technology
graduating class students. We have done this project for the fulfillment of our Bachelor science
degree in Information Technology. To do so we are going to develop the new way to Teaching
and learning support system which means students can follow their education through online and
get their resources. This document contains the brief description of background information of
the universities and project, method of data collection and analysis, description of the existing
system and modeling and design of the new system or proposed system.
The development and advancement of computer technology makes computers to be a part

of everyday human life activities. Education is an area where the human is involved in a day to
day exercise of his life. It is an area which requires due attention, for it deals with behavioral,
attitude and skill changes. The same is true for the use of computer in education. This work has
enabled the delivery of learning materials to be efficient and it has also achieved inter exercise
among students and instructors. Furthermore it has established the support education based
learning theory along with the collaborative based to be applicable for the School of computing
and informatics in MTU.
MTU_Teaching and Learning Support System for SCI IT 2015 Page iii
Table of Contents
Chapter-I ....................................................................................................................................................... 1
1.1 Introduction .................................................................................................................................. 1
1.2 Background of the Project ............................................................................................................ 2
1.3 Statement of the problem ........................................................................................................... 3
1.4 Objectives of the Project ............................................................................................................. 3
1.4.1 General Objectives .................................................................................................................... 3
1.4.2 Specific objectives ............................................................................................................................ 3
1.5 Scope and Limitation .................................................................................................................... 4
1.5.1 Scope of the Project .................................................................................................................. 4
1.5.2 Limitation of the Project ....................................................................................................... 4
1.6 Significance of the project .................................................................................................................. 4
1.7 Feasibility Analysis .............................................................................................................................. 5
1.7.1 Economic Feasibility ......................................................................................................................... 5
1.7.2 Technical feasibility .......................................................................................................................... 5
1.7.3 Time Feasibility ................................................................................................................................ 5
1.8 Data Collection Methodology ............................................................................................................. 5
1.8.1 Observation and interview. ............................................................................................................. 5
1.8.2 System Analysis and Design Methodology ...................................................................................... 6
1.9 Project schedule.................................................................................................................................. 7
1.10 Budget .............................................................................................................................................. 8
CHAPTER -II ............................................................................................................................................... 9
Description of the existing system ............................................................................................................ 9
2.1 Introduction ........................................................................................................................................ 9
2.2 Major functions/Activities in the Existing System .............................................................................. 9
2.3 Business rules .................................................................................................................................... 11
2.4 Hardware/software requirement ..................................................................................................... 12
2.4.1 Hardware requirements.......................................................................................................... 12
2.4.2 Software requirements ........................................................................................................... 12
2.5 Actors in the existing system ............................................................................................................ 13
2.6 Problems of the existing system. ...................................................................................................... 13
MTU_Teaching and Learning Support System for SCI IT 2015 Page iv

2.6.1 Performance related problem ................................................................................................... 13
2.6.2 Economic .................................................................................................................................... 13
2.6.3 Efficiency related problem ......................................................................................................... 13
2.6.4 Service ........................................................................................................................................ 13
2.7 Practices to be preserved ................................................................................................................. 14
2.8 The Proposed System to Address Problems with the Current System.............................................. 14
2.9 System requirements of the new system ......................................................................................... 14
2.9.1 Functional requirements............................................................................................................ 14
2.9.2 Non-functional requirements .................................................................................................... 15
Chapter-III ............................................................................................................................................... 16
Object Oriented Analysis ........................................................................................................................ 16
3.1 Introduction ...................................................................................................................................... 16
3.2 System Requirement Specifications (SRS) ........................................................................................ 16
3.3 Use case documentation....................................................................................................................... 19
3.4 Sequence diagram............................................................................................................................. 37
3.5 Activity diagram ................................................................................................................................ 41
3.6 Analysis level class diagram (conceptual modeling) ......................................................................... 42
3.7 Business rule of the new system....................................................................................................... 43
3.8 User interface prototype .................................................................................................................. 45
CHAPTER-IV ................................................................................................................................................. 46
System Design ......................................................................................................................................... 46
4.1 Introduction ...................................................................................................................................... 46
4.2 Class type architecture .................................................................................................................. 46
4.3 State Chart Modeling ........................................................................................................................ 48
4.4 Class modeling .................................................................................................................................. 49
4.5 Deployment modeling ................................................................................................................ 50
4.6 Persistence data management ......................................................................................................... 51
4.6.1 Persistence layer ........................................................................................................................ 52
4.7 User interface design ........................................................................................................................ 52
CHAPTER V .................................................................................................................................................. 55
IMPLEMENTATION .................................................................................................................................. 55
MTU_Teaching and Learning Support System for SCI IT 2015 Page v

5.1 Introduction ...................................................................................................................................... 55
5.2 Sample code some part of the system.............................................................................................. 55
5.3 Testing ............................................................................................................................................... 60
5.3.1 Test case specifications .................................................................................................................. 61
5.5 Hardware and software acquisition .................................................................................................. 65
CHAPTER VI ............................................................................................................................................. 66
Summary, Conclusion and Recommendation ......................................................................................... 66
6.1 Summary ........................................................................................................................................... 66
6.2 Conclusion ......................................................................................................................................... 66
6.3 Recommendation.............................................................................................................................. 67
6.4 Reference .......................................................................................................................................... 68
6.5 Glossaries of the terms ..................................................................................................................... 69
MTU_Teaching and Learning Support System for SCI IT 2015 Page vi

List of table
Table 1 project schedule................................................................................................................................ 7
Table 2 budget .............................................................................................................................................. 8
Table 3 Description of login Use case with actor Administrator ................................................................ 19
Table 4 Description of login Use case with actor Instructor ...................................................................... 20
Table 5 Description of Upload resources Use case with actor Instructor.................................................. 21
Table 6 Description of Delete resources Use case with actor Instructor ................................................... 22
Table 7 Description of Add Student Use case with actor Administrato ..................................................... 22
Table 8 Description of Update Student Use case with actor Administrator .............................................. 23
Table 9 Description of search Student Use case with actor administrator............................................... 24
Table 10 Description of Delete Student Use case with actor Administrator .............................................. 25
Table 11 Description of Add Instructor Use case with actor Administrator ............................................... 25
Table 12 Description of update Instructor Use case with actor Administrator .......................................... 26
Table 13 Description of search Instructor Use case with actor administrator ........................................... 27
Table 14 Description of Delete Instructor Use case with actor Administrator ........................................... 28
Table 15 Description of Give comment Use case with actor Student ....................................................... 29
Table 16 Description of Download Use case with actor Student............................................................... 30
Table 17 Description of Add department Use case with actor Administrator ........................................... 31
Table 18 Description of Update department Use case with actor Administrator .................................... 31
Table 19 Description of search Department Use case with actor administrator ....................................... 32
Table 20 Description of Add exercise Use case with actor Instructor ........................................................ 33
Table 21 Description of Delete exercise Use case with actor instructor .................................................... 34
Table 22 Description of take exercise exercise Use case with actor Student ............................................. 34
Table 23 Description of search Course Use case with actor administrator ................................................ 35
Table 24 Description of Add course Use case with actor administrator .................................................... 36
Table 25 Description of Update course Use case with actor Administrator .............................................. 36
Table 26 Description of Delete Course Use case with actor administrator ................................................ 37
Table 27 Log in test case specification ....................................................................................................... 62
MTU_Teaching and Learning Support System for SCI IT 2015 Page vii
List of figure
Figure 1 Input output process for preparing learning resources ................................................................. 10

Figure 2 Input output process for preparing exercise. ............................................................................... 11
Figure 3 use case diagram........................................................................................................................... 18
Figure 4 Login sequential diagram ............................................................................................................ 38
Figure 5 Add Student sequence diagram .................................................................................................... 38
Figure 6 Delete Student sequence diagram ................................................................................................. 39
Figure 7 Upload sequence diagram ............................................................................................................ 39
Figure 8 Download sequence diagram ....................................................................................................... 40
Figure 9 Add department Sequence diagram ............................................................................................. 40
Figure 10 Add exercise Sequence diagram ................................................................................................. 41
Figure 11 Instructor activity diagram .......................................................................................................... 41
Figure 12 Administrator activity diagram ................................................................................................... 42
Figure 13 student activity diagram ............................................................................................................ 42
Figure 14 conceptual modeling diagrams .................................................................................................. 43
Figure 15 User interface prototype ............................................................................................................ 45
Figure 16 Class type Architecture diagram ............................................................................................. 47
Figure 17 Login State Chart Diagram ...................................................................................................... 48
Figure 18 Add department State Chart Diagram ....................................................................................... 49
Figure 19 Upload State Chart Diagram....................................................................................................... 49
Figure 20 modeling diagram Class .............................................................................................................. 50
Figure 21 Deployment diagram ............................................................................................................... 51
Figure 22 Persistent data diagram .............................................................................................................. 52
Figure 23 Home page form ........................................................................................................................ 53
Figure 24 Admin login form ....................................................................................................................... 53
Figure 25 instructor home page.................................................................................................................. 54
Figure 26 Admin home page ..................................................................................................................... 54
Figure 27 unit test ....................................................................................................................................... 60
MTU_Teaching and Learning Support System for SCI IT 2015 Page viii
Chapter-I
1.1 Introduction
Mizan-Tepi University is a one of University found in South nation Nationality of Ethiopia
providing educational service for the society.
Mizan-Tepi University was established at in April 2000. MTU has two campus branches: Mizan
main campus and Teppi Branch.in Mizan Campus Social faculty, health department, agriculture
and natural resources. In Tepi campus College of engineering and technology, college of
Computational and Natural Science and school of Computing and Informatics. The university
has upgraded its capabilities, adding new institutes and departments, programs and research
facilities. Today, MTU is a comprehensive university engaged in the provision of all-round
education, research, training, & community service through its diversified areas of academic
units. MTU is actively engaged in expansion activities to increase its intake capacity.
School of computing and informatics is one of the schools in Mizan Tepi University. The
department of school of computing and informatics was first established under the faculty of
Engineering and Technology. At first time only one department that is computer science.
Information Technology started in 2003 under college of Engineering and Technology. Also new
department start in 2006, that department is called information System. Then among of them are
get new name in 2006, it is called school of computing and informatics. Department in the school
of computing and informatics are studies on different main courses. The Main study of computer
science is: Programming languages, computer systems, algorithms, and human-computer
interaction.The main study of Information Technology is: Programming languages, Networking,
Databases, Web systems, Information Assurance and security and human-computer interaction.
Also the main study of Information System is: Programming languages, Application
Development, Internet Systems Architecture and Development, Database Design and
Administration, Systems Infrastructure and Integration.So, school of computing and informatics
is giving education for the above three department. Our teams also depends on the distribution
education in school of computing and informatics, we develop support system.
That new system is not says change the whole manual system to new system, it develop
additionally to support the manual system.Our new system is called
MTU_Teaching and Learning Support System for SCI IT 2015 Page 1

MTU_Teaching and Learning support System for school of computing and informatics.
Teaching and Learning Support System is a form of electronically supported learning and
teaching methodology. It‟s the use of computer and internet technologies to deliver Learning to
the short term training program students or learners that enables them to learn at internet service.
In other Learning system is an integrated and distributed web-based system for developing,
delivering and achieving learning for the students.
Teaching And Learning support System is also the computer and network-enabled transfer of
skills and knowledge. Teaching And Learning support System applications and processes include
Web-based learning, computer-based learning, virtual education opportunities and digital
collaboration. Content is delivered via the Internet, intranet/extranet, audio or video and CD-
ROM.
Teaching and Learning process is the major part of the university and the way to sharing
knowledge between instructor and students. Also Teaching and Learning is main case of building
of university. In Mizan-Tepi University, there are different exercise, different system, and
different process. Those all action in university is practice for prepared good condition for
education way.
Generally, teaching and learning also important is the Mizan-Tepi University. So, we are
developing project MTU_Teaching and Learning Support System for School of computing and
informatics.
1.2 Background of the Project

Teaching and Learning Support System is a web based application for the students to learn
online. It is the process where by students directly get educational services (resources), without
an intermediary service over the network.
This application consists of three set of users Students, instructors, Administrator. Instructor is
allowed to perform the following actions. Receive questions posted by students and reply to
them. Prepare some handouts, softcopy books, video teachings and other relevant files and
upload to the system.

Students have to register in the system by admin side and login to access the system resources.
Once logged in, the students have the privilege to ask questions to the instructor or other their
friends. The students can get answer when the question has been answered. Students can get the
resources which upload by instructor. They have the privilege to search for the learning
resources in the system. After searching then they can download the attached file.
Administrators are the super power users of the system. The administrator can see all the
Students and Instructor‟s Profile information and manage user. Also check Upload relevant files
to the system. Admin can also able to generate reports. Therefore, Teaching and Learning
support system have main function for school of computing and informatics. Such as: reduce
consume time when sharing resource, the way of resource, to reduce paper work etc.
1.3 Statement of the problem

The statements of problems are the problems with the manual system. So the problems with the
manual system are explained as follows.
 Instructors may not be available at the time when the student is convenient
 All learning is not available for the students at a time, which means each leanings
distribution process is slow.
 Expenditures of resources like: papers, printer, handouts, and worksheets etc.
 All important resource prepared on hardcopy is difficult
 No more exercise exercise for student
1.4 Objectives of the Project
1.4.1 General Objectives

The general objective is to develop MTU_Teaching and Learning Support system for school of
Computing and informatics.
1.4.2 Specific objectives

There are several specific objectives that we will follow in order to meet the general
objectives of the project. These objectives will have their own impact on the completeness of
the project. Some of the specific purposes are mentioned as follows:
 Provide course material with different media types (audio, text and video)
 Provide online practical exercise.
 Provide upload file (handout, references etc.).
 Provide to download any learning resources uploaded by the instructors.
 To support the manual system
 To reduce the work of instructor/staff
1.5 Scope and Limitation
1.5.1 Scope of the Project

The scope of the Project is mainly focused on developing Mizan-Tepi University Teaching and
learning support System for school of computing and informatics that largely focuses on
developing web based application system including the following functionalities:
 Uploads of learning resources (handout, reference, and teaching videos)

 Downloads of these learning resources (handout, softcopy, video teachings)
 Add exercise.
 View the result of exercise
 Give comment (feedback process).
 Add user (student and instructor)
 Add department and course
1.5.2 Limitation of the Project

Limitation is what we have not included to our Project or what we do not going to implement in
this project. This are:
1. Regarding with teaching and learning process even if some different activities, we focus
only with resource distribution and what we have explained under the scope of the
project.
2. The given question is only choice

3. The system only displays the result of exercise only as soon as the student submits.
1.6 Significance of the project

The main significant of this project is to help the MTU school of computing and informatics
teaching and learning support system process: -
 To perform their works faster, efficiently and accurately.
 To speed up the service teaching process of School of Computing and informatics.
 To easy access of uploaded resources.
 Secure and with wise use of resources available.
 Protect unauthorized access.
 To easy access of exercise.
 Secure and with wise use of resources available.
 Helps to administer learning system.
 To helps student to developed with technology.
 To help student to more information
1.7 Feasibility Analysis
1.7.1 Economic Feasibility

The team has done cost-benefit analyses which enable to specify the benefits and costs
associated with the project. According to this the team puts as the new system is economically
feasible.
1.7.2 Technical feasibility

Since the proposed system doesn‟t require much technical expertise and can be integrated
with other company information systems it is technically feasible.
1.7.3 Time Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this
means estimating how long the system will take to develop, and if it can be completed in
a given time period using some methods like payback period. In time feasibility our
project will be finished in a proper time given to us.
1.8 Data Collection Methodology
1.8.1 Observation and interview.

Observation is common methods of scientific research to collect the data. We use
observation to know the existing system, the location of manual.

Interview is particularly useful for getting the history behind the participant‟s
experiences. We used interview to get information about the existing system for
developing our project. The interview will be conducted on the director of manual
office.
1.8.2 System Analysis and Design Methodology

We have used object oriented methodology in this project to model the functionality of
the system, to organize the objects, classes, to identify the relationship between each objects
and classes and the behavior of the objects. Because object oriented methodology enable us
to reuse, maintain, modify design and code of the system and it increases consistency among
analyzer, designer and taste

1.9 Project schedule
It is determining start and finish date for project exercise.
No Project phase
May 2015
Mar2015
Nov2014
Apr2015
Dec2014
Feb2015
Jun2015
Jar2015
1 Proposal
2 Analysis existing
3 Object Oriented Analysis
4 Designing the system
5 Presentation
6 Implementation(coding)
7 Testing
8 Presentation
Table 1 project schedule

1.10 Budget
Budget also one of the obligations to succeed this project.
Item Quantity Unit cost per item (in Total in birr

cost birr)
Printing 90 paper 2.00 180.00

Paper 1 packet 1.00 100.00
Pen 10 4.00 40.00
Flash 2 200.00 400.00
Cover page 2 10.00 20.00
Laminating 2 20.00 40.00
Laptop 2 15,000.00 30,000.00
Total cost 30,500.00
Table 2 budget

CHAPTER -II
Description of the existing system
2.1 Introduction
School of computing and informatics is one of school in Mizan Tepi University. Under this
school there are three departments. Such as: Information System, Computer Science and
information Technology.
When we study about the existing system of school of computing and informatics, SCI is give
different service for student. Such as: Teaching and Learning service, examination service,
grading service and etc. from this service we focused on teaching and learning service. Teaching
and Learning service is one of the services that are the place to exchange knowledge and the one
who have not knowledge is getting the education. Also our team studying how to the manual
system give education and develop additional new system for our school. So, we focused only on
manual Teaching and Learning system in school of computing and informatics for developing
new system.
Under this chapter also deals with analyzing the purpose, goals, objectives and function of the
existing system on teaching and learning 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 nonfunctional requirements of the proposed system. During
this phase, the analyst must become fully aware of the root problems and must develop enough
knowledge about the existing system to enable an effective solution to be proposed. The first
exercise is assembling of the formal requirement for the proposed system. The second exercise is
logical modeling that allows the analysis to view the current system by focusing on what it does
instead of how it does.
2.2 Major functions/Activities in the Existing System

There is different exercise in manual system in school of computing and informatics on
distribution of education. The most exercise is the followings.
 Preparing learning resources.

This is the exercise performed by instructors to distribute any learning resources

Such as: handouts, softcopy, Worksheet, video, reference
 Workflow of preparing resources or materials
 This workflows starts after the instructor is assigned for the given course by the course
committee.
 The instructor selects the topics from the course he has assigned to teach.
 Then he prepares notes on the selected topics.
 The prepared note will be printed and given for the students.
Figure 1 Input output process for preparing learning resources
 Prepare Exercise
It is so important to give exercise for students after they finish the course to evaluate
their understanding .This exercise is used in the existing system of school of computing and
informatics teaching and learning process to evaluate their understanding after the end of each
portion in the course. Also this exercise prepared student for examination and used to
understanding education.

 Work flow for preparing exercise
 This workflow starts after the students have finished any given portion of the course.
 Then the instructor prepares the exercise or exercise from that portion.
 At the ends the students will be try the exercise given by instructor.
Figure 2 Input output process for preparing exercise.
2.3 Business rules

In every organizations or institutions there are rules and policy, which used to govern all
activities in specified work flow, control the work flow, and performed in the work
environment. So School of computing and informatics in MTU governs and controls the
work flow through the following business rules in side of teaching and learning process.
 Each student and instructor must have a unique ID number.
 A student who is absent consequently shall provide a satisfactory
explanation to his/her instructor.

 A student absent for more than one week for personal illness shall bring a
letter from a student health service office from appropriate Mizan-Tepi
University Student Clinic.
 The instructor prepares the note for the course he /she are giving.
 The instructors give some exercise at end of chapter for student.
2.4 Hardware/software requirement
2.4.1 Hardware requirements

refers to the physical components that make up a computer system.
 Computer: - computer is a machine capable of doing many things. We use it to type on it

and install all software and programming language. All tasks are done on computer.
 Network Cable: - used to get the internet access by connecting internet line from internet
switch to computer
 Flash Disk and CD/DVD: - used for the movement of data from one machine to another.
 Switch is a device that channels incoming data from any of multiple input ports .
2.4.2 Software requirements

is any set of machine-readable instructions that directs a computer's processor to perform
specific operations.
Some software which used to project:
 HTML: is a language which used to create electronic documents (called pages).

 PHP is a server scripting language. is an acronym for "PHP: Hypertext
Preprocessor”
 MySQL as database storage.
 XAMPP is the most popular PHP development environment and the place which
link to the database.
 JavaScript: - JavaScript is very interesting language used to validate data and
develop different messages.
 Notepad is a source code editor for Windows.

2.5 Actors in the existing system
An existing system compromises different players to carry out its job. Among those
different actors (players), the most common are:
 Dean of school: the person who manage the school of computing and informatics
 Instructors: They produce some learning resources and teach students.
 Students: Peoples who get the learning services.
2.6 Problems of the existing system.

It was used to identify the problems in the existing system in case of performance, information,
economic, time,accurate,services. The problems identified are presented as follow:-
2.6.1 Performance related problem

Performance related problem can be measured by using throughput. These are throughput
of different processes in the existing system.
 Throughput
For the reason that of every exercise in the existing system is manual based it is unable to
provide some necessary information on time.
 Wastage of time to organize & integrate related files.
 High resource time and throughput.
2.6.2 Economic
This term is a direct relation with that of „cost‟ needed per each exercise performed in the
system. It needs more budgets to prepare and distribute the learning sources.
2.6.3 Efficiency related problem

There is also an efficiency problem with the existing system. Workers waste their time due to
redundantly input data..
2.6.4 Service
The system is inflexible to new or exceptional situations

The system is inflexible to change
The system is not coordinated with other systems (standalone system)

So as to solve the existing problems, we attempt to build a computer based MTU Teaching and
Learning support system for school of computing and informatics which can perform efficiently
handling Student information, to upload and download any resources and Give exercise.
2.7 Practices to be preserved

Here most of the main activities that are performed in the current system will be preserved by
manual replication of those activities. That is each exercise that is applicable to the system are
designed and automated to achieve the best functionality. The team may also develop new
system that is Teaching and Learning support system to the existing system. These new system
will be web based to the current system that will change the way the current system operates, and
services given to its users.
2.8 The Proposed System to Address Problems with the Current System
Even though an existing system provides different functions that are stated above, it is
not to mean that the functions are satisfactory. This is because all the processes (actions)
performed are not effective and efficient. To overcome or improve this operation the team comes
up with a new proposed system Teaching and Learning support System for school of computing
and informatics in MTU, this new system is a Web based application that enables the users to
access the services given by the system through the Internet. The new system is targeted to
address the problems of the current systems and to support additional manipulations. It also
proposed to satisfy beneficiaries by fulfilling different features in the new system. To solve such
problems the newly developed system will play an important role. Based on the user inspection,
the proposed system can hold user comfort interface too. The main Intention of developing the
new system is that not to make the whole educational style to web based, instead to add some
functionality to the existing system by developing website that is more interactive to use which
holds different supportive Learning materials, video lectures, softcopy, and reference.
2.9 System requirements of the new system

2.9.1 Functional requirements
Functional requirements describe the interactions between the system and its environment
independent of its implementation. The environment includes the user and any other external
system with which the system interacts. In this system the functional requirements specified are:

 Add exercise or exercise: The system should able to store the exercise into the database
and the student can take it when needed.
 Add student and instructor: The system helps administrator to add user.
 Delete student and instructor: The system helps the administrator to delete user.
 Uploads of resources: The system helps instructor to upload any necessary files and
documents that are usable for education purpose only.
 Downloads of resources: The students can download any documents that are uploaded
by the instructors.
 Add department: the admin can add department when it necessary.
 Add course: the admin can add course when it necessary.
 Give comment: The system helps the students to comment on the system.
 The system shall logout administrator, instructor and student
2.9.2 Non-functional requirements

Nonfunctional requirements describe user-visible aspects of the system that are not directly
related with the functional behavior of the system. It describes the aspect of the system that is
concerned with how the system provides the functional requirements. According to our
system the nonfunctional requirements are:
 Performance
The system shall be error free while operating with a huge set of data. The system will be
accessed by many users. The system must have a good response time.
 User Interface
The system shall be user friendly. The developed system provides web application user
interfaces that are compatible with browsers like Internet explorer, Mozilla Firefox, Google
chrome.
 Security and Access Permissions
The system shall be secured with different secure mechanisms. In another way
authentication is provided to all the users, only authenticated users can use. It means if the user is
an administrator then he/she can be able to manage the data. All others unregister users only have
the rights to retrieve limited information from the system.
 Resources
The system must be compatible with specified hardware and software environment.

Chapter-III
Object Oriented Analysis
3.1 Introduction
We have used an object oriented methodology to analyze the requirements that are needed to
model the functionalityof the proposed system.We have used different types of UML diagrams
which are include use case diagram, sequence diagram, exercise diagram, user interface
Prototyping and analysis level class diagram to model the proposed system. Each and every
diagram has documentation to show their functionality and how they are operated.
3.2 System Requirement Specifications (SRS)

The following lists of objects are System Requirement Specifications (SRS) for Teaching and
Learning support System for SCI modeling.
 Use Case diagram list and their details description
 Actors list
 Sequence diagram
 Exercise diagram
 Analysis level class diagram
 User Interface prototyping diagram
To draw use case diagram for the system it is important to identify the actors or players of
the system and use case names used in the system. So according to our projects the actors in
the proposed system are:
 Administrator
Administrator is Person who has managing exercise over the system and manages the
user (instructor and student). He also assumes the role of supervisor in the sense that he
enforces the "Terms of use" of the site, and has the right to revoke clients‟ privileges by
deleting their resources.
 Instructor
Is a person who has the privilege of uploading, and updating any learning resources and
add exercise for students.
 Student
Person who uses the system in order to download resource and use what was uploaded.

The use case names used in the system are:
1. Add department
2. Update department
3. Search Department
4. Add course
5. Update course
6. Search course
7. Delete course
8. Upload resources
9. Download resources
10. Delete resource
11. Add exercise
12. Take exercise
13. Delete exercise
14. Add student
15. Search student
16. Delete student
17. Search Instructor
18. Update student
19. Add instructor
20. Delete instructor
21. Update instructor
22. Give Comment

Depending on the actors and use case names listed above we have draw the following use case
diagram. The description of use case and actors is explained in the use case documentations.
Figure 3 use case diagram

3.3 Use case documentation
Each and every use case we have used in this project is explained in table form as
following table.
Use case name: Login
Actor: Administrator
Description This use case allows the Administrator to log in to the system
Flow of events Actor action System response
step1: This use case is initiated Step3: The system validates the password and inserted
when the administrator selects user name to identify whether the user is legal or
administrator login form and illegal.
inserts username and password.
Step4: The system displays the administrator
Step2:click on login button homepage if the user is legal user.
Step5:The administrator can

access the administrator
homepage
Step6: Use case ends.
Alternative events: Step3: If the User name and password is not valid, send a notification to the
administrator to reselect user name and re-inter password again.
Pre-condition: The login form is currently displayed on the screen and the administrator is ready to log
in.
Post-condition: The administrator logged in to the system and select tasks.
Table 3 Description of login Use case with actor Administrator

Use case name: Login
Actor: Instructor
Description This use case allows the Instructor to log in to the system

step1: This use case is initiated Step3: The system validates the password and
when the Instructor selects the user selected user name.
name and inserts his password.
Step4: The system displays the department
Step2:click on login button selection form for instructor.
Step5:.The instructor selects the Step6: The system displays the selected
department. department.
Step7: The Instructor can access

the selected department and can
perform different tasks.
Alternative Step3: If the User name and password is not valid, send a notification to the
events: Instructor and redirect to the previous login form to redo user name selection and
password insertion again.
Pre-condition: The login form is currently displayed on the screen and the Instructor is ready to log
in.
Post-condition: The Instructor is logged into the system and performs his tasks.
Table 4 Description of login Use case with actor Instructor

Use case name: Upload resources
Actor: Instructor
Description This use case allows the Instructor to upload the learning resources and other
necessary documents to the system

step1: This use case is initiated when the Step2: The system
Instructor selects the Upload resources button. displays the Upload
Step3: The Instructor fill name of course, form.
course code and selects the documents to be
uploaded and click on upload Step4: The system
process and upload the
Step5: Use case ends. resources.
Pre-condition: The instructor should have to prepare resources to be uploaded.
Post condition: The document will be uploaded on the data base.
Table 5 Description of Upload resources Use case with actor Instructor
Use case name: Delete resources
Actor: Instructor
Description This use case allows the Instructor delete the uploaded resources by the course
code if not needed so far.
step1: This use case is initiated when the Step2: The system
Instructor insert the course code and click button searches the resource
with inserted course
Step5: Use case ends after the Instructor seen codes.
deleted confirmation.
Step3: The system
deletes the resource.

Step4: The system notify
the as the resource is
deleted.
Alternative Step2: The system notifies the non-existence of resources with the inserted
event code.
Pre-condition The resource needed to be deleted should exist first.
Post condition The resource find to delete was deleted.
Table 6 Description of Delete resources Use case with actor Instructor

Use case Add Student
name:
Description This use case allows the Administrator to Add Student.
Flow of Actor action System response

events
step1: This use case starts when the Step2: The system
administrator browse Add Student form. displays the Add Student
form.
Step3: Then admin fills the necessary information.
Step5: The system
Step4: Then he/she click on button validates the inserted
information.
Step6: The system notify the

as the Student is Add
Step7: Use case ends after the confirmation is
sent for the administrator.
Alternative event Step5: The system determines the invalidation of the inserted information and
notifies to re-insert information again.
Pre-condition
The administrator login to the system and browse Add Student form
Post The administrator Adds the new Student.
condition
Table 7 Description of Add Student Use case with actor Administrato

Use case name: Update Student
Description This use case allows the Administrator to Update Student.
step1: This use case starts when the Step3: The system
administrator browse Update Student form. displays the Update
Student form.
Step2:admin click on update
Step6: The system
Step4: Then admin fills the necessary validates the inserted
information. information.
Step5: Then he/she click on button Step7: The system notify the
as the Student is update

Pre-condition
The administrator login to the system and select and identify the updated
information
Post condition The administrator updates the student information.
Table 8 Description of Update Student Use case with actor Administrator

Use case Search Student
code:
Description This use case allows the administrator to search the Student from the system

events
step1: This use case is initiated when the admin Step4: The system process
login and searches the Student by Student id search functions for inserted
Step2: insert id Student id.
Step3: click search button. Step5: The system displays

the Student.
Step6: The administrator selects the Student from
displayed Student.
Alternative Step4: The system notifies the non-existence of Student with the inserted Student id
event
Pre- The Administrator should have to know the Student id.

condition:
Post The system displays the searched Student.

condition:
Table 9 Description of search Student Use case with actor administrator
Use case name: Delete Student
Description This use case allows the Administrator to delete Student.
step1: This use case starts when the Step2: The system displays
administrator login the system and selects the delete Student form.
delete Student button.
Step4: The system validates
Step3: Then the administrator fills the the inserted information.
necessary information and click on delete
Step5: The system notify the as

button. the Student is deleted.

Alternative Step4: The system determines the invalidation of the inserted information and
event notifies to re-insert information again.
Pre-condition The administrator login to the system and there must be Student to be deleted
Post condition The Student deleted from system.
Table 10 Description of Delete Student Use case with actor Administrator
Use case Add Instructor

name:
Description This use case allows the Administrator to Add Instructor.

events
step1: This use case starts when the Step2: The system displays the
administrator browse Add Instructor form. Add Instructor form.
Step3: Then admin fills the necessary Step5: The system validates the
information. inserted information.
Step4: Then he/she click on Add button Step6: The system notify the as the
Instructor is Add
Pre-condition
The administrator login to the system and browse Add Instructor form
Post The administrator Adds the new Instructor.
condition
Table 11 Description of Add Instructor Use case with actor Administrator

Use case Update Instructor
name:
Description This use case allows the Administrator to Update Instructor.
step1: This use case starts when the Step3: The system displays
administrator browse Update Instructor form. the Update Instructor form.
Step2:admin click on update Step6: The system validates

the inserted information.
Step5: Then he/she click on update button the Instructor is update

Pre-condition
The administrator login to the system and select and identify the updated information
Post condition The administrator updates the instructor information.
Table 12 Description of update Instructor Use case with actor Administrator

Use case Search Instructor
code:
Description This use case allows the administrator to search the Instructor from the system

events
searches the Instructor by Instructor id search functions for inserted
Step2: insert id Instructor id.

the Instructor.
Step6: The administrator selects the Instructor from
displayed Instructor.
Alternative Step3: The system notifies the non-existence of Instructor with the inserted Instructor id
event
Pre- The Administrator should have to know the Instructor id.

condition:
Post The system displays the searched Instructor.

condition:
Table 13 Description of search Instructor Use case with actor administrator

Use case name: Delete Instructor
Description This use case allows the Administrator to delete Instructor.
step1: This use case starts when the administrator Step2: The system displays
selects delete Instructor button. the delete Instructor form.
Step3: Then the administrator fills the necessary Step4: The system validates
information and click button. the inserted information.
Step6: Use case ends after the confirmation is sent Step5: The system notify the as
for the administrator. the Instructor is deleted.
Alternative Step4: The system determines the invalidation of the inserted information and
event notifies to re-insert information again.
Pre- The administrator login to the system and there must be Instructor to be deleted
condition
Post The Instructor deleted from system.

condition
Table 14 Description of Delete Instructor Use case with actor Administrator

Use case name: Give comment
Actor: Student
Description This use case allows the student to give comment.

step1: This use case starts when the student Step2: The system displays the
selects comment button. comment form.
Step3: Then the student insert his E-mail
Step4: The system validates the
address and click on button
inserted E-mail address.
Step5: The student comments on the system and
the click on button Step6: The system notify the as
the comment is sent.
Step7: Use case ends after the notification is
sent for the student.
Alternative Step4: The system determines the invalidation of the inserted E-mail address and
event notifies to re-insert valid E-mail address again.
Pre-condition The student must have valid e-mail address.
Post condition The comment will be sent.
Table 15 Description of Give comment Use case with actor Student

Use case Download resource
name:
Actor: Student
Description This use case allows the Student to download resources.

events
step1: This use case starts when the Student Step3: The system displays
selects download button. the resources with inserted
course code.
Step2: The Student inserts the course code he/she
wants to download and click on button. Step5: The system process
downloading.
Step4: The selects the document he/she want to
download and click on download button Step6: The system notifies the
download completed.
Step7: Use case ends after the notification is sent
for the student.
Pre- The Student have to be valid user, they have to valid account.
condition
Post The Student downloads the document he needs.

condition
Table 16 Description of Download Use case with actor Student
Use case Add Department

Name:
Actor: Administrator.
Description This use case describes the process of add Department information.

events
Step 1. This use case initiated by when administrator Step2. The system display form
login and click on add department. Step 5. Add will record on the
system.
Step3.admin fill information
Step4.click on button add

Step 6. Use case ends.
Pre- The system must verify the user to add the content.
condition
Post Admin can view added department.

condition
Alternative Post condition is not succeeding, and then the system will display an error
Learning’s: message and return back to check the existence of pre-condition.
Table 17 Description of Add department Use case with actor Administrator
Use case name: Update department
Actor : Administrator
Description This use case allows the Administrator to Update department.
step1: This use case starts when the Step3: The system displays the
administrator browse Update department Update department form.
form.
Step6: The system validates the
Step2:admin click on update inserted information.
Step4: Then admin fills the necessary Step7: The system notify the as the
information. department is update
Step5: Then he/she click on button

Pre-condition
The administrator login to the system and select and identify the updated
information
Post condition The administrator updates the department information.
Table 18 Description of Update department Use case with actor Administrator

Use case Search Department
code:
Description This use case allows the administrator to search the Department from the system

events
searches the Department by Department name search functions for inserted
Step2: insert department name Department name.

the Department.
Step6: The administrator selects the Department
from displayed Department.
Alternative Step4: The system notifies the non-existence of Department with the inserted Department name
event
Pre-condition: The Administrator should have to know the Department name.
Post condition: The system displays the searched Department.
Table 19 Description of search Department Use case with actor administrator
Use case Add exercise

name:
Actor: Instructor
Description This use case is used for the instructor to add activities.

events
Step1: First the Instructor login to the system and click on the
add exercise button.
Step2: The system displays

the add exercise form.
Step3: The Instructor selects the course and gives the exercise
name and insert how many question he/she want add.
Step4: The instructor adds the activities.

Step6: The system process
Step5:click add button the added exercise.
Step8: Use case ends after the notification is sent for the Step7: The system notifies the
Instructor. exercise successfully added.
Pre-condition The instructor should have to prepare the exercise that he wants to add.
Post The exercise will be added.

condition
Table 20 Description of Add exercise Use case with actor Instructor
Use case code: Delete exercise
Actor: Instructor
Description This use case allows the instructor to delete the add exercise by the course code if
not needed so far.
step1: This use case is initiated when the Step2: The system searches
instructor insert the course code and click button the course code with
inserted course code.
Step5: Use case ends after the instructor seen
deleted confirmation. Step3: The system deletes
the exercise.

the exercise was deleted.
Alternative event Step2: The system notifies the non-existence of course with the inserted code.
Pre-condition The course code of exercise needed to be deleted should exist first.
Post condition The exercise find to delete was deleted.

Table 21 Description of Delete exercise Use case with actor instructor
Use case take exercise

name:
Actor: Student
Description This use case is help for the students to take the exercise and submit it.

events
Step1: The student login to the system and click on
take exercise button.
Step3: The system displays the
Step2: Then the student selects the course and selects exercise for the selected course
the exercise title for selected course. and exercise title.
Step4: The student writes the exercise (select answer Step5: The system processes
for the given question) and submits after they finish. the answer of the student and
displays the result of the
Step7: Use case ends after the student gets the student.
feedback of the exercise.
Step6: The system automatically
gives the exercise feedback.
Pre- The exercise should have to store on the database by the instructor.
condition
Post The student will take the exercise.

condition
Table 22 Description of take exercise exercise Use case with actor Student
Use case Search Course

code:
Description This use case allows the administrator to search the Course from the system

events
searches the Course by Course code search functions for inserted
Step2: insert Course code Course code.

the Course.
Step6: The administrator selects the Course from
displayed Course.
Alternative Step4: The system notifies the non-existence of Course with the inserted Course code
event
Pre- The Administrator should have to know the Course code.

condition:
Post The system displays the searched Course.

condition:
Table 23 Description of search Course Use case with actor administrator
Use case Code: Add Course
Actor: Administrator.
Description This use case describes the process of add course information.
Step 1. This use case initiated by the Step 3. Add will record on the
administrator by add available course. system.
Step 2: administrator insert course name

and course code then click button.
Step 4. Use case ends.
Pre-condition The system must verify the user to add the content.

Post condition Admin can view added course.
Alternative Post condition is not succeeding, and then the system will display an error message
Learning’s: and return back to check the existence of pre-condition.
Table 24 Description of Add course Use case with actor administrator
Use case Update course

name:
Description This use case allows the Administrator to Update course.
step1: This use case starts when the administrator Step3: The system displays the
login and browse Update course form. Update course form.
Step2:admin click on update Step6: The system validates the

inserted information.
Step7: The system notify the as the
Step5: Then he/she click on update button course is update
Alternative event Step6: The system determines the invalidation of the inserted information and notifies
to re-insert information again.
Pre-condition
The administrator login to the system and select and identify the updated information
Post condition The administrator updates the course information.
Table 25 Description of Update course Use case with actor Administrator

Use case code: Delete Course
Description This use case allows the administrator to delete the add Course by the course code if not
needed so far.
step1: This use case is initiated when the Step2: The system searches
administrator insert the course code and click button the course code with inserted
course code.
Step5: Use case ends after the administrator seen
deleted confirmation. Step3: The system deletes the
course.

the course was deleted.
Alternative Step2: The system notifies the non-existence of course with the inserted code.
event
Pre-condition The course code needed to be deleted should exist first.
Post condition The course find to delete was deleted.
Table 26 Description of Delete Course Use case with actor administrator
3.4 Sequence diagram

A sequence diagram is a form of interaction diagram which shows objects a lifelines
running down the page time and their interactions over there represented or message
arrows. Arrows shows from the source lifeline to the target lifeline. Sequence shows
object communicate with each other and what messages trigger for those
communications

Figure 4 Login sequential diagram
Figure 5 Add Student sequence diagram

Figure 6 Delete Student sequence diagram
Figure 7 Upload sequence diagram

Figure 8 Download sequence diagram
Figure 9 Add department Sequence diagram

Figure 10 Add exercise Sequence diagram
3.5 Activity diagram
Figure 11 Instructor activity diagram

Figure 12 Administrator activity diagram
Figure 13 student activity diagram
3.6 Analysis level class diagram (conceptual modeling)

We have used class diagram to describe the detailed understanding of the problem for our
system. Using this diagram we showed classes of a system, their relationship and attributes of the

class. It also describes the type of objects in the system and various kinds of static relationships
that exist in the system.
Figure 14 conceptual modeling diagrams
3.7 Business rule of the new system

As we have tried to explain in the business rule of the existing system there are many business
rule that the university have in teaching process. So it is important to inherit this some of
business rule for the new system that we are going to develop to achieve purpose of teaching
process of the university. That means the system should have to include the business rule of the
system. This are explained as follows:

 Each student has his/her own unique ID number: That means our system should not accept
one ID number for two or more students (one ID number only for one student).
 The students have no any privilege to edit resources on the system.
 All users have an account to access the system.
 The system administrator has the privilege to manage the whole system.

3.8 User interface prototype
Figure 15 User interface prototype

CHAPTER-IV
System Design
4.1 Introduction
This chapter includes and describes the designing and architectural parts of the
proposed system. As we have mentioned previously, in this project, we have used an
object oriented system development methodology to establish and define the
proposed system components, interfaces, behaviors or architectures. The
architectural strategy that we follow to develop this system is put the architecture of
a system into several layers.
Specifically, the purposes of the system are:-
 To ensure security in the system by using different security mechanisms.

 To make the data organized and centralized implementing a database system.
 To increase the flexibility of the proposed system.
 To specify how the system do some tasks for the user.
4.2 Class type architecture

Since our system modeling approach is object oriented, we have to describe the
system in terms of its architecture. In this section we have demonstrated different types of
class type architectures; that represent a high level layering strategy for software
application. The various layers are represented by the rectangles and collaboration
between layers indicated by the arrows. The primary name of the layer is indicated first,
and other common names indicated in parenthesis.
1. Interface: This layer wraps or covers access to the system and system interface. There
are two categories of interface class-user interface (UI) classes that provide people access
to the system and system interface (SI) classes that provide access to external systems to
the system. However, the aforementioned classes are among user interface (UI) elements of
the system. E.g. Log in Form Screen ().
2. Control/process layer: This layer represents controller/process class that implements
business logic that involves collaborating with several business or domain classes or even
other process classes.

3. Domain: This layer implements the concepts pertinent to your business domain such as
customer focusing on the data aspects of the business objects, plus behaviors specific to
individual objects.
4. Persistence/Data layer: This layer is used to encapsulate the capacity to store, retrieve
and delete objects permanently without revealing details of the under laying storage
technology.
5. System layer: This layer is used to represents system class that provides operating
system specific functionality for the applications, isolating the software from the operating
system (OS) by wrapping OS specific feature.
Generally what we have explained in the above is described in the following form of
architecture.
User Interface (system interface)

- Administrator form screen ()
-Instructor form screen ()
-student form screen ()
Control/process layer System

(Application, controller)
-Validate System User
(infrastructure
plat form)
Domain (Business)
Persistent classes (Data) Store

search Delete update
MTUdb
Figure 16 Class type Architecture diagram

4.3 State Chart Modeling
State chart modeling is used to show the sequence of states that an object goes through,
the events that cause the transition from one state to the other and the actions that result
from a state change. The team used to design the behaviors of the objects by drawing the
state diagram. The state chart diagram depicts the state of objects as their attributes
change from one state to the other state; we draw some of state in the following.
Figure 17 Login State Chart Diagram

Figure 18 Add department State Chart Diagram
Figure 19 Upload State Chart Diagram
4.4 Class modeling

Class modeling are the mainstay of object oriented analysis and design, and before the UML
most methodologies called them object models instead of class models. In this document

we have used class models to explain the class and the attributes of each class with their
data types, operation and their interrelationships.
Figure 20 modeling diagram Class
4.5 Deployment modeling

The software going to be developed is allowed by UML model. UML deployment
diagram show physical view of system, taking software into real world by showing
how software gets assigned to hardware and how communicates.
The deployment diagram shows how the software components, processes, and objects
are deployed into the physical architecture of the system.
It shows the configuration of the hardware units (e.g. Computers, communication
devices, etc.) and how the software components are distributed across the units.
:Aplication/
server
Department Mngmt
:Client
Course Mngmt :MTU database
Adminstrator
Search perisistancedata
Instructor Mngmt
Instructor
Student Mngmt
Student
MTU DB
Upload resourcse
Remove resource
add activity
Give Comment
take activity
Download resources
Figure 21 Deployment diagram
4.6 Persistence data management

Persistence data model are used to communicate the design of a database, usually a
relational database, to both users and other developers.
Persistence are used the schema of database. The strength of persistence data models is
that data entities are conceptually the same as the table of relation data base and that
attributes are the same as table columns.

4.6.1 Persistence layer
Persistence layer encapsulate the capability to store, retrieve, and delete objects/data
permanently without revealing details of the underlying storage technology. In the current
database system we have used different tables as object and each object is related to each
other and enforced by referential integrity by the use of foreign key and primary key. This
schema enables as data manipulation exercise such as select, search, delete, update on the
data base.
Figure 22 Persistent data diagram
4.7 User interface design

User interface is the part of application or system software that enable user of the system to
interact with it. It may contain input boxes, message boxes and different controls. It also contains
some help page that supports the user to simply interact with the system. The system that we
proposed to submit has different forms. These are mentioned as follows:
The home page user interface, this home page form is visible to any user of the system.

Figure 23 Home page form
Figure 24 Admin login form

Figure 25 instructor home page
Figure 26 Admin home page

CHAPTER V
IMPLEMENTATION
5.1 Introduction
In this part of our project we are going to explain about System Implementation coding,
testing, hardware and software acquisition, user manual presentation.
5.2 Sample code some part of the system

Student Login Html Code
<?php
include('loginstud.php'); // Includes Login Script
?>
<html>
<head>
<link rel="stylesheet" type="text/css" href="div.css" />
<link rel="stylesheet" type="text/css" href="css.css" />
<link rel="stylesheet" type="text/css" href="table.css" />
<link href="slideshow/imageslider.css" rel="stylesheet" type="text/css" />
<script src="slideshow/imageslider.js" type="text/javascript"></script>
<script type="text/javascript" src="javascript/mootools.js"></script>
<script type="text/javascript" src="javascript/visualslideshow.js"></script>
<link rel="stylesheet" type="text/css" href="slideshow.css" media="screen" />
<style type="text/css">.slideshow a#vlb{display:none}</style>
<title>MTU_TLSS</title>
<SCRIPT LANGUAGE="JavaScript">
function check() {
mt=document.form1.username.value;
if (mt.length<1) {
alert("Please Enter User Name");

document.form1.username.focus();
return false;
}
tt=document.form1.password.value;
if(tt.length<1) {
alert("Please Enter Password");
document.form1.password.value;
return false;
} return true;}
</script>
</head>
<body>
<br /><br />
<div id="content">
<?php include "head-nav.php";?>
<div id ="menu">
<?php include "navigation1.php"; ?>
<div class="right">
<div id="sidebar_container">
<div class="sidebar">
<script src="style/time.js" language="javascript" type="text/javascript"></script>
<body onLoad="yourClock()", onUnload="stopClock(); return true">
<form name="the_clock">
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr align="center"><td><a class="mainlevel">Time: <input type="text"
name="the_time" size="10" style="padding-bottom:5px;" align = "top"></a></td></tr>
<tr align="left"><td><br/></td></tr><br/> </table>

</form>
<h1 style="font-family:rockwell;color:#253529;font-size:20px;" align="center">
Student Login
</h1><br>
<form name="form1" method="post" onSubmit="return check();">
<table width="200" border="0">
<tr><td><span class="style2">Username </span></td>
<td><input id="name" name="username" placeholder="username" type="text"></td>
</tr> <tr>
<td><span class="style2">Password</span></td>
<td><input id="password" name="password" placeholder="**********"
type="password"></td>
</tr> <tr>
<td colspan=2 align=center class="errors">

<input name="submit" type="submit" id="submit" value="Login">
</td> </tr> <tr>
<td colspan="3"><span class="style2"><?php echo "<font color= 'red' size='3'>".$error;
?></span></td>
</tr>
</table>
<h1 style="font-family:rockwell;color:green;font-size:15px;" align="center">
<a href="forgetpassword.php">Forget your password?</a></h1>
</form>
<br/>
<script src="style/calander.js" language="javascript"
type="text/javascript"></script>
<br/> </div> </div>

</div> 
<div id ="middle" style="height:735px;width:738px;border:1px solid #ccc;font:15px/25px
Georgia, Garamond, Serif;overflow:auto;">
<img src="images/gate.jpg" width="120%" height="40%">
<fieldset>
<h1 style="font-family:rockwell;color:green;font-size:20px;" align="center">
</h1>
</fieldset>
</div> <?php
include "menu_sub.php";
?></div> <?php
include "footer.php";?>
</div> <br /><br /><br /><br />
</body>
</html>
PHP Student Login Code

<?php
session_start(); // Starting Session
$error=''; // Variable To Store Error Message
if (isset($_POST['submit'])) {
if (empty($_POST['username']) || empty($_POST['password'])) {
$error = "Username or Password is invalid";}
else{
$username=$_POST['username'];
$password=$_POST['password'];
$con = mysql_connect("localhost","root");

mysql_select_db("education", $con);
$sql = "select * from student where username='".$username."' and password='".$password."' and
status='active'";
$result = mysql_query($sql,$con);
$records = mysql_num_rows($result);
$row = mysql_fetch_array($result);
if ($records==0){
$error = "Username or Password is invalid or your account was deactivated";
}else{
$_SESSION['stid']=$row['stid'];
$_SESSION['fname']=$row['fname'];
$_SESSION['gender']=$row['gender'];
$_SESSION['department']=$row['department'];
$_SESSION['year']=$row['year'];
$_SESSION['class']=$row['class'];
$_SESSION['email']=$row['email'];
$_SESSION['alogin']=$row['stid'];
//header("location:student/index.php");
echo' <meta content="2;student/index.php" http-equiv="refresh" />';}
mysql_close($con);
}}?>
Code for database connection

<?php
$cn=mysql_connect("localhost","root","") or die("Could not Connect My Sql");
mysql_select_db("education",$cn) or die("Could connect to Database");
?>

5.3 Testing
Final phase of implementation is testing. Testing is a process to show the correctness of the
program. Testing is checking of the system workability in an attempt to discover errors and
avoiding such errors from the system. In this the team members tested the entire system as a
whole with all forms, code, modules. In this we tested all the functionalities in the System. All
errors in the forms, functions, modules have been tested. The following are different testing
strategies.
Unit testing
Unit testing is every module of the System is separately tested. It is often done by the
programmer to test that the unit he/she has implemented is producing expected output against
given input.
Some of errors that controls are
 When administrator creates account for student, he needs to add to the system and when
they miss some information the system displays error message as follows.
For example: when username is not filled it displays:
Figure 27 unit test

Integrated testing
The process of bringing together all the modules that a program comprises for testing purpose
System testing
System test insures that the entire integrated software system meets requirements. It tests a
configuration to insure known and predictable results. System testing is based on process
description and flows, emphasizing pre-driven process links and integration points.
In essence system testing is not about checking the individual parts of design, but about checking
the system as a whole. In effect it is one huge component.
Volume Testing
The purpose of volume testing is to find weakness in the system with respect to its handling
of large amount of data during extended time periods.
Acceptance testing
The process by which users test completed information of system, the end result of which is the
user acceptance of the system. Acceptance testing checks the system delivers what was
requested.
5.3.1 Test case specifications

Before the project is released, it has to have passed through a test cases suit, so that the required
functionality is met and previous functionality of the system is also not broken to do this, there is
existing test cases which checks for the previous functionality. New test cases are prepared and
added to this existing test suit to check for the added functionality.
Test case describes an input description and compares the observed output with expected output
to know the outcome of the test case. If it is different, then, there is a failure and it must be
identified. Here we will see the result of testing in tabular format.

Test Case1: Log In
Table 27 Log in test case specification
PURPOSE: This test is done to ensure that only authorized users are permitted to use the MTU_Teaching and
Learning Support System for School Computing and Informatics.
Input Expected Result Actual outcome Pass/Fail
Valid User Name and The user logs to the The user logs to the system Pass
Valid Password system successfully. successfully.
If inserted only The system displays an The system displays an error

username,witout error message “Please message “please enter
password enter password” password” Fail
If the username or The system displays a The system displays a message Fail
password Text Box or message “please fill user “please fill user name and
both are not filled. name and password” password”

Test Case 3: New student registration
Test case name: create account
PURPOSE: This test is done to ensure that the system successfully creates account.
Table 5.2: Create user test case specification
Input Expected Result Actual Outcome Pass/Fail
All the inputs are valid The system performs the The system display a message “user
operation and redirects to the account created successfully”.
display user. Pass
If Numbers is inserted The system displays a message The system displays a message „Character
in place of name of „Character only and” and rejects. only and” and rejects
user Fail
All valid inputs and The system displays a message The system displays a message „Incorrect
invalid E-mail „Incorrect email” and rejects. email” and rejects.
Fail
If the confirmation The system displays a message The system displays a message „Password
password is not valid „Password not matched” and not matched” and rejects.
rejects. Fail
If all input are valid The system displays a message “ The system displays a message „user is Fail
and the inserted id is This user is exist” and rejects. exist” and rejects.
exist in education
database
Test Case 3: Performance
Purpose: To check whether the system responds to a request by the user within a few seconds.
Table 5.3: Performance test case specification
Inputs Expected Result Actual Outcome Pass/Fail
Data entered to one of the The system should respond The system should respond Pass
form and using one of the automatically within a few automatically within a few
buttons. seconds as soon as the user seconds as soon as the user sent
sent the request. the request.

Test Case4: Integration
Purpose: To check whether the different component of the system work together.
Table 5.4: Integrity test case specification
Inputs Expected Result Actual Outcome Pass/Fail
Trying to load the The different component of the The different component of the
other forms by using system should work together. system work together.
the main form. Pass
Accessing the data by The system displays the data The system displays the data
using the different from the data base from the data base
forms Pass
5. 4 User manual presentation

User manual is document describing the user interface of the system such that a user unfamiliar with the
system can use it. It states about the operation information for the portions of the system. This part will help
the user to develop an ability to read and understand the considerable information presented in the software.
o Getting started
Activate Xampp server from the Desktop or Start up Menu if it‟s not activated. Then click on start of
Apache and MySQL to stop..

Then that click on MySQL Admin to access php admin and it open browser.
 In the run new tap type the URL of the page (example localhost/edu/index.php) and the enter from
keyboards.
5.5 Hardware and software acquisition

Software
 Network card and fast Ethernet port for networking and connectivity.
 Windows 7 operating system
 Noted++
 web browser
 Adobe photo shop
Hardware
 Flash disk 8GB
 Computer
 Printer
 Cable

CHAPTER VI
Summary, Conclusion and Recommendation
6.1 Summary
The development and advancement of computer technology makes computers to be a part
of everyday human life activities. Education is an area where the human is involved in a day to
day exercise of his life. It is an area which requires due attention, for it deals with behavioral,
attitude and skill changes. The same is true for the use of computer in education. This work has
enabled the delivery of learning materials to be efficient and it has also achieved interexercise
among students and instructors. Furthermore it has established the support education based
learning theory along with the collaborative based to be applicable for the School of computing
and informatics in MTU. These project work by HTML web page and developed using the php
web technology.
6.2 Conclusion
In general the project (system) that the team developed will benefit the University by changing
its business range from helping the manual to computerize by developing web based application.
The overall benefits of the system are:
 Provide sufficient services.

 Minimize the time required to perform task.
 Facilitates the services given by the University in case of teaching and learning process.
 Facilitates by giving practical exercise
While developing a system in Team the group member have acquired more knowledge and
experience about the different phases of the software development life-cycle, design and other
programming language. As software developers, the team has worked together and assessed
risks, and minimizes them.

6.3 Recommendation
Using this new system will make the university more profitable than before or to achieve
their goals that is to give attention for giving education ,so the team greatly recommends the to
give more attention to this new developed system.
We would like to recommend that the system is open for interested groups or individuals who wish to add
new functionalities especially for all college and school in Mizan_Tepi University.
Finally we would like to recommend to Mizan-Tepi University to use this system by enhancing it to
the way it can give short term training education to the students.

6.4 Reference
Books
 ObjectOriented_Software_Engineering Using UML
 Systems_Analysis_and_Design___Ninth_Edition.
 The_unified_modeling_language_reference_manual_second_editiin
Internet
 http://www.google.com /online teaching and learning
 http://www.codeproject.com
 http://www.sourcecodester.com/
 http://www.findsourcecode.com
 http://www.freestudentprojects.com
 http://www.f1sourcecode.com/

6.5 Glossaries of the terms
Definition of Terms
MTU--Mizan-Tepi University
SCI--- school of computing and informatics
Mgmt.—management
Act or act--exercise
Acc ---account
Pass or pswd—password
DB--database
MTUDB -- Mizan-Tepi university data base
HTML-- hypertext markup language
UML -- unified modeling language
IS---Information System
IT---Information Technology
CS---Computer Science
Usn-username

Naga Ass A A Documentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Naga Ass A A Documentation

Uploaded by

Copyright:

Available Formats

Mizan-Tepi University

School of Computing and Informatics

2. Natenael ……… Mekonen ETR/594/04

3. Merob …………….. Tegene ETR/528/04

4. Dechasa ……… …Asratu ETR/237/04

5. Abdurahman ………….Abay ETR/521/04

ADVISOR: prof.ephraim uy. Basal

Submission date: 05/10/2007

Name and signature of Members of the Examining Board

Name Signature Date

___________________________ ____________ ___________

___________________________ ____________ ___________

___________________________ ____________ ___________

___________________________ ____________ ___________

___________________________ ____________ ___________

___________________________ ____________ ___________

___________________________ ____________ ___________

Name______________________ Signature_______________ Date__________

2. NATENAEL MEKONEN Signature_______________ Date__________

3. MEROB TEGENE Signature_______________ Date__________

4. DECHASA ASRATU Signature_______________ Date__________

5. ABDURAHMAN ABAY Signature_______________ Date__________

MTU_Teaching and Learning Support System for SCI IT 2015 Page i

MTU_Teaching and Learning Support System for SCI IT 2015 Page ii

The development and advancement of computer technology makes computers to be a part

MTU_Teaching and Learning Support System for SCI IT 2015 Page iv

MTU_Teaching and Learning Support System for SCI IT 2015 Page v

MTU_Teaching and Learning Support System for SCI IT 2015 Page vi

Figure 1 Input output process for preparing learning resources ................................................................. 10

MTU_Teaching and Learning Support System for SCI IT 2015 Page 1

1.2 Background of the Project

MTU_Teaching and Learning Support System for SCI IT 2015 Page 2

1.3 Statement of the problem

1.4 Objectives of the Project

1.4.1 General Objectives

1.4.2 Specific objectives

1.5 Scope and Limitation

1.5.1 Scope of the Project

 Uploads of learning resources (handout, reference, and teaching videos)

1.5.2 Limitation of the Project

2. The given question is only choice

1.6 Significance of the project

1.7 Feasibility Analysis

1.7.1 Economic Feasibility

1.7.2 Technical feasibility

1.7.3 Time Feasibility

1.8 Data Collection Methodology

1.8.1 Observation and interview.

MTU_Teaching and Learning Support System for SCI IT 2015 Page 5

1.8.2 System Analysis and Design Methodology

MTU_Teaching and Learning Support System for SCI IT 2015 Page 6

3 Object Oriented Analysis

4 Designing the system

Table 1 project schedule

MTU_Teaching and Learning Support System for SCI IT 2015 Page 7

Item Quantity Unit cost per item (in Total in birr

Printing 90 paper 2.00 180.00

MTU_Teaching and Learning Support System for SCI IT 2015 Page 8

Description of the existing system

2.2 Major functions/Activities in the Existing System

 Preparing learning resources.

MTU_Teaching and Learning Support System for SCI IT 2015 Page 9

Figure 1 Input output process for preparing learning resources

_________________ _

_________________ _

_________________ _

_________________ _

_________________ _

_________________ _

_________________ _

Name______________ Signature_ Date____

2. NATENAEL MEKONEN Signature_____ Date

3. MEROB TEGENE Signature_____ Date

4. DECHASA ASRATU Signature_____ Date

5. ABDURAHMAN ABAY Signature_____ Date