Sie sind auf Seite 1von 51

PDIS

PRINCIPLES OF DATA AND INFORMATION SYSTEMS

SYSTEM ANALYSIIS REPORT


SYSTEM REQUIIREMENTS SPECIIFIICATIIONS

XXXX X. XXXX
MSIT Student

JERRY R. FLORES
Professor

OCTOBER 2009
UNIVERSITY OF SOUTHERN MINDANAO
Information System Project

Online Faculty Performance Evaluation


A Report on Preliminary Investigation and Analysis of the Current Systems

Systems Analysis Report


April 2009

© 2009 Marnie XX X. XXXXX, Davao City; 0919.301.1592; marn_000@yahoo.com.ph,


All rights reserved.
TABLE OF CONTENTS

Pages

Title Page 1
Table of Contents 2
Introduction 3
Background Information 3
Scope 3
Stakeholder and Development Team 5
Fact Finding Methods 7
Procedure and Methods 9
The Current System 12
DFD – Current System 13
Description of the Current System 14
Problem Cause and Effect Analysis 15
Strategic Implications 16
Proposed Process Model 17
Description of the Proposed System 18
User Expectations and Objectives 19
INTRODUCTION

BACKGROUND INFORMATION

Teachers are one of the backbones of an institution. Their effort, skills and

perseverance aid on molding the students to become successful in their desired

field. Some people will conclude that if a student will excel in his field, will

graduate with flying colors and will successfully pass the nationwide or

international exam, one factor that influences it is the teacher. Thus, some said

that it is still depend on the student’s ability and determination.

Teacher’s performances are sometimes criticized not only by the co-

teachers, but by the students as well, because they are the direct contact of the

teachers. However, those judgments cannot be considered true without a fact.

Thus, every academic institution nowadays conducted the faculty performance

evaluation to assess the effectiveness of the teaching personnel.

The University of Southern Mindanao, Kabacan, North Cotabato is one of

the leading institution that conducts regular faculty performance evaluation. This

activity is done every semester wherein each student has to rate his teacher per

subject, head of the academic office has to rate his subordinates, and faculty

itself has to rate his own and his co-faculty.

The HRM officer and its staff which are the prime movers of the said

activity find it difficult and hard to automatically furnish accurate reports and

results. However, the process takes a lot of time and it takes many days or

months to compute for the result. The student rater in this activity will be given
sheets of paper and by the use of pen selects one numerical scale that would

serve as the grade of the ratee per question. The HRM personnel will wait for the

submission of all students in a certain classroom and will proceed to the next

available students in a room. The scenario will be repeated to comply with the

desired number of students raters. As to the head of academic office, he has to

give to his subordinates the performance evaluation sheets for peer and for self.

Common problems of the HRM office found in this arena, due to the hectic

schedules of the heads and the faculty, they may neglect the forms that would

cause to the delay of the computation of the Human Resource Management

Office. It is for that reason this system is proposed to address the problems of

the office of the Human Resource Management. The main purpose of the system

is to speed up the transaction and to speed up the calculation of results.


Scope

USM is composed of many colleges and consist of many teaching forces.

However, the system’s operation will focus only on one college – College of

Engineering and Computing, wherein the center of ICT development is expected

to start. The system covers only the evaluation of faculty performance wherein

students are the raters. The system falls on this scope because among the

raters, students are the most difficult to facilitate. Nevertheless, the faculty may

view the result of the evaluation.

The system didn’t cover the enrollment and scheduling system to acquire

students and faculty information. These aspects will be entered by the authorized

people into the system. The part of automation is the process of checking or

selecting one among five numerical scales that will serve as the rate in a certain

domain question. The calculation of weight is also included in the system.


Stakeholders and Development Team

The following persons are involved in the making of the system:

Information Workers - whose jobs involve the creation, collection, processing,


distribution and use of information. A single individual can and does many roles.

IT vendors and consultants are those who sell hardware, software and services
to businesses or system end users for incorporation into their information system.

System Analysts are the people who will facilitate the development of information
system and computer applications by bridging the communication gap that exists
between nontechnical system owners and the users and technical system
designers and builders.

System Administrators are the staff at the Office of the Human Resource
Management Office assigned to maintain and facilitate the faculty performance
evaluation.

System Builders are the specialist who will construct, test, and deliver the system
into operation. They are the proponents of this report.

System Designers are the specialist who will design the system to meet the
user’s requirements. They are the proponents of this report

System owners are actually who will pay for the system to be built and
maintained. They are the administrators of the USM.

System Users are the people who will use the system to perform or support the
work to be completed.
Fact-Finding

The researcher is connected to an IT solutions company that is currently

situated at Davao City. One of the aims of the company is to provide possible

solutions to existing manual processes and operations into automations

particularly to the neighboring towns and provinces.

This can be done by conducting observations and surveys pertaining to

the information system they are using. After finding out that the College of

Engineering and Computing at USM is planning to upgrade their faculty

performance evaluation, he submitted a proposal addressed to the dean of the

College of Engineering and Computing, USM, Kabacan.

Negotiations and planning pertaining to schedules, cost and system

requirement followed.
PROCEDURES AND METHODS USED DURING INVESTIGATION

This section was designed to give you a brief summary of the

methods and procedures used in our investigation. You may notify us of

any potential omissions or mistakes that may render our findings incomplete

or inaccurate.

Procedures

Data Flow Diagram

This report contains high-level pictures that diagram the flow of documents and
data through your system. In the interest of brevity, his report only contains high-
level pictures of the current system.

The pictures use the following special symbols:

A square represents a person, department, organization, or


system that is beyond the scope of the system that we
studied, but which provides input to or receives outputs from
the system being studied. In other words, the squares define
where the system begins and ends.

A rounded rectangle represents work that is performed in, by,


or for the system. This includes work performed by people
and machines.

An open-ended box represents data storage, either


temporary or permanent. This includes in/out boxes, log
sheets, reference books, manual files, and computer files.

An arrow represents the actual flow of documents,


messages (possibly verbal), and reports through the system.
Each arrow can be thought of as a pipeline through which
one or more occurrences of the named flow travel.
ENTITIES
Student – the raters of the online faculty performance.
Faculty – who will be evaluated by the students and can view the result online.
HRMO Head – who will give details of faculty and students and the schedules for
evaluation.

IDENTIFIED PROCESSES / TRANSACTIONS


Add Student is the process of adding new student to be a rater.
Add Faculty is the process of adding a faculty to be rated.
Add Question is the process of adding or modifying evaluation questions.
Evaluate is the process wherein a student rate their teacher online.
Schedule is the process wherein the admin allocate an exact date for evaluating
the students.
View result is the process where a faculty can view the students’ comments and
rating
Generate Report is the process of printing reports.

IDENTIFIED DATA STORES


tbl_comments – stores all students’ comments to their teachers.
tbl_eval_schedule – faculty evaluation schedules are stored.
tbl_eval_student – the list of students who evaluated their teachers.
tbl_instructor – stores the personal details of a teacher.
tbl_questionaire - stores all questionnaires according to categories.
tbl_rate – stores the students’ rate in a certain teacher.
tbl_student – stores the personal details a student.
tbl_user - stores the administrative users.

IDENTIFIED DATA FLOWS


Instructor Details
Student Details
Ratings
Schedule Details
Evaluation Results
Comments
THE CURRENT SYSTEM

Analysis of the Current System

The current system is not effective at all in this growing digital age.

Institutions are adopting Information Systems can minimize time and offers

accurate results.

If we will gather the reasons of why the University need to cope and

compete with the new trends of processing data, the following will be the most

appropriate:

1. the current system uses paper and pen to process the data;

2. the current system take too much time, especially on the evaluation

scheduling;

3. the current system didn’t product quick and accurate results coming from

the inputs of the students;

4. file management system is vulnerable to loss of confidentiality, integrity and

availability.
Data Flow Diagram of the Current System

HRMO Head
Date 1.0
Date D1 – Date Folder
Schedule

Questionnaire D2 – Evaluation Sheet


Folders

2.0
Questionnaire D3 – Used Sheets Folder
Distribute
forms
Ratings
Student

3.0
Ratings
Evaluate Ratings

Ratings

4.0
Compute Result
D4 – Result Folder

Result
5.0 Result

Result Print
Teacher
Description of Operation – Current System

The HRMO will set duration of faculty performance evaluation during class

hours. An officer coming from the HRMO will distribute the questionnaire forms to

each of the student in a particular class. Questionnaire form commonly will range

from 3 to 4 pages.

The forms contain section wherein a student writes his entire subject

teacher for the current semester. Questions according to categories follow after

that section with corresponding choices of numerical rates from 1 to 5 as the

highest rate.

The HRMO personnel will collect the evaluation forms after the time

allotted for the students to evaluate their teachers. The HRMO personnel will then

manually compute for the weighted average of each faculty with the evaluated

sheets coming from the students as the basis of the computation. The used

evaluation sheets or questionnaires will be placed in folders and be stored in

cabinets.

The computed rating will be formatted into a more readable form,

generates a copy of it and let the authorized person signed for authentication.
Problem Cause-and-Effect Analysis

Problems Cause and Effect


Uses Paper and pen Due to paper and pen, evaluation sheets
submitted to the HRMO personnel may
not contain clear answers.
Consumed much time It took almost months to let the students
evaluate their teachers to cope up with
the target number of raters.
Slow and inaccurate Results can be acquired when the target
results numbers of raters are done evaluating.
Due to manual computation, a possibility
of inaccurate results.
Prone to loss of An answered forms are placed in an
confidentiality, integrity unsecured place, therefore it is subject to
and availability loss.
Strategic Implications

The developer believes that the current system needs to be

improved. One of the main approaches of doing it is to understand the

needs of the clientele – the students. Are the students satisfied with the

services the institute offered pertaining to evaluation? Aren’t there ways for

them to be satisfied? Are the officer in-charge not willing to improve the

current system? If the administration answered opposite to

the questions presented. Then they understood and agreed to change

the system. They comprehend the problems and are willing to grasp the

possible solutions.

The need is to make it easy and fast for the HRMO personnel and to

the students as well the proceedings of faculty performance evaluation. The

proposal can fast generate reports on evaluation of the faculty

performance. The following discussions will assist on

analyzing how the proposed system will work for the institute.
PROPOSED PROCESS MODEL

Data Flow Diagram

HRMO Head
Student details 1.0 Student details tbl_student
Add
Evaluation Results

Student
Faculty details tbl_instructor

2.0
Faculty details tbl_questionaire
Add
Faculty
tbl_eval_schedule
Question Details

Question Details
3.0
Add
Question

Schedule Details
Faculty details
Student details
Schedule Details 4.0
Schedule

Question Details

Login info, Rate and


5.0 Evaluation Details
Student Comments Evaluate
Student Details tbl_eval_student
Ratings
Comments
tbl_rate

6.0 tbl_comments
Generate Comments
Ratings
Reports
Instructor Details

7.0 Comments
Faculty Login info
View Ratings
Evaluation
Results Result
ONLINE FACULTY PERFORMANCE EVALUATION

Description of Operation – Proposed System

The system is considered online-stand alone because it never

depends on information coming from another system. The information

needed to be processed by the system will be entered by the system

administrator.

The administrator will input the students’ details within the College,

and the faculty members’ details, as well as the domain questions to be

used during the faculty performance evaluation.

The administrator, through the authority given by the head of office

will set a schedule as to when shall the evaluation starts and ends. During

the scheduling activity, the administrator will set the target student raters on

each faculty.

The students will rate their teachers at their own pace. Students will use their

Identification number and their password to sign in to the online system for them to

do the conduct of evaluating their teachers. Evaluation has four categories,

additional comments, and consists of related questions. Each question has five

numeral scales and each scale corresponds to a certain description as follows:

Numerical Scale Description


5 Outstanding
4 Very Satisfactory
3 Satisfactory
2 Fair
1 Poor
Category Area
A Commitment
B Knowledge of Subject Matter
C Teaching for Independence Learning
D Management of Learning
Add Comments Add Comments

Students click submit button to post their rates.

A faculty can view results and comments submitted by the students. This

can be done when a faculty uses his username and password to sign in to the

online system. Evaluation results can be printed for future use.

User Expectations and Objectives


System Objectives System Constraint
To automate the current system HRMO personnel will no longer visit
each class to conduct a faculty
performance evaluation. The system
administrator will post all
questionnaires online.
To minimized time HRMO personnel will just set schedule
for the students to rate. Students may
do the conduct during their vacant time
as long as the computer to be used is
online.
To provide quick and accurate results System has the capability of automatic
calculation of results. HRMO personnel
will no longer do the traditional way of
computation.
To improved file management and Ratings and results are stored in a
security centralized storage. No longer
unsecured folders and cabinets.
System Requirements Specifications
October 10, 2009

TABLE OF CONTENTS
Pages
Title Page 1
Table of Contents 2
Introduction 3
System Description Overview 5
Project Drivers 10
The purpose of the Product 10
Users of the product 11
Project Environment Constraints 12
Mandated Constraints 12
Procedures, Naming Conventions, and definitions 13
Procedures 13
Naming Convention and definitions 15
Functional Requirements 17
The Conceptual Data Flow Diagram 17
The Level 0 DFD 18
Description of Operation 19
The Use Case Diagram 20
Requirements Narratives 21
Hardware and Network Architecture 22
Hardware and Software Specification 23
Data Requirements 25
Security Requirements 27
Backup and Recovery 28
Requirements Modification 29
Final Software Requirement Specification Agreement 30
Appendices 32

INTRODUCTION

Teachers are one of the backbones of an institution. Their effort, skills and

perseverance aid on molding the students to become successful in their desired


field. Some people will conclude that if a student will excel in his field, will

graduate with flying colors and will successfully pass the nationwide or

international exam, one factor that influences it is the teacher. Thus, some said

that it is still depend on the student’s ability and determination.

Teacher’s performances are sometimes criticized not only by the co-

teachers, but by the students as well, because they are the direct contact of the

teachers. However, those judgments cannot be considered true without a fact.

Thus, every academic institution nowadays conducted the faculty performance

evaluation to assess the effectiveness of the teaching personnel.

The University of Southern Mindanao, Kabacan, North Cotabato is one of

the leading institution that conducts regular faculty performance evaluation. This

activity is done every semester wherein each student has to rate his teacher per

subject, head of the academic office has to rate his subordinates, and faculty

itself has to rate his own and his co-faculty.

The HRM officer and its staff which are the prime movers of the said

activity find it difficult and hard to automatically furnish accurate reports and

results. However, the process takes a lot of time and it takes many days or

months to compute for the result. The student rater in this activity will be given

sheets of paper and by the use of pen selects one numerical scale that would

serve as the grade of the ratee per question. The HRM proctor will wait for the

submission of all students in a certain classroom and will proceed to the next

available students in a room. The scenario will be repeated to comply with the
desired number of students raters. As to the head of academic office, he has to

give to his subordinates the performance evaluation sheets for peer and for self.

Common problems of the HRM office found in this arena, due to the hectic

schedules of the heads and the faculty, they may neglect the forms that would

cause to the delay of the computation of the Human Resource Management

Office. It is for that reason this system is proposed to address the problems of

the office of the Human Resource Management. The main purpose of the system

is to speed up the transaction and to speed up the calculation of results.

System Description Overview


The system is very simple and can be accessed online. Using your
favorite web browser you can access it by typing http://opevaluation.biz.nf on the
URL bar. Biz.nf offers free web hosting, and currently it is used while conducting
tests and debug operations through the system’s maturity and until user
acceptance.
The following figures show the overall functionality of the system.

Figure 1: Homepage

At the homepage, you can find three modules: Student, Faculty and

Administrator. Home and About-us tabs are common to every module.

Student Mode:

Figure 2: Home of student mode


When a student log on to his account by the use of username and
password, he can do either one of the following:
1. Evaluate his instructor;
2. Comments to instructors and suggestions to administrator;
3. View his account.
Figure 3: Student Account / Profile

Figure 4: Evaluating Instructor


 Selecting evaluate tab directs a student to the list of faculty where he was
connected.
 Click the faculty name directs the questionnaire.

Figure 5: Performance Evaluation Questionnaire.

 Questionnaire has five categories:


o A – Commitment
o B – Knowledge of Subject Matter
o C – Teaching for Independent Learning
o D – Management of Learning
o Comments
 Rating can be selected by clicking the drop-down menu.
 Rating has five levels:
o 5 – Outstanding
o 4 – Very Satisfactory
o 3 – Satisfactory
o 2 – Fair
o 1 – Poor
 Hitting the SAVE RATING button posts the rating to the database and it
may be viewed by the instructors.

Figure 6: Comments to Instructors


Figure 7: Comments to Administrator

Figure 8: Faculty Panel

 A faculty has to log in using Id number and password.


Figure 9: Faculty Home mode

 A faculty can view his profile.


 A faculty can view evaluation results and the evaluators
 A faculty can view comments

Figure 10: Administration Panel

 Admin Panel shows the summary of all system’s operations.


 Admin can add questionnaires.
 Admin can add new faculty.
 Admin can add new student.
 Admin sets the evaluation schedule and the target raters.
Figure 11: Adding questions

 Each question has 2 action buttons: Edit (designated by a pencil) and


Delete (designated by an X icon).
 Adding questions would also mean setting the category(group) and sort
order.

Figure 12: Adding a faculty

 Click on Add button to successfully add a faculty.


Figure 13: Setting Evaluation Schedule

 Select instructor to set the schedule of evaluation.


 Specify target date.
 Year
 Semester
 Target Evaluators
 Click Add

Figure 14: Viewing Results (On-going or Finish)


Figure 15: Adding a student
PROJECT DRIVERS

The purpose of the Product

The purpose of this system is to make it easy and fast for the

HRMO personnel to manage the faculty performance evaluation transaction.

Not only to the personnel but also to the students who will act as evaluators of

the faculty performances.

This product develops to automate the current paper and pen processing

of faculty performance evaluation. Through it, the processing time can be

minimized and it can quickly generate accurate results. The products also

address the problem of data loss of availability, integrity and confidentiality.

It will be implemented at the College of Engineering and Computing of the

University of Southern Mindanao, Kabacan. USM decided to focus only to one

college as a sort of system evaluation. If they find the product very much

effective, they will implement it in the whole university.


Users of the Product

The HRMO personnel will be the authorized person to control the overall

processing of the system. HRMO personnel will be given administrative username

and password. But his authority is still subject to the HRMO head, he provides

every detail necessary for the performance evaluation schedules.

A student plays a very essential role in the system. Data to be processed

by the system comes from them. They act as the evaluator of the faculty

performances and without their roles the main goal would not be completed.

Faculty has the right to be informed regarding the results of the

evaluation. These would help them act responsibly on their job.

The builders are the prime movers in building the system. Their skills in

terms of coding and analysis are needed for the regular maintenance or

depending upon the agreed contracts.


PROJECT ENVIRONMENT CONSTRAINTS

Mandated Constraints

The following are the basic constraints in defining solutions to the problems.

1. Duration of the projects – The owners and the builders should agree to a

certain schedule on developing the projects. This is to avoid time to market habit

on the eleventh hour.

2. Budget – Amount should be given to those who work for the project.

Amount not only for the developer but also for the facilitator to make the

project a reality.

3. The system analyst – The analyst should be well rounded about the task

given to him to come up and to fit in with the agreed contracts as to when will

the project be finished and how much the company would pay for the specified

requirements.

4. The system owners – They should be present during the project making. This is

to check whether or not the project still following the right track towards the goal.

5. The system users – They should be involved to naturally orient them on the

processes, functionalities of the product.

6. Clear Objectives - The Company should have a clear goal. This set goal is to be

followed by the developers and would set the project according to the defined

standards and objectives.


PROCEDURES, NAMING CONVENTIONS, AND DEFINITIONS

Procedures

The researcher is connected to an IT solutions company that is currently

situated at Davao City. One of the aims of the company is to provide possible

solutions to existing manual processes and operations into automations

particularly to the neighboring towns and provinces.

This can be done by conducting observations and surveys pertaining to

the information system they are using. After finding out that the College of

Engineering and Computing at USM is planning to upgrade their faculty

performance evaluation, he submitted a proposal addressed to the dean of the

College of Engineering and Computing, USM, Kabacan.

Negotiations and planning pertaining to schedules, cost and system

requirement followed. The following aspects were identified on the later activity:

ENTITIES
Student – the raters of the online faculty performance.
Faculty – who will be evaluated by the students and can view the result online.
HRMO Head – who will give details of faculty and students and the schedules for
evaluation.

IDENTIFIED PROCESSES / TRANSACTIONS


Add Student is the process of adding new student to be a rater.
Add Faculty is the process of adding a faculty to be rated.
Add Question is the process of adding or modifying evaluation questions.
Evaluate is the process wherein a student rate their teacher online.
Schedule is the process wherein the admin allocate an exact date for evaluating
the students.
View result is the process where a faculty can view the students’ comments and
rating
Generate Report is the process of printing reports.
IDENTIFIED DATA STORES
tbl_comments – stores all students’ comments to their teachers.
tbl_eval_schedule – faculty evaluation schedules are stored.
tbl_eval_student – the list of students who evaluated their teachers.
tbl_instructor – stores the personal details of a teacher.
tbl_questionaire - stores all questionnaires according to categories.
tbl_rate – stores the students’ rate in a certain teacher.
tbl_student – stores the personal details a student.
tbl_user - stores the administrative users.

IDENTIFIED DATA FLOWS


Instructor Details
Student Details
Ratings
Schedule Details
Evaluation Results
Comments

Naming Convention and definitions

Table names, column names will be named according to the standard

naming convention of software development. Tables and codes will be named as

follows:

TABLES

tbl_comments

tbl_eval_schedule
tbl_eval_student

tbl_instructor

tbl_questionaire

tbl_rate
tbl_student

tbl_user

Relationships
A student may evaluate one or many instructors. The number

depends on the subject enrolled by the student. An instructor can be

evaluated once or many by the students. This depends on the subjects a

teacher handled.
FUNCTIONAL REQUIREMENTS

The Conceptual Data Flow Diagram

Evaluation Results
HRMO Student
Head Student Details

0
Faculty Details Online Faculty
Performance Log in info, Rate &
Comments
Schedule Details Evaluation
System

Log in info Evaluation Results

Faculty
The Level 0 Data Flow Diagram

HRMO Head
Student details 1.0 Student details tbl_student
Add
Evaluation Results

Student
Faculty details tbl_instructor

2.0
Faculty details tbl_questionaire
Add
Faculty
tbl_eval_schedule
Question Details

Question Details
3.0
Add
Question

Schedule Details
Faculty details
Student details
Schedule Details 4.0
Schedule

Question Details

Login info, Rate and


5.0 Evaluation Details
Student Comments Evaluate
Student Details tbl_eval_student
Ratings
Comments
tbl_rate

6.0 tbl_comments
Generate Comments
Ratings
Reports
Instructor Details

7.0 Comments
Faculty Login info
View Ratings
Evaluation
Results Result
Description of Operation

The HRMO personnel is the main operator of the system. He is the

only one who has an authority to add student, add faculty and questionnaires.

This information that the personnel fed into the system will be process at the

1.0 until process 3.0 and it will be stored on tables instructor, student and

questionnaire.

Process 4.0 shows the process on setting the performance evaluation

schedule. In this process, some information coming from instructor table and

student table is necessary. Students as evaluator should be specify and

faculty name for the scheduling. The process then will be stored at table

eval_schedule.

Process 5.0 shows the process where a student logs on to his account.

The process of performance evaluation will happen here. Information coming

from table questionnaire such as the list of questions is needed, also, an

information generated from eval_schedule is really necessary in this process.

Results of evaluation process will be stored at tables eval_student, rate and

comments. Information stored are the students tracer that he evaluated a

certain faculty, he rated and commented too.

Process 6.0 is a process wherein the administrator generates the

result of the evaluation. Information are coming from tables rate, instructor

and comments.

Process 7.0 is the process where a faculty logs on to his account. The

main purpose is to view the rating the results of evaluation. Information will be
coming from rate and comments table.
The Use Case Diagram

Add Student HRMO Add Faculty


Head
Submit details initiates Submit details
initiates
Post Details Post Details
initiates
Edit/ Delete Details initiates Edit/ Delete Details

initiates initiates

initiates
Add Question initiates Schedule
HRMO
Submit details Personnel Submit details

initiates
Post Details initiates Post Details

initiates
Edit/ Delete Details initiates Edit/ Delete Details

Evaluate Student initiates Reports

Submit details Submit details


initiates initiates
Evaluate / Comments initiates Print

Edit/ view Details


initiates

Faculty

View initiates

Submit details initiates

Edit/ view Details initiates

View details
Requirements Narratives

The developer make use of the PHP, it is a widely-used general-purpose

scripting language that is especially suited for Web development and can be

embedded into HTML. PHP is used for the interface development intended for

the users of the system.

MySQL is also used, it is a relational database system that is used to store

information. MySQL can store many types of data from something as tiny as a

single character to as large as complete files or graphics. Although it can be

accessed by most programming languages, it is often coupled with PHP because

they work together with ease.

Information stored in a MySQL database hosted on a web server can be

accessed from anywhere in the world with a computer. This makes it a good way

to store information that needs the ability to change over time, but also needs to

be accessed over the net. Some examples that can utilize MySQL are a web

message board or a customer's shipping status.

The Apache HTTP Server Project is an effort to develop and maintain an

open-source HTTP server for modern operating systems including UNIX and

Windows NT. The goal of this project is to provide a secure, efficient and

extensible server that provides HTTP services in sync with the current HTTP

standards.
Hardware and Network Architecture

The users may access the system within the organization (within red),

however, they may also access it outside.


Hardware and Software Specification

(Server and Back Unit)


Any Microsoft Windows Server Operating System (Advanced Server
2000 recommended)
SQL Server Version 7.0 (Standard Edition) or higher Internet Explorer 5.1 or
higher (Any web browser) Microsoft Windows Common Controls must be
installed Microsoft Office (Any)
Microsoft Visual Studio 6.0 (Enterprise Recommended) Network Utility Program
Back up utility program

Hardware: (Client)
Monitor with screen resolution of 1024x728
Compatible Mouse and keyboard
Any Processor with a speed of 1.5Ghz or higher recommended
128mb of RAM
Video card with memory of 32mb or higher recommended
Network Interface card Uninterrupted Power Supply (Server)
Monitor with screen resolution of 1024x728
Compatible Mouse and keyboard
Any Processor with a speed of 1.5Ghz or higher recommended
(Dual Processor Recommended)
128mb of RAM (512 recommended)
Video card with memory of 32mb or higher recommended
Network Interface card Uninterrupted Power Supply Peripherals:
Network Cables Switch/Hub RAID Devices
CD-ROM

Software: (Client)
Any Windows Operating System (Win 2000,XP Professional Recommended)
MySQL Server Version 5.0 (Standard Edition) Internet Explorer 5.1 or higher
(Any web browser) Microsoft Windows Common Controls must be installed
Microsoft Office (Any)
Apache Server
PHp
DATA REQUIREMENTS

Relationship

A student may evaluate one or many instructors. The number

depends on the subject enrolled by the student. An instructor can be

evaluated once or many by the students. This depends on the subjects a

teacher handled.
SECURITY REQUIREMENTS

The following are the types of security requirements the project should

contain.

Define the authentication requirements in detail. These include the

preferred strategy for resolving forgotten passwords, addressing account

lockouts, etc. If certain critical transactions shouldrequire re-

authentication, this is the right time to specify that.

Auditing and logging requirements of the software are another

aspect that should be identified. The business owner should specify what activity

should be logged, the level of detail required and who should have access

to these logs. This assists designers chose an appropriate logging strategy and

capture the details most relevant to the business owner.

Intrusion monitoring requirements are another class of

requirements that the owner is best positioned to specify. Increasingly, intrusion

detection capability is moving from the network layer to the application layer, as

generic network layer intrusion detection systems cannot understand threats

specific to a business context.


REQUIREMENTS MODIFICATION

Specified requirements corresponds an appropriate amount in the cost

benefit analysis. Costs are being suit to the exact features of the system to be

developed. Time and schedule of the development were also recorded in the

schedule of activities or the time frame. Workers agreed to contracts of what to

do and when to finish the work.

Any changes raised by the owners or the end users would mean change

of the modules, change of the work, change of the schedule and change of the

cost.
FINAL SOFTWARE REQUIREMENT SPECIFICATION AGREEMENT

= Requirement Specification Agreement=

This is a legal agreement between University of Southern Mindanao,


Kabacan, North Cotabato and Marnie Dave Eballes & Co. By signing this
contract, you are agreeing to be bound by the terms of this
Agreement.
If you do not agree to the terms of this Agreement, promptly pay
an amount for the time and skill we spent on studying and analyzing the
problems and the possible solutions of it. This agreement was mentioned in the
contract signed by two parties that upgraded software will be developed and
installed in your company.

Builders. The number of developers was reflected in the Development Team in


the Analysis Report. These people should conduct a regular sessions to talk
about the development of the product. Sessions will be conducted on the first
and third Saturday of every month.
Time and Schedule. Time and schedule should be thorough follow by
those who are involved in the system development. Work of those involved
should be in accordance with the set time and schedule.
Cost. This aspect was reflected in the cost benefit analysis.
System. Defined requirements of the system are the job intended to be
performed by the developers. Any recommendations by the owners during the
making and not stated in the system requirement will not be honored.

Owner Services. From time to the, the services of the owners and end users
are necessary. This is to check and validate if the system being developed
conforms to the specified requirement needed by the owner and are reflected in
the requirement specification.
Installation. The system will be installed right after it has finished and in
accordance to the schedule.
Orientation. The team will conduct an orientation to the users of the system
twice. First is during the installation, second when the need arise. A manual
will be given to the company as a guide of the system’s operation.
Maintenance. The product conforms to two- year maintenance. The
following years, should be charge of 2% of the total amount paid by the owner.
Modification. Specified requirements corresponds an appropriate amount
in the cost benefit analysis. Costs are being suit to the exact features of the
system to be developed. Time and schedule of the development were also
recorded in the schedule of activities or the time frame. Workers agreed to
contracts of what to do and when to finish the work.Any changes raised by the
owners or the end users would mean change of the modules, change of the
work, change of the schedule and change of the cost.

This agreement is protected by copyright laws and international treaty


provisions. If you do not agree to the terms of this Agreement, promptly pay an
amount for the time and skill we spent on studying and analyzing the problems
and the possible solutions of it. For any questions you may contact Marnie
Dave Eballes & Co.

ASSCAT – IEIS
Second Party

Date

Marnie Dave Eballes & Co.


First Party

Date

Signed in the presence of: