Uploaded on:
Category: Animals / Pets
The Gymnastics System. The Gymnastics System. Imagine a scenario in which we change client .... on Figure 4-3,
Slide 1

´╗┐Elaboration Lecture OO09 Gymnastics System Example Cont\'d

Slide 2

References The Booch Method Guide, for Rose 2.0

Slide 3

Teaching Points Validation Architectural Design Planning

Slide 4

Review What are the results of compositional outline? How might you approve you space examination?

Slide 5

Validation Are we fabricating the right item? Utilize the necessity

Slide 6

Gymnastics System Example The "scoring" use case

Slide 8

When to Stop Domain Analysis You have distinguished all space elements that assume a part and characterized their classes You have determined the connections between each of these classes

Slide 9

When to Stop Domain Analysis You have connected with every class all operations performed on it (from utilizations cases) You have broke down every operation to the point where you comprehend what it needs to do and what different classes are included

Slide 10

Packages are composed in a chain of importance of layers where every layer has an all around characterized interface e.g. The OSI model for system administrations is a layered engineering Classic three-level design Presentation (windows, reports, and so forth.) Application Logic (undertakings and principles that oversee the procedure) Storage (persevering capacity instrument) Layered Architecture

Slide 11

Three-level Architecture

Slide 12

Identified by the partition of the application rationale into an unmistakable center layer Presentation layer is free of utilization rationale and just advances solicitations to center level Middle level speaks with a back end stockpiling layer Three-level Architecture (cont\'d)

Slide 13

Advantages the open door for reuse the likelihood of appropriating application rationale on a system assignment of engineers to build particular level (in light of interface specs, that is great OO deterioration) Three-level Architecture (cont\'d)

Slide 14

The intelligent expansion of three-level design You can break down a three-level into different administrations Multi-layered Architectures

Slide 15

Multi-layered Architectures

Slide 16

The Gymnastics System

Slide 17

What on the off chance that we change UIs? Imagine a scenario in which we change DBMS. (by what method would we be able to make the design less helpless against change) The Gymnastics System

Slide 18

The substance of an arrangement is to set up a progression of emphasess (executable discharges) for development and to appoint use cases to cycles An arrangement apportions every utilization case to an emphasis (executable discharge) and distinguishes a begin date for every cycle Planning

Slide 19

Allocate Use Cases: By level of client need By compositional Risk address chance right on time By level of exertion uses cases with calendar chance early generally meet discharges you may part huge use cases Executable Release Plan

Slide 20

Classes to be actualized Inputs you may need to give drivers Output you may need to give stubs ASIDE: A great dependable guideline is that you will deliver as much test outfit as creation code Other arranging information

Slide 21

Executable discharge : Scoring Report Goal : Verification and fruitful utilization of navigational ways and score deduction rationale for the scores of an opposition. Begin Date : 26 Aug 98 Effort : 12 engineer weeks Classes to be executed : Competition, Event, Trial, RawScore, Team Use Cases to be Implemented : Scoring Inputs : Dummy database (approved ahead of time) with a meet, an opposition, all occasions for that opposition, all contending groups and gymnasts for the opposition, and all trials and crude scores. Yields : The information expected to assemble the report on Figure 4-3, "Yield of the Gymnastics System," on page 25 of prerequisite spec. A DB utility dump of the crude contribution for correlation.

Slide 22

Teaching Points Validation Architectural Design Planning