Pdfcoffee.com learning-management-system-srs-5-pdf-free and SOFTWARE REQUIREMENT SPECIFICATION VER 1.0 E-LEARNING WEBSITE3.2.4 Registering for a Course – StudentThe registration process will be held at the institute. 3.2.5 Dropping a Course - StudentDro PDF

Preview

Summary

Download Pdfcoffee.com learning-management-system-srs-5-pdf-free and SOFTWARE REQUIREMENT SPECIFICATION VER 1.0 E-LEARNING WEBSITE3.2.4 Registering for a Course – StudentThe registration process will be held at the institute. 3.2.5 Dropping a Course - StudentDro PDF

Description

Software Requirements Specification for Virtual Classroom System

Page 1

Software Requirements Specification for

Virtual Classroom System Version 1.0

Prepared by

Group Name Lokesh Jaliminche Gurudatt Kulkarni

12MCS0058 12MCS0043

[email protected] [email protected]

Instructor: Prof. Kumar K. Course: Advanced Software Engineering Date:

29/03/2013

Contents 1

INTRODUCTION...............................................................................................................................................3

1.1

DOCUMENT PURPOSE....................................................................................................................................3

1.2

PRODUCT SCOPE...........................................................................................................................................3

Software Requirements Specification for Virtual Classroom System

2

3

4

Page 2

1.3

INTENDED AUDIENCE AND DOCUMENT OVERVIEW......................................................................................4

1.4

DEFINITIONS, ACRONYMS AND ABBREVIATIONS..........................................................................................4

1.5

DOCUMENT CONVENTIONS...........................................................................................................................4

1.6

REFERENCES AND ACKNOWLEDGMENTS......................................................................................................5

OVERALL DESCRIPTION..............................................................................................................................7 2.1

PRODUCT PERSPECTIVE................................................................................................................................7

2.2

PRODUCT FUNCTIONALITY...........................................................................................................................7

2.3

USERS AND CHARACTERISTICS.....................................................................................................................8

2.4

OPERATING ENVIRONMENT..........................................................................................................................9

2.5

DESIGN AND IMPLEMENTATION CONSTRAINTS.............................................................................................9

2.6

USER DOCUMENTATION..............................................................................................................................10

2.7

ASSUMPTIONS AND DEPENDENCIES............................................................................................................10

SPECIFIC REQUIREMENTS........................................................................................................................11 3.1

EXTERNAL INTERFACE REQUIREMENTS......................................................................................................11

3.2

FUNCTIONAL REQUIREMENTS.....................................................................................................................13

3.3

Non Functional requirements..........................................................................................14

SYSTEM DESIGN............................................................................................................................................15 4.1

DATAFLOW DIAGRAM.................................................................................................................................15

4.2

UML

DIAGRAMS..........................................................................................................................................18 5

SCOPE OF

EXTENSION.....................................................................................................................................24

1 Introduction Developing a Virtual Classroom System to promote a greater count of students to splurge into the field of Education. It integrates the benefits of a physical classroom with the convenience of a ‘no-physical-bar’ Virtual Classroom System, minus the commuting hazards and expenses. It will usher in the immense flexibility and sophistication in the existing learning platform structures,

Software Requirements Specification for Virtual Classroom System

Page 3

with the perfect blend of synchronous and asynchronous interaction. It provides a means of collaborative learning for the students.

There are basically 4 types of users:

•

Student

•

Faculty

•

College Management (Dean, HODs, Principal)

•

Administrator

1.1 Document Purpose The document specifies the software requirement specification for Virtual Classroom System. The software requirement specification document is prepared for certain class of audiences which is comprised of professional and experts. It is prepared in a manner which will help the professionals, managers and experts to build an effective Virtual Classroom System.

1.2 Product Scope VCS (Virtual Classroom System) aims to promote a greater count of students to splurge into the field of Education. It integrates the benefits of a physical classroom with the convenience of a ‘no-physical-bar’ Virtual Classroom System, minus the commuting hazards and expenses. It will usher in the immense flexibility and sophistication in the existing learning platform structures, with the perfect blend of synchronous and asynchronous interaction. It provides a means of collaborative learning for the students. The benefits of having VCS is that student can attend lectures as per their convenience. They can appear for exams, view progress reports and participate in extra-curricular activities online. Faculties can evaluate test sheets, schedule test and perform related activities online. The system will provide easy-to-access web based service which can give management an effective means of managing all resources.

Software Requirements Specification for Virtual Classroom System

Page 4

1.3 Intended Audience and Document Overview The document is intended for the people of following profession:-

•

Project managers-Project managers are those who supervise the entire project.

•

Implementers or coding expertise-This category of professionals implements the design stated by the developers using programming languages. They are responsible for all the application modules and graphical user interfaces.

•

Tester- This class of people test the developed system with the help of certain test cases and determine the efficiency and estimates the performance of the system.

•

Documentation writers-Documentation writers prepare the user manuals and other necessary documents for proper setting of the system in a certain operating environment.

•

Virtual Classroom Users-The people who wants the system in their Educational Institutes. They are responsible for quality of software requirement specification document through their valuable comments on the initial requirement documents.

1.4 Definitions, Acronyms and Abbreviations Definitions: Users: Student, Faculty, Management, Admin Admin: Application administrator responsible for application management. Management: Registered users which manage the entire working of Virtual Classroom. Faculty: Registered teachers of VCS to teach the students studying in VCS. Students: Registered users of VCS as the students of the classroom.

Lecture: A Video/PowerPoint Presentation/Notes on any subject/topic related to any course.

Software Requirements Specification for Virtual Classroom System

Discussion Time: A scheduled time slot during which a faculty will be available (online) for discussion with students and their doubt clearance. Assignment: Two types of assignments: Self-Practice --> The one's those are not to be submitted and will just work as practice exercises. Submission Assignments -->These are to be submitted within a given a deadline. Examination: Test conducted to evaluate the performance of a student in a particular subject/course. Attendance: Statistical report of a student showing the number of classes attended by him/her in comparison to total classes being held.

Progress Report: Report showing the progress of a student after the examination is being conducted. It will be a cumulative course report.

Acronyms and Abbreviations: VCS: Virtual Classroom System HTML: Hypertext MarkupLanguage HTTP: Hypertext Transfer Protocol HTTPS: Secure Hypertext Transfer Protocol

1.5 References and Acknowledgments [1] UML Diagram [pdf] by Prof Kumar K., VIT University [2] Software Engineering A Practioner’s Approach, Roger S Pressmen [3] VIT Academics, http://academics.vit.ac.in/

Page 5

Software Requirements Specification for Virtual Classroom System

Page 6

2 Overall Description 2.1 Product Perspective HTML CLIENT [Admin, Management, Faculty, Student]

•

HTTP/HT TPS

Application Server

Database Server

The web pages (XHTML/JSP) are present to provide the user interface on customer client side.

•

Communication between customer and server is provided through HTTP/HTTPS protocols.

•

The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.

•

On the server side web server is for EJB and database server is for storing the information.

Software Requirements Specification for Virtual Classroom System

Page 7

2.2 Product Functionality Virtual Classroom System is a service that support digital learning process of teaching and learning in the class room and can be divided virtually at several other classes at several different locations. Students can choose courses, attend lectures, take exams, view their attendance records, progress reports etc as per their convenience, also faculty can upload documents, videos and other teaching related materials. Administrator can manage the system from a dashboard.

2.3 Users and Characteristics Users of the VCS can be any person who is interested in having online lectures, meeting or even a conversation. Mainly we can categories the users as lecturers, students, management and administrator Users: Student, Faculty, Management, Admin Student: Each student can participate lecturers by sending a request to the lecturer through the site. They can view the white board and the presentations real-time while listening to the lecture. They can also interact with the lecturer and the other students without interrupting the lecture and also can participate online exams the lecturer has given.

Faculty: As faculties, they can distribute their lectures real-time without staying in a class room but having all the features in a class room. A software white board is provided to demonstrate the lectures. The documentations/presentations can be distributed prior to the lecture. Lecturer can interact with the students by answering their questions. Lecturer can also conduct an exam by storing a set of questions. According to the instructions given by the lecturer, the system will generate an exam paper.

Management: Management is responsible for maintaining the financial details of the users registered for various courses, they have the responsibility of introducing new courses, maintaining the existing courses, address any problems which the users are facing regarding any faculty or course.

Software Requirements Specification for Virtual Classroom System

Page 8

Admin: As admin, they have the task of maintaining the system such as maintaining the database, performing regular backups, keeping the system running and handling any failure of the system.

2.4 Operating Environment Software Interface Client: Web Browser, Operating System (any) Web Server: WAS, Operating System (any) Data Base Server: DB2, Operating System (any) Development End: WSAD, DB2, Rational Application Developer

Hardware Interface CLIENT SIDE PROCESSOR

RAM

DISK SPACE

PENTIUM III

256 MB

1 GB

WEB SPHERE

PENTIUM III at 1

512 MB

2 GB

APPLICATIO

GHz

N SERVER DB2 V9.1

PENTIUM III at 1

512 MB

1 GB(Excluding

INTERNET

SERVER SIDE

Communication Interface •

Client on Internet will be using HTTP/HTTPS protocol.

•

Client on Intranet will be using TCP/IP protocol.

Software Requirements Specification for Virtual Classroom System

Page 9

2.5 Design and Implementation Constraints •

For ensuring platform independence of the software the implementation will be JAVA so the end user system must have a JAVA run time environment.

•

User must have flash player to view videos and animations.

•

The browsers must have plug-ins to view presentation slides.

•

Good internet connection speed for uninterrupted service.

2.6 User Documentation •

A readme file to help the user with the installation of the software.

•

A well documented user manual.

2.7 Assumptions and Dependencies •

A student can register for only one course at a time.

•

Financial Transaction are managed by Admin who ensure their integrity

Software Requirements Specification for Virtual Classroom System

Page 10

3 Specific Requirements 3.1 External Interface Requirements

3.1.1 User Interfaces •

LoginUI The login interface enables you to integrate user login with the content of our website. The system offers protection by storing passwords in encrypted form.

•

RegistrationUI The registration interface enables a new user to register to the system. Image based authentication is provided while registration.

•

NoticesUI The notices interface enables the students to view notices posted by their faculty members. This also lets faculty members post notices on the notices interface.

•

FilesUI The files interface enables the user to download learning materials. Here they can also upload their assignments. The faculty member has the facility to upload documents,presentations.

•

ExamsUI The exam interface enables the students to take exams. This interface will have timer to monitor the timing.

•

EvaluationUI The evaluation interface enables the faculty member to present the detailed evaluation pattern of the exam and the students can see the evaluation of the exams they have attempted

•

ReportUI

Software Requirements Specification for Virtual Classroom System

Page 11

The report interface displays various reports such as progress reports, ongoing course reports, etc. •

CourseUI The course interface enables the student to view the course he has registered.

3.1.2 Hardware Interfaces The additional hardware necessary for participation in the VCS sessions is a computer headset (combination of headphones and a microphone), webcam (optional) and minimum 56Kbps of bandwidth internet connection.

3.1.3 Software Interfaces DB2 is used as the database server. All the user's data and system data will be stored in the DB2 Database. To access the DB2 database we have to implement software interfaces using java. As the web server we use WebSphere HTTP server along with. It contains the server side database handling and the client implementation to view the html and Flash content. HTML is produced by the execution of the codes deployed in the WebSphere server. As Java server we use WebSphere server. Server which runs as an application deployed in the. WebSphere HTTP servers are directly interfaced with the Java server. And also there is a special java interface to communicate with DB2 database server. We transfer webcam output to each other via the web browser’s Flash client. The client which has the multimedia equipment such as Web Cam and microphone can transmit the real time data captured using Flash. White board distribution. This flash application fetches the images periodically and transmits the whiteboard content to the server

3.1.4 Communications Interfaces Client on Internet will be using HTTP/HTTPS protocol. Client on Intranet will be using TCP/IP protocol.

Software Requirements Specification for Virtual Classroom System

Page 12

3.2 Functional Requirements •

Students can choose courses, attend lectures, take exams, view their attendance records, progress reports etc as per their convenience.

•

Attend lectures either at the scheduled time or on request view lecture at a later time.

•

Faculties can take lectures, upload assignments, announcements, evaluate answer sheets and also can upload lectures and other discussions in various formats as in videos, power point presentation etc.

•

Upload and download of various assignments, college notices, student’s notices, journals, videos.

•

Real time collaboration among users via chat rooms, shared and interactive whiteboards.

•

Asynchronous communication in the form of Emails, discussion boards that enable communication to occur at "convenient-times" that suit student schedules and are not accessed at simultaneous or prearranged times.

•

There can be forums, blogs etc to discuss various queries and to put up suggestions posted both by students and teachers.

•

Administrators can generate reports, log files, backup/recovery of data at any time.

•

Shared documents and media library that can help in active learning of a student.

•

Image library.

•

One-to-many, many-to-one and many-to-many information sharing.

•

Availability of voice mail box to allow faculties to get the descriptive messages left by the students.

•

Provisions of resources to arouse the interest of students in extra-curricular activities like public speaking and grasp the chance to enhance their personalities.

•

Students can take up various quizzes which can help them realize their inbuilt talents in various fields.

Software Requirements Specification for Virtual Classroom System

Page 13

3.3 Non-functional Requirements Reliability: The video quality should be clear and good .The audio could be heard well. The video and audio of lectures should be synchronised well.

Responsiveness: Less response time should be there so that student and faculty should feel g...