OUTREACH CONFERENCE MANAGEMENT SYSTEM REQUIREMENTS GATHERING CASE STUDY.

BY -- RAJKAMAL,MIRIYALA

VIGNESH,GHANTA

BHARATH, KASHYAP

KOMPELLA, VARUN KUMAR,SRAVAN KUMAR.

INTRODUCTION:Define: Requirements Engineering.

The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed.

Requirements focus on customer needs not on the solution or implementation.

REQUIREMENTS CLASSIFICATION(1)

User RequirementsSystem Requirements

Define : User Requirement

Statements in natural languages plus diagrams of the services the system provides and its operational constraints.

Define : System Requirement

System requirements set out the system’s functions, services and operational constraints in detail. It should define exactly what is to be implemented.

REQUIREMENTS CLASSIFICATION(2)

Functional Requirements.Non-functional Requirements.

Define: Functional Requirement.

These are the statements of services the system should provide.

Now, these can be both User and System requirements.

Define: Non-Functional Requirement.

These are the constraints on the services offered by the system.

They can include timing constraints, constraints on the development process or standards.

They apply to the system as a whole not to individual features.

Define: Domain Requirements

These are the requirements that come from the application domain of the system.

They can be functional or non-functional in nature.

FUNCTIONAL REQUIREMENTS

Information dissemination Choosing web-page templates from pre-

constructed templates. Registration. Update Registration. Payment handling. Printing of Confirmations, invitation letters and

payment receipts. Automated sending of updated registration info

to delegates and payments info to accounts dept through mails.

Generate and print various types of reports on different categories.

(CONTD) Automatic submission of various documents. Management and Monitoring of PC. Automatic generation of latest events. Sending emails to PC members, referees and the

authors for inviting submissions, reviews. Paper assignment based on the preferences of the PC

members. Response of an author to a review. Online discussion of papers. Automatic preparation of conference proceedings. Sending automatic submission acceptance and

rejection notifications. Accommodation bookings, vendor DBMS, volunteer

management.

DOMAIN SPECIFIC REQUIREMENTS Registration. Payment handling Automatic preparation of conference proceedings.

CUSTOMER SPECIFIC REQUIREMENTS Registration. Payment handling.

PRIORITY OF REQUIREMENTS

Based on the feasibility of doing tasks offline with limited resources

Must be: Information dissemination Registration (including providing for modification

and confirmation) Automated submission of documents Monitoring and management of programming

committee Payment handling (by providing a payment

gateway)

(CONTD)

Should be: Automatic list generation of latest events like new

submissions, papers assigned for reviews, reviews submitted, etc.

Sending automatic submission acceptance and rejection notifications.

Response of an author to a review. Management and Monitoring of PC. Online discussion of papers.

(CONTD)

Could Be: Allowing preparation of lists of delegates based on

category and payment status Automatic preparation of conference proceedings. Accommodation bookings, vendor DBMS, volunteer

management. Paper assignment based on the preferences of the

PC members.

BUSINESS VALUE

Saves a lot of money spent on building a portal from scratch for every conference thanks to similarity in requirements of all conferences.

Can also be sold as a product

BUSINESS VALUE - 2

The ultimate objective is to offload from Ajay the arduous tasks of conference management and to make it a best commercial product.

Conflicts between needs and wants: Making conference management easy for Ajay is

a need while selling the software as a product is a want.

NON FUNCTIONAL REQUIREMENTS

Security Confidentiality Integrity Availability

Scalability Changeability Stability Usability Portability

NON FUNCTIONAL REQUIREMENTS

Domain Specific 1. Security. 2. Copyright Law. Organization Specific

1. Security.

CONSTRAINTS

Requirements are bound to add, because it's given in the document itself of having new features.

Time Limit Given is at the max 8 months, because next conference in 12 months

Money constraint is there, so can’t afford to buy any COTS system to integrate into this system.

ASSUMPTIONS

Payments made can't be cancelled. Different Email-Id’s will be created for

different sections. Mailing lists to be created for effective

communication between various roles of system.

Remote Access of our system should be there, "Handling of Registrations, submissions etc. by partner institutions", which implies this system can be remotely accessed.

Various levels of authentication are required for the system.

AMBIGUOUS

This system should allow Program chairs to communicate.

The project shouldn't be very expensive Online discussion of papers Payment Handling.

NON-TESTABLE

In the requirements we cant get the quantitative description of the fastness of the system. Hence this non-functional requirement cant be tested.

NON-FEASIBLE

Automatic Assignment of the papers based on the preferences of the program chairs.

INCONSISTENT

Contacting Professional Software Development organizations for the job.

Trying to assign this job to IIIT students as a major project.

Different plans for the product for different people.

REQUIREMENT GATHERING PROCESS

Document Analysis Interviewing Brain Storming Prototyping Survey