Week 6

1
Week 6

• Domain Analysis

2
Objective

• To explain some important terms in domain
  analysis.
• To analyse methodologies in domain analysis

3
What is domain analysis?

• Domain engineering and analysis always used
  interchangeably or inconsistently.
• Domain analysis (first introduced in the 1980s)
  is an activity within domain engineering.
• It is a process of identifying, collecting,
  organizing and representing the relevant
  information in a domain, based upon the study of
  existing systems and their development histories,
  knowledge captured from domain experts,
  underlying theory, emerging technology within a
  domain..
• Domain analysis also can be defined as the
  process by which a software engineer learns
  background information.

4
Domain analysis

• Domain analysis is performed on a class of
  systems rather than a single system.
• Domain analysis identifies common elements in
  this class of systems, and requires a common
  understanding of the domain.
• These common elements can be exploited to
  facilitate reuse, or to increase time to market
  for future variations and product line
  applications.

5
Input for Domain Analysis

• Technical literature
• Existing applications
• Customer survey
• Experts advice
• Current/future requirements

6
Output for Domain Analysis

• Class taxonomies
• Reuse standard
• Functional model
• Domain language

7
Why perform domain analysis?

• Models essential requirements
• Domain analysis looks at the real world objects
  and relationships exist between objects
• Clarifies understanding of real world
• Analyze the objects in and around the system to
  be built
• Establish a common vocabulary among analysts and
  users
• This process will produce a domain model which
  used to model use cases.

8
Current Domain Analysis Methodologies

• McCain's Product-Oriented Domain Analysis and
  Engineering
• Prieto-Diaz's Domain Analysis for Reusability
• Simos' Domain Analysis and Engineering For
  Building An Organon
• SPC's Domain Analysis and Engineering In The
  Synthesis Environment
• Lubar's Domain Analysis IDeA
• Feature-Oriented Domain Analysis (FODA)
• PROTEUS 
• Sherlock Domain Analysis Methodology

9
Sherlock Domain Analysis Methodology

• Domain Definition
• Domain Characterization
• Domain Scoping
• Domain Modeling
• Domain Framework Design
• Domain Framework Development

10
Domain Definition Phase

• Domain Vocabulary
• Classified Information on the Domain
• History of the firm
• Information from the Domain Expert
• Information from the Market Experts
• Available products
• Market History
• Current Market Trends
• Definition of Feasible Domain, Strategic Domain,
  Current Domain
• Feasibility Analysis

11
Domain Characterization Phase

• Internal Values
• Features
• Quality
• External Values
• Interoperability between users
• Interoperability between products
• Expectataions

12
Domain Characterization Phase

• Description of the Installed Based
• Compatibility
• Users flow
• Market segment and pricing policy
• Plan of development new products

13
Domain Scoping

• Variability space
• Attributes of products in the domain
• Constraints on the attributes
• Definition of the product strategies
• Identification of the products strategies

14
Domain Modeling

• Use-case model
• Analysis Model
• Domain use-case model
• Domain analysis model
• Traces between use cases and analysis classes

15
Domain Framework Development

• Definition of the nature of the domain framework
• Architecture of the domain framework
• Documentation of the component in the domain
  framework
• Guidelines to develop products using framework

16
Differences

• Domain analysis is involved with organizing and
  documenting the common components and
  architectures of the domain
• Domain engineering is involved with the more
  concrete step of building the components,
  methods, and tools for the development of a
  system in the domain based on the domain
  analysis.