soen343-week5 - SOEN 343 Software Design Section H Fall...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler http://www.cs.concordia.ca/~gregb/home/soen343h-f06.html
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Outline Importance of domain model, use cases, operation contracts for design Layers MVC Use case realization, Jacobson robustness analysis, traceability GRASP Controller principle (Larman 17.13) Design for visibility (Larman ch 19)
Background image of page 2
Design Model : Register enterItem (itemID, quantity) : ProductCatalog spec = getProductSpec( itemID ) Require- ments Business Modeling Design Sample UP Artifact Relationships Vision Glossary The logical architecture is influenced by the constraints and non-functional requirements captured in the Supp. Spec. Domain Model * * Supplementary Specification Use-Case Model Register ... makeNewSale() enterItem(. ..) ... ProductCatalog ... getProductSpec(. ..) ... 1 1 class diagrams (a static view) interaction diagrams (a dynamic view) UI package diagrams of the logical architecture (a static view) Domain Tech Services Design Model
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Logical Architecture – Simple Layers Domain UI Swing not the Java Swing libraries, but our GUI classes based on Swing Web Sales Payments Taxes Technical Services Persistence Logging RulesEngine
Background image of page 4
Logical Architecture – Layers UI (AKA Presentation , View) Application (AKA Workflow, Process, Mediation, App Controller) Domain (AKA Business, Application Logic, Model) Technical Services (AKA Technical Infrastructure, High-level Technical Services) Foundation (AKA Core Services, Base Services, Low-level Technical Services/Infrastructure) width implies range of applicability P GUI windows p reports p speech interface p HTML, XML, XSLT, JSP, Javascript, . .. p handles presentation layer requests p workflow p session state p window/page transitions p consolidation/transformation of disparate data for presentation p handles application layer requests p implementation of domain rules p domain services ( POS , Inventory ) - services may be used by just one application, but there is also the possibility of multi-application services p (relatively) high-level technical services and frameworks p Persistence , Security p low-level technical services, utilities, and frameworks p data structures, threads, math, file, DB, and network I/O more app specific dependency Business Infrastructure (AKA Low-level Business Services) p very general low-level business services used in many business domains p CurrencyConverter
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 03/28/2011.

Page1 / 35

soen343-week5 - SOEN 343 Software Design Section H Fall...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online