[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)

  1. Will Tracz
  2. DSSA(Domain-Specific Software Architecture)
  3. ACM SIGSOFT Software Engineering Notes V20n3(Jul 1995)pp49-60
      Example (theatre seat booking system) with insights
    1. Domain model::=Net(scenarios, domain dictionary, context diagram, ERD, DFDs, State transition models, object model)

    2. reference requirements::=Net{ functional, nonfunctional, implementation}

    3. reference architecture::=follwing
      1. model, configuration decision tree, schema or design record, dependency diagram, component interface descriptions, constratins, rationale

      (End of Net)

      How toy example compares to real world.

      ----- Insights

    4. p50: distingush problem space from solution/design space. domain analysis is about a family of systems or a product line informal needs statement is a place to start separate functional requirements from design and implementation requirements scenarios are good...
    5. p52: domain dictionaries evolve, not everyone agrees, must record all definitions,
    6. p54: iterative, do not overspecify objects at the domain level
    7. PR define problem space, QST define soltion space.
    8. p57: styles of architecture
    9. p58: requirements need to evolve thru feedback, reflect back into documentation, rationales and interdependences, separate user interface from functionallity
    10. p58: subsets of requirements determine design decisions/configurations
    11. p61: Use tools and methods alrady in use for doamin modelling as well.

Search for bibliographic items containing a matching string.

(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.

To see the complete bibliography (1Mb+) select:[Bibliography]