SRS:
1.1 Purpose of this document:
The purpose of this SRS is to serve as the repository for all of the requirements that the CHAIRMAN
system shall or should possess.This specification is the primary document upon which all of the subsequent design, implementation, and test/validation plan will be based.
1.2 Scope of the system
CHAIRMAN is a web application that shall support every aspect of the conference organization
process. This includes paper submission, reviewer assignments, revised and camera-ready paper
submission, registration handling of the conference participants.
1.3 Definitions, acronyms, and abbreviations
Mandatory requirements are defined by using the word “shall”.
Desirable requirements are defined by using the word “should”.
SRS – Software Requirements Specification
CMS – Conference Management System rather than Content Management System
DBMS – Database Management System
PC – Program Committee
1.4 References
This SRS is based on IEEE Std. 830-1998 IEEE Recommended Practice for Software Requirements
Specifications found.
1.5 Overview
Our goal is to complete the project within the allotted deadline and also within the budget fulfilling all the requirements and queries posted by the user.
2. Overall description
2.1 Product perspective
This system is a server side multiple tier web application. It uses external relational database
management system as a data tier. Every user of this system uses only a web browser as a client to
connect to the system. The system and its business logic shall be based on Visual Bascic 6.0
technology which provides platform independence and hopefully rapid application development.
2.1.1 User interfaces
User interface shall be provided through the web browser. This means that it is constrained by the web
browser capabilities.
2.1.2 Software interfaces
One external system shall be the MS ACCESS. There shall be an abstract layer between the system and the MS ACCESS to provide database calls independent from the database vendors. Visual Basics 6.0 serves that purpose.
2.1.3 Hardware Interface
The hardware interfaces in the project includes both server side as well as the client side.
2.1.4 Server Side
Operating System used are Windows Xp / Me. Processor is Pentium 4 with minimum 1gb RAM and hard drive with at least 40 gb.
2.1.5 Client Side
Here the Operating System used is Windows Xp/ Me. Processor is Pentium 4 with minimum 1gb RAM and hard drive with at least 40 gb.
2.2 Product functions and features
The system shall be able to handle multiple sub-conferences.
The system shall support special sessions.
The system shall support on-site participants.
The system shall support paper submission.
The system shall support review process.
The system shall support conference program creation.
The system shall support registration.
2.3 User characteristics
Majority of users will be the academic staff. Higher technical knowledge, experience with the similar
web applications should not be necessary. The system & user interface should be intuitive. In case
intuitive solutions are not possible, detailed explanations should be provided.
2.4 Constraints
Web server should be reliable. Server uptime is critical around author and reviewer deadlines. Web
server and database should be capable of receiving a large (around 50) number of requests
simultaneously. System shall possess these features on a server with one Pentium 4 on 2.4GHz and
with 1GB of RAM.
2.5 Assumptions and dependencies
The system’s interface towards the database shall be through the VB6.0 driver. Such driver is
provided by the VB vendor. System can be migrated to another database vendor only if that vendor
provides the VB6.0 driver.
3 Specific requirements
3.1 External interfaces
Every form for which user provides data shall be validated i.e. must conform to regular expression.
This validation shall be performed both on the client side and on the server side.
3.2 Security requirements
User must carefully fill the online form as its one time process to avoid duplication. If the user enters wrong details and submits he cannot change it again or register again for security purpose.
3.3 System Administrator
3.3.1 Personal data
System administrator has username and password. These values are initially predefined by System
Administrator himself. His e-mail can be used as a contact for any problems related to system.
3.3.2 Conference creation
System administrator is role with the highest rank and is mandated that system functions properly.
System administrator shall create new conference. 3.3.3 Browsing conferences
System administrator shall be able to browse existing conferences in database. By clicking on the
desired conference he becomes conference administrator for that conference and has ability to change
all data.
3.4 Conference Administrator
3.4.1 Conference management
Only conference administrator is able to change all users and conference data.
3.4.2 Conference data
Only the conference administrator is able to change the conference parameters that can be defined or changed through a form.
3.4.3 Review form
Only the conference administrator shall be able to edit or review form.
3.5 Registration Form
3.5.1 Event Information
The conference administrator provides the topic for the presentation, the venue and the date of submission.
3.5.2 Participant Information
The conference administrator provides the registration form for the participant which consists of :-
Participant Name, College Name, Department Name, Contact Number, Address, Email Id etc.
3.6 Paper Management
The conference manager collects all the papers submitted in the database and reviews it. He then selects the appealing papers and send a call back letter to the selected participant including the date of paper presentation and the venue. And he finally selects the winner out of the selected participant after the presentation gets over.
No comments:
Post a Comment