1. Seraphim

2.  Our Clients: ◦ Ms. J’aimé Pfeiffer (Capital Region BOCES) ◦ Ms. Jen Cannell (Questar III)  Guests ◦ Dr. Meg Fryling ◦ Dr. Darren Lim

3.  Lauren Mathews: Team Leader  Daniel Street: Web Master  Nicholas Roth: Database Manager  Kevin Mango: Development Director  Tyler Carpenter-Rivers: Document Analyst

4. Seraphim’s clients, Ms. Jen Cannell and Ms. Jaimé Pfeiffer, are in need of a single sign-on system for students to access and download e-books from their district’s libraries.

6.  Student  Teacher  Administrator

7.  Login (Username, Password, District)  Access to e-books in district & level  Viewing: Genres, Subjects, Levels  Searching  My Account  Inactivity Log-Out

8.  All E-Book Access  Teaching Books  Edit Students

9.  My Account: ◦ User Types (Edit/Add/Remove) ◦ Vendors (Update/Add/Remove) ◦ Books (Update/Edit)

10. ActorSystem BoundaryParticipation Line UseExtends Relationship Includes Relationship

16. LinkPage Redirect

19. Initial NodeFinal NodeDecision Node Activity ObjectData Object Split/Join Flow

28. ProcessEntity Data Flow Data Store

35.  All users can log-in  All users can search e-books  All users can withdraw e-books  Teachers can edit student information  Teachers can access teacher’s editions  Administrators can edit vendor information  Administrators can edit all user types  Administrators can edit e-books information

36.  Responsive  Scalable  Secure  Viewable  Intuitive  Maintenance

41. http://oraserv.cs.siena.edu/~perm_seraphim/prototypes/

44.  Prototype – Database, Main Screen  Detailed Design Kill the Dragon!!!

46. System Definition Project Plan Problem Overview System Life Cycle Use Case Narratives Deployment Diagram Website Map Activity Diagram Data Flow Diagrams Requirements Inventory Data Dictionary Testing Plan What’s Next