1. 11/4/2009 Requirements Specification

2. Our Client… Dr. Timoth C. Lederman Professor of Computer Science Siena College And To All Other Guests 11/4/2009 Requirements Specification

3.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

4. Alexander Evanciew Robert DeSarbo Timothy Egan Alexander Johnson Kelly Monroe David Nopper Team Leader Webmaster Systems Administrator Information Specialist Database Administrator 11/4/2009 Requirements Specification

5.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

6. 11/4/2009 Requirements Specification

7.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

8.  Must improve current MapBuilder mashup of the OldGMCtrucks.com website users  Allow OldGMCtrucks.com website users ability to locate other members via map  Improve functionality: increased user capabilities and interface ease of use 11/4/2009 Requirements Specification

9.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

10.  A general graphical overview  Purpose: To depict the broad functionality, users, and dependencies of a system 11/4/2009 Requirements Specification

11. 11/4/2009 UML Diagram Requirements Specification

12.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

13.  Member  Administrator  Super Administrator 11/4/2009 Requirements Specification

14.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

15. 11/4/2009 Requirements Specification  A pictorial representation  There are for main elements

16. 11/4/2009 Requirements Specification

17. 11/4/2009 Requirements Specification

18. 11/4/2009 Requirements Specification

19. 11/4/2009 Requirements Specification

20.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

21.  A complete, detailed list of all system functions  Separated into general user interface and four user types 11/4/2009 Requirements Specification

22.  Requirement that do not apply to a specific user 11/4/2009 Requirements Specification

23.  Login / Logout  View and interact with map  View/add/edit/delete personal information › Required Fields › Optional Fields › Email is a special case › Difference between Member and Admins 11/4/2009 Requirements Specification

24.  View/add/edit/delete pins on map  View/add/edit/delete events on map › Required Fields › Optional Fields › Difference between Member and Admins  Register or cancel registration for an event 11/4/2009 Requirements Specification

25.  Generate search reports and search for directions  Create and delete accounts  Request forgotten password  Change password  Request email change  Delete account 11/4/2009 Requirements Specification

26.  Introduction  Our Model  Problem Overview  UML Use Case Diagram  User Case Narratives  Data Flow Diagrams  Functional Requirements Inventory  Timeline 11/4/2009 Requirements Specification

27. 11/4/2009 Requirements Specification

28.  …What’s next? 11/4/2009 Requirements Specification

29.  The Preliminary Design 11/4/2009 Requirements Specification

30.  …for your time and patience  Questions? 11/4/2009 Requirements Specification