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

Process Specification – Phase II

Process Specification – Phase II Continued

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

Functional Requirements Spec

Non-functional Requirements Specs – Performance

Non-functional Requirements Specs – Reliability

Non-functional Requirements Specs – Security

Data Model Diagram

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

Prototype – Login

Prototype – Initiate Meeting

Prototype – Calendar

Prototype – Respond to invite

Prototype – Monitor Meeting

Questions?