1 / 7

4. Architecture

4. Architecture. Artifact: Analysis Class. Abstraction of one or several classes or subsystems Focuses on handling functional requirements Postpones non-functional requirements Larger granularity and more conceptual Seldom defines interfaces - operations, signature

hayes-dudley
Download Presentation

4. Architecture

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4. Architecture

  2. Artifact: Analysis Class • Abstraction of one or several classes or subsystems • Focuses on handling functional requirements • Postpones non-functional requirements • Larger granularity and more conceptual • Seldom defines interfaces - operations, signature • High level description of cohesive subset of behavior • Defines attributes - higher level • Defines relationships - conceptual - navigation not important • Fits one of the stereotypes: boundary, control, entity

  3. Boundary Classes • Interaction between system and its actors • Receiving / presenting information and requests • Translates actor’s input into events in system • Translates interesting events into presentable form • Models part that depends on the actors • Collect requirements on system’s boundaries • Windows, forms, UI, printer, sensor, APIs • Fairly kept at higher level • Describes what it achieves not how • Related to at least one actor and vice versa • actors communicate with system through these objects

  4. Entity Classes • Models information that is long lived • Often derived directly from business entity class • May involve complex behavior related to information it represents • Presents the logical data structure • Tells what information the system depends upon

  5. Control Classes • Sequencing, coordination of other objects • Behavior that is not naturally placed in either Entity or Boundary classes • These behavior belong neither to interface nor to specific information • May represent complex calculations not specific to any one entity class • Encapsulate and isolate changes to control, sequencing, transactions, and calculations

  6. Architecture • System must be layered • Each layer taking care of different concerns • N-tier architecture contains n such layers • Typically you should at least follow a 3-tier architecture

  7. 3-Tier Architecture Presentation Tier Entity Tier Business Tier

More Related