ProjectReport-Pages.ppt

Project: Rooms And Colloquium System Current Rooms System Problem Statement Replace current room reservation system additional functionality better documentation better extensibility better integration with colloq Process Requirements Requirements Requirements Requirements Requirements Requirements Requirements Use Cases Use Case, for a User High Level Design High Level Design High Level Design High Level Design High Level Design High Level Design Software Targets Tomcat Servlet API Java JSSE JavaMail JAF PostgreSQL Refining Design Refining Design Components Focusing Refining Refining Sequence Refining Refining Refining Refining From Design to Implementation Program Design Event ? EventHandler ? Database Event: 1. Related to Reservation (view, make, cancel, delete…) 2. Related to Room (view, add, delete,edit…) 3. Related to User(add, delete, change privilege…) 4. Related to Colloquium(add, delete, edit…) Program Design EventHandler (make SQL, deliver SQL result): 1. Reserve Handler 2. Room Handler 3. User Handler 4. Colloquium Handler Program Design Class interaction Sequence Diagram Actor: Visitor / Account User / Administrator Objects: HTML Servlet EventHandler Database Example: (add a room available for reservation): Sequence Diagram Expansion of Design One specific Handler for one specific Event! Example: RoomHandler broken into: viewRoomHandler, addRoomHandler, deleteRoomHandler, … Why so many handlers? Better to implement: Each handler processes specific request, generate specific response web. Better to distribute implementation tasks. Redundancy? — Just repeat of some headers, the functional part is different for different handlers (no repeat). Difference from Design— remove old reservation records Implementation Observations Diagrams in design phase can not predict the exact number of classes, objects used in implementation. BUT really make clear the logics of the project (logic components, interactions). Really helps in impl