Project: Rooms And Colloquium System

1
Project Rooms And Colloquium System
ROOMS Team CS706, Analysis of Software
Artifacts Fall 2001
2
Current Rooms System
3
Problem Statement

• Replace current room reservation system
• additional functionality
• better documentation
• better extensibility
• better integration with colloq

4
Process
Requirements
Use Cases
System Design
Program Design
Implementation
Testing
5
Requirements
Requirements
6
Requirements
Requirements
Will Benton
7
Requirements
Requirements
Gerry Tutsch
Will Benton
8
Requirements
Requirements
Will Benton
Gerry Tutsch
Dave Parter
9
Requirements
Faculty
Requirements
Gerry Tutsch
Dave Parter
Will Benton
10
Requirements
Faculty
Current Users
Requirements
Gerry Tutsch
Dave Parter
Will Benton
11
Requirements
Marv Solomon
Faculty
Current Users
Requirements
Gerry Tutsch
Dave Parter
Will Benton
12
Use Cases
13
Use Case, for a User
14
High Level Design
15
High Level Design
User
16
High Level Design
Client
User
17
High Level Design
Client
Server
User
18
High Level Design
Client
Server
Persistence
User
19
High Level Design
Client
Server
Persistence
User
20
Software Targets

• Tomcat
• Servlet API
• Java
• JSSE
• JavaMail
• JAF
• PostgreSQL

21
Refining Design
Browser
Servlet
PostgreSQL
User
22
Refining Design
Browser
Servlet
PostgreSQL
User
JDBC
HTTP or HTTPS
23
Components
24
Focusing
Browser
Servlet
PostgreSQL
User
JDBC
HTTP or HTTPS
25
Refining
Servlet
request
Handler
Rooms Servlet
JDBC
HTTP
response
26
Refining
request
Rooms Servlet
Handler
JDBC
HTTP
response
Web Page
HTML Form
27
Sequence
28
Refining
Handler Factory
request
Handler
Rooms Servlet
JDBC
HTTP
response
Web Page
HTML Form
29
Refining
Handler Factory
ltltcreategtgt
request
Handler
Rooms Servlet
JDBC
HTTP
response
Web Page
HTML Form
30
Refining
Handler Factory
ltltcreategtgt
request
Handler
Rooms Servlet
JDBC
HTTP
response
Web Page
HTML Form
31
Refining
ltltabstractgtgt HTMLForm
ltltcreategtgt
request
Rooms Servlet
ltltconcretegtgt Handler
JDBC
HTTP
response
ltltconcretegtgt WebPage
ltltconcretegtgt HTMLForm
32
From Design to Implementation
33
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)

34
Program Design

• EventHandler (make SQL, deliver SQL result)
• 1. Reserve Handler
• 2. Room Handler
• 3. User Handler
• 4. Colloquium Handler

35
Program Design

• Class interaction

SQL
request
Interface (HTML)
Servlet
Event Handler
Database
36
(No Transcript)
37
Sequence Diagram

• Actor Visitor / Account User / Administrator
• Objects
• HTML
• Servlet
• EventHandler
• Database
• Example (add a room available for reservation)

38
Sequence Diagram
39
Expansion of Design

• One specific Handler for one specific Event!
• Example
• RoomHandler broken into
• viewRoomHandler,
• addRoomHandler,
• deleteRoomHandler,

40
Why so many handlers?

• Better to implement Each handler processes
  specific request, generate specific response
  web-page.
• Better to distribute implementation tasks.
• Redundancy?
• Just repeat of some headers, the functional
  part is different for different handlers (no
  repeat).

41
(No Transcript)
42
Difference from Design remove old reservation
records
43
(No Transcript)
44
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 implementation!

45
Walkthrough

• Make Reservation

46
We need this thing to make a reservation.
Talking with Customer
47
Make Reservation in Requirements Doc
48
Make Reservation in Use Case Document
49
Make Reservation in Use Case Diagram
50
Make Reservation in Logical Class Diagram
51
Make Reservation in DB Schema
52
Make Reservation Sequence Diagram
53
Make Reservation Class API
54
Make Reservation in Help Manual
55
Test Plan
56
Test Plan
Unit Testing
57
Unit Testing

• The system component functions properly.
• The components design requirement is satisfied.
• Unit testing is implemented by code writers.

58
Test Plan
Unit Testing
59
Code Review

• Code Walkthrough
• Review the code and accompanying documentation
• Code Inspection
• Review codes correctness, efficiency,
  performance
• Code Walkthrough is implemented in the Room
  Reservation System

60
Test Plan
Unit Testing
Integration Testing
61
Integration Testing

• Verify the system components work together
  properly

Tester
Use Case Code Writer
Integration Leader
62
Test Plan
Unit Testing
Integration Testing
System Testing
63
Test Plan
Unit Testing
Integration Testing
Function Testing
Performance Testing
Interface Testing
Acceptance Testing
System Testing
64
System Testing

• Function testing
• the system performs its functions as specified in
  the requirement
• Performance testing
• security, accuracy, speed and reliability
• Acceptance testing
• the system requested by customers is the system
  that was built

65
Integration and System Testing Make A
Non-Recurring Reservation

• 1. Requirement
• A User can reserve a given room for a specified
  time range.
• Each reservation must be associated with a
  contact person.
• Each reservation has a purpose (a brief piece of
  text).
• User Account User

66
Integration and System Testing Make A
Non-Recurring Reservation
2. Sequence diagram and use case
67
Room Reservation System Testing Report Form
68
The Product
69
Client (basic)
70
Client (graphical)
71
Summary, Stories and Demo
72
People

• Class Professor
• Somesh Jha (jha_at_cs.wisc.edu)
• Group Mentors
• Will Benton (willb_at_cs.wisc.edu),
• Jerry Tutsch (tutsch_at_execpc.com)
• Group Members
• Brian Bowers (blbowers_at_cs.wisc.edu),
• Andrew Palmer (palmeran_at_biostat.wisc.edu),
• Hongwei Zhu (hzhu_at_cs.wisc.edu),
• Ming Li (mingl_at_cs.wisc.edu),
• Minyi Xu (minyi_at_cs.wisc.edu),
• Naijun Zhou (naijun_at_cs.wisc.edu),
• Keith Noto (noto_at_cs.wisc.edu)

73
Thank you!

• The Rooms Team would like to thank
• Somesh Jha
• Will Benton
• Jerry Tutsch
• Marvin Solomon
• David Parter
• Everyone who gave input!