Synergy Distributed Meeting Scheduler Phase I interim report.

Slides:



Advertisements
Similar presentations
Synergy Distributed Meeting Scheduler(SDMS) TEAM:4 Rutvij Mehta Shruti Mehta Shveta Mupparapu Meghna Swetha Raguraman Rakesh Sanapala Venkata Jaganadh.
Advertisements

Synergy Distributed Meeting Scheduler High Fliers.
Information technology solutions development Fundamentals of Information Technology Session 3.
Imran Hussain University of Management and Technology (UMT)
Stoimen Stoimenov QA Engineer SitefinityLeads, SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] February 10, 2009.
Part 4: Evaluation Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what, where, and when Chapter.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Project Execution.
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
Project KickStart Product Requirements Document Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint.
Phase II Instructor: Dr. Lawrence Chung Rachel Bock, Ruben Cavazos, Chih-Lin Cheng, Victor Isbell, Swathi Kandimalla, Nikhil Mishra, Amy Polcari, Ramon.
Modernizing Legacy Systems Lucy Watts, PMP RKV Technologies Inc.
M EETING S CHEDULER S YSTEM Team Members: Aaron Tull Rachel Weldon Derek Horner.
Dineshwari Byrappa Nagraj Rashi Gupta Shreya Modi Swati Satija Magesh Panchanathan.
Engineering Design Process
Presented by Vinit Patwa Prasanna Kumar Thiagarajan Shiva Sangam Meghana Satpute Azharuddin Mohammed Ritesh Patel Tarun Chandra Samireddy Rutvij Desai.
SDMS Project Phase Ⅰ Duk-Jin Kim Tu Peng Yan Shi.
T Project Review Magnificent Seven Project planning iteration
ARRANGING INTERVIEW AND ASSESSMENT EVENTS. Terminology NHS Jobs uses the following terms: An ‘event’ is a collection of one or more appointments taking.
Eric Anderson Liga (Li-Chia Kuo)‏ Elodie Mambounou José Perez Daniel Qi Le Qiao (Joe)‏ Arturo Saracho Russell Smith Josh Wu Tech-9 Members Advanced Requirements.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
INFO 627Lecture #101 Requirements Engineering and Management INFO 627 Review Glenn Booker.
Requirements Engineering ments_analysis.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Synergy Meeting Scheduler System GeetanjaliJeffYogita.
Team Communication and Difficult Conversations Chapter 3.
Synergy™ Distributed Meeting Scheduler Organize meetings with SDMS SynergySoft, Inc. presents:
Synergy Meeting Scheduler System T-squared, S-cubed TJ Andrews Thriveni Movva Sadequa Azam Sama Malik Scott Denson.
Presented by Michael Hale Nelson Lopez Malini Srinivasan Sai Prasanth Sridhar Wanjun Huang Limin Tang Rutvij Desai.
User Management. Basics SDMS shall maintain a database of all users. SDMS shall maintain a database of all users. SDMS shall not limit the number of registered.
Prototyping 101 (from idea to solution). Thomas A. Edison “I have not failed, I've just found 10,000 ways that won’t work”
Phase 1 Interim Instructor: Dr. Lawrence Chung Rachel Bock, Ruben Cavazos, Chih-Lin Cheng, Victor Isbell, Swathi Kandimalla, Nikhil Mishra, Amy Polcari,
CPO Users Forum Managing Group Work in the Classroom Managing the Equipment Between Teachers.
Meeting Scheduler Carl Fernandes Mahbubur Rahman Haque Muaz Jamshed Rahul Kotian Ramakrishnan Jayavelu Sujith John Zachariah Interim Presentation -2 on.
CS 5150 Software Engineering Lecture 7 Requirements 1.
Systems Development Life Cycle
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY © Tomi Männistö, Varvana Myllärniemi, 2008 T Software Architectures.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Presented by –Call of Duty School of Requirement Engineering University of Texas, Dallas Web Meeting Scheduler System System Requirement Specification.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
D R A T D R A T ABSTRACT Every semester each department at Iowa State University has to assign its faculty members and teaching assistants (TAs) to the.
 SAP AG 2007, SAP CSUN 2007 Conference Presentation / 1 Presented by Team “Call of Duty” 29 th April 2010 CS 6361, University of Texas At Dallas.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Requirements Engineering ments_analysis.
Information Systems Dr. Ken Cosh Lecture 9.
SynergySoft™ Distributed Meeting Scheduler Requirements Review Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker.
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
Presented by –Call of Duty School of Requirement Engineering University of Texas, Dallas Web Meeting Scheduler System System Requirement Specification.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Project or Work?. Do you know the difference? List 3 ways you think they are the same? List 3 ways you think they are different?
Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.
Requirements in the product life cycle Chapter 7.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
HighImpactSoft 2010 Organizing a Better Future. Agenda Specify Goals ScopeDefinitions Process Model Preliminary Requirements Issues and solutions TraceabilityPrototype.
Synergy Meeting Scheduler System Abhinav Reddy Tummalapally Lavanya Devara Swetha Vangala Satyanarayana Karthik Upadrasta.
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Synergy Distributed Meeting Scheduling System Francisco Puente Arundhati Solapurkar Jung-Chi Lin.
The Development Process of Web Applications
Web Meeting Scheduler System
Project Management Managing Project Execution
2010 Organizing a Better Future
Synergy Meeting Scheduler System
Enterprise Requirements Literal
Software Life Cycle Models.
Duk-Jin Kim Tu Peng Yan Shi
Presentation transcript:

Synergy Distributed Meeting Scheduler Phase I interim report

The Real World Problem  Tedious process of scheduling a meeting  Low efficiency of communication  Conflicts on time and resources  Lack of virtual meeting support

What SDMS Brings  Save time  Enhance communication  Reduce conflict  Solve conflict automatically or quickly by manual  Support virtual meetings.

Stakeholders  End users  Organizations which will use this system  IT support of the system in organizations  Synergy Inc  System Engineers  Development and testing team  Maintenance team

Functional Requirements  Monitor meetings  Plan meetings  Support conflict resolution  Management between participants  Support user interaction  Concurrency

Non-Functional Requirements  Usability  Flexibility  Accuracy  Convenience  Performance  Security  Privacy

Issue #1  Issue: What will be the environment for the SMDS?  Options: 1.User can freely create accounts 2.Used within an organization 3.Administrator can create accounts  Resolution: –Consider option 2 & 3

Issue # 2  Issue: Impossible to schedule a meeting that satisfies both early and convenient constraint.  Options: 1.Choose the most convenient 2.Choose the earliest date 3.Give the user the option to choose  Resolution: –Consider option 3

Issue # 3  Issue: How to support distributed meeting?  Options: 1.System should provide pre define templates to describe virtual location for typical virtual meeting COTS products. 2.Is up to the user provide the required information 3.Is up to the administrator to provide support.  Resolution: –Consider option 1

Issue # 4  Issue: A conflict occurs if two meetings with a same priority tries to access a same resource.  Options: 1.Quit negotiation after a user-define number of attempts 2.Create a mediator role that will decide which meeting gets the slot  Resolution: –Consider option 2

Issue # 5  Issue: Resource conflicts not defined.  Options: 1.Notions of equipment and locations need to be included in the system and resources should be reserved for the meeting. 2.Let the user manage the allocation of resources by themselves  Resolution: –Consider option 1

Issue # 6  Issue: How to reduce conflicts?  Options: 1.Participants can see availability of the meeting rooms and equipments when they specify prefer time or available time 2.Any participates should be able to see availability of other users.  Resolution: –Consider option 1 & 2

Next Subphase  Finalize the SRS  Refine the requirements  Release the final prototype

Questions?