New Documentation

ABSTRACT
The university is one of the fields that are embracing technology to improve education, facilities, and
systems on campus. Unfortunately, not all universities today are still equipped with the necessary
technology to meet their needs. They are still tallying the results of faculty evaluations manually, which is
time-consuming and frustrating for university personnel. Our Admas University at Addis Ababa, Ethiopia
instructors are evaluated by manual paper based evaluation question. The existing system is not fully
computerized. There is fully manual job. First the form is prepared by the university standard based on
different criteria to different evaluators such as: - forms filled by student, co-workers, and head with a
little different criterion. Instructor evaluation is widely regarded as the most effective tool for improving
the quality of instruction in universities. In almost every stage of the decision-making process, timely and
accurate information is useful. The Online Instructors’ Evaluation System will facilitate the collection and
analysis of faculty evaluation data in less time. The Online Instructors’ Evaluation Systems is a paperless
process in which the evaluator evaluates the teacher using the computer and the system. Students and
instructors or administrator evaluation of teaching is a student or instructor or administrator to teacher’s
teaching work evaluation, to carry out this work is the starting point of improving teachers' teaching
quality. This paper discusses the use of PHP and SQL Server technology design and implementation of an
online teaching evaluation system. The whole system is divided into students or instructors operating and
backstage management of two modules, the system needs to design the database of the evaluation of
teachers' work, focusing on the Session object, data aggregation processing, validation, and other key
technologies, and finally introduce the entire system to run the application instance and effect, and shows
the main functions of the system. Compared with other similar systems, it does not usually need to have
large amounts of data management and maintenance. The results of the software evaluation met the
researchers’ objectives and are thus worthy of continuation and development. The overall mean of the
system evaluation indicated that the developed study was extremely useful and could be of great
assistance to the university. The outcomes of the faculty members’ evaluations improved their usage.
Here we conducted the Online Instructors’ Evaluation Systems at Admas University, Addis Ababa,
Ethiopia. In this project, we developed an IES that facilitates various activities taking place at the Admas
University, Addis Ababa, Ethiopia. The IES do different activities such as evaluate instructor and view
average result. This project must be an active document that grows with changes while anticipating future
requirements like integrates the system to Admas University student website or registrar.
ACKNOWLEDGEMENT
We would like to acknowledge all those very helpful people who have assisted us in our project. We want
to thank Mr. Mezgebu for his patience and guidance, all instructors of Admas university, and Mr.
Muluken and Mr. Mosses for providing us with materials in abundance.
Contents
.................................................................................................................................................................... 1
Submitted to: Mr Mezgebu Ayenabeba.......................................................................................................1
ABSTRACT....................................................................................................................................................2
ACKNOWLEDGEMENT.................................................................................................................................3
CHAPTER ONE: INTRODUCTION...................................................................................................................1
1.1 Background of the organization.............................................................................................................1
1.2 Motivation.............................................................................................................................................1
1.3 Statement of the problem.....................................................................................................................2
1.4 Objectives..............................................................................................................................................2
1.4.1 General objectives..........................................................................................................................2
1.4.2 Specific objectives...........................................................................................................................2
1.5 Literature review...................................................................................................................................2
1.6 Scope and limitation..............................................................................................................................3
 Scope...................................................................................................................................................3
 Delimitation.........................................................................................................................................4
1.7 Methodology.........................................................................................................................................4
1.7.1 Data gathering techniques..............................................................................................................4
1.7.2 System analysis and design methodology......................................................................................5
1.8 System development model..................................................................................................................5
1.9 System development tools....................................................................................................................5
1.9.1 Hardware tools...............................................................................................................................5
1.9.2 Software tools.................................................................................................................................5
1.9.3 Documentation tools......................................................................................................................6
1.10 Significant of the project.....................................................................................................................6
1.11 Feasibility study...................................................................................................................................7
1.11.1 Technical feasibility......................................................................................................................7
1.11.2 Operational feasibility...................................................................................................................7
1.11.3 Economic feasibility......................................................................................................................7
1.12 Work breakdown structure and schedule...........................................................................................8
CHAPTER TWO: SYSTEM ANALYSIS............................................................................................................10
2.1 Introduction to system analysis...........................................................................................................10
2.1.1 Existing system.............................................................................................................................10
2.1.2 Proposed system..........................................................................................................................10
2.2 Functional requirements.....................................................................................................................10
2.3 Non-functional requirements..............................................................................................................13
2.4.1 Actor identification...........................................................................................................................14
2.4.2 Use case identification......................................................................................................................14
2.5 Use case description............................................................................................................................15
2.6 Sequence diagram...............................................................................................................................22
2.7 Activity diagram...................................................................................................................................24
2.8 Class diagram.......................................................................................................................................24
2.8.1 Class implementation...................................................................................................................24
CHAPTER THREE: DESIGN..........................................................................................................................26
3.1 Purpose and goals of design................................................................................................................26
3.3 Current software architecture.............................................................................................................27
3.4 Proposed software architecture..........................................................................................................27
3.4.1 Subsystem decomposition............................................................................................................27
3.4.2 Component diagram.....................................................................................................................27
3.4.3 Deployment diagram....................................................................................................................27
3.4.4 Persistence modeling for OODB...................................................................................................28
3.4.5 Access control and security..........................................................................................................31
3.4.6 Boundary conditions and exception handling...............................................................................32
3.4.6.1 Boundary Conditions.............................................................................................................32
3.4.6.2 Exception Handling...............................................................................................................32
3.5 User interface design...........................................................................................................................33
CHAPTER FOUR: SYSTEM IMPLIMENTATION AND TESTING.......................................................................36
4.1 Implementation...................................................................................................................................36
4.1.1 Introduction..................................................................................................................................36
4.1.2 Coding standards..........................................................................................................................36
4.1.3 Implementation strategy..............................................................................................................36
4.2 Testing.................................................................................................................................................36
4.2.1 Test type.......................................................................................................................................36
4.2.2 Overview of manual testing and automated testing tools............................................................37
4.2.3 Test plan.......................................................................................................................................37
4.2.4 Defects classification management..............................................................................................37
4.2.5 Test report....................................................................................................................................38
CHAPTER FIVE: CONCLUSION AND RECOMMENDATION...........................................................................39
5.1 Conclusion...........................................................................................................................................39
5.2 Recommendation................................................................................................................................39
Glossary.....................................................................................................................................................39
References.................................................................................................................................................40
Annex 1: Sample coding for HTML (index).................................................................................................43
Annex 2: Sample coding for DB (To student).............................................................................................55
Annex 3: Sample coding for result report..................................................................................................56
Annex 4: Sample coding for login..............................................................................................................61
CHAPTER ONE: INTRODUCTION
1.1 Background of the organization
Admas University commenced its operation in October 1998 under the name “Admas Business Training
Centre.” Then Training Centre then started delivering training services in certain tailor–made, six–month,
short–term programmes. By undertaking deep assessments of further training needs and making
preparations in terms of the required human and material resources, the centre upgraded itself to a college
status as of April 1999. After deep objective assessments of further training needs and making
preparations in accordance with the requirements of the Ministry of Education, the College was upgraded
to the status of a University College as of March 2007. Admas University has become a fully-fledged
university as of July 2014 (Hamlie 2006 E.C.). [26] With the objective of expanding its quality services,
the University opened ten (10) colleges/campuses/faculties so far. Eight of these campuses are found in
Ethiopia among which six are in Addis Ababa while the rest two are in Bishoftu and Mekelle towns. The
other two campuses are located out of Ethiopia in the capitals of Somaliland and Puntland (i.e. Hargeissa
and Garowe, respectively). Apart from the regular mode, the University also has a Distance Education
College with more than 50 (fifty) coordination offices throughout the country.
Instructor’s evaluation is a necessary step in ensuring proper instruction. Traditionally, instructors’

evaluation is used as a tool to appraise instructors on how they are doing their job.
The term ”performance” refers to a series of outcomes produced over a period of time and does
not refer to the performer’s attributes, personal characteristics, or competencies. It is intended to
identify the strengths and flaws of teaching. Instructors’ evaluation is typically regarded as the most
effective approach for improving the quality of education in the university. In almost every stage of the
decision making process, timely and reliable information is useful. The Online Instructors’ Evaluation
System will facilitate the collecting and analysis of faculty evaluation data in less time. The Online
Instructors’ Evaluation System is a paperless process in which the evaluator evaluates the teacher using
the computer and the system. The university is one of the fields that are adopting technology to improve
education, facility, and systems that they are using inside their campus. Unfortunately, today, not all
universities are still equipped with the proper technology to use for the advancement of their needs. In
terms, if processing a faculty evaluation to be used for the semester, Admas university is one of them.
They are still using the manual procedure of tallying the result of faculty evaluation which is very time-
consuming and frustrating for the university personnel.
1.2 Motivation
Instructor’s evaluation is widely understood to the most effective tool to improve the quality of
instruction in universities. Accurate information is useful in virtually every stage of the decision making
process. Problem are identified when information reveal that some aspects of performance can be place in
the hands of decision makers, the sooner problems can be corrected, lessening the potentially undesirable
or costly consequences to the organization. So that we motivated to do the Online Instructors Evaluation
system because:
A big interest on web based application.
1
To apply our favorite PHP, Java script, OOP knowledge
To share our contribution for the coming generations who will do on instructor evaluation system
To come up with a unique, simplified, and easy to apply system
To solve the bottlenecks of paper based instructor evaluation approach
1.3 Statement of the problem

Now a day due to paper works instructors evaluation systems, there are a lot problems when we use paper
based such as it is not economic:- there is extravagance in paper, printing resources; there is wastage of
labor and time; it is difficult to calculate the overall evaluations of a single instructor; it is not accessible
etc. So that we decide to work on instructors’ online evaluation systems to alleviate such problems.
1.4 Objectives
1.4.1 General objectives
The general objective of this research proposal is to develop an online instructor evaluation system for
higher education institutions that is user-friendly, reliable, and valid. The system should be able to
provide accurate data on instructor performance that can be used for both formative and summative
purposes.
1.4.2 Specific objectives

The specific objectives are the following.
To develop an online evaluation system for instructors that is user-friendly and easy to
navigate at Admas University.
To provide an efficient and effective way to evaluate instructors’ teaching effectiveness.
To create a system that allows instructors to receive feedback on their teaching skills and make
improvements to their teaching methods.
To enhance the quality of education by promoting effective teaching practices.
To create a module that will evaluate faculty according to the following criteria:
Methodology and teaching strategies
Class room management
Personality & interpersonal skills.
1.5 Literature review

Instructor evaluation is a critical component of any higher education institution’s assessment process. It
allows students to provide feedback on their instructors’ performance, which can help improve the quality
of education. However, traditional paper-based evaluation systems are often time-consuming and
2
inefficient, and they may not capture all the relevant data. [21] An online evaluation system could be a
more efficient and effective way to collect instructor feedback. Teaching performance evaluation is a
necessary and important step to ensure good teaching instruction. Traditionally teaching performance
evaluation is used as a tool to update teachers on how they are doing their job. Performance is defined as
a set of outcomes produce during a certain period of time and does not refer to the attributes, personal
characteristics or ability of the performer. [25]
Instructor’s evaluation is widely understood to the most effective tool to improve the quality of
instruction in universities. Accurate information is useful in virtually every stage of the decision making
process. Problem are identified when information reveal that some aspects of performance can be place in
the hands of decision makers, the sooner problems can be corrected, lessening the potentially undesirable
or costly consequences to the organization. [20]
With these insights and concepts in mind, the researcher’s wishes to improve the process of the evaluating
teachers in selected private schools in Addis Ababa City, (Ethiopia), preferably Admas University, in
order to contribute to a more efficient faculty monitoring and evaluation records in the university
environment. Systems for teacher evaluation vary from sophisticated national systems to localized,
informal approaches. [23]
There are a lot related works by researchers from simple to advance by using data mining techniques
especially 6th International Conference on Smart Computing and Communications, ICSCC by Alok
Kumara and Renu Jain 2017, Faculty Evaluation System. [24] Under this paper, the students have a full
responsibility to assign their own evaluation criteria’s and can evaluate their instructors. And the system
can generate different reports like individual teacher report which is only based on the students feedbacks,
teacher comparative report which is comparatively describe the efficiency of the instructors with the
colleagues, and feature grading report which shows the letter grading of the instructors efficiency based
on the students criteria’s.
In addition to this, there are so many systems which can report the performance of the teacher in
qualitative data. For example Addis Ababa university instructor evaluation system give
feedbacks qualitatively. There is similar work too in Mekele University which was conducted by first
degree computing department graduate students. This system can compute both qualitative and
quantitative data of the instructors. [27]
1.6 Scope and limitation

In this study, the researchers adopted to develop the proposed system with the following features. This
system will collect and more accurate data analysis of instructors’ evaluation in lesser time. The system
has provided easy to access to the faculty and students during evaluation. The following are the
capabilities and features of the system.
 Scope
Secured evaluation results
Displays reports
3
Can print semester and yearly reports instructors’ evaluation forms
Accepts and validate users
Generate the evaluation results
Ready for online and Intranet/internet
Only the admin and the concerned staff can see the results
 Delimitation
The student can only evaluate once per semester
The student can only evaluate his/her professor once
The system will be used once every semester
One student can proxy for another student while students are taking the evaluation on their own device in
their own time
It increases the chance of not providing the exact data sometimes
Lack of response rate: One of the primary challenges with online instructor evaluations is that they often
have a low response rate. Students may be less likely to complete evaluations if they feel they won’t be
read or acted upon, or if they don’t feel invested in the process
Limited scope: Online evaluations may not provide a comprehensive picture of an
instructor’s performance. They may only focus on certain aspects of teaching, such as course content or
instructional delivery, and may not capture other important factors, such as the instructor’s engagement
with students outside of class
Insufficient feedback: Some online evaluation systems may only provide limited feedback to instructors,
which can make it difficult for them to identify areas where they need to improve
Lack of standardization: Online evaluation systems may vary in terms of their format and questions,
which can make it difficult to compare results across different courses or instructors
Bias and subjectivity: Online evaluations may be subject to bias and subjectivity. For example, students
may rate an instructor poorly if they disagree with their teaching style, rather than objectively evaluating
the quality of their instruction
1.7 Methodology
1.7.1 Data gathering techniques
In order to gather the relevant data, we use both primary and secondary way of data collection so that help
us for studying the system analysis.
4
Primary data collection: Practical observation:-enables us to list out the existing system problems, since it
is what we see or observe in reality.
Secondary data collection: we were going to faculty of informatics department head, Mr. Mezgebu
Aynabeba, and we get forms that are prepared for the university standards.
1.7.2 System analysis and design methodology

The project is conducted in three phases.
Phase-1: Requirements gathering: The first phase of the project involved gathering requirements for the
online evaluation system. This involved conducting a literature review of similar systems and
interviewing instructors and students to understand their needs and preferences
Phase-2: System design and development: The second phase of the research proposal will involve
designing and developing the online evaluation system based on the requirements gathered in Phase 1.
The system will be designed to be user-friendly and accessible to both instructors and students
Phase-3: System testing and evaluation: The final phase of the research proposal will involve testing and
evaluating the online evaluation system. This will involve conducting a pilot study to evaluate the
system’s effectiveness in promoting the system’s reliability, validity, and usability. The third and final
phase will involve analyzing the data collected in the pilot study and making revisions to the online
evaluation system based on the findings.
1.8 System development model

The project modeling process is prototyping. Users are actively involved in the development. Since in this
methodology a working model of the system is provided, the users get a better understanding of the
system being developed. Errors can be detected much earlier. Quicker user feedback is available leading
to better solutions.
1.9 System development tools

1.9.1 Hardware tools
This system was web based application. To run these system users need electronic devices like
Computers starting Window 10 OS, Mobile Phones (Both in Android and iPhones) that contain internet
connection and support any browsers like Chrome, Firefox etc.
1.9.2 Software tools

Among different design methodology, we developed our system by object oriented design paradigm.
Front-end Technologies: We used the front-end of the software systems developed using HTML, PHP,
JavaScript, CSS, and Bootstraps.
Back-end Technologies: One of the most important technologies in the implementation, and deployment
of the software system is the back-end or database technology. We decide to use MySQL.
MySQL server compared to others:
5
MySQL Advantage is a suite of for web based application, and well- supported ones–that work together
to run interactive, dynamic Internet sites.
MySQL is characterized as a free, fast, reliable open source relational database. It does lack some
sophistication and facilities, but it has an active development team and, as it goes from release to release,
more capabilities are added. At certain times there will be a trade-off between speed and capabilities, and
the MySQL team intends to keep their database engine fast and reliable.
My SQL Features:
Because of its unique storage engine architecture MySQL performance is very high
Supports large number of embedded applications which makes MySQL very flexible
Use of Triggers, Stored procedures and views which allows the developer to give a higher productivity
Allows transactions to be rolled back, commit and crash recovery
It's secure: MySQL includes solid data security layers that protect sensitive data from intruders. Rights
can be set to allow some or all privileges to individuals. Passwords are encrypted
It's inexpensive: MySQL is included for free with NetWare® 6.5 and available by free download from
MySQL Web site
1.9.3 Documentation tools

All pieces of software should have some form of documentation that explains, in detail, what the product
is, how it works, and why it works that way.
“If it isn’t documented, it doesn’t exist” – Sitepoint, A Guide to Writing Your

First Software Documentation
[28] So that we used MS-Word, MS-PowerPoint, MS-Visio, LaTeX (Especially for proposal), and some
code editors like VS Code to generate or edit some codes. And for writing purpose and save the codes, we
used different devices; desktops and laptops.
1.10 Significant of the project

The people who benefited from the Online Instructors’ Evaluation System are the following.
Administrator: It is now easier for the administrators of the university to focus on analyzing the
performance of individual faculty members in order to find their strengths and weaknesses, as well as
how to use the data to make merit pay and promotion decisions. They can use a valid and reliable faculty
performance record to do this. This system will assist the administrator in reducing the amount of time
spent processing, encoding, and computing the assessment.
Faculty: The system would offer faculty with an instant result of their evaluation, which will assist them
in improving their teaching approaches. The system will assign a score to each component of the
evaluation and will indicate the faculty member’s strong and poor points.
6
Students: The system gives opportunities for the students to express their gratitude and acknowledgment
for outstanding faculty members, as well as a means of communicating their thoughts and concerns about
underperforming faculty members without regard for time or space constraints.
Future Researchers: To the future researchers, this program designed software and hardware will serve as
an effective tool and reference who would intend to make any further relevant study particularly the
Online Instructors’ Evaluation System.
1.11 Feasibility study

Before analyzing the problem and understand the context of this project, we have to analyze the
requirement of the task to perform. So now we are going to analyze the requirement. We are going
through some phase in this term. In the first phase we have to study the existing system, compare to the
requirement of the new system. Both are equally important to make it better. First activity serves as a
basis of giving the functional specifications. Then, successful design of the proposed system. It is difficult
to understand the properties and requirement of a new system. Also it is equally difficult to think of
existing system. So we can go through feasibility study.
Feasibility is measure of how beneficial the development of the application will be to an organization.
This is done by studying the existing system and get the ideas about new system.
There are some considerations are important in feasibility analysis. They are economic,
technical, and operational.
1.11.1 Technical feasibility

In this new system evaluation permission is given by the departmental admin and students fill the
questions form by their taken subject in his present semester. And Admin will give the centralized
permission including for instructors too. And input, output, permission, procedures are checked
technically. So technically it will more feasible than manual system.
1.11.2 Operational feasibility

If we can turn out the proposed system into an information system then it will beneficial. That will meet
the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as
an important part of the project implementation. Some of the important issues raised are to test the
operational feasibility of this system or project. Some operations are used to check the system and solve
it. The system will be used and work properly if it is being developed and implemented. User
authentications are to be safe.
1.11.3 Economic feasibility

Economic analysis is the most used method for the measurement of effectiveness of a proposed system.
We can call it cost benefit analysis, which is a procedure to determine the benefits and saving that are
expected from this system compare with costs. The innovation of the new system has much influence on
the economical side. Manual system is costly. And waste of paper. If users are fluent with the new
automated system it will cut down the costs, which is economically feasible.
7
1.12 Work breakdown structure and schedule
A work-breakdown structure (WBS) in project management and systems engineering is
a deliverable-oriented breakdown of a project into smaller components. A work breakdown
structure is a key project deliverable that organizes the team's work into manageable sections.
8
9
CHAPTER TWO: SYSTEM ANALYSIS
2.1 Introduction to system analysis
2.1.1 Existing system
The existing system to evaluate is manual. An A4 sized paper is provided to the student and student fill
the teacher’s code, course code etc. Then the fill their answer of the provided MCQ questions about the
course teacher or instructor based on how the course teacher maintain and teach the course. And then
manually go through the answer sheet and manually calculate the points. We think it is too long process
and time consuming
2.1.2 Proposed system

Instructor’s Evaluation system is a web application more reliable and efficient service. Any operations
can be done easily with an easy interaction with the system. Furthermore the system especially could
evaluate instructors and might calculate the evaluation result more easily than before the existing system.
The proposed system has many applications and advantages compared to the existing system. It solves the
problems of the existing system and increase the performance of the evaluation. In our proposed system
we develop a web based application instructor’s evaluation system that is capable of controlling the
evaluation form. The applications of proposed system are:
Replace the manual to automated system
The proposed system enables to calculate the evaluation result and store evaluation information in the
database
The application composes different forms to store data to the database and retrieve required information
from the database
Create accounts for different users
2.2 Functional requirements

The functional requirements of proposed system are:
[FR-01]: Add admin information
Description: The system must allow the administrator continuously add admin information based on the
correct input given.
Requirements: The system need inputs like full name, email address, Image, PW. Fill the inputs
correctly.
Last action: Click on save
[FR-02]: Add subject information
Description: The system must allow the administrator continuously add subject information based on the
10
Requirements: The system needs inputs like subject code, subject, description. Fill the inputs correctly.
[FR-03]: Add class information
Description: The system must allow the administrator continuously add class information based on the
Requirements: The system needs inputs like curriculum, year level or batch, section. Fill the inputs
correctly.
[FR-04]: Add academic year
Description: The system must allow the administrator continuously add academic year based on the
Requirements: The system needs inputs like year and semester. Fill the inputs correctly.
[FR-05]: Add evaluation criteria
Description: The system must allow the administrator continuously add evaluation criteria based on the
Requirements: The system needs inputs criteria’s. Write down the criteria on the space criteria form.
[FR-06]: Delete evaluation criteria
Description: The system must delete evaluation criteria based on the order.
Requirements: The system must allow the administrator to delete evaluation criteria in the system by
clicking the delete button.
[FR-07]: Update evaluation criteria
Description: making or becoming different from the previous record.
Requirements: To update evaluation criteria fill the criteria id what you want then click update button.
[FR-08]: Add questionnaires
11
Description: The system must allow the administrator continuously add specific evaluation criteria which
are called questionnaires based on the correct input given.
First click on Action, then manage. Now we have two options or tasks that should be done.
Question form
Requirements: The system needs inputs like evaluation criteria (Just select from the database) and
questions which are the specific evaluation criteria.
Evaluation restriction or assigning of instructors for evaluation
Requirements: The system needs inputs like instructor name to be evaluated, his/her class, and his/her
subject (Just select from the database).
Last action: Click on add list followed by save
[FR-09]: Add student and instructor records
Description: The system must continuously add students and instructor information based on the correct
input given.
Requirements: The system need inputs like full name, school id and class (Just select from the database),
email address. Fill the inputs correctly.
[FR-10]: Evaluate information
Description: The system must display the instructor to be evaluated for each single criterion.
Requirements: Evaluate the instructor based on the criteria.
Last action: Submit evaluation
[FR-11]: Evaluation report: instructor report or overall report
Description: The system must display the instructor or overall evaluation result in table format for each
single criterion with its number of participants.
Requirements: The admin firstly select instructor name then click the view evaluation result button.
Last action: The admin can generate the result as printable hard copy or save as pdf.
[FR-12]: Create account
Description: The system must continuously create account based on the correct input given.
Requirements: The system need inputs like username, password, email address.
12
2.3 Non-functional requirements

Non-functional requirements of the proposed system are:
[NFR-1] Usability
Description: the system must be easy understandable by the clients.
Requirement: the system is object oriented approach.
[FR-2] Reliability
Description: it describes the functionality of the system
Requirement: the system must be includes all the requirements of the client
[NFR-3] Performance
Description: describes the ability of the system for its function and Waiting for an application to load can
be frustrating for an end user. so make them a quick start up is extremely important
Requirements: The System must have a startup time of less than 5 seconds
[NFR-5] Supportability
Description: the system must be run in all operating systems
Requirement: The system must compile and run successfully on any Windows
[NFR-7] Implementation
Description: The system is implemented using PHP, HTML and uses MySQL for DB
Requirement: the system must be corrective, adaptive, or perfective though time
[NFR-8] Interface
Description: boundary between the user and the system
Requirement: the system has an interface that enables for the data flows from the DB
[NFR-9] packaging
Description: installing of the system by the client to use it
Requirement: the installation time must be less than 5minutes
13
2.4.1 Actor identification
The operating environment of a software system consists of the users, devices, and programs that the
system interacts with. These are called actors. Therefore we have primary actors (initiates an interaction
with the system) and secondary actors (The system initiates interactions with secondary actors). For
example a user clicks the search button on an application's user interface. The application sends SQL
query to a database system. The database system responds with a result set. The application formats
displays the result set to the user. In this scenario the user is a primary actor because he initiates the
interaction with the system (application). The database system is a secondary actor because the
application initiates the interaction by sending an SQL query. Here we have three actors in our projects.
So that the primary actor is administrator and the secondary actors are the students and the instructors.
2.4.2 Use case identification

Use case diagrams are created to visualize interaction of our system with external world. Also a
use case model is the representation of the system intended functions and its environment. The
functionalities are specified by the “use case” and “the actor “specified to the environment. Since
the identification of these two entities goes hand in hand, we have identified them together.
The actors are: -
 Student
 Instructors
 Head
 Administrator
The use cases are: -
 Login
 Evaluate Instructors
 Update account
 Create account for user
 Add instructor records
 View evaluation result
 add new evaluation Criteria
 Delete evaluation criteria
 Modify evaluation criteria
 Register department information like Semester, Batch, Section, Year, Course
14
uc Use Case Mo...
SOC Instructor Evaluation
Add departments add ev alutain criteria
add course
Add Semister
<<initiate>>
<<initiate>>
«include»
+<initiate> «include»
add section
«include»
<<initiate>>
«include» <<initiate>>
Set parameter
«include»
«include» Update Ev aluation criteria

Chairhead <<initiate>> «include»
<<initiate>>
Login Administrator
«include»
Add Instructor <<initiate>>
«include»
«include»
«extend»
Update Instructor
Update Account
View Ev aluation Result
<<initiate>>
Logout
Initiate
<<initiate>>
Ev aluate
<<initiate>>
Instructor
students
Figure 1 use case diagram
2.5 Use case description

Add student and instructor records
Use case Add student and instructor records
name
Identifier UC 001
Actor(s): Chair Head
Description Allows Chair Head to add records of the Chair students and
instructors.
Precondition Chair Head must have an account, the students and the
instructors are going to register in the Chair.
15
Basic course 1. Click on Add record button
of actions 2. Choose to add the students or the instructor’s record.
3. Fill the information
4. Click Add button
5. Use case ends
Alternative Step1. If the Chair Head don’t have an account, the login
course of fails.
action Step4. If the students or the teacher’s information is not
correct or not fully added. Add record will fail.
Post The teachers or students information is added.

condition
Add Chair Head Record
Use case Add Chair Head Record

name
Identifier UC 002
Actor(s) Administrator
Description Allow administrator to add the Chair Head information.
Precondition Administrator must have an account and the Chair head must
be selected as a Chair head by the admin.
Basic course 1. administrator login in his/her own account
of actions 2. Click on Add record button
3. Fill the information
4. Click Add button
5. Use case ends
Alternative Step1. If the administrator doesn’t have an account, the login

course of fails.
action Step3. If the Chair head information is not correct or not
fully added. Add record will fail.
Post Chair head information is added
16
condition:
Fill evaluation form

Use case Fill evaluation form
name
Identifier UC 003
Actor(s) Student, instructors, Chair head
Description Allows the Actor(s) to fill the evaluation form to evaluate
teachers
Preconditio Actor(s) must be authorized to perform this activity and the
n Chair Head must activate the evaluation date and the
evaluation instructor’s.
Basic 1. Actor(s) enters username and password to the system.

course of 2. Clicks on evaluation button
actions 3. Selects the teacher name to evaluate.
4. Fills the evaluation form.
5. The system calculates the evaluation result
6. Clicks save button
7. The use case ends
Alternative Step 1. If the student’s username or password is incorrect the

course of system displays incorrect username or password and displays
action try again.
Step 4. If the evaluation form is filled partially or not filled
at all, the system displays fill all the fields’ message.
Post the system will calculate the evaluation result
condition
Modify account information

Use case Modify account information
17
name
Identifier UC 004
Actor(s) Administrator, Chair Head, instructor’s and Student
Description Allows all the users to modify their account information
from the system
Preconditio all users must have an account
n
Basic course 1. Enters username and password to the system.
of actions 2. Clicks update button
3. selects the place to update their password
4. modify the password
5. Clicks save button
6. The system saves changes made by the user
7. The use case ends
Alternative Step 1. If the user’s username or password is incorrect the

course of system displays incorrect username or password and displays
action try again.
Post the user account information will be updated

condition
View evaluation result
Use case View evaluation result

name
Identifier UC 005
Actors Chair head, instructor‘s
Description Visits the calculated result that came from students

evaluation form.
Precondition Both Chair head and instructor‘s must have an account and
18
the student must full fill the evaluation form.
Include Calculate evaluated result
Basic course 1. Both instructor‘s and Chair head login in his/her own
of action account
2. Click evaluation result button
3. The Chair head have the ability to visit the evaluated
result of all of the instructor‘s.
4. The instructors have the possible ability to visit only
his/her evaluation result.
5. Use case ends
Alternative Step 1. If both instructor‘s and Chair head doesn’t have an

course of account, then the login will fail.
action
Post The system will display all the instructors’ evaluated results.
condition
Add new evaluation criteria
Use case name Add new evaluation criteria
Identifier UC 006
Actors Chair head
Description Allows Chair head to add new evaluation criteria

or new evaluation question.
Precondition Chair head must have an administrator account.
Basic course of action 1. Chair head logins in his/her own account.

2. Clicks on the Add button.
3. Writes new criteria’s to be added.
4. Then clicks the save button.
19
5. Use case ends.
Alternative course of Step 1. If Chair head doesn’t have an account,
action then the login will fail.
Post condition The evaluation criteria successfully added
Modify evaluation criteria
Use case Modify evaluation criteria

name
Identifier UC 007
Actors Chair head
Description Allows Chair head to update evaluation criteria or update

evaluation question.
Preconditio Chair head must have an administrator account.

n
Basic course 1. Chair head logins in his/her own account.

of action 2. Clicks on the update button.
3. Searches the questions to be updated.
4. Update the questions selected.
6. Use case ends.
Alternative Step 1. If Chair head doesn’t have an account, then the login
course of will fail.
20
action Step 3.If the question that is being searched is not available
the system displays error message.
Post The evaluation criteria successfully updated
condition
Delete evaluation criteria

Use case Delete evaluation criteria
name
Identifier UC 008
Actors Chair head
Description Allows Chair head to delete evaluation criteria or evaluation
question.
Precondition Chair head must have an account.
Basic course 1. Chair head logins in his/her own account.
of action 2. Clicks on the delete button.
3. Searches the questions to be deleted.
4. Delete the questions selected.
6. Use case ends.
Alternative Step 1. If Chair head doesn’t have an account, then the
course of login will fail.
action Step 3.If the question that is being searched is not available
the system displays error message.
Post The evaluation criteria successfully deleted
condition
Manage account
Use case Manage account
name
21
Identifier UC 009
Actors Administrator
Description The administrator manages the account of the other actors.
Like Chair head, students and instructors.
Precondition Administrator must have an administrator account.
Basic course 1. Login by using own account.
of action 2. Searches manageable account.
3. Deletes account.
5. Use case ends.
Alternative Step 1. If all users don’t have an account, then the login will
course of fail.
action Step 3. If the account that is being searched is not available
the system displays no account with this user name message.
2.6 Sequence diagram

A Sequence diagram is a graphical representation of sequences of communications between objects i.e.
sequence of method invocation of objects which results in accomplishing some tasks. The emphasis in a
sequence diagram is on the sequence of messages. A Sequence diagram is a structured representation of
behavior as a series of sequential steps over time. It is used to depict work flow, message passing and how
elements in general cooperate over time to achieve a result. The sequence diagram for this system is
shown in the next section.
22
sd Class Mo...
Actor Menu<<UI>> evaluateInstructor FormControler evaluationform<<UI>> DB
Click
fill evaluation form
link()
BasicCourseOfaction
Click()
initiate()
Create()
DisplayForm()
Fill
Form()
Invalid()
please select the value ()
Valid()
Evaluate()
Succesfully
evaluated()
Actor:
customer
X X X X
X
X
Figure 2 Sequence diagram for create actor’s account
23
sd Use Case Mo...
Actor ApplicationForm LoginControler Login<<UI>> UserAccount

Login
Basic Course of action
click()
Initiate()
<<create>>()
enter username and password()
UserName()
Password()
Validate(Username,Password)
Invalid()
Invalid username or password Reenter again()
valid()
Succesfully Loged in()
acces required page()
X X X X X
Figure 3 Sequence diagram for login
2.7 Activity diagram

Activity diagrams graphically represent the performance of actions or sub-activities and the transactions
that are triggered by the completion of the actions or sub-actions. It is a means of describing the workflow
of activities. The purpose of an activity diagram is to provide a view of flows and what is going on inside
a Use Case. The activity diagram for this system is shown in the next section.
2.8 Class diagram

2.8.1 Class implementation
In this project we have 11 classes each has its own activities.
Dashboard: It displays the overall activities that the admin is done in number.
24
Subject: It is the class of added subjects in the system that the instructor thought the students.
Class: This allows adding the batch, the type of degree, and the section of the student.
Academic year: This allows to add the academic year and the semester of the calendar. After we added
the year, we should do the system default “YES” and the evaluation status “STARTED” to ready the
academic year for evaluation.
Evaluation criteria: To add the criteria of evaluation in to the system by admin.
Questionnaires: The system allowed the administrator continuously adds specific evaluation criteria
which are called questionnaires based on the correct input given. It shows “Academic Year”, “Semester”,
“Questions”, “Answers”, and “ACTION”.
First click on Action, then manage. Now we have two options or tasks that should be done.
Question form: We added specific evaluation criteria to the system.
Evaluation restriction or assigning of instructors for evaluation: This allowed us to add the instructors to
be evaluated.
Instructors: This class allowed the admin to add the instructions of the university to the system by their
assigned subjects with the university.
Students: This allowed to add the students into the system.
Evaluate: This allowed to evaluate the instructors.
Evaluation reports: This showed the reports of the evaluation in different information and we can save or
print the evaluation.
Administrators: This class allowed us to update the administrators account.
25
CHAPTER THREE: DESIGN
3.1 Purpose and goals of design
The main aim of the design is to show the different type of class type architecture such as user interface,
process/control, business/domain, persistence and system layers and also different types of system
modeling techniques that are used for the implementation of the system such as class, component, and
deployment modeling. Also some system design techniques such as user interface, training and
maintenance designs are also to be covered in this design chapter. The design goals are derived from non-
functional requirements that means non-functional requirement is the description of the feature
characteristics and attribute of the system as well as any constraints that may limit the boundary of the
proposed solution.
Design goals describe the qualities of the system that the developers should consider.
Reliability: It is very reliable.
Security: IES should be secured, i.e., not allow other users or unauthorized users to access data that has
no the right to access it
Fault Tolerance: IES should be fault tolerant to loss of connectivity with the service
Modifiability: IES system should be modifiable for further modification and enhancement of the
application
Performance: The system should respond fast with high throughput, i.e. it should Perform evaluation and
report generation in a time less than 2 minutes.
Cost: The system should be developed with minimum cost possible. In reality there is always trade-offs or
disadvantages and therefore, from its previous experience the university prefers to invest more in
development cost than maintenance cost to minimize bugs which may appear the later stage.
End User Criteria: - The system should have simple and understandable graphical user
Interface such as forms and buttons which have descriptive names. It should give reliable response
for each user request at least before the session expires. All the interfaces, forms and buttons are
written or designed in a simple language or common language so that the user can access it without any
difficult.
26
Response time: As we mentioned the performance characteristics in the non-functional requirement of the
requirement analysis document the system should respond the user requests within a specified period of
time and up to the standard response time after the request has been issued.
3.3 Current software architecture

Currently the System Architecture is a manual based, that’s why we are intended to develop computerized
system to solve the problem of this paper based instructors evaluation system for the university. The
instructor’s evaluation system uses manual based architecture to calculate and process instructor’s
evaluation. Thus we can say the instructors evaluation have no specified architecture at the moment. We
are unable to document the current software architecture. Although we have not observed any architecture
it is common that web based application best fit with client/server architecture.
3.4 Proposed software architecture

3.4.1 Subsystem decomposition
Record management: This sub system Record information like school information, instructor’s
information, students information
View management: The user module includes the functionalities; View instructors result.
Database: This component of the IES application comprise relational database store information in
various tables regarding student list, faculty list, evaluation, questionnaires, criteria, and other service
detail.
Account Management: It includes; but not limited to:
Add user account
Delete user account
Maintain the system
Manage User Authentication and access control
3.4.2 Component diagram

The component diagram's main purpose is to show the structural relationships between the components of
a system, management of the system, database and operations performed on databases.
3.4.3 Deployment diagram

The IES will have three main components: the client, the web server, and the database server. The web
server of the IES will run at HTML & PHP and will contain all subsystems. The database server will use
XAMP SERVER database and will handle all persistent data storage. Again, the client will access the IES
website through their internet browser (i.e. Mozilla Firefox, Google Chrome, Internet Explorer…).The
web server and the database server will be hosted on the same physical machine. However it is possible to
place on separate machines is desired.
27
deployment Deployment M o...
depl oym ent of SOC IES
«devi ce» System application

client machine
SOC IES
Internet
brow ser(mozila,
crome,safari)
<<HT T P>>
serv er
w eb
serv er(appache)
<<i nstal l >>
database
serv er(mysql)
Figure 4 Deployment diagram
3.4.4 Persistence modeling for OODB

The IES used the XAMP SERVER database engine for storing data. This allowed the database to be
easily integrated with and accessed by the rest of the system. The database retained user information and
calculated the input given before. Each of the items was a separate table. We describe data object for each
table below.
Table object Type Length Default value Null

Id Int 30 - X
Year varchar 8 - X
Semester varchar 30 - X
Status Varchar 8 - X
Table 1 data object for academic_list

Id Int 30 - X
Curriculum Varchar 10 - X
Level varchar 10 - X
Section varchar 10 - X
Table 2 data object for class_list
28
Id int 30 - X
Criteria varchar 50 - X
Order_by int 30 - X
Table 3 data object for criteria_list

Evaluation_id varchar 30 - X
Question_id varchar 30 - X
Rate varchar 20 - X
Table 4 data object for evaluation_answers

Evaluation_id Int 30 - X
Academic_id Int 30 - X
Class_id Int 30 - X
Student_id varchar 30 - X
Subject_id varchar 30 - X
Faculty_id Int 30 - X
Restriction_id Int 30 - X
Table 5 data object for evaluation_list

Id Int 30 - X
School_id Varchar 100 - X
First name Varchar 200 - X
Last name Varchar 200 - X
Email Varchar 200 - X
Password Varchar 20 - X
Table 6 data object for faculty or instructor_list
29
Id Int 30 - X
Question Varchar 100 - X
Order_by Int 30 - X
Criteria_id int 30 - X
Table 7 data object for question_list

Id Int 30 - X
Faculty_id Int 30 - X
Class_id Int 30 - X
Subject_id int 30 - X
Table 8 data object for restriction_list

Id Varchar 30 - X
School_id Varchar 100 - X
Password Varchar 20 - X
Class_id Varchar 30 - X
Table 9 data object for student_list

Subject Varchar 30 - X
Code Varchar 30 - X
Description Varchar 200 - X
Id varchar 20 - X
Table 10 data object for subject_list
30
Id Int 30 - X
Name Varchar 20 - X
Contact Varchar 20 - X
Address Varchar 30 - X
Cover_img varchar 30 - X
Table 11 data object for system_settings

ID Int 30 - X
Password varchar 20 - X
Table 11 data object for user
3.4.5 Access control and security

System access control and security is the main issue of the project. Therefore system identify someone
who is, what he/she wants to access, check whether the somebody is authorized or not and granting
permission or deny. Thus the system provides protection over system from unauthorized users and allows
those who have an authority to access the system and even an authorized body forgot either of his/her
user name or password the system prompts to correct again. We are concerned with information security
and application controls. The information security of the IES aims to preserve:
Confidentiality: The only people to see the data those authorized to see it. Private data is kept private
personal privacy is respected.
Integrity: It can integrate with any Admas University websites.
Availability: The registered instructors or user data is available at all times to authorized users
Accountability: It is possible to discover that after the event who has modified what data in the IES.
C=create R= read U=update D=delete
IES Student Instructor Admin

C R U D C R U D C R U D
Student information x √ x x x x x x √ √ √ √
Instructor information x √ x x √ √ √ √
School information x x x x x x x x √ √ √ √
31
Account x x x x x x x x √ √ √ √
Result x x x x x √ x x x √ x x
School information x x x x x x x x √ √ √ √
Evaluation Questionnaires x x x x x x x x √ √ √ √
Evaluation criteria x x x x x x x x √ √ √ √
Table 1 Access control
3.4.6 Boundary conditions and exception handling
3.4.6.1 Boundary Conditions

Startup and Shutdown: The IES does not have any startup or shutdown procedures. Since it is a website,
startup and shutdown are controlled by the web server and host, both of which are outside of IES’s scope.
The website is designed to be online 24 hours a day; 7 days a week; 365 days a year except during system
maintenance. If the web server and host are running, then IES is operational
Initialization: The IES does not require any initialization upon system startup. When creating the website
for the first time some interesting persistent data needed to be added to the database. However these
operations can be performed at any time. If the web server is rebooted for example, it is not necessary to
re-add the previously performed operations, since this information already exists inside the database
3.4.6.2 Exception Handling

The Exception handling subsystem manages the following exceptions.
Database Exception – Occurs when there is an error accessing the database. Recovery from this error is
achieved by displaying an error message stating that the database is temporarily unavailable.
Access Control Exception – Occurs when a user is trying to access a function that they do not have
permission to access. Recovery from this error is achieved by preventing the user for executing this
function
Data Validation Exception – Occurs when a user tries to add HTML, a DATA BASE query, or any other
unauthorized text into a string. Recovery from this error is achieved by removing the unauthorized text
32
cmp Class Mo...
VIEW MANAGEMENT
EVALUATION MANAGEMENT
DATABASE
RESULT MAAGEMENT ACCOUNT MANAGEMENT
Figure 5 Subsystem architecture
3.5 User interface design

This page is available for students, instructors, and administrator to login and do different tasks.
33
Figure 6 Log in form
Figure 10 after log in as an admin
34
Figure 10: Evaluation form as an admin
35
CHAPTER FOUR: SYSTEM IMPLIMENTATION AND TESTING
4.1 Implementation
4.1.1 Introduction
The implementation document enables the user (society) as well as the administrator to work with the
system and to use the application efficiently and effectively. It helps users not to be confused with the
system. It includes sample snapshot. It gives the users a brief over view of the system
4.1.2 Coding standards

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 in this we tested all the
functionalities in the System. All errors in the forms, functions have been tested.
4.1.3 Implementation strategy

Final phase of implementation is testing. Testing is a process to show the correctness of the program.
Testing is checking of System Implementation is the phase where objectives of physical operations of the
system turned into reality i.e. real working model. The crucial phase in the system development life cycle
is the successful implementation of the new system design. The process of converting as new system into
an operational one is known as system implementation. This includes all those activities that take place to
convert from an old system to a new system.
4.2 Testing
4.2.1 Test type
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.
Acceptance Testing: Acceptance testing is the process of testing system (e.g. software, lots of
manufactured mechanical parts, or batches of chemical products) prior to its delivery. A system is mainly
developed for an end user normally a customer of the school. A system is said to be accepted if and only
36
if the user of the system is satisfied. In this perspective acceptance testing is widely used to prove that
system performs as per the requirements. In acceptance testing the user provides the input data to validate
the system operation. It is also known as functional testing, black-box testing, release acceptance, QA
testing, application testing, confidence testing, final testing, validation testing, or factory acceptance
testing.
System Testing: It is the final step of testing. In this the team members tests the entire system as a whole
with all forms, code. This form of testing is popularly known as Black Box testing or System tests. In this
the team members tests all the functionalities in the System. All errors in the forms, functions are tested
Integration testing: When individual units are combined and tested as a group then it is called integration
testing. In this test we can find fault of the combination and interaction between those integrated units or
components.
We have successfully tested all the parts of the codes.
4.2.2 Overview of manual testing and automated testing tools

a) Manual testing is any type of testing where someone physically clicks through the user-path being
tested — either by following written instructions to test a specific feature or by clicking around in an
unscripted way. We checked the following manually.
- Usability testing: Testing performed to ensure the end user will be able to use the application with
ease
- Ad-hoc testing: Informal testing without any documentation often used to test a feature when there
isn’t enough time to run a complete suite of formal tests.
- Exploratory testing: Unscripted testing performed to catch bugs not found by traditional testing.
b) Automated testing uses software tools or coding frameworks to automatically run tests that validate
user paths, UI workflows, input fields, and more by using the testing tools Katalon studio, Perfecto, and
Selenium.
4.2.3 Test plan

We had planned on the following table for test plan.
No Activities to be tested Months of the year

February March April May
1 Add or delete subject
2 Add or delete class
3 Add or delete students
4 Add or delete criteria
5 Generate instructors reports
6 System test
7 Integration test
4.2.4 Defects classification management
This sub system manages the components defect of the IES as follows.
37
Improper calling function defects: These problems easily manageable by using the comments of the
output. Then based on the comment we solved the problems by automated and manual testing.
DB connection defect: The system faced unable to store and keep the input evaluation report in the
system. This defect took several hours to fix the problem.
Unexpected output: This was happed a month ago. We need the evaluation report based on the students
that filled the space provided. But the system showed the same result for all evaluations as 100%.
Log in interface defects: We managed this problem by assigning different account types as admin,
instructor, and students.
4.2.5 Test report

We faced different problems when we checked the system out. The following are the main test reports.
Unit test
Test Case 1:
Test Case ID = Administrator – TestCase01
Unit to Test = create account
Assumptions = successfully created!
Test Data = Username (invalid, Valid, empty)
Password(invalid, valid, empty)
User type(Selected, empty)
Password (invalid, valid, empty)
conform password (not match, matched, empty)
Steps to be Executed Data Expected Results
Empty username and all others Any valid data for the other
“username must Required”
filled and Click Add button fields
Empty password and Click Any valid data for the other
“password must Required”
Add button fields and last name empty
Not select user type and Click “select user type you want
Not select user type
add button to be!”
Password not Match Type unmatched password "Password do not match!"
Test Case 2:
38
Test Case ID = Admin – TestCase02
Unit to Test = add student
Assumptions = successfully registered!
Test Data = first Name (invalid, Valid, empty)
Last name(invalid, valid, empty)
Id(valid, empty)
year(valid, empty)
section(invalid, valid, empty)
Steps to be Executed Data Expected Results
Empty first Name and all

Any valid data for the other “First name must have
others filled and Click Add
fields alphabet characters only”
button
empty last name and Click Any valid data for the other “Last name must have
Add button fields and last name empty alphabet characters only”
CHAPTER FIVE: CONCLUSION AND RECOMMENDATION

5.1 Conclusion
Automated Online Teachers Evaluation System is a web application. The main concept of this system is
to reduce the amount of paper and convert all documentation into digital. And also maintain the accuracy
of the system. We tried to give our best to build this system. But still we need some improvements in
future.
5.2 Recommendation
After building the system we have gathered and found that our system might need some more
modification. These features might be developed in future.
Authority Login System: Authority can view result to develop quality of education.
Others survey system. If authority wants to operate any other survey, then it can be develop.
e-application system: Integrating this system with the student e-application registrar system.
Glossary
Main terms
39
Use case: A use case expresses a contract between the stakeholders of a system about its behavior. It
describes the system’s behavior and interactions under various conditions as it responds to a request on
behalf of the stakeholders, the primary actor, showing how the primary Actor’s goal gets delivered or
fails. The use case collects together the scenarios related to the primary actor’s goal.
Scenario: A scenario is a sequence of action and interactions that occurs under certain conditions,
expressed without branching.
Actor: Something with behavior. It might be a mechanical system, computer system, a person, an
organization or some combination.
Use case diagram: In UML, the diagram showing the external actors, the system boundary, the use cases
as ellipses, and arrows connecting actors to ellipses or ellipses to ellipses. Primarily useful as a context
diagram and table of contents
Sequence diagram: In UML, the diagram showing actors across the top, owning columns of space, and
interactions as arrows between columns, with time flowing down the page. Useful for showing one
scenario graphically.
Class diagram: Class diagrams show the classes of a system and their interrelationship’s. Class diagrams
are often mistakenly referred to as object models.
IES: Instructor evaluation system.
PHP: - PHP Hypertext Preprocessor used for back end.
HTML: - Hyper Text Markup Language used for front end.
SQL: - Structural Query Language.
CSS: - Cascading Style Sheet used to style the interface of web.
UML: - Unified Modeling Language.
RAD: Requirement analysis document
LAN: local area network
OOD: object oriented design used to design the project by representing real world things.
SDD: system design document
DB: Database
OODB: Object oriented database
References
[1] Walter Savitch: “Problem solving with C++ – The Object of Programming”, Menlo Park:
Addison-Wesley, 1996.
40
[2] Deitel P.J., Deitel H.M. - Java How to Program 9th Edition-Copy
[3] R. Elmasri and S. B. Navathe: “Fundamentals of Database Systems”, 4th edition, Addison-
Wesley.
[4] A. Silberschatz, H. F. Korth, and S. Sudarshan: “Database System Concepts”, McGraw Hill,
5th edition, 2005.
[5] Object Oriented Software Engineering: A Use Case Driven Approach by Ivar Jacobson,
Patrik Jonsson, ACM Press Staff, Magnus Christerson, Gunnar Overgaard
[6] ObjectOrientedSof twareEngineeringU singUMLP atternsandJ ava (2)-Copy
[7] Bernd Bruegge and Allen H. Dutoit:“Object-Oriented Software Engineering Conquering
Complexity and Changing Systems”, Prentice Hall, 2000
[8] A. S. Tanenbaum: “Modern Operating Systems”, 2nd edition, Prentice Hall, 2001.
[9] Alfred Aho, Ravi Sethi, V.Jeffery Ullman D. “COMPILERS PRINCIPLES,
TECHINQUES AND TOOLS “, Addison- Wesley, 1988.
[10] Steven Holzner: “Visual Basic .Net Programming Black Book”, Dream Tech Press.
[11] Olson, David L.: “Introduction to Information Management Systems”, 2001.
[12] N. Whitten: “Managing Software Development Projects: Formula for Success”, 2nd edition,
Wiley, 1995.
[13] Prof Janet Clinton (January 19, 2017) Teacher Effectiveness Systems, Frameworks, and
Measures Retrieved from https://docs.education.gov.au/system /files/doc/other/teacher
effectrpt2017.pdf
[14] Cara Jackson, Ph.D. and Kirsten Mackler (April 2016) Assessing Effectiveness Retrieved
from
https://static1.squarespace.com/static/54dc2642e4b0469314195dca/t/571fa9501dbaec3234c9dc3/1461692771724/
UrbanTeachersEvaluationModelApril2016.pdf
[15] Doug McKee Oct 6th, 2014 Student Evaluations as Measures of Teaching Quality Retrieved
from http://teachbetter.co/blog/2014/10/06/student-evals-as-measuresof-teaching-quality/
[16] Handbook GRCC March 13, 2013, Grand Rapids Community College Faculty Evaluation
41
System Retrieved from https://www.grcc.edu/sites/default/files/attach
ments/Faculty%20Evaluation%20System.pdf
[17] Sylvia A. White August 2013 A Comparison of Teacher Evaluation, Student Surveys and
Growth Scores to Identify Effective Teaching Traits Retrieve from

https://search.proquest.com/openview/fd96c4eb25f7048d6d4771868b2dcfba/1?
pqorigsite=gscholar&cbl=18750&diss=y
[18] Radhika Nayani Published 2010 Web-based Student Evaluation Of instruction Retrieve
from https://books.google.com.ph/books?id=qoyRnQAACAAJ
[19] Goe, L., Bell, C., & Little, O. 2008, June Approaches to Evaluating Teacher Effectiveness
Retrieve from http://growththroughlearningillinois.org/Portals/0
/Documents/ApproachesToEvaluatingTeacherEffectiveness-1.pdf
[20] Emily Donnelli, Amber Dailey and Marthann 2005, Schulte, Faculty Evaluation Model for
Online Instructors: Mentoring and Evaluation in the Online Classroom
[21] Cecilia Isidro ANIDO 2009, Online Teaching Performance Evaluation System: A Tool for
Quality Education
[22] Leah T. Salas 2015, A Web and Mobile-Based Performance Evaluation System
[23] Imelda M. Taguiam 2016, Web-Based Faculty Evaluation System of Apayao State College,
Philippines
[24] Alok Kumara and Renu Jain 2017, Faculty Evaluation System 6th International Conference
on Smart Computing and Communications, ICSCC
[25] Salah Alkhafaji and Sriram B. 2013, Instructor’s Performance: A Proposed Model for
Online Evaluation International Journal of Information Engineering and Electronic
Business.
[26] https://admasuniversity.edu.et/?pageid=79
[27] Instructor Evaluation System for School of Computing; A FINAL PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF
BSc. In Computer Science, 2015/16 Mekele university, Ethiopia
[28] https://www.sitepoint.com
42
Annex 1: Sample coding for HTML (index)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">

<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="viewport" content="initial-scale=1, maximum-scale=1">

<title>Instructor Evaluation System</title>
<meta name="keywords" content="">
<meta name="description" content="">
<meta name="author" content="">

<link rel="stylesheet" type="text/css"
href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.0.0-beta.2.4/assets/
owl.carousel.min.css" />

<link rel="stylesheet" type="text/css" href="css/bootstrap.min.css">

<link rel="stylesheet" type="text/css" href="css/style.css">

<link rel="stylesheet" href="css/responsive.css">

<link rel="icon" href="images/fevicon.png" type="image/gif" />

<link rel="stylesheet" href="css/jquery.mCustomScrollbar.min.css">

<link rel="stylesheet" href="https://netdna.bootstrapcdn.com/font-
awesome/4.0.3/css/font-awesome.css">

<link href="https://fonts.googleapis.com/css?family=Open+Sans:400,700|
Poppins:400,700&display=swap" rel="stylesheet">

<link rel="stylesheet" href="css/owl.carousel.min.css">
<link rel="stylesheet" href="css/owl.theme.default.min.css">
<link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/fancybox/2.1.5/jquery.fancybox.min.c
ss" media="screen">
<style>
43
body:before {
content: '';
position: absolute;
top: 0;
left: 50%;
width: 15%;
height: 100%;
background: #980000;
z-index: -1;
transform: skew(-30deg)
}
body:after {
content: '';
position: absolute;
top: 0;
right: 50%;
width: 15%;
height: 100%;
background: #d40000;
z-index: -1;
transform: skew(-30deg);
box-shadow: 00px 10px 10px black
}
.head {
font-size: 2em!important;
font-weight: 500;
text-shadow: 1px 1px 1px white
}
.count {
font-size: 30em!important;
text-shadow: 1px 1px 10px black
}
.counter {
font-size:xx-large;
min-width: 300px;
background: #111;
height: 300px;
display: flex;
align-items: center;
justify-content: center;
flex-direction: column;
44
color: white;
padding: 10px;
box-shadow: 5px 5px 50px black
}
</style>
</head>
<body>


<div class="header_section">
<div class="header_bg">
<div class="container">
<nav class="navbar navbar-expand-lg navbar-light bg-light">
<a class="logo" href="index.html"><h2>Admas IES</h2></a>
<button class="navbar-toggler" type="button" data-
toggle="collapse" data-target="#navbarSupportedContent" aria-
controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle
navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse"
id="navbarSupportedContent">
<ul class="navbar-nav mr-auto">
<li class="nav-item active">
<a class="nav-link" href="index.html">Home</a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html">About</a>
</li>
<a class="nav-link" href="services.html">Bid</a>
</li>
<a class="nav-link" href="vacancy.html">Vacancy</a>
</li>
<a class="nav-link" href="contact.html">Contact
Us</a>
</li>
<a class="nav-link"
href="dashboard/index.php">Login</a>
</li>
</ul>
<div class="call_section">
45

</div>
</div>
</nav>
</div>
</div>

<div class="banner_section layout_padding">
<div id="my_slider" class="carousel slide" data-ride="carousel">
<div class="carousel-inner">
<div class="carousel-item active">
<div class="banner_taital_main">
<div class="row">
<div class="col-md-6">
<h1 class="banner_taital">Admas University</h1>
<p class="banner_text">Instructor Evaluation
System</p>
<div class="btn_main">


</div>
</div>
<div class="image_1"><img
src="images/ethiopianStudents.jpg"></div>
</div>
</div>
</div>
</div>
</div>
46
<div class="carousel-item">
<div class="banner_taital_main">
<div class="row">
<h1 class="banner_taital">Evaluate Your
Instructors</h1>
<p class="banner_text">Help your Teacher to
Improve </p>

</div>
<div class="image_1"><img
src="images/ethiopianStudents.jpg"></div>
</div>
</div>
</div>
</div>
</div>
</div>
<a class="carousel-control-prev" href="#my_slider" role="button"
data-slide="prev">
<i class="fa fa-arrow-left" style="font-size:24px"></i>
</a>
<a class="carousel-control-next" href="#my_slider" role="button"
data-slide="next">
<i class="fa fa-arrow-right" style="font-size:24px"></i>
</a>
</div>
</div>

</div>


<div class="services_section layout_padding">
<h1 class="services_taital"><span style="color: #fcce2d">Our</span>
Departments</h1>
<div class="services_section_2">
47
<div class="row">
<div class="image_main">
<img src="images/Admas-University.jpg" class="image_8"
style="width:100%">
<div class="text_main">
<div class="seemore_text">Social Department</div>
</div>
</div>
</div>
<img src="images/images.jpg" class="image_8"
style="width:100%">
<div class="seemore_text">Science Department</div>
</div>
</div>
</div>
</div>
<div class="row">
<img src="images/images (1).jpg" class="image_8"
style="width:100%">
<div class="seemore_text">Business Department</div>
</div>
</div>
</div>
<img src="images/admas-sttu.jpg" class="image_8"
style="width:100%">
<div class="seemore_text">Art School </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>


48
<div class="news_section layout_padding">
<h1 class="news_taital">Our About</h1>
<p class="news_text">Admas University online istructor evaluation
System.The system is design and developed by Asrat and his team mates.</p>
<div class="news_section_2">
<div class="row">
<div class="news_taital_box">
<p class="date_text">01 Jan 2023</p>
<h4 class="make_text">Make it Simple</h4>
<p class="lorem_text"> The system will allow Admas
University student, instructor and Head of the department will evaluate in one
System.the user must have an account to evaluate.</p>
<p class="post_text">Post By : Asrat</p>
</div>
</div>
<img src="images/Evaluating_Online_Teaching.jpg"
class="image_6" style="width:90%">
<h6 class="plus_text">+</h6>
</div>
</div>
</div>
</div>
</div>


<div class="blog_section layout_padding">
<h1 class="news_taital">Our Bolg</h1>
<p class="news_text">In this Blog the stuff will share ideas</p>
<div class="blog_section_2">
<div class="row">
<img src="images/img-7.png" class="image_7"
style="width:100%">
</div>
<h4 class="classes_text">Best Classes and study</h4>
<p class="ipsum_text"> To discuss in order to exchange
information or ideas. communicate. brainstorm. intercommunicate. put heads
together.</p>
</div>
</div>
49
</div>
<div class="read_bt"><a href="#">Read More</a></div>
</div>
</div>


<div class="client_section layout_padding">
<div id="main_slider" class="carousel slide" data-ride="carousel">
<div class="carousel-inner">
<div class="carousel-item active">
<h1 class="client_taital">Best Instructor of the Month</h1>
<div class="client_section_2">
<div class="client_left">
<div><img src="images/client-img.png"
class="client_img"></div>
</div>
<div class="client_right">
<h3 class="client_name">Abebe Ayele</h3>
<p class="client_text">Abebe Ayele is Social Studies
instructor of Admas University Bole Campus. </p>
</div>
</div>
</div>
</div>
<h1 class="client_taital">Best Student of the Month</h1>
</div>
<h3 class="client_name">Ayele Abebe</h3>
<p class="client_text">Ayele Abebe is Social Studies
student of Admas University Bole Campus </p>
</div>
</div>
</div>
</div>
<h1 class="client_taital">Best Campus</h1>
50
</div>
<h3 class="client_name">Bole Campus</h3>
<p class="client_text">Bole Campus is best for cleans
</p>
</div>
</div>
</div>
</div>
</div>
<a class="carousel-control-prev" href="#main_slider" role="button"
data-slide="prev">
<i class="fa fa-angle-left"></i>
</a>
<a class="carousel-control-next" href="#main_slider" role="button"
data-slide="next">
<i class="fa fa-angle-right" style="font-size:24px"></i>
</a>
</div>
</div>


<div class="newsletter_section layout_padding">
<div class="counter">
<div class="head">Total Website Visit</div>

<div id="counter">00</div>
</div>
</div>


<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
51
</div>


<div class="contact_section layout_padding">
<div class="container-fluid">
<div class="row">
<div class="col-md-6 padding_left0">
<div class="mail_section">
<div class="contact_img">
<h1 class="contact_taital">Why This System?</h1>
</div>
</div>
</div>
<h1 >Admas IES</h1>
<p>This system is developed for admas University.The
system is mainly for Head of the department to asses the instructor level of
education and interaction with the students. </p>
<h1> current Date and Time</h1>
<h2 id="displayDateTime"></h2>
<div class="map_main"></div>
</div>
</div>
</div>
</div>


<div class="footer_section layout_padding">

<div class="footer_section_2">
<div class="row">
<div class="col-lg-3 margin_top">
<div class="call_text"><a href="#"><img src="images/call-
icon1.png"><span class="padding_left_15">Call Now +251 921279545
</span></a></div>
<div class="call_text"><a href="#"><img src="images/mail-
icon1.png"><span class="padding_left_15">info@admas.com</span></a></div>
</div>
<div class="col-lg-3">
<div class="information_main">
<h4 class="information_text">About</h4>
52
<p class="many_text">Admas University online istructor
evaluation System.The system is design and developed by Asrat and his team
mates.</p>
</div>
</div>
<div class="col-lg-3 col-md-6">
<h4 class="information_text">Helpful Links</h4>
<div class="footer_menu">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="about.html">About</a></li>
<li><a href="services.html">Bid</a></li>
</ul>
</div>
</div>
</div>
<div class="footer_logo"><a href="index.html"><img
src="images/download.jpg"></a></div>
</div>
</div>
</div>
</div>
</div>
</div>


<div class="copyright_section">
<p class="copyright_text">© 2023 All Rights Reserved. <a
href="https://html.design">Admas University</a></p>
</div>
</div>


<script>
// Get the counter element
const counterEl = document.getElementById("counter");
// Get the current count from local storage or start at 0
53
let count = localStorage.getItem("count") || 0;
// Increment the count and update the counter element

count++;
counterEl.innerHTML = count;
// Store the new count in local storage

localStorage.setItem("count", count);
</script>
<script src="js/jquery.min.js"></script>
<script src="js/popper.min.js"></script>
<script src="js/bootstrap.bundle.min.js"></script>
<script src="js/jquery-3.0.0.min.js"></script>
<script src="js/plugin.js"></script>

<script src="js/jquery.mCustomScrollbar.concat.min.js"></script>
<script src="js/custom.js"></script>

<script src="js/owl.carousel.js"></script>
<script
src="https:cdnjs.cloudflare.com/ajax/libs/fancybox/2.1.5/jquery.fancybox.min.js">
</script>
<script
src="https://cdn.jsdelivr.net/jquery.counterup/1.0/jquery.counterup.min.js"></
script>
<script
src="https://cdnjs.cloudflare.com/ajax/libs/waypoints/2.0.3/waypoints.min.js"></
script>
<script>
function updateCounter() {
fetch('https://api.countapi.xyz/update/eval.tokewholetrade.comeval/
eval.tokewholetrade.comeval/?amount=1')
.then(res => res.json())
.then(data => counterElement.innerHTML = data.value)
}
updateCounter()
counterElement = document.getElementsByClassName('count')[0];
</script>
54
<script type="text/javascript">
var today = new Date();
var day = today.getDay();
var daylist = ["Sunday","Monday","Tuesday","Wednesday
","Thursday","Friday","Saturday"];
var date = today.getFullYear()+'-'+(today.getMonth()
+1)+'-'+today.getDate();
var time = today.getHours() + ":" + today.getMinutes() + ":" +
today.getSeconds();
var dateTime = date+' '+time;
document.getElementById("displayDateTime").innerHTML = dateTime + '

<br> Day :- ' + daylist[day];
</script>
</body>
</html>
Annex 2: Sample coding for DB (To student)

<?php include('db_connect.php');
function ordinal_suffix1($num){
$num = $num % 100; // protect against large numbers
if($num < 11 || $num > 13){
switch($num % 10){
case 1: return $num.'st';
case 2: return $num.'nd';
case 3: return $num.'rd';
}
}
return $num.'th';
}
$astat = array("Not Yet Started","Started","Closed");
?>
<div class="col-12">
<div class="card">
<div class="card-body">
Welcome <?php echo $_SESSION['login_name'] ?>!
<br>
<div class="col-md-5 mt-3">
<div class="callout callout-info">
<h5><b>Academic Year: <?php echo $_SESSION['academic']['year'].' '.
(ordinal_suffix1($_SESSION['academic']['semester'])) ?> Semester</b></h5>
55
<h6><b>Evaluation Status: <?php echo $astat[$_SESSION['academic']
['status']] ?></b></h6>
</div>
</div>
</div>
</div>
</div>
Annex 3: Sample coding for result report

<?php $faculty_id = isset($_GET['fid']) ? $_GET['fid'] : ''; ?>
<p>
Translate language:
</p>
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({
pageLanguage: 'en'
},
'google_translate_element'
);
var $googleDiv = $("#google_translate_element .skiptranslate");
var $googleDivChild = $("#google_translate_element .skiptranslate div");
$googleDivChild.next().remove();
$googleDiv.contents().filter(function () {
return this.nodeType === 3 && $.trim(this.nodeValue) !== '';
}).remove();
}
</script>
<script type="text/javascript"
src="https://translate.google.com/translate_a/element.js?
cb=googleTranslateElementInit">
</script>
<?php
function ordinal_suffix($num)
{
$num = $num % 100; // protect against large numbers
if ($num < 11 || $num > 13) {
switch ($num % 10) {
56
case 1:
return $num . 'st';
case 2:
return $num . 'nd';
case 3:
return $num . 'rd';
}
}
return $num . 'th';
}
?>
<div class="d-flex w-100 justify-content-center align-items-center">
<label for="faculty">Select Instructor</label>
<div class=" mx-2 col-md-4">
<select name="" id="faculty_id"
onchange="displayOverallResult()"
class="form-control form-control-sm select2">
<option value=""></option>
<?php
$faculty = $conn->query("SELECT *,concat(firstname,'
',lastname) as name FROM faculty_list order by concat(firstname,' ',lastname)
asc");
$f_arr = array();
$fname = array();
while ($row = $faculty->fetch_assoc()):
$f_arr[$row['id']] = $row;
$fname[$row['id']] = ucwords($row['name']);
?>
<option value="<?php echo $row['id'] ?>" <?php echo
isset($faculty_id) && $faculty_id == $row['id'] ? "selected" : "" ?>><?php echo
ucwords($row['name']) ?></option>
<?php endwhile; ?>
</select>
</div>
</div>
</div>
<div class="row">
<div class="col-md-12 mb-1">
<div class="d-flex justify-content-end w-100">
<button class="btn btn-sm btn-success bg-gradient-success"
style="display:none" id="print-btn"><i
class="fa fa-print"></i> Print</button>
57
</div>
</div>
</div>
<div class="row">
<div class="list-group" id="class-list">
</div>
</div>
</div>
<div class="callout callout-info" id="printable">
<div style="margin-bottom: 10px;">
<h3 class="text-center">Overall Evaluation Report</h3>
<hr>
<table width="100%">
<tr>
<td width="50%">
<p><b>Instructor: <span
id="fname"></span></b></p>
</td>
<td width="50%">
<p><b>Academic Year: <span id="ay">
<?php echo $_SESSION['academic']
['year'] . ' ' . (ordinal_suffix($_SESSION['academic']['semester'])) ?>
Semester
</span></b></p>
</td>
</tr>
<tr>
<td width="50%">
<p><b>Class: <span
id="classField"></span></b></p>
</td>
<td width="50%">
<p><b>Subject: <span
id="subjectField"></span></b></p>
</td>
</tr>
</table>
58
<p class=""><b>Total People Evaluated: <span
id="tse"></span></b></p>

</div>

<div class="col-md-6" style="float: center;">

<div class="list-group">
<p style="width: 330px;padding: 20px;background:
Brown; color: #fff; font-size:20px; font-weight: bold;"
id="displayArea"></p>
</div>
</div>
</div>



</div>
</div>
</div>
<style>
59
.list-group-item:hover {
color: black !important;
font-weight: 700 !important;
}
</style>
<noscript>
<style>
table {
width: 100%;
border-collapse: collapse;
}
table.wborder tr,
table.wborder td,
table.wborder th {
border: 1px solid gray;
padding: 3px
}
table.wborder thead tr {
background: #6c757d linear-gradient(180deg, #828a91, #6c757d)
repeat-x !important;
color: #fff;
}
.text-center {
text-align: center;
}
.text-right {
text-align: right;
}
.text-left {
text-align: left;
}
</style>
</noscript>
<script>
$(document).ready(function () {
$('#faculty_id').change(function () {
if ($(this).val() > 0)
window.history.pushState({}, null, './index.php?
page=report&fid=' + $(this).val());
load_class()
60
})
if ($('#faculty_id').val() > 0)
Annex 4: Sample coding for login

<!DOCTYPE html>
<html lang="en">
<?php
session_start();
include('./db_connect.php');
ob_start();
// if(!isset($_SESSION['system'])){
$system = $conn->query("SELECT * FROM system_settings")->fetch_array();

foreach($system as $k => $v){
$_SESSION['system'][$k] = $v;
}
// }
ob_end_flush();
?>
<?php
if(isset($_SESSION['login_id']))
header("location:index.php?page=home");
?>
<?php include 'header.php' ?>
<style>
body {
width: 100vw;
height: 100vh;
background:
url('https://assets.siemens-energy.com/siemens/assets/api/uuid:d1279bc9-a3da-
4899-a656-60854be1cb20/width:1125/quality:high/siemens-energy-cyber-security-
services.jpg');
background-size: cover;
}
.title {
text-align: center;
font-size: x-large;
}
.title2 {
text-align: center;
font-size: x-large;
font-style: italic;
61
}
.forget {
text-align: center;
}
</style>
<body class="hold-transition login-page bg-white">

<div class="login-box">
<div class="login-logo">
<a href="#" class="text-white"></a>
</div>

<div class="card">
<div class="card-body login-card-body">
<b><p class="title2">Admas IES</p></b>
<b><p class="title">Login with User Type</p></b>

<form action="" id="login-form">
<div class="input-group mb-3">
<input type="email" class="form-control" name="email" required
placeholder="Email">
<div class="input-group-append">
<div class="input-group-text">
<span class="fas fa-envelope"></span>
</div>
</div>
</div>
<div class="input-group mb-3">
<input type="password" class="form-control" name="password" required
placeholder="Password">
<div class="input-group-append">
<div class="input-group-text">
<span class="fas fa-lock"></span>
</div>
</div>
</div>
<div class="form-group mb-3">
<label for="">Chose Account Type</label>
<select name="login" id="" class="custom-select custom-select-sm">
<option value="1">Admin</option>
<option value="3">Student</option>
<option value="2">Instructor</option>
</select>
62
</div>

<div class="col-12">
<button type="submit" class="btn btn-primary btn-block">Sign
In</button>
</div>
<div class="row">
<div class="col-8">
<div class="icheck-primary">
<a href="#">
<label class="forget" for="remember">
Forget Password?
</label>
</div>
</div>

</div>
</form>
</div>

</div>
</div>

<script>
$(document).ready(function(){
$('#login-form').submit(function(e){
e.preventDefault()
start_load()
if($(this).find('.alert-danger').length > 0 )
$(this).find('.alert-danger').remove();
$.ajax({
url:'ajax.php?action=login',
method:'POST',
data:$(this).serialize(),
error:err=>{
console.log(err)
end_load();
},
success:function(resp){
if(resp == 1){
location.href ='index.php?page=home';
63
}else{
$('#login-form').prepend('<div class="alert alert-danger">Username or
password is incorrect.</div>')
end_load();
}
}
})
})
})
</script>
<?php include 'footer.php' ?>
</body>
</html>
64

New 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

New Documentation

Uploaded by

Copyright:

Available Formats

ABSTRACT

Instructor’s evaluation is a necessary step in ensuring proper instruction. Traditionally, instructors’

not refer to the performer’s attributes, personal characteristics, or competencies. It is intended to

A big interest on web based application.

To come up with a unique, simplified, and easy to apply system

To solve the bottlenecks of paper based instructor evaluation approach

1.3 Statement of the problem

1.4.2 Specific objectives

navigate at Admas University.

To provide an efficient and effective way to evaluate instructors’ teaching effectiveness.

To enhance the quality of education by promoting effective teaching practices.

Methodology and teaching strategies

Class room management

Personality & interpersonal skills.

1.5 Literature review

1.6 Scope and limitation

Accepts and validate users

Generate the evaluation results

Ready for online and Intranet/internet

The student can only evaluate his/her professor once

The system will be used once every semester

It increases the chance of not providing the exact data sometimes

Limited scope: Online evaluations may not provide a comprehensive picture of an

1.7.2 System analysis and design methodology

1.8 System development model

1.9 System development tools

1.9.2 Software tools

MySQL server compared to others:

Allows transactions to be rolled back, commit and crash recovery

1.9.3 Documentation tools

“If it isn’t documented, it doesn’t exist” – Sitepoint, A Guide to Writing Your

1.10 Significant of the project

1.11 Feasibility study

technical, and operational.

1.11.1 Technical feasibility

1.11.2 Operational feasibility

1.11.3 Economic feasibility

2.1.2 Proposed system

Replace the manual to automated system

Create accounts for different users

2.2 Functional requirements

[FR-01]: Add admin information

Last action: Click on save

[FR-02]: Add subject information

Last action: Click on save

[FR-03]: Add class information

Last action: Click on save

[FR-04]: Add academic year

Last action: Click on save

[FR-05]: Add evaluation criteria

Last action: Click on save

[FR-06]: Delete evaluation criteria

Last action: Click on save

[FR-07]: Update evaluation criteria

Description: making or becoming different from the previous record.

Last action: Click on save

[FR-08]: Add questionnaires

Last action: Click on save

Evaluation restriction or assigning of instructors for evaluation

Last action: Click on add list followed by save

[FR-09]: Add student and instructor records

Last action: Click on save

[FR-10]: Evaluate information