1. Synergy Meeting Scheduler System
Sama Malik
Scott Denson
Thriveni Movva
TJ Andrews

2. Process Specification – Phase II

3. Process Specification – Phase II Continued

4. Our roles Role Team Member Responsibilities Team Lead TJ Andrews
Map out the process, determine deadlines, coordinate meetings, and compile documentation
Requirements Engineers
Sama Malik, Thriveni Movva
Refined the system functional and system non-functional requirements from the Phase I understanding and modified specifications, elaborate and expand on them to allow improved understanding
Designer
Scott Denson
Refined prototype to develop a more functional product

5. Functional Requirements Spec

6. Non-functional Requirements Specs – Performance

7. Non-functional Requirements Specs – Reliability

8. Non-functional Requirements Specs – Security

9. Data Model Diagram

10. Issues & Resolution Issue 1: What is Security? Ambiguous verbiage
Res 1: Login and administrative tools. No encryption because only meeting scheduler, and no fingerprinting because requires additional hardware
Issue 2: What functionality should we develop?
Res 2: Limited time, so through our context analysis, we decided to limit functionality to extending previous project and develop “Meeting invite”, “Respond to invite”, “Modify database”, “Monitor meeting”, and “Login”
Issue 3: Why are Synergy Soft requirement engineers expected to develop class diagrams and fully functional prototype
Res 3: Because we’re forced to

11. Prototype – Login

12. Prototype – Initiate Meeting

13. Prototype – Calendar

14. Prototype – Respond to invite

15. Prototype – Monitor Meeting

16. Questions?