1 / 33

Domain-Specific Software Architecture

Domain-Specific Software Architecture. By Zhiying Lin. Agenda. What is Domain-specific software engineering ( DSSE ) ? What is domain-specific software architecture ( DSSA ) ? How can DSSA be processed ? Summary. What is DSSE ?.

blithe
Download Presentation

Domain-Specific Software 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. Domain-Specific Software Architecture By Zhiying Lin

  2. Agenda • What is Domain-specific software engineering ( DSSE ) ? • What is domain-specific software architecture ( DSSA ) ? • How can DSSA be processed ? • Summary.

  3. What is DSSE ? • An approach to software engineering that is characterized by extensively leveraging existing domain knowledge.

  4. Traditional Software Engineering Too many choices Different concepts

  5. Architecture-Based Software Engineering How to implement? What’s the effective software architectures?

  6. Domain-Specific Software Engineering How to implement? Reference architecture Application-specific architecture Which domain is it belong to?

  7. What is domain-specific software architecture? Definition. A DSSA comprises: • A reference architecture. • A component library. • An application configuration method for selecting and configuring components.

  8. How DSSA can be processed? Stage 1. Define the Scope of the Domain Stage 2. Define/Refine Domain-Specific Concepts/Requirements Stage 3. Define/Refine Domain-Specific Design and Implementation Constraints Stage 4. Develop Domain Architectures/Models Stage 5. Produce/Gather Reusable Workproducts

  9. Stage 1: Define the Scope of the Domain Define what can be accomplished -- emphasis is on the user's needs. Inputs • Experts • Existing systems • Existing documentation (e.g. textbooks, articles)

  10. Stage 1: Define the Scope of the Domain Outputs • Block diagram of the domain of interest including inputs and outputs to the domain and high-level relationships between functional units/elements in the domain • List of people's names to serve as future references or validation sources • List of projects with pointers to documentation and source code • List of needs to be met by applications in this domain

  11. Stage 2: Define/Refine Domain-Specific Concepts/Requirements Similar to Requirements Analysis -- emphasis is on the problem space. Inputs • Outputs from Stage 1 • Selected systems • Selected documentation (e.g., textbooks, articles)

  12. Stage 2: Define/Refine Domain-Specific Concepts/Requirements Outputs • Domain Models • Scenarios • Domain Dictionary • Context Information Diagram • Entity/Relationship Diagram • Object Diagram • Data-Flow Diagram • State-Transition Diagram • Functional requirements (Reference requirements) Feature model Information model Operational model

  13. Stage 2: Define/Refine Domain-Specific Concepts/Requirements A domain model is a product of context analysis and domain analysis. Context analysis Define the boundaries of a domain and the relationship of the entities inside the domain to those outside. Domain analysis Identify, capture, and organize the domain assets.

  14. Scenarios The scenarios consist of a list of numbered, labeled scenario steps or events followed by a brief description.

  15. Domain Dictionary The domain dictionary consists of commonly used words or phrases found in the scenarios and customer needs document (statement of work).

  16. Context Information Diagram It describes the high-level data flow between the major components in the system.

  17. Entity/Relationship (ER) Diagram • It describes the entity relationship in the problem domain. • There are basically two types of relationships of interest: 1. Aggregation: "a-part-of" relationships 2. Generalization: "is a" relationships

  18. Object diagram It identifies the objects in the application domain rather than in the software.

  19. Data-Flow Diagram It focuses on the data exchanged within the system, with no notion of control.

  20. State-Transition Diagram It describes the events and states that take place in the domain.

  21. Functional Requirements • It is a part of reference requirements. (Reference requirements are used to facilitate the mapping of the requirements for each system within a given domain to the canonical domain-specific solution) Three type: mandatory/optional/variable requirements. • It defines characteristics of the problem space.

  22. Stage 3:Define/Refine Domain-Specific Design and Implementation Constraints Similar to Requirements Analysis -- emphasis is on the solution space. Inputs • Outputs from Stage 1, especially the context diagram • Outputs from Stage 2, especially control and data flow diagrams, and rationale

  23. Stage 3:Define/Refine Domain-Specific Design and Implementation Constraints Outputs • Non-Functional Requirements • Design Requirements • Implementation Requirements

  24. Non-Functional Requirements Eg, security, performance, reliability.

  25. Design Requirements Eg, architecture style, user interface style.

  26. Implementation Requirements

  27. Stage 4:Develop Domain Architectures/Models Similar to High-Level Design --emphasis is on defining module/model interfaces and semantics. Input: The input to this stage consist of the inputs and outputs of the previous stages. Outputs A Reference Architecture

  28. Reference Architecture • What is it? Reference Architecture is the set of principal design decisions that are simultaneously applicable to multiple related systems, typically within an application domain, which explicitly defined points of variation. • When to develop? Not too-early; not too-late.

  29. Reference Architecture • Reference Architecture Model • Configuration Decision Diagram • Architecture Schema/Design Record • Reference Architecture Dependency Diagram • Component Interface Descriptions • Constraints and Rationale

  30. Reference Architecture Model All designs start out with some simple abstraction based on the architecture style.

  31. Stage 5:Produce/Gather Reusable Workproducts Eg, Implementation/collection of reusable artifacts (e.g., code, documentation, etc.). Input The interface specifications generated in Stage 4 and related artifacts from existing systems are the primary inputs to this stage. Output • Reusable components and associated test cases and documentation • Cross reference of components to requirements, constraints, and architecture

  32. Summary • What is Domain-specific software engineering ( DSSE ) ? • The three principle concerns of the DSSE. • What is domain-specific software architecture ( DSSA ) ? • How can DSSA be processed ?

  33. Reference Taylor , R.N; Medvidovic , N.; Dashofy , E.M.; , “Software Architecture: Foundations, Theory, and Practice,” Wiley, 2009. Will Tracz, “DSSA (Domain-Specific Software Architecture) Pedagogical Example”, Software Engineering Notes vol 20, no 3, Page 49-63, July 1995. Will Tracz, “Domain-Specific Software Architecture (DSSA) Frequently Asked Questions (FAQ)”, Software Engineering Notes vol 19, no 2, Page 52-57, Apr 1994. Will Tracz, Lou Coglianese, “A Domain-Specific Software Architecture Engineering Process Outline”, Software Engineering Notes vol 18, no 2, Page 40-50, Apr 1993.

More Related