Elaboration

1
Elaboration

• Lecture Oo19
• Gymnastics System Example Contd

2
References

• The Booch Method Guide, for Rose 2.0
• Fowler Scott, UML Distilled Applying the
  Standard Object Modeling Language, AWL, 1997,
  Chapt 2
• Larman, C., Applying UML and Patterns An
  Introduction to Object Oriented Analysis and
  Design, PH, 1998

3
Teaching Points

• Architectural Design
• Planning

4
Review

• What are the products of architectural design?
• What is a three-tier architecture?

5
Multi-tiered Architectures

• The logical extension of three-tier architecture
• You can decompose a three-tier into multiple
  services

6
Multi-tiered Architectures
7
The Façade Pattern

• Context/Problem
• A common, unified interface to a disparate set of
  interfaces - such as a package is required
• Solution
• Define a single class that unifies the interface
  and give it responsibility for collaborating with
  the package

8
Compiler Example
9
Façade General Structure
10
The Gymnastics System
11
The Gymnastics System

• What if we change user interfaces?
• What if we change DBMS? (how can we make the
  architecture less vulnerable to change)

12
Planning

• The essence of a plan is to set up a series of
  iterations (executable releases) for construction
  and to assign use cases to iterations
• A plan allocates each use case to an iteration
  (executable release) and identifies a start date
  for each iteration

13
Executable Release Plan

• Allocate Use Cases
• By level of user priority
• By architectural Risk
• address risk early
• By level of effort
• uses cases with schedule risk early
• roughly equal releases
• you may split large use cases

14
Other planning data

• Classes to be implemented
• Inputs
• you may have to provide drivers
• Output
• you may have to provide stubs
• ASIDE A good rule of thumb is that you will
  produce as much test harness as production code

15
Executable release Scoring Report Goal
Verification and successful use of navigational
paths and score derivation logic for the scores
of a competition. Start Date 26 Aug 98 Effort
12 developer-weeks Classes to be implemented
Competition, Event, Trial, RawScore, Team Use
Cases to be Implemented Scoring Inputs Dummy
database (validated in advance) with a meet, a
competition, all events for that competition, all
competing teams and gymnasts for the competition,
and all trials and raw scores. Outputs The data
needed to build the report on Figure 4-3, Output
of the Gymnastics System, on page 25 of
requirement spec. A DB utility dump of the raw
input for comparison.
16
Teaching Points

• Architectural Design
• Planning