SDMS Meeting Scheduler

1. SDMS Meeting Scheduler Getting People Together

2. Getting People Together • Project Goals • Provide Requirements for Meeting Scheduler • Define and clarify customer goals • Provide a prototype for customer feedback • Help define and solidify requirements

3. Group Breakdown

4. Requirements Sources • Initial requirements • Client and Customer Interviews • Existing Systems • Meeting Wizard • http://www.meetwizard.com • Meeting Scheduler • http://www.math.unipd.it/~fross/soft-sched.html • Microsoft Outlook

5. Project Process • Identify roles and stake holders • Assign and carry out activities

6. Project Process • Create activity diagram • Identify Stake holders • Model System • Enterprise FR • System FR • Finalize Model • Functional • Non Functional • Develop prototype • Document issues • Finalize the requirements

7. Enterprise Requirements • Domain level questions • Who are the stakeholders? • Who has meetings? • What is the setting/environment for meetings? • In what manner do meetings take place? • How do people set up meetings? • What are the problems/issues with setting up meetings? • Domain Modeling using UML • Used Activity Diagram to model domain • Used Sequence Diagram to help refine the process

8. Enterprise Requirements • Domain Modeling

9. Functional Requirements • Describe the goals of the system • The functions that need to executed • The outputs from the functions • Modeling the Functional Requirements • Use Case Diagrams to identify primary goals • Acti-grams to formally define • Inputs, output , controls and mechanisms • Sequence and Activity Diagrams to define process

10. Functional Requirements • Use Case Diagram

11. Functional Requirements • Sequence Diagram

12. Functional Requirements • Activity Diagram

13. Problems Using UML • Cannot Describe Input, Output, Control and Mechanism. • No Formal Definition Solution: Expanding UML Using some notation in IDEF

14. Functional Requirements • Acti-Gram Describing the whole system

15. Functional Requirements • UML+ Defining activities in SDMS

16. Functional Requirements • UML+ Defining activities in SDMS

17. Functional Requirements • Formal Definition Logon Input: Username, Password. Output: Username, Password. Control: null. Mechanism: Initiator. Verify Logon Input: Username, Password. Output: A boolean variant notifying whether user logged on successfully or not. Control: User Profile DB. Mechanism: Computer. Check Pref/Excl Set Input: Potential Participant List. Output: Date Range. Control: Participant’s Preference and Exclusion Set. Mechanism: Initiator. Send Request Input: Potential Participant List (including Important Participant List, Active Participant List and General Participant List) and Date Range. Output: Potential Participant List and Date Range. Control: User Profile DB. Mechanism: Initiator. Broadcast Request Input: Potential Participant List and Date Range. Output: Date Range. Control: null. Mechanism: Important Participants, Active Participant. ……

18. Non-Functional Requirements • Define the Constraints of the System in terms of: • Reliability • Availability • Performance • Security • Dependency Graph to describe relationships to Scheduler the concepts

19. Non-Functional Requirements • Dependencies

20. Prototype • Phase II Functionality • Login / Logout • Define User Profile • Schedule Meeting • Phase III Functionality (future) • Meeting Approval • View Schedule • Accept / Reject / Cancel

21. Prototype – Screen Shots

22. Prototype – Screen Shots

23. Prototype – Screen Shots

24. Conclusion • Provided a process to define the requirements of the system • The process is a feedback loop to help refine the goals • Provide a prototype to help clarify goals • The prototype help clarify goals by provide a visual hands-on experience • Customers provide feedback based on tacit knowledge

25. Questions • Questions ?