Outreach Conference Management System

1. Outreach Conference Management System Group – 33 Piyush Rai Piyush Arora SupritAcharya SaniaZehraZaidi MayankGoyal

2. Domain Specific FR’s Finance : Money Collection & Expenditures to be incurred. Providing Conference Details : date, template of paper etc. List Generation PC Committee Selection Reviewing the papers External Referees Selection Assigning papers to members

3. Domain Specific FR’s continue… Discussion between PC Committee Members Email Notification of the payment made by the authors of the papers Managing Database vendors and volunteers

4. User Specific FR’s Notifications about the conference Conference specific details Details related to acceptance/rejection of paper Lodging facilities Details User information modification

5. Business Value Delivered • Reusability of resources • As the resources don’t change much across conferences. • Saving Money and Time • Not many changes required with changing conferences. Ultimate Objective • Conference held is of high quality. • Needs of both the users as well as the stake holders are satisfied.

6. Conflicts : needs v/s wants Stake holders want more profit with lesser investment Users want an efficient system catering to their basic requirements User may require thorough comments on his/her paper User wants that the overall review process should be fast

7. Non functional requirements-Domain specific Reliability and Efficiency: Overall performance of the system remains unchanged and consistent Maintainability: Minimum people required for maintenance, once the system is developed. Security: Payment of money and data submission. Portability: The system remains consistent across all the conferences. Recoverability: Data recovery in case of crashes. If the system crashes then the recoverability functionality needs to be incorporated.

8. Non functional requirements-Organizational Specific Reliability: No Plagiarism should be allowed. Scalability: Efforts involved in maximizing the end users i.e. the users interacting with the system. Affordability: The attributes of the system that are affordable to the organization. Open Source VS Proprietary or licensed tools. Evolvability: Ease with which newly developed modules can be included in the development process.

9. Assumptions • All conferences have almost same modus operandi • Users’ requirements are completely fulfilled by the information provided • User Friendly Interface

10. Restrictions and Constraints • Restrictions • Money allotted for the project • Technical knowledge of developers • Constraints • Deadlines

11. Ambiguous requirements • High Quality : Ensuring quality of high standards is a requirement. But there are no benchmarks set for the same. Non-feasible requirements • Ensuring constant efficiency over different conferences. • As conferences may vary in scale.

12. Non-testable • Plagiarism • In paper submission • In paper review • In committee selection • In the information provided by the user about himself/herself. • Performance efficiency • It can’t be tested during the development phase.

13. Irrelevant Requirements • Selection procedure of PC committee. • External Referees’ selection. • Managing the volunteers. • Lodging facility details. • Conference Details.

14. Requirement Gathering Methods • Interview • conversation with (one or more)stake holders to elicit or validate needs and requirements. • Joint Application Development ( JAD ) • collaboration between stake holders and system analysts to identify requirements in a concentrated and focused efforts. • Survey Method • electronic or paper based method

15. Best Suited Method • Joint Application Development (JAD) Session • Advantages : • Allows simultaneous gathering and consolidation of large amount of information. • Produces large amount of high quality information in a short time. • Discrepancies can be resolved immediately with the help of the felicitator. • A forum to explore different points of view on a topic. • Disadvantages : • Requires significant planning and scheduling effort. • Requires significant stakeholder commitment of time and effort.

16. 2nd Best Suited Method • Survey Method • Advantages : • Reaches a large number of stake holders or other source of information • Gathers significant amount of focused data in short time. • Provides good results when used to validate assumptions after the use of interview technique. • Disadvantages : • Response level is often low, especially to large surveys. • Responses limited to the scope of questions asked • Resolving the conflicts in the information requires additional analysis.

17. Least Suited Method • Interview Method • Advantages : • Easy : can be done with minimal preparation • Interviewing individuals and small groups requires less efforts • Interviewing individuals and small groups requires less stake holder commitment • Explores and clarifies topics in more details • Disadvantages : • Interviewer may ask questions according to his preconceived views thus can influence the response • Time consuming and inefficient in case stake holders are more • Additional interviews required to resolve conflicts • Doesn’t allow stake holders to hear and elaborate upon the information being relayed

18. Thank You !