1. R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10

2. Welcome Our Client Dr. Timoth C. Lederman Professor of Computer Science Siena College 2Code Shark Solutions

3. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 3Code Shark Solutions

4. Introduction Our Team Kurt Greiner Team Leader Daniel Rotondo Webmaster Ryan Godfrey Lead Programmer Rebecca Wilson Information Specialist Akeem Shirley Database Administrator Brittany Lintelman Documentarian 4Code Shark Solutions

5. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 5Code Shark Solutions

6. ROSES Problem Definition Site lacks functionality Inconsistent menu No Search feature Is not aesthetically pleasing 6Code Shark Solutions

7. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 7Code Shark Solutions

8. Functional Requirements General User: View Website Search 8Code Shark Solutions

9. Non-Functional Requirements System must be: Aesthetically pleasing Easily navigable Easily maintainable Easily modifiable Stable 9Code Shark Solutions

10. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 10Code Shark Solutions

11. Usage Case Narratives 11 Tells a story for each of the users describing their interaction with the system Also explains the abilities each user has for interacting with the system Code Shark Solutions

12. System Users Course Instructor General User Students Recommenders Future Employer Family/Friends Alumni 12Code Shark Solutions

13. Course Instructor Site Administrator Can add to and edit all parts of the website Use the website as a reference 13Code Shark Solutions

14. Students Makes use of the website’s calendar and links for both sections of the course. Uses the past teams’ websites and documents as a reference point. 14Code Shark Solutions

15. Recommender Can search for specific Software Engineering students and gain access to their resume, picture, class, and information related to their Software Engineering course. 15Code Shark Solutions

16. Future Employer Navigate website with ease Use the search function to find prospective employees 16Code Shark Solutions

17. Family/Friends Can search for Software Engineering Students to view the talents and accomplishments of their family and friends. 17Code Shark Solutions

18. Alumni Can search for themselves or other students to view past achievements for reminiscent purposes or in the chance of being interviewed by an alumnus this can also serve as a reference. 18Code Shark Solutions

19. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 19Code Shark Solutions

20. UML Use Case Diagram Used to show how users interact with system. Users or ‘Actors’ interact through ‘Uses’ Lines are drawn to demonstrate a relationship 20Code Shark Solutions

21. UML Use Case Legend 21Code Shark Solutions

22. UML Use Case Diagram 22Code Shark Solutions

23. UML Deployment Diagram 23 Show devices and execution environments for a system Shows protocols for interaction with the system Code Shark Solutions

24. UML Deployment Diagram 24Code Shark Solutions

25. Website Map Legend 25Code Shark Solutions

26. Website Map 26Code Shark Solutions

27. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 27Code Shark Solutions

28. Data Flow Diagrams Used to show the movement of data throughout system Acts as visual aid to demonstrate how system works Context Diagram - The highest and most general representation of data flow Level 0 – Shows the major processes of the system Level 1 – Shows in-depth the look at one use Level 2 – Decomposes each process 28Code Shark Solutions

29. Context Diagram 29 Highest, most general level of data flow in our system. Shows interactions between users, databases, and website Code Shark Solutions

30. Level 0 Diagram 30 Shows major processes of the system. Code Shark Solutions

31. Level 1 Diagram 31 Shows data flow of one of the main uses; viewing the website. Code Shark Solutions

32. Level 2 Diagram 32 Decomposes the main process of the system; searching. Code Shark Solutions

33. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 33Code Shark Solutions

34. Data Dictionary Lists all data entities and variable with in a system Used to help understand items in the database 34Code Shark Solutions

35. Data Dictionary Excerpt 35Code Shark Solutions

36. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 36Code Shark Solutions

37. Test Plan Documents the strategy used Ensures that the Functional Requirements are met Includes all of the following: unit testing, integration testing, system testing, and acceptance testing. 37Code Shark Solutions

38. Our Strategy Break the project in to units Ensure the units work properly alone Make sure the units interact correctly Test that the whole system functions as expected Guarantee that all Functional and Non-functional requirements are met 38Code Shark Solutions

39. Unit Test Excerpt 39Code Shark Solutions

40. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 40Code Shark Solutions

41. Prototype Screens Screen shots of our current work in progress Allows client and guests to work more visually Screens are conceptual and subject to change 41Code Shark Solutions

42. Current Menus 42Code Shark Solutions

43. New Main Menu 43Code Shark Solutions

44. New Sub-menu 44Code Shark Solutions

45. Old Calendar 45Code Shark Solutions

46. New Calendar 46Code Shark Solutions

47. New Functionality: Search 47Code Shark Solutions

48. Search Results 48Code Shark Solutions

49. Student Result Page 49Code Shark Solutions

50. Year Results Page 50Code Shark Solutions

51. Mobile Version Smart phones and other mobile devices are becoming increasingly popular. Student will always need to see what’s due in Software Engineering at any given moment. Many websites will not display properly on mobile devices Code Shark Solutions51

52. Mobile Screenshots Code Shark Solutions52

53. Mobile Screenshots cont. Code Shark Solutions53

54. Agenda Introduction Problem Definition Requirements Inventory Usage Case Narratives UML Diagrams & Website Map Data Flow Diagrams Data Dictionary Testing Prototype screens What is next? 54Code Shark Solutions

55. What’s Next? 2010 – DONE! 2011: 55Code Shark Solutions

56. Thank You! Questions? Comments? Have a nice Holiday Season! 56Code Shark Solutions