No Zama Group Phase Three Completion Report Members
No. Zama Group Phase Three Completion Report
Members’ Roles Lance: General Document, Writer, Web-Site Developer, Presentation / Document Writer, Presentation Speaker Toshi: Data Base Developer, General Document Writer, GUI Developer, Final Presentation / Document Writer, Schedule-Keeper Bryan: JSP Programmer, General Document Writer, Proem Developer, Minutes-Taker Jeff: Extractor Programmer, Proem Developer, GUI Developer, JSP Programmer, Committee Representative
Tools We Used Ø Ø Ø Ø Ø JBuilder 5 Forte 4 j Text Pad Dream. Weaver Flash Tomcat Web Server Visio Class 2000 UML Modeler Java Server Pages SQL Editor
Trip Down Memory Lane Quick review of how we got here: First Stop: Review Iterative Design Process Second Stop: Review of Use Cases Third Stop: Review System Design Changes Fourth Stop: Review of Diagrams
First Stop: Iterative Development Process
Second Stop: Use Cases
Use Case 1: Search Books Name: Search Books Performing Actor: Customer (human), other infomediators, Amazon. com Entry Condition: Customer wants to buy book. Customer knows specific information about how to search for book. Customer has PC connected to Internet Exit Condition: listing of prices of book
Use Case 1: Search Books Event Flow: Customer selects search category Customer enters search criteria Customer submits search criteria by pressing button System determines price comparisons by utilizing infomediators Price comparison chart is displayed for the Customer (exit condition reached)
Use Case 2: Customer Profile Name: Customer Profile Participating Actor: Customer Entry Condition: Customer has initialized profile request Exit Condition: Web confirmation displayed in browser window.
Use Case 2: Customer Profile Event Flow: System prompts customer for information Customer inputs information Customer clicks Submit button to send request for new profile for processing System checks to see if user already has a profile If no previous profile exist new profile is created and the appropriate message of such is sent to user via HTML
Third Stop: System Design Refinement Changes for each iteration
No. Zama System Model
Fourth Stop: Diagrams
Class Diagram: Search Books
Sequence Diagram: Search Books – iterations 1 ->2 ->3
Use Case 2: Customer Profile *
Sequence Diagram: Customer Profile (Log In) – iteration 2 (old)
Sequence: New Customer Registration
Customer Registering Personal Info:
Success!
Sequence: Customer Login
Logging in…
Welcome Duck!
Administrator Deleting Profile
Administrator login
Admin deleting user ‘Duck’
‘Duck’ Deleted
Customer Logout Sequence
Customer Logged Out
Sequence: Check Purchase Record
Customer Checking Purchase Records
Sequence: Customer Editing
Customer Editing Profile
Customer Profile Edited!
Whatever Happened to Book Recommendation? Diagrams of things yet to be…
Class Diagram: Book Recommendation
Sequence Diagram: Book Recommendation
Proem Integration Peerlets, Peerlets everywhere…
Questions… ?
BEERS ALL AROUND !!!
- Slides: 40