Page 235 - DCAP405_SOFTWARE_ENGINEERING

Software Engineering

Notes Arango and Prieto-Diaz present a model of domain analysis summarized in the following SADT
diagram:

This model explains domain analysis as an activity that takes multiple sources of input, produces
many different kinds of output, and is heavily parameterized. For example, one parameter is the
development paradigm (e.g., SA, Jackson, OO). Raw domain knowledge from any relevant
source is taken as input. Participants in the process can be, among others, domain experts and
analysts. Outputs are (semi) formalized concepts, domain processes, standards, logical
architectures, etc. Subsequent activities produce generic design fragments, frameworks, etc.

Notes While this account gives an inspiring initial insight into domain analysis, it is not
the full story. Several refinements are presented next.

Product Definition Domain Analysis

When a product is seen as part of a new or an existing stream of products, the domain of this
product stream may itself be studied. This study will in general go beyond technical aspects of
the product.

Example: Strategic alignment, longer term marketing aspects, product positioning, risk
analysis, common look-and-feel, covering a diversity of product features, etc., will play a role in
conjunction with investigations of generic terminology, logical architectures, reliability
standards, and other general considerations.

228 LOVELY PROFESSIONAL UNIVERSITY