Case Study: Annexure-2

CASE STUDY: School Learning Management System (SLMS)

(Note: This case study will allow students to use their system requirement collection and
documentation skills, if followed the case study will lead to a thorough understanding of SRS
development)
The International Public School has several branches across the globe, needs to implement
an online learning system to provide students a common source of learning. This online
learning management system will deliver several features which include course contents,
assignments, feedback, grades and other related activities. International Public School has
already given the project proposal to WizTek IT Inc. – A fastest growing learning technology
company. Wiztek IT Inc. must develop a proposed School Learning Management System for
International Public School by using standardized software engineering processes and
activities.
 Identifying system development process.
WizteK IT Inc. decided to follow software development life cycle (SDLC) activities
in order to develop the proposed School Learning Management System for
International Public School. At initial phase the following SDLC activities are
included:
- Requirement gathering: In this activity the development team discusses the
problems/issues with various stakeholders (mainly school administration and staff
members) to bring out as much information as possible on their requirements. The
requirements are further envisioned into functional and non-functional requirements.
• Studying the existing or obsolete system and software
In order to study the current system, the existing learning management system (i.e.
Moodle) is referred to develop clear and feasible system requirements. The
following key features are identified in existing system (i.e. Moodle):
 Provide the user (student/teacher) with a page to login/logout.
 Provide the user (student/teacher) with a page to create and view courses, and to
view activities associated with each course.
 Provide the user (teacher) with quiz development features.
1|Page [Introduction to Software Engineering ITSE202]
Case Study: Annexure-2

 Provide the user (student) a feature to attempt the quiz activity.

 Provide the use (student/teacher) a feature to create and access gradebook.
 Provide the user (student/teacher) a feature to upload/download course related
contents.
 Provide the user (student/teacher) a feature to send/receive text messages.
 Provide the user (teacher) a feature to enroll and remove course participants.
 Responses to queries shall take no longer than 3 milliseconds to load onto the
screen.
 The system shall display confirmation messages to users within 4 milliseconds.
 The files generated by the user are only accessible by the admin.
 Application should store files in MySQL database and must no share them.
 The policy framework should be accessible only by teachers.
 The Moodle LMS shall be available to users all the time.
 The Moodle LMS shall logout automatically, if idle for more than 10 Minutes.
The above identified features may be used as a baseline requirements for the proposed
system. Therefore, the following table represents the requirements proposed by the systems
analyst.
List of requirements to be considered for proposed SLMS
Communication tools
Forum creation and management for SLMS.
E-mail for SLMS.
Sharing of online notes for SLMS.
Online chat for SLMS.
Assistance tools
Search of educational content for SLMS.
Calendar for SLMS.
Online help for the students for SLMS.
Online help for the tutors for SLMS.

2|Page [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

Self-evaluation tools for SLMS.

Creation of groups of students for SLMS.
Administration tools
User authentication for SLMS.
Role management for SLMS.
Students’ enrolment in various courses for SLMS.
Course tools
Scheduling of educational activities for SLMS.
Grading tools for SLMS.
Students’ tracking tools for SLMS.
Test/quiz creation for SLMS.
Course management for SLMS.
Educational content creation tools
Course templates for SLMS
Graphical user interface (GUI) customization for SLMS.
Courses organization for SLMS.
Instructional design tools for SLMS.

 Preparing software requirements specification (SRS)

In order to develop the SRS for School Learning Management System (SLMS),
systems analyst is required to follow the standardized template of SRS. Systems
analyst may use either IEEE templates or a customized template designed by the
organization. In this case study, we have used a customized template for the SRS. In
the following section, SRS for SRS for School Learning Management System (SLMS)
given for your understanding.

3|Page [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

Software Requirements
Specification

For

SCHOOL LEARNING
MANAGEMENT SYSTEM (SLMS)

Version:

Prepared by:

Department:

Date, Month, Year

4|Page [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

Table of Contents
Contents Page No.
1. Introduction 6
1.1 Purpose 6
1.2 Document Conventions 6
1.3 Intended Audience and Reading Suggestions 6
1.4 Project Scope 6
1.5 References 6
2. Overall Description 6
2.1 Product Perspective 6
2.2 User Classes and Characteristics 7
2.3 Operating Environment 7
2.4 Assumptions and Dependencies 7

3. System Features 7
3.1 Login Page 7
3.2 View Course 8
3.3 Attempt Quiz Activity 8
3.4 Participate in Chat Activity 8
3.5 View User Profile 9
3.6 Logout 9
4. External Interface Requirements 9
4.1 User Interfaces 9
4.2 Hardware Interfaces 9
4.3 Software Interfaces 9
4.4 Communications Interfaces 10
5. Nonfunctional Requirements 10
5.1 Performance Requirements 10
5.2 Safety Requirements 10
5.3 Security Requirements 10
5.4 Software Quality Attributes 10
Appendix A: Glossary 11

5|Page [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

1. Introduction

1.1 Purpose

The purpose of this section is to provide the audience with a general, background information
and an understanding of “SCHOOL LEARNING MANAGEMENT SYSTEM (SLMS).”

1.2 Document Conventions

Acronyms and Abbreviations:

a. LMS: Learning Management System

b. SRS: Software Requirements Specification
c. UC: Use Case

1.3 Intended Audience and Reading Suggestions

The intended audience for the SCHOOL LEARNING MANAGEMENT SYSTEM include
developers and designers, and other users- institute heads, students, and faculty members who
are interested to use the SLMS.

Developer and Designers: If the developer or designer wants to read, change, modify or add
new requirements into the existing system, he/she must first consult this document, update the
requirements in an appropriate manner and pass the information correctly to the other phases of
the development process.

Users: The users of this SLMS may review the specifications presented in this document
determines if the application has all the suitable requirements and whether the software
engineer/developer has implemented all of them.

1.4 Project Scope

School Learning Management System is a very beneficial web-based application for educational
institution. This application supports each and every feature of desired LMS and provide
effective and efficient platform for the users.

1.5 References
Appendix A: Glossary

2. Overall Description
2.1 Product Perspective
6|Page [Introduction to Software Engineering ITSE202]
Case Study: Annexure-2

School learning management system is a free source e-learning platform for the students
registered in International Public School. There are approximately 15,000 registered users
including students and faculty members in all the branches of International Public School
across the world.
2.2 User Classes and Characteristics
 Schooling Community
This application is of great use to the schooling community who are currently using or
are interested in using LMS.
 Physical Actors:
Student: The student is the one who login to SLMS and uses various features of this
LMS.
Teacher: The teacher is the one who creates and upload courses, quiz, assignment and
other teaching related activities.

2.3 Operating Environment

 The SLMS shall operate with the any web browser.
 The SLMS shall operate on Windows 7 and above operating system.
 The SLMS is free of cost and can be accessed by any registered user.

2.4 Assumptions and Dependencies

 The server used for SLMS is Apache 2.22.
 The database used for SLMS is MySQL 5.5.31.
 The operation of the SLMS depends on the number of concurrent users and the
activities accessed.

3. System Features

3.1 Login Page

3.1.1 Description
 Provide the user with a page to login to SLMS.

3.1.2 Use Case Sequence

 User clicks on Login Link.
 Login Page is displayed
 User Enters Username and Password
 Username and Password are validated from MySQL Database.
 User Clicks on Login Button
 Home Page is displayed if Username and Password is correct else Error Message is
displayed.

3.1.3 Functional Requirements

 The user shall be able to view and click on Login Link.
7|Page [Introduction to Software Engineering ITSE202]
Case Study: Annexure-2

 The user shall be able to enter the username and password

 The database shall be able to validate username and password.

3.2 View Course

3.2.1 Description and Priority
 Provide the user with a page to view courses and to view activities associated with each
course

3.2.2 Use Case Sequences

 User clicks on Courses Link
 Courses are displayed
 User Clicks on a particular course
 The course page and associated activities are displayed

3.2.3 Functional Requirements

 The user shall be able to view and click on the Courses Link.
 The user shall be able to view the activities associated with each course.

3.3 Attempt Quiz Activity

3.3.1 Description and Priority
 The user shall be able to attempt the quiz activity.

3.3.2 Use Case Sequences

 User clicks on Quiz Activity
 The quiz is displayed.
 User clicks on Next
 The subsequent quiz page is displayed.
 User clicks on Finish Quiz
 The quiz result is displayed.

3.1.3 Functional Requirements

 The user shall be able to view and answer the quiz questions.

3.4 Participate in Chat Activity

3.4.1 Description and Priority
 The user shall be able to participate in chat activity.

3.4.2 Use Case Sequences

 User clicks on Chat Activity
8|Page [Introduction to Software Engineering ITSE202]
Case Study: Annexure-2

 Chat Room is displayed.

 User posts messages.
 Message is displayed.

3.1.3 Functional Requirements

 The user shall be able to view chat room and post messages.

3.5 View User Profile

3.5.1 Description and Priority
 The User shall be able to view User Profile.

3.5.2 Use Case Sequences

 User clicks on Settings -> User Profile
 User Profile page is displayed.

3.5.3 Functional Requirements

 The user shall be able to view user profile

3.6 Logout
3.6.1 Description and Priority
 The user shall be able to Logout.

3.6.2 Use Case Sequences

 User clicks on Logout link
 User is logged out and index page is displayed.
3.6.3 Functional Requirements
 The user shall be able to logout from the System.

4. External Interface Requirements

4.1 User Interfaces

 The system shall provide all functionalities and activities supported by SLMS
 The pages shall permit complete navigation and item selection
 Provide User interface to create a policy
 Provide User interface to add a context
 Provide User interface to edit policy

4.2 Hardware Interfaces

 Processor 1GHz or faster
 RAM 1GB (32bit) or 2GB (64bit)
 Hard disk space 16GB (32bit) or 20GB (64bit)

9|Page [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

4.3 Software Interfaces

 Apache Server 2.2 and MySQL 5.5.31 and PHP 5.4.6 must be installed

4.4 Communications Interfaces

 The SLMS shall use MySQL Database named “SLMS”
 The SLMS shall be able to send emails to the users.
 The SLMS uses PHP 5.4.6 to generate LMS pages.

5. Nonfunctional Requirements

5.1 Performance Requirements

 Responses to queries shall take no longer than 3 milliseconds to load onto the screen
after the user submits the query for 1 user.
 The system shall display confirmation messages to users within 4 milliseconds after the
user submits information to the system.
 The system should generate policy with an accuracy of 99%.

5.2 Safety Requirements

 Consistency: Checking the fact that all clients must be attached to one server, so there is
an appropriate control of the information.

5.3 Security Requirements

 The files generated by the user are only accessible by the admin and application should
store these files in MySQL database and must no share them.
 The policy framework should be accessible only by teachers.

5.4 Software Quality Attributes

 Availability-1: The Optimized Moodle LMS shall be available to users all the time.
 Availability -2: Checking that the system always has something to function and always
pop up error messages in case of component failure.
 Efficiency-1: The Optimized Moodle LMS shall generate the correct pages with an
accuracy of 99%.
 Efficiency-2: Checking that the system provides the right tools to support all its
features.

10 | P a g e [Introduction to Software Engineering ITSE202]

Case Study: Annexure-2

Appendix A: Glossary

Definitions:
 Apache JMeter: The Apache JMeter™ desktop application is open source software, a
100% pure Java application designed to load test functional behavior and measure
performance. It was originally designed for testing Web Applications but has since
expanded to other test functions.
 Web Application: A web application is an application that is accessed by users over a
network such as the Internet or an intranet.
 Web Design: Web design encompasses many different skills and disciplines in the
production and maintenance of websites.
 Web Designer: A web designer is someone who engages in web design.

11 | P a g e [Introduction to Software Engineering ITSE202]