Software Requirements Specification For Education Portal (Online Centralized Examination Registration System with Data Export)

SRS-OCERWDE-V2

Version: 2 Date: 29/03/2011.

1 Copy right 2011 of MoE and eDruk IT Consultancy

1 Revision Table
SL # 1 2 Version 1 2 Author Tenzin Norgay Tenzin Norgay Date 24/03/11 29/03/11 Project Manager have recommend for the iteration of SRS format. Remarks

2 Copy right 2011 of MoE and eDruk IT Consultancy

2 Sign-Off

Project Name: Project Manager: Sponsor(s): Date:

Education Portal Karma Dorji Ministry of Education, DIT, MoIC

The Approvers signature below indicates that the contents of the attached document have been reviewed and accepted subject to the following categories.

Deliverable SRS

Version 2

Description Software Requirement Specification Document for Online Centralized Examination Registration System with data export.

Categories: A B C Agree with contents Agree, subject to incorporation of comments Disagree, comments included

Approver Name/Title Sponsor Project Manager

Signature

Sign Date

Subject to Category

Comments

3 Copy right 2011 of MoE and eDruk IT Consultancy

3 Owners and List of Contacts

Name Email Phone Role

Karma Dorji

karma@edruk.com.bt

332277

Project Manager / System Analyst / Lead Developer / Code Reviewer

Tenzin Zangmo Lam Penjor Babul Subba Tenzin Norgay Kuenley

tenzin@edruk.com.bt edruk@edruk.com.bt edruk@edruk.com.bt edruk@edruk.com.bt edruk@edruk.com.bt

332277 332277 332277 332277 332277

Asst. Project Manager / Developer Developer / Designer Developer / Designer Developer / Designer Project Leader / Developer / Designer

Sonam Dhendup

edruk@edruk.com.bt

332277

Graphic Designer

4 Definitions, Acronyms, and Abbreviations

SRS: Software Requirement Specification. E-Portal: Education Portal, Client/Users: BBE, SCHOOLS, DEO, Internet user at the Internet access point UC OCER: Use Case for Online Centralized Examination Registration System with data export. Server: A system that runs in Linux always monitoring the actions. HTTP: Hyper Text Transfer Protocol User-ID: Unique username issued to each user on login. Password: Unique word given to each user as a secret code. OCER-DIC: Design and implementation constraints. OCER-UD: User documentation. OCER-AS: Assumption. OCER-DS: Dependencies. OCER-SF: System Features. OCER-SF-DP: Description and Priority. OCER-SF-S/R: Stimulus/Response Sequence. Priority Level:1- low priority 5- Medium priority. 9- High Priority. 4 Copy right 2011 of MoE and eDruk IT Consultancy

5 References
The following documents were referred to, while specifying the SRS document: RFP TOR D2-Existing Scenario Report, Survey on Education Service Portal, 12-02-2010, by iTechnologies D3-Future Plan Study Report, Survey on Education Service Portal, 12-02-2010, by iTechnologies D4- Gap Analysis Report, Survey on Education Service Portal, 12-02-2010, by iTechnologies D5- Portal / Future Requirements, Survey on Education Service Portal, 12-02-2010, by iTechnologies D6 Hardware and Infrastructure Requirements, Survey on Education Service Portal, 12-022010, by iTechnologies D7- Portal and ETL framework, Survey on Education Service Portal, 12-02-2010, by iTechnologies Requirement Gathering Report, by eDruk Requirement Validation Report, by eDruk Study Report, by eDruk Meetings with stakeholders, and clients by eDruk.

Document Conventions

This document is written using the following document conventions with its own special meaning: Font Times New Roman Times New Roman (Bold) Meaning Normal Text Specifies that the point is being stressed and should be given more importance Times New Roman (Italic) Special cases, where the system is not catered to, or is something that should be thought for

5 Copy right 2011 of MoE and eDruk IT Consultancy

future development Cambria : Size 14 Cambria : Size 13 Line Spacing Heading Sub heading 1.5

7 Abstract
Bhutan Board of Examination will have an interface for online centralized examination registration system with data export mechanism. Here the students can register online and access their register number or index number directly from the system. School can upload and access students information from the system. BBE focal person will extract and export the data in the system for results processing.

6 Copy right 2011 of MoE and eDruk IT Consultancy

Table of Contents
1 2 3 4 5 6 Revision Table....................................................................................................................................... 2 Sign-Off ................................................................................................................................................ 3 Owners and List of Contacts ................................................................................................................. 4 Definitions, Acronyms, and Abbreviations ........................................................................................... 4 References ............................................................................................................................................. 5 Document Conventions ......................................................................................................................... 5 8.1 Purpose................................................................................................................................................ 8 8.2 Brief Scope of Project ..................................................................................................................... 8 8.3 Project Scope ...................................................................................................................................... 8 8.4 Portal Objectives ............................................................................................................................. 9 8.5 Intended Audience and Reading Suggestions ..................................................................................... 9 8.6 Document overview .......................................................................................................................... 10 9 Overall Description ............................................................................................................................. 10 9.1 Product Perspective ........................................................................................................................... 10 9.2 Product Features................................................................................................................................ 11 9.3 User Classes and Characteristics....................................................................................................... 11 9.4 Operating Environment ..................................................................................................................... 11 9.5 Design and implementation constraints ............................................................................................ 13 9.6 User Documentation: ........................................................................................................................ 14 9.7 Assumptions and Dependencies: ....................................................................................................... 14 9.7.1 Assumptions: .................................................................................................................................. 14 9.7.2 Dependencies: ................................................................................................................................ 14 9.8 User view of the software ................................................................................................................. 14 10 10.1 System Features .............................................................................................................................. 15 Business Process: ........................................................................................................................ 15 10.2 System Feature 1 (Register for the Examination) ........................................................................... 16 10.3 System Features 2 (Schools/Principal will upload the student data in the System) ........................ 18 10.4 System Features 3 (Export the Data in the system) ........................................................................ 20 11 External Interface Requirements ......................................................................................................... 22 11.1 User Interfaces ................................................................................................................................ 22 11.2 Communications Interfaces ............................................................................................................. 23 12 Non-functional Requirements ......................................................................................................... 24 12.1 Data Requirement for Online Centralized Examination Registration System ................................ 24 6 Other Requirements ................................................................................................................................. 27

8 Introduction ................................................................................................................................................ 8

7 Copy right 2011 of MoE and eDruk IT Consultancy

8 Introduction
8.1 Purpose
This is the first draft of SRS, revision 1.for online centralized examination registration system. The purpose of this document is to define the SRS for online centralized examination registration system, to be developed for the Ministry of Education, as per the RPF documents being provided, and as per our proposal.

The document covers

Interfaces Functional Capabilities Performance Levels Data Structures/Elements Training Requirements Safety Reliability Security/Privacy Quality Constraints and Limitations

8.2 Brief Scope of Project

The main scope of the portal project is: Online centralized examination registration system with data export mechanism

8.3 Project Scope

The main scope of the online registration system is to ensure all the schools to have a systematic registration system and to access the index number and results of the examination online in the system. There will an interface for schools and teachers to export and upload the examination data in the system and published the results of examination online in the system. 8 Copy right 2011 of MoE and eDruk IT Consultancy

8.4 Portal Objectives

Main Objectives of the Education Portal are: Improve systemic efficiency in service delivery mechanism Widen access to high quality, relevant and diverse resources and learning opportunity to teachers and students Expose all learners, in advantaged and disadvantaged, to enriched educational experiences. Provide to all learners and teachers the means of communications and collaborations Information sharing, communication and collaboration among agencies

8.5 Intended Audience and Reading Suggestions

Sl No 1.

Audience Project Manager

Description Project Manager can use this document to update the project plan. The document also gives the project manager the overall software, broken down to smaller parts, so that the whole picture of the whole application ca be derived from the modules within the application.

2.

Developers / Designers

Developers and designers can use the SRS to design and develop the software. It has specified the business process, data requirements, validated process flow, data flow diagram, use case diagrams, and interfaces.

3.

Testers

Testers can use the SRS to design their test case from the use cases in the SRS, they can also come out with the required inputs to get particular outputs from the application.

4.

Documentation Writers

Documentation writers can use the SRS to write the Administrator and User Documents. All the required business

9 Copy right 2011 of MoE and eDruk IT Consultancy

process and data flow are clearly mentioned from which the documentations can be done. 5. Users Users can also get an overall picture of the whole application, as users would be confined to particular module of the system, when used, and would be difficult to get the whole picture. The SRS document can help users understand the whole application.

8.6 Document overview

The first section of SRS builds a brief idea what the proposed System of online centralized examination registration is and what is the need behind having it. Along with this background information it also provides the reference information for further study, design and implementation. The second section shows the way to overall description of application, functions, perspective, operating environment, design and implementation constraints, data inputs required. The third section explores the various descriptions of external interfaces such as user interface, hardware interface, communication interface and software interface. The fourth section is written with a goal to show the various system features in detail. The subsections give an elaborate description of individual features. The fifth section focuses on details of non-functional requirements such as security requirements, safety requirements etc.

Overall Description

9.1 Product Perspective

Education Portal is a new web based application that is being developed completely as a new system. Some of its components or modules include integration with existing systems in Ministry of Education

10 Copy right 2011 of MoE and eDruk IT Consultancy

9.2 Product Features

Education Portal is a web based application, whereby the application is accessed via web browser, without the need to have any client software installed on the users to access the application.

9.3 User Classes and Characteristics

The following are the different user and their role in the system: Name Students School/Principal Responsibilities Student will do register to their examination through the system. Schools will upload the students data in the system for the registration in examination. BBE BBE focal person will view and verify the uploaded student data and process it for the registration through the system.

9.4 Operating Environment

The Specification is very generic. The servers are for the core infrastructure, where it will be hosted centrally. If certain applications are to be run in remote schools, the hardware requirement to be computed on the basis of services that would be run in that location.

Item Sl. 1.

Item

Qty.

Configuration

Remarks

Database Server

2 x Quad core Itanium proc / 16 GB memory / 4 x 146 GB SAS internal disk / RAID controller / redundant power supply / 2 x 1Gbps network ethernet port /

Database servers (Running mysql server as Database server, on Linux Platform)

11 Copy right 2011 of MoE and eDruk IT Consultancy

Item Sl.

Item

Qty.

Configuration

Remarks

cluster Will host all the (Minimum Requirement) database for Education Portal 2. Web server 1 2 x Quad core Itanium proc / 32 GB memory / 2 x 146 GB internal disk / redundant power supply / 2 x 1Gbps network ethernet port. Will host Content Management System, Java Framework 3. Web Conference Server 1 2 x Quad core Itanium proc / 32 GB memory / 4 x 146 GB internal disk / redundant power supply / 2 x 1Gbps network ethernet port. Web Conference Server This will run the Web Server (Apache, on Linux Platform)

4.

Application Server

2 x Quad core Itanium proc / 64 GB memory / 6 x 146 GB SAS internal disk / RAID controller / redundant power supply / 2 x 1Gbps network ethernet port / cluster

Will Run the following Applications (Library System, School Administration, ESWS, Procurement Requisition, Online E-Learning(moodle), and all applications, with Reporting Application, Data Integration Application BUS)

12 Copy right 2011 of MoE and eDruk IT Consultancy

Item Sl. 5.

Item

Qty.

Configuration

Remarks

Backup server

2 x Quad core Itanium proc / 64 GB memory / 8 x 146 GB SAS internal disk / RAID controller / redundant power supply / 2 x 1Gbps network ethernet port / cluster

Backup Server

Operating System (OS) 6. 7. Suse Linux Ubuntu 1 1

Network Infrastructure 8. Switch 1 24 port / Gigabit ethernet

Site Related 9. 10. 11. Rack UPS Internet connectivity 1 1 1 2 x 10 KVA as req. dual redundant At least 1 mbps at the core location

9.5 Design and implementation constraints

System ID OCER-DIC-1 Description The school should have the internet access to get register their students online in the system. OCER-DIC-2 For ensuring platform independence of the software the implementation will be JAVA so the end users system must have a JAVA run time environment.

13 Copy right 2011 of MoE and eDruk IT Consultancy

9.6 User Documentation:

A user document should be provided at the end of the development. It should have the following: System ID OCER-UD-1 OCER-UD-2 Description A readme file to help the user with the installation of the software. A well documented user manual.

9.7 Assumptions and Dependencies:

9.7.1 Assumptions: We have made the following assumptions: System ID OCER-AS-1 OCER-AS-2 Description Students registering for their examination online in the system. Student accessing their index number from the system.

9.7.2 Dependencies: System ID OCER-DS-1 Description This software would need JAVA runtime environment and some additional packages for working. OCER-DS-2 It will need an internet access point to every school in Bhutan.

OCER-DS-3

It will need a web browser for viewing the published presentation.

9.8 User view of the software

This software will have graphical user interface that are very user friendly. The user will have no difficulty in working with these user interfaces. The users will import required files into the softwares window, place these files on the time line and edit the duration these files should be displayed. All these operations will be made easy by the softwares user interfaces.

14 Copy right 2011 of MoE and eDruk IT Consultancy

10 System Features
10.1 Business Process:

Figure1: Process Flow of Online Centralized Examination Registration.

Explanation: Here the student will be registering for their examination through the system, and then the teachers or the schools will upload the students data in the system for registration. Once the student submits the registered form in the system, they will get their index number generated by the system. The BBE will extract the uploaded data from the system and view and verify the student details before processing for assigning the index number.

15 Copy right 2011 of MoE and eDruk IT Consultancy

10.2 System Feature 1 (Register for the Examination)

10.2.1 Description and Priority: System ID Name Description Description The student will have an access to register themselves for their examination. The students will fill up the form given OCER-SF1-DP-1 Priority in the system and will be register by submitting it. Registration for examination by the student will be in first priority in the system processes and is in 9th level in priority.

10.2.2 Stimulus/Response Sequences: Name OCER-SF1-S/R-1 Description If the students wants to be register for the examination, they have to fill up the necessities details in the form, the system will display the registration form with the option to send or Cancel after the user have finish filling up the form. OCER-SF1-S/R-2 After that student can submit the filled up form by clicking the Send button, then the system will notify the form is send. OCER-SF1-S/R-3 If the user dont want to send the form, by clicking on cancel button, system display with the message your form will be cancelled click Yes to continue cancellation or No to continue sending.

OCER-SF-S/R-4

When filling up the form, if the user has left some of the fields empty and try to send the form, system will display you cannot leave the field empty. Fill up the empty Fields.

16 Copy right 2011 of MoE and eDruk IT Consultancy

10.2.3 Functional Requirements 10.2.3.1 Use Case Diagram:

Figure 2: Use Case for Online Centralised Examination Registration System.

17 Copy right 2011 of MoE and eDruk IT Consultancy

10.2.3.2 Detailed Use Case: Name Use Case Name Description Student registers for the examination.

Identification

UC OCER1.

Description Pre-Condition

Students will register for the examination in the provided form. Registration form should be provided to the students.

Post-Condition

System will do assign the index number.

Basic Course of Action:

Students will go online for registration. Student will enter the details in registration form. Student will sign up the registration form. System will be generating the index number for the students.

Trigger Exception Paths Alternative Paths

Students submit the registration form by clicking on send button.

10.3 System Features 2 (Schools/Principal will upload the student data in the System)
10.3.1 Description and Priority System ID Name Description Description Once the students are registered, principal or teachers will verify and upload the students data in the system for further process.

18 Copy right 2011 of MoE and eDruk IT Consultancy

OCER-SF2-DP-1 Priority Verifying and uploading of data will be 9th level of priority level.

10.3.2 Stimulus/Response Sequence: Name OCER-SF2-S/R-1 Description When the schools/ principal want to verify and upload the student data, they login to their user account. The system will provide the user interface to login with their password and user name. OCER-SF2-S/R-2 If the user has type incorrect username or password, the system shows validation window with the message your username or password is incorrect, please check your username and password properly and try again

10.3.3 Functional Requirement 10.3.3.1 Detailed Use Case: Name Use Case Name Identification Description Description Upload Students Data in the system. UC OCER 2. Teachers and principal from the schools will upload the data in BBE format in the system. Pre-Condition Post-Condition Basic Course of Action Students should be registered. BBE data format should be provided. Data will be uploaded in the system. BBE will export the data in the system. Student will register for the examination. Schools will upload the students detail in the system. BBE will verify and export the data in the system.

19 Copy right 2011 of MoE and eDruk IT Consultancy

Trigger Exception Paths Alternative Paths

Schools will upload the data in the system by clicking in upload button.

10.4 System Features 3 (Export the Data in the system)

10.4.1 Description and Priority: System ID Name Description Description Once the data are uploaded, BBE focal person will verify and export the data in the system for further process. Then the system will generate student index OCER-SF3-DP-1 Priority number. Export of data in the system will be the 6th priority level.

10.4.2 Stimulus/Response Sequence: Name OCER-SF3-S/R-1 Description BBE will enter into the system with their user name and password to export the uploaded data in the system, the system will provide the user interface for processing the data in the system. OCER-SF3-S/R-2 The BBE will verify and approved or reject the registered form for the students. The system will notify that the registration have been approved or rejected by BBE. OCER-SF3-S/R-3 Once the BBE finished processing the registered form by students in a given interface, the system will generate the Index number and display in the system.

20 Copy right 2011 of MoE and eDruk IT Consultancy

10.4.3 Functional Requirement 10.4.3.1 Detailed Use Case: Name Use Case Name Identification Description Pre-Condition Post-Condition Basic Course of Action Description Export the data in the system. UC OCER 3. BBE focal person will export the data in the system. Student data should be uploaded and reached to BBE. Student will get registered and can access their registered number. Trigger Student will register for the examination. Schools will upload the students data in the system. BBE focal person will export the data in the system. System will generate the student index/registered number.

BBE will export the data by clicking export button and cancel by clicking in cancel button.

Exception Paths Alternative Paths

21 Copy right 2011 of MoE and eDruk IT Consultancy

11 External Interface Requirements

11.1 User Interfaces
The user interface is an important part of this software and will make the software very user friendly. The user interfaces of this software are expected to be as follows:

Figure 3: Student Examination Registration Form

22 Copy right 2011 of MoE and eDruk IT Consultancy

Figure 4: System Generating the Index Number

11.2 Communications Interfaces

Since our system is a web-based system almost all the performance can use the system if the web browser is included. HTTP can be used as a standard communication tools and in addition to improve to security a browser supporting SSL is needed. Also, the users computer must be able to connect to the Internet.

23 Copy right 2011 of MoE and eDruk IT Consultancy

12 Non-functional Requirements
12.1 Data Requirement for Online Centralized Examination Registration System

24 Copy right 2011 of MoE and eDruk IT Consultancy

25 Copy right 2011 of MoE and eDruk IT Consultancy

26 Copy right 2011 of MoE and eDruk IT Consultancy

6 Other Requirements

Figure 5: Activity Diagram for Online Examination Registration

27 Copy right 2011 of MoE and eDruk IT Consultancy