NOTE: This template is shareware downloaded from www.processimpact.com.

All shareware payments are donated to the Norm Kerth Benefit Fund to help a consultant who is disabled with a brain injury. Please visit http://www.processimpact.com/norm_kerth.html to make a shareware payment ($10 suggested). Thank you!

Software Requirements Specification

for

Integrated Modules for Client Relations

Version 1.0 approved

Prepared by

Cruzat | Isip | Pilien | Soliveres

Team PICS (MathHub Tutorial Center)

December 18, 2013

eLearning versions of several popular Process Impact training seminars are available at www.processimpact.com/elearning.shtml , including In Search of Excellent Requirements, Exploring User Requirements with Use Cases, Writing High -Quality Requirements, Software Inspections and Peer Reviews, and Project Management Best Practices. Single-user and corporate-wide site licenses are both available.
Copyright 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for <Project>

Page ii

Table of Contents
Table of Contents ..................................................................................................................... ii Revision History ....................................................................................................................... ii 1. Introduction ......................................................................................................................... 1
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 Purpose ....................................................................................................................................... 1 Document Conventions ............................................................................................................... 1 Intended Audience and Reading Suggestions............................................................................... 1 Project Scope .............................................................................................................................. 1 References .................................................................................................................................. 1 Product Perspective..................................................................................................................... 2 Product Features ......................................................................................................................... 2 User Classes and Characteristics ................................................................................................. 2 Operating Environment ............................................................................................................... 2 Design and Implementation Constraints ...................................................................................... 2 User Documentation ................................................................................................................... 2 Assumptions and Dependencies .................................................................................................. 3 System Feature 1- Registration System ....................................................................................... 3 System Feature 2 - Scheduling System.... 3 System Feature 3- Time Tracker ................................................................................................. 4 System Feature 4 - Feedback and Key Metrics 4 User Interfaces ............................................................................................................................ 5 Hardware Interfaces .................................................................................................................... 5 Software Interfaces ..................................................................................................................... 5 Communications Interfaces ......................................................................................................... 5 Performance Requirements ......................................................................................................... 5 Safety Requirements ................................................................................................................... 6 Security Requirements ................................................................................................................ 6 Software Quality Attributes ......................................................................................................... 6

2. Overall Description ............................................................................................................. 1

3. System Features ................................................................................................................... 3

3.1 3.2 3.3 3.4 4.1 4.2 4.3 4.4 5.1 5.2 5.3 5.4

4. External Interface Requirements ....................................................................................... 5

5. Other Nonfunctional Requirements ................................................................................... 5

6. Other Requirements ............................................................................................................ 6 Appendix A: Glossary ............................................................................................................... 6 Appendix B: Analysis Models ................................................................................................... 6 Appendix C: Issues List ............................................................................................................ 6

Revision History
Name Date Reason For Changes Version

Software Requirements Specification for <Project>

Page 1

1. Introduction
1.1 Purpose

This System Requirements Specification is for MathHub Tutorial Center, Katipunan, Quezon City. The program is intended to computerize the businesss client relations system, which is comprised of an online client registration form, tutorial scheduling system, time tracker and feedback features. These components will be further discussed in the next sections .

1.2 Document Conventions

This part will be elaborated and modified as the project progresses.

1.3 Intended Audience and Reading Suggestions

Prospective developers of the system software. The administrators and other stakeholders of MathHub Tutorial Center.

1.4 Project Scope

Goals: to have a system that would integrate the registration process, scheduling, time tracking of consumed hours spent by the client, and provide means to obtain client feedback for service improvement. Benefits: 1. Faster and convenient registration means for clients 2. Easy access for client information on the part of the administrators of the business 3. Will result to a more organized, compact, and efficient customer database (less office space consumed for piling papers) Objectives: To computerize MathHubs main business function which is client enrollment in their tutorial service. Business strategy: To accommodate as many students as the means and resources of the permits.

1.5 References

Hoffer, Jeffrey, et al. Modern System Analysis and Design. Pearson Education South Asia, Jurong, Singapore. 2011

Software Requirements Specification for <Project>

Page 2

2. Overall Description
2.1 Product Perspective

This is a new system because MathHub Tutorial Center does not have any existing system software that addresses this particular function of their business.

2.2 Product Features

Client information are now stored in a computer, as opposed to MathHubs previous method of compiling the hard copy of clients forms manually. Furthermore, online registration will be enabled so as to accommodate the clients anytime, anywhere and at their most convenient time. Information inputted will be consolidated into a database, with a copy stored on the business computer and an online back-up will be created The new system software will also enable the administrators to monitor day-to-day operations with the scheduling system feature. Easier way to obtain and compile feedback from clients.

2.3 User Classes and Characteristics

Secretary of MathHub - one of the favored users and at the same time the person that will be frequently using the system. The Academic Director and Managing Director of MathHub - also a favored user because they are concerned in monitoring the number of clients enrolled in the tutor service. Clients can only use the registration system feature of the software system.

2.4 Operating Environment

The system software will run primarily on the offices desktop computer. The desktop computer will have a Windows Operating System since it is the operating system readily available on the office computers. Google Drive will also be used as a platform for online backup of information.

2.5 Design and Implementation Constraints

Memory and/or hard disk space that can last within a considerable period of time.

2.6 User Documentation

User manual Built-in tutorial

Software Requirements Specification for <Project>

Page 3

2.7 Assumptions and Dependencies

Memory/Hard disk space may be a possible constraint Some of the system may depend on Google Drive The internet connection of the Tutorial Center must be fast enough to process the information that will be synced online.

3. System Features
3.1 System Feature 1 Registration System
3.1.1 Description and Priority

High priority feature An online form linked in MathHubs website and Facebook page (for maximum visibility. Here, the clients can register anytime, anywhere or at the convenience of their home. Benefit: 9 (to make form processing more efficient and space saving) Penalty: 9 (Since client information must be of priority in this type of framework. Delaying the starting point of the project delays the whole the project) Cost: 7 (Moderate cost since online apps such as Google can be used for this part)

3.1.2

Stimulus/Response Sequences

Access the online form by clicking the link. Fill up the fields required in the online form. Submit the form to the database by clicking submit.

3.1.3

Functional Requirements

If the client will input inappropriate or wrong information on the form fields, the online field will reload the form with the fields with erroneous information inputted is highlighted so that the client can go over it and correct the entry.

3.2 System Feature 2 Scheduling System

3.2.1 Description and Priority

This will be composed of two parts, namely: 1. The preferred schedule table - where the agreed time slots for both tutors and tutees can be seen on separate sheets. This will include a function where the administrator can search particular tutor-tutee schedule. 2. The real schedule table - contains the adjected schedule for the week that takes into account all the cancellation of schedules between tutor and tutees. Benefit: 9 (easier access to tutor-tutee schedule on the part of the management) Penalty: 9 (Since scheduling is a vital part of the operation of MathHub) Cost: 8 (since this might require a new coding)

Software Requirements Specification for <Project>

Page 4

3.2.2

Stimulus/Response Sequences

The administrator will be asked for authentication to access the schedule table. Upon submission of the clients top three preferred schedule, the administrator will input the schedule in the system. The schedule system software will now arrange the schedule to see if theres no conflict with existing tutoring schedule.

3.2.3

Functional Requirements

If the client will input inappropriate or wrong information on the form fields, the online field will reload the form with the fields with erroneous information inputted is highlighted so that the client can go over it and correct the entry.

3.3 System Feature 3 Time Tracker

3.3.1 Description and Priority

This aims to computerize the log-in, log-out system of the daily tutorial sessions.The time tracker will help the administrators in keeping track of the usage of the package/hourly rates of the clients on the daily course of business. Benefit: 9 (a big help in both the administrators and the clients in seeking transparency and accuracy in the consumption or usage of the tutorial package availed from MathHub) Penalty: 8 Cost: 8 (since this might require a new coding as well)

3.3.2

Stimulus/Response Sequences

The administrator will be asked for authentication to access the time tracker system from the desktop computer of MathHub.Once the tutee arrives, the administrator (or whoever is in charge of the reception) will search for the record of the client in the time tracker. When the administrator clicks the start session button, the computer will automatically record the time the session started. When the session ends, the administrator should just click the end session button and the system will automatically record the time the session ended.

3.3.3

Functional Requirements

If the administrator erroneously clicks the start session or end session button, he/she can click the undo session button. In turn, the software will ask again for authentication before it undo the action.

3.4 System Feature 4 Feedback and Key Metrics

3.4.1 Description and Priority

Aims to provide a feedback system for the tutors of the business. This is important especially since MathHub Tutorial Center is a service-type business. Together with the feedback system is the key metrics feature. This will tabulate and/or consolidate all the feedback forms submitted. As an output, this will produce a graph summarizing the trend of the business activity for varying length of time (monthly, quarterly, semiannual and annual).

3.4.2

Stimulus/Response Sequences

After the tutorial sessions, the clients will be sent a link through email. This link will direct them to the online feedback form, with the questions or fields to be filled up are patterned after the manual feedback form distributed by MathHub before operations.

Software Requirements Specification for <Project>

Page 5

This will be filled up by the clients. After clicking the submit feedback button, the data inputted will then be consolidated and organized by the program. Relative statistics will be computed such as average students per week, month or year. It can also show them then days where there are notably more students going on tutorials.

3.4.3

Functional Requirements

Will be updated as the project progresses.

4. External Interface Requirements

4.1 User Interfaces
The interface will look like (or will be patterned) CRS because there would be tabs for different features of the software. The following are the main tabs that can be seen in the homepage: Registration Scheduling Time Tracker Feedback and Progress Reports

4.2 Hardware Interfaces

The primary hardware to be used is a desktop computer which is available at the office. Other components that will be needed are router for internet connection, tablet for e-signature (to be used in forms and time tracker feature), mobile phone for customer relations, printer and scanner for pertinent documents.

4.3 Software Interfaces

We intend to use online applications that are readily accessible and user friendly such as Google Apps and the Microsoft Office set in building the overall systems.

4.4 Communications Interfaces

To improve customer relations management, we will make use of email and online forms our communication channels to reach the clients. There would be an online registration form in the website. A confirmation message will be sent to the customers email upon receipt of the registration form. For feedback and suggestion, there would also be an online form in the website.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The responses from the online registration forms will be sent real time. On the other hand, the confirmation will be delivered within 24 hours from Mondays to Saturdays. The forms submitted every Saturdays will be confirmed every Mondays.

Software Requirements Specification for <Project>

Page 6

5.2 Safety Requirements

The system might be infected with viruses or bugs or hacked. When theres an overload of information, the system may corrupt. To prevent these circumstances, it is advised to install antivirus software and to enable log-in features exclusively for authorized persons.

5.3 Security Requirements

The system will come with an authentication/log-in feature which will enable the administrators to control the number of people which can access the data collected by the system.

5.4 Software Quality Attributes

To be determined in the future as the project progresses.

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>