OOPortal OOPortal

Domain Partitioning  «Prev  Next»
Lesson 8

Domain partitioning Conclusion

This module discussed how domain partitioning provides a breakdown of the overall system into cohesive units of work. In the finished application these units may be combined to support different workflows or job duties. Domain partitioning also sets the stage for architectural partitioning because each type of work or functionality might imply a different architectural approach.

Completing domain partitioning

So how do you know when you are done with domain partitioning? You must allocate every use case and every class in your analysis models to a domain partition, and all object model associations must be preserved. Nothing from your analysis model can be lost in the transition!
You should now be able to:
  1. Identify the resources used for domain partitioning
  2. Perform domain partitioning using use cases
  3. Explain how package diagrams may be used to model domain partitions/li>
  4. Assign analysis classes to domain partitions
  5. Test the domain partition for completeness
  6. Identify and define dependencies between partitions
  1. Specification-abstraction level: input definition
    1. Just indicating the language is insufficient
    2. Abstraction-level indicates amount of design already done
    3. for example: task DFG, tasks, CDFG, FSMD
  2. Granularity: specification size in each object
    1. Fine granularity yields more possible designs
    2. Coarse granularity better for computation, designer interaction
    3. e.g. tasks, procedures, statement blocks, statements
  3. Component allocation: types and numbers, for example,. ASICs, processors, memories, buses
  4. Output: format and uses: For example, new specification, hints to synthesis tool

Specification Abstraction Levels

  1. Task-level dataflow graph: A Dataflow graph where each operation represents a task
  2. Task: Each task is described as a sequential program
  3. Arithmetic-level dataflow graph: 1) A Dataflow graph of arithmetic operations along with some control operations 2) The most common model used in the partitioning techniques
  4. Finite state machine (FSM) with datapath: A finite state machine, with possibly complex expressions being computed in a state or during a transition
  5. Register transfers: The transfers between registers for each machine state are described
  6. Structure: 1) A structural interconnection of physical components 2) Often called a netlist

Glossary terms

  1. Package: A general-purpose mechanism for grouping models and model elements, typically by similar functions or uses within the context of a system. See also: Component

Domain Partitioning - Quiz

Click the Quiz link below to test what you learned in this module.
Domain Partitioning - Quiz