Вы находитесь на странице: 1из 14

CEBU INSTITUTE OF TECHNOLOGY

UNIVERSITY

COLLEGE OF COMPUTER STUDIES

Software Requirements Specifications


for
Web Based Learning Object Research Instrument (LORI) Evaluation System

Signature
CARLO INTILA PROGRAMMER, ANALYST
REYLAN VILI PROGRAMMER, ANALYST

Preface
This is the software requirements specifications (SRS) document for the web based LORI evaluation system.
The intended audience of the SRS are the administrator, users, teachers and research personnel. Also, any
future maintenance staff should be aware of the information contained herein. However, foreknowledge of certain
computer systems and basic knowledge of computers is an asset to understanding the SRS.

Table of Contents
Signature............................................................................................................................................................................................2
Preface................................................................................................................................................................................................3
Table of Contents...............................................................................................................................................................................4
List of Figures....................................................................................................................................................................................5
1. Introduction...................................................................................................................................................................................6
1.1. Purpose......................................................................................................................................................................................................6
1.2. Scope.........................................................................................................................................................................................................6
1.3. Definitions, Acronyms and Abbreviations................................................................................................................................................6
1.4. References.................................................................................................................................................................................................7
1.5. Overview...................................................................................................................................................................................................7

2. Overall Description.......................................................................................................................................................................8
2.1. Product perspective...................................................................................................................................................................................8
2.2. Product functions......................................................................................................................................................................................8
2.3. User characteristics...................................................................................................................................................................................9
2.4. Constraints...............................................................................................................................................................................................9
2.5. Assumptions and dependencies................................................................................................................................................................9

3. Specific Requirements ...............................................................................................................................................................10


3.1. External interface requirements..............................................................................................................................................................10
3.1.1. User interfaces.......................................................................................................................................................................10
3.1.2. Hardware interfaces...............................................................................................................................................................10
3.1.3. Software interfaces.................................................................................................................................................................10
3.1.4. Communications interfaces....................................................................................................................................................10
3.2. Functional requirements..........................................................................................................................................................................11
3.2.1. Use case 1: Administrator Add Users ....................................................................................................................................11
3.2.2. Use case 2: Student, Research Personnel and Teacher Registers in the System ......................................................................11
3.2.3. Use case 3:Student Access Web Based LORI Main Page ......................................................................................................11
3.2.4. Use case 4:Add, Edit or Delete Question Items .....................................................................................................................12
3.2.5. Use case 5:Administrator, Research Personnel, Teacher View or Print Statistical Data .........................................................13
3.3. Performance Requirements.....................................................................................................................................................................13
3.4. Design constraints..................................................................................................................................................................................13
3.5. Software system attributes......................................................................................................................................................................14
3.5.1 Reliability...............................................................................................................................................................................14
3.5.2 Availability..............................................................................................................................................................................14
3.5.3 Security...................................................................................................................................................................................14
3.5.4 Maintainability.......................................................................................................................................................................14

List of Figures

Figure 1 System Environment


The Web- based LORI Evaluation System has four active actors and one cooperating system.
The teachers and students access the Online Project Study through the Internet or through a Local Area Network
where there is a connection to the LORI server. Any research personnel, teacher or administrator with
communication link to the LORI server can manage their own project study. The administrator accesses the
entire system directly.
<< The division of the Web- based LORI Evaluation System into four component parts, the Online Project study,
Project Manager, System Manager and the User Manager, are examples of using domain classes to make an
explanation clearer. >>

1. Introduction
1.1. Purpose
Develop a web-based Learning Object Research Instrument (LORI) application allowing administrators, teachers
and research personnel to prepare an evaluation form for a project. Optionally, allow administrators, teachers and
research personnel to add, edit, and delete question items in an evaluation form. Depending on the restrictions
set the evaluation form will be evaluated by a group of students or teachers. The application also must be able to
print different types of statistical reports.
Being such a strategically important functionality to multiple units, the web-based LORI application will be designed for general use via the internet however, implemented only for use by CIT-Us E-Learning Center, teachers, research personnel and students. Although the first implementation will rely on CITs technical infrastructure,
the application will be designed to be portable to other infrastructures.
I

1.2. Scope
The purpose of this product is to:

Reduce operational costs.


Allow quick adding, editing, and deleting, thus reducing and simplifying the time cycle of processing an
evaluation form
Evaluations will be stored electronically, making it easier to view and print statistical reports.
Ensure accuracy
Since LORI application is of interest to multiple units on campus, the intent of this project is to create a
flexible system that can be accessed in multiple locations.
In general the product scope focuses on streamlining evaluation recording. The evaluations made by the
end users will be the basis of the on how effective a project is.

1.3. Definitions, Acronyms and Abbreviations


Term
Administrators

Definition
The super user of the system, capable of viewing all available
projects and print statistical reports associated to the project

End- users

May include students or teachers who will evaluate a project

LORI evaluation system

The web- based application

Software Requirements
Specification

A document that completely describes all of the functions of a


proposed system and the constraints under which it must
operate. For example, this document.

LORI) - Learning Object Research Instrument


CIT-U Cebu Institute of Technology - University

1.4. References
Dazar, J. et. al. (2010). Research Methods in Human-Computer Interaction. Bell and Bain, Glasgow . 116-117.
Bailey, J. E. and Pearson S. W. (1983). Development of a Tool Measuring and Analyzing Computer User
Satisfaction. Management Science, 29 (5), 530-544.
Clementine, K. et. al.( 2004). Online Grades and Subjects Evaluation System.
Leacock, T. L., & Nesbit, J. C. (2007). A Framework for Evaluating the Quality of Multimedia Learning Resources.
Educational Technology & Society, 10 (2), 44-59.
Thorpe, S. (2002). Online Student Evaluation of Instruction: An Investigation of NonResponse Bias.
www.airweb.org/forum02/550.pdf
Wang, Y. & Zhi, X. (2009). An Evaluation System for the Online Training Programs
in Meteorology and Hydrology. www.ccsenet.org/journal.html
Anderson HM, et. al. (2005) Online Student Course Evaluations: Review of Literature and a Pilot Study
Chang, C. (2001). Construction and Evaluation of a Web-Based Learning Portfolio System: An Electronic
Assessment Tool.
Wode, J. & Keiser, J. (2001). Online Course Evaluation Literature Review and Findings.

1.5. Overview
The next chapter, the Overall Description section, of this document gives an overview of the functionality of the
product. It describes the informal requirements and is used to establish a context for the technical requirements
specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written primarily for the developers and
describes in technical terms the details of the functionality of the product.

2. Overall Description
2.1. Product perspective
The Web-Based Learning Object Research Instrument Evaluation System is an online application that will run in
a web server. The system uses PHP as the main programming language and MySQL database for the storage of
data. The system is capable of generating the statistical results which will be used by the administrator of the ELearning Center, teachers and research personnel for decision makings like how a efficient and effective a
project is.

2.2. Product functions


Adding of users of the System
1.
2.

Administrator enters user information to the system.


The system saves the information.

Registration of Users
1.
2.
3.
4.
5.

User enters ID number.


The system verifies if the ID number exists.
The user enters the username and password.
The system verifies the duplication of the username.
The system saves the username and password

Evaluation of a Project
1.
2.
3.
4.
5.
6.
7.

User opens the main page.


User opens the project evaluation page.
User enters username and password.
The system verifies if username and password is correct.
User selects the available project to be evaluated
User answers the evaluation form.
The student submits his/her answers.

Creating a project
1. Administrator, research personnel and teachers creates a project.
2. Administrator, research personnel and teachers add, edit, delete questions items for a project.
3. Administrator, research personnel and teachers assigns a project to be evaluated by a specific group of
students or teachers.
Printing of Statistical Reports
.
1.
2.
3.

The research personnel and teacher except from the administrator can only open their project.
Administrator, research personnel and teachers select a statistical report.
Administrator, research personnel and teachers print the selected statistical report.

2.3. User characteristics


The users of the system are the following; Administrator, Teachers, Research Personnel and Students. The
administrator must have a thorough knowledge about the operation of a web server and management of an
online database system. The research personnel, teacher and students must also be acquainted about the
applications of Information Technology.

2.4. Constraints

A slow internet connection will affect on how fast the web forms will be loaded in the browser.

The web based LORI system works 100% in browsers like Mozilla Firefox version 5.0 and up, and
Internet Explorer versions 7.0 and up.

The software requirements specification of this document adheres to the IEEE Std 830-1998 standards.

2.5.

Assumptions and dependencies

If this application will be used in CIT-U Learning Center, the process by which the evaluation of the project is
done will not need to be altered. The project proponents currently using Open Source software like PHP and
MySQL to manage projects and generation and evaluation of statistical reports. The Web-based LORI Evaluation
System will run in various operating systems as long as the correct Apache Server is installed.

3. Specific Requirements
3.1. External interface requirements
3.1.1. User interfaces
The user interface shall be web-based, allowing users to remotely access the system via several applications.
Users will be able to use the software through applications such as Microsoft Internet Explorer, Mozilla, et al.
The user interface shall use forms and handle errors that may be committed from inexperienced end users.

3.1.2. Hardware interfaces


Server Side
* Operating System : Windows XP/7/2003 or higher
* Processor : Intel Chipset or any compatible
* Memory : 2 GB
* Hard Drive Capacity :100GB, expandable
* Fast Internet Connection
Client Side
* Operating System : Window XP, Window Vista or Window 7
* Browser : Internet Explorer 6 and above. Mozilla or Google Chrome.
* Memory : 1 GB
* Fast Internet Connection

3.1.3. Software interfaces

Apache Web server

PHP 5.0

MySQL database

3.1.4. Communications interfaces

all evaluation will be done via web forms

3.2. Functional requirements


3.2.1. Use case 1: Administrator Add Users

Use Case Description


1. The administrator adds and saves user information.
2. The program stores it in the database.

3.2.2. Use case 2: Student, Research Personnel and Teacher Registers in the System

Use Case Description


1. The user enters id number. If the id number exists, the program will asked the user to enter username and
password. If id number does not exist, the program will prompt the user about the error.
2. The program verifies if there is a duplication of usernames.
3. The program saves the new user in the database.

3.2.3. Use case 3:Student Access Web Based LORI Main Page

Use Case Description


1. The student opens the program.
2. The program asked for the username and password.
3. The student enters the username and password.

3.2.4. Use case 4:Add, Edit or Delete Question Items

Use Case Description


1. The student selects a project.
2. The program verifies if student has already evaluated the project.
3. The student answers the evaluation form.
4. The student submits the answers.
5. The program verifies if all items have been answered. If all items have been answered, the program stores the
data.

3.2.5. Use case 5:Administrator, Research Personnel, Teacher View or Print


Statistical Data

Use Case Description


1. The administrator, Research Personnel and Teacher can create a new project.
2. The administrator, Research Personnel and Teacher can only add, edit or delete question items related to their
project.
3. If the user performs deletion of items the program verifies it before it is deleted in the database.
4. The administrator, Research Personnel and Teacher can assign a group of students to evaluate a project.

3.3. Performance Requirements


The important aspect of the Web Based LORI is online constraints. The performance of the system based on the
internet connection of the client. Hence client must have fast internet connection to maximize the efficiency of the
system
The accountability is a vital feature and this could be only assured by working with UPS and a steady internet
connection. So uninterrupted power supply and internet connection is badly needed.

3.4. Design constraints


3.4.1 Web Based LORI shall be a web application.
3.4.2 The application shall have a relational database.
3.4.3 The application shall be implemented using PHP Codes and My SQL.
3.4.4 The user interface shall be implemented using common Web Browsers.
3.4.5 The application shall require an Internet connection to execute conducting study and update changes in the
database.

3.4.6 The application shall display error messages to the user when an error is detected.
3.4.7 The data processing module using PHP to My SQL shall be saved as a separate Win32 DLL file.
3.4.8 The control module that the PHP executable calls, and controls the database processing and file generation
shall be implemented using PHP Codes and saved as a separate Win32DLL file.
3.4.9 Object Oriented logic and processing shall be implemented in PHP Codes.
3.4.10 HTML generation module shall be implemented using PHP Codes, saved as a separate Win32 DLL file.
3.4.11 No error condition shall cause the application to exit prematurely.
3.4.12 The PHP code shall be used to interface to the Access database and shall also be used to create HTML
and text pages.

3.5. Software system attributes


3.5.1 Reliability
The program should be carefully planned, constructed and tested such that it behaves flawlessly for the end user.
Errors, including rendering problems, are unacceptable. In order to minimize these problems, all software will be
carefully designed using UML diagrams and a Design to Test approach should be used for the Implementation
Stage.

3.5.2 Availability
The Program is available in any web browser as long it is connected to the internet. The computer is either
connected to the internet or on local network that is connected to the Web-based LORI server.

3.5.3 Security
The server on which the Online Software resides will have its own security to prevent unauthorized
write/delete/read access.
The PC on which the software resides will have its own security. Only the administrator will have a super access
to physical access to the machine and the program on it. The special protection built into this system provides the
research personnel and teacher to read/write edit its corresponding study. The students are also provided by a
username and password to answer the item questions in each study.

3.5.4 Maintainability
The Administrator should periodically check the web server for appropriate updates to ensure current content.
This mechanism must be planned for in the development of the Web-based Learning Objective Review
Instrument System.

Оценить