1. Welcome Dr. Eric Breimer Associate Professor of Computer Science Siena College 515 Loudon Road Loudonville, NY 12211 112/9/2009Digital Evolutions | Preliminary Design | SaintBook

2. 2 Preliminary Design by December 9, 2009 12/9/2009Digital Evolutions | Preliminary Design | SaintBook

3. 3 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

4. 4 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

5. 5 Janelle Rizzo: j e08rizz@siebna.edu Team Leader Alan DiStasio: ac28dist@siena.edu Webmaster Dan Quickenton: dj28quic@siena.edu Systems Analyst Chris Badalucco: c10bada@siena.edu Lead Systems Administrator Erik Mulvaney: ec24mulv@siena.edu Project Engineer Mike Stellato: mp03stel@siena.edu Information Specialist 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Team Members Digital Evolutions

6. 6 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

7. 7 12/9/2009 Development and Testing Digital Evolutions | Preliminary Design | SaintBook Waterfall Model

8. 8 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

9. 9 12/9/2009 Problem Overview Digital Evolutions | Preliminary Design | SaintBook  Connect members of Siena community  Group oriented  Promote 6 R’s  User and Group Pages

10. 10 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

11. 12/9/200911Digital Evolutions | Preliminary Design | SaintBook Tells a story about the user  The General User  Administrator  Alumni  Guest  Super Administrator

12. 12 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

13. 12/9/200913Digital Evolutions | Preliminary Design | SaintBook  What the system will be able to do  Specific behaviors/functions  Testable features of the system  Requirements organized by user

14. 12/9/200914 The General User Digital Evolutions | Preliminary Design | SaintBook  Manage User Home/Profile tabs  Friends  Create/Join Groups  Posting  Message Center  Browse

15. 12/9/200915 Administrator Digital Evolutions | Preliminary Design | SaintBook Additional abilities:  Disable Users, Groups, or Content  Reinstate any disabled information  Label Groups

16. 12/9/200916 Alumni Digital Evolutions | Preliminary Design | SaintBook Restrictions:  Group Creation  Group Management Guests Limited Abilities:  View Public User Page information  View Public Group Page information

17. 12/9/200917 Super Administrator Digital Evolutions | Preliminary Design | SaintBook Not an actual user  User account  Accessed by more than one user  Grant Admin access  Remove Admin access

18. 18 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

19. 12/9/200919Digital Evolutions | Preliminary Design | SaintBook Legend:

20. 12/9/200920Digital Evolutions | Preliminary Design | SaintBook Shows the breakdown of a system Hierarchical arrangement Boxes represent each module or process Arrows represent the join for each relationship

21. 12/9/200921Digital Evolutions | Preliminary Design | SaintBook

22. 12/9/200922Digital Evolutions | Preliminary Design | SaintBook

23. 12/9/200923Digital Evolutions | Preliminary Design | SaintBook

24. 12/9/200924Digital Evolutions | Preliminary Design | SaintBook

25. 12/9/200925Digital Evolutions | Preliminary Design | SaintBook

26. 12/9/200926Digital Evolutions | Preliminary Design | SaintBook

27. 12/9/200927Digital Evolutions | Preliminary Design | SaintBook

28. 12/9/200928Digital Evolutions | Preliminary Design | SaintBook

29. 12/9/200929Digital Evolutions | Preliminary Design | SaintBook

30. 12/9/200930Digital Evolutions | Preliminary Design | SaintBook

31. 31 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

32. 12/9/200932Digital Evolutions | Preliminary Design | SaintBook KEY: Unique (U) – This piece of data cannot be duplicated anywhere, each must be individually unique. For example each email for each user must be unique. Non Null (NN) – This piece of data must have a value, it cannot be empty. Name – The name of the piece of data. Type – The value type for each piece of data. A number given in parentheses after the type is the maximum length the value can be. Restrictions – Any limitations or specifications for that piece of data. Description – Describes a little about what the piece of data is. Section it appears in – A list of all the sections of screens the piece of data appears on. Example – Provides an example of what the piece of data should be.  List of all data entities dealing with the system  Any data inputted, manipulated, or stored

33. 12/9/200933Digital Evolutions | Preliminary Design | SaintBook NameTypeRestrictionsDescriptionSection it Appears InExample AnswerTextnone An answer to a question the user creates for their profile3,7,9,10,11,12My favorite color is red. Captionvarchar(32)NNCaption for an image3,7,9,10,11,12Me in Hawaii! First Namevarchar(32)AlphabetUsers First Name2,3,6,8,9,10,11,12Alan FriendBooleanTrue/False, NN Indicates if two users are friends9,10,12TRUE FriendRequestRecievervarchar(32)AlphaNumeric, NN The user who received the friend request9,12je08rizz@siena.edu FriendRequestSendervarchar(32)AlphaNumeric, NN The user who sent the friend request9,12ac28dist@siena.edu GradStatusvarchar(32)AlphabetThe status level of the user7,9,10,12Senior GradYearint(4)integer, NNYear the User Graduated82010 Group DescriptionTextNN A brief description about the group9,10 The CS club is the best club. We were founded in….. GroupAffiliationTextnone, NN Indicates how the user is affiliated with a group7,10,12 Alan is the communication officer of the CS club. GroupEnableBooleanTrue/False, NN Whether or not the group is enabled to be seen by users at the descrestion of administrators3FALSE GroupFanRecieverintinteger The group id of the group who received the fan request9,1214 GroupFanRequestintinteger The group id of the group who sent the fan request9,1223 GroupIdintinteger, U, NNId number of a group3,5,6,7,9,10,11,1212

34. 34 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

35. 3512/9/2009Digital Evolutions | Preliminary Design | SaintBook  Determined by functional requirements  Start with unit tests  Integration test  Full system test  Results presented in Acceptance Test Document

36. 3612/9/2009Digital Evolutions | Preliminary Design | SaintBook Pass/Fail Status Test NumberDescription Action to perform test (input) State Before TestExpected resultObserved result F1.001Username text box is blankNoneBlank text box Sign In button is disabled F1.002Password text box is blankNoneBlank text box Sign In button is disabled F1.003 Invalid character(s) inputed into any text box * … ".. ' / ?Blank text box Invalid character(s) message displayed and Sign In button is disabled F1.004Enabled Sign In button User inputs both a username and a password Disabled Sign In button Sign In button is enabled F1.005Wrong username User inputs a username that is not in the database and clicks the enabled Sign In button Blank text box Wrong username message displayed to user F1.006Wrong password User inputs a password that does not match the password in the database for the username they inputed and clicks the enabled Sign In button Blank text box Wrong password message displayed to user F1.007General User, Admin, Alumni Login User inputs a username that belongs to either a General User, Admin, or Alumni, inputs the correct password, and clicks the enabled Sign In button Blank text boxes General User, Admin, or Alumni brought to their User Home tab F1.008Guest Login User inputs a username that belongs to a Guest, inputs the correct password, and clicks the enabled Sign In button Blank text boxes Guest brought to the Browse page F1.009Super Admin Login User inputs a username that belongs to the Super Admin, inputs the correct password, and clicks the enabled Sign In button Blank text boxes Super Admin brought to the Generic Super Admin Home page

37. 37 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

38. 3812/9/2009Digital Evolutions | Preliminary Design | SaintBook

39. 3912/9/2009Digital Evolutions | Preliminary Design | SaintBook

40. 4012/9/2009Digital Evolutions | Preliminary Design | SaintBook

41. 4112/9/2009Digital Evolutions | Preliminary Design | SaintBook

42. 4212/9/2009Digital Evolutions | Preliminary Design | SaintBook

43. 4312/9/2009Digital Evolutions | Preliminary Design | SaintBook

44. 4412/9/2009Digital Evolutions | Preliminary Design | SaintBook

45. 4512/9/2009Digital Evolutions | Preliminary Design | SaintBook

46. 4612/9/2009Digital Evolutions | Preliminary Design | SaintBook

47. 4712/9/2009Digital Evolutions | Preliminary Design | SaintBook

48. 4812/9/2009Digital Evolutions | Preliminary Design | SaintBook

49. 4912/9/2009Digital Evolutions | Preliminary Design | SaintBook

50. 5012/9/2009Digital Evolutions | Preliminary Design | SaintBook

51. 5112/9/2009Digital Evolutions | Preliminary Design | SaintBook

52. 5212/9/2009Digital Evolutions | Preliminary Design | SaintBook

53. 5312/9/2009Digital Evolutions | Preliminary Design | SaintBook

54. 5412/9/2009Digital Evolutions | Preliminary Design | SaintBook

55. 5512/9/2009Digital Evolutions | Preliminary Design | SaintBook

56. 5612/9/2009Digital Evolutions | Preliminary Design | SaintBook

57. 5712/9/2009Digital Evolutions | Preliminary Design | SaintBook

58. 58 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

59. 59 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Timeline - Gantt Chart

60. 60 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Timeline - Gantt Chart (Cont.)

61. 61 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Agenda

62. 62 Detailed Design Acceptance Test Document and Presentation: February 2010 Document and Presentation: April 2010 12/9/2009Digital Evolutions | Preliminary Design | SaintBook What’s Next

63. 63 Questions? 12/9/2009Digital Evolutions | Preliminary Design | SaintBook Thank You