1 / 6

SynergySoft ™ Distributed Meeting Scheduler

SynergySoft ™ Distributed Meeting Scheduler. Interim Progress Report Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker. 3 Areas of Effort. Redux Extensions and improvements to our initial deliverable Advance Preparation Startup activities and background gathering

barth
Download Presentation

SynergySoft ™ Distributed Meeting Scheduler

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SynergySoft™ Distributed Meeting Scheduler Interim Progress Report Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker

  2. 3 Areas of Effort • Redux • Extensions and improvements to our initial deliverable • Advance Preparation • Startup activities and background gathering • Phase II Requirements • New/changed requirements

  3. Redux • Add enhancements to use case diagram to handle exceptions, • Update operational senario to include exceptional situations, • Improve activity diagrams including SADT concepts, and • Rework dependency diagrams with FRs as ovals and NFRs as clouds.

  4. Advanced Preparation • Focus has been on implementation • Investigate use of .jsp scripts for implementation, • Locate code sources & code examples, especially calendar week layout, • Investigate algorithms for scheduling and conflict resolution, and • Continue with competitive market analysis to see other functions and implementations.

  5. Phase II Requirements • Continue use of IEEE document format, • Extend our current process specification, • Add UML and SoftGoal interdependency graphs (RML/Telos concepts), • Continue to track issues and resolutions, and • Implement functional prototype.

  6. Questions?

More Related