elaboration l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Elaboration PowerPoint Presentation
Download Presentation
Elaboration

Loading in 2 Seconds...

play fullscreen
1 / 22

Elaboration - PowerPoint PPT Presentation


  • 433 Views
  • Uploaded on

Elaboration. Lecture OO09 Gymnastics System Example Cont’d. References. The Booch Method Guide, for Rose 2.0. Teaching Points. Validation Architectural Design Planning. Review. What are the products of architectural design? How would you validate you domain analysis?. Validation.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Elaboration' - daniel_millan


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
elaboration

Elaboration

Lecture OO09

Gymnastics System Example Cont’d

references
References
  • The Booch Method Guide, for Rose 2.0
teaching points
Teaching Points
  • Validation
  • Architectural Design
  • Planning
review
Review
  • What are the products of architectural design?
  • How would you validate you domain analysis?
validation
Validation
  • Are we building the right product?
  • Use the requirement
gymnastics system example
Gymnastics System Example
  • The “scoring” use case
when to stop domain analysis
When to Stop Domain Analysis
  • You have identified all domain entities that play a role and defined their classes
  • You have specified the relationships between each of these classes
when to stop domain analysis9
When to Stop Domain Analysis
  • You have associated with each class all operations performed on it (from uses cases)
  • You have analyzed each operation to the point where you understand what it needs to do and what other classes are involved
layered architecture
Packages are organized in a hierarchy of layers where each layer has a well-defined interface

e.g. The OSI model for network services is a layered architecture

Classic three-tier architecture

Presentation (windows, reports, etc.)

Application Logic (tasks and rules that govern the process)

Storage (persistent storage mechanism)

Layered Architecture
three tier architecture cont d
Identified by the separation of the application logic into a distinct middle layer

Presentation layer is free of application logic and just forwards requests to middle tier

Middle tier communicates with a back end storage layer

Three-tier Architecture (cont’d)
three tier architecture cont d13
Advantages

the opportunity for reuse

the possibility of distributing application logic on a network

allocation of developers to construct specific tier (based on interface specs, that is good OO decomposition)

Three-tier Architecture (cont’d)
multi tiered architectures
The logical extension of three-tier architecture

You can decompose a three-tier into multiple services

Multi-tiered Architectures
the gymnastics system17
What if we change user interfaces?

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

The Gymnastics System
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

Planning
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

Executable Release Plan
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

Other planning data
slide21

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.

teaching points22
Teaching Points
  • Validation
  • Architectural Design
  • Planning