Term
|
Definition
| the creative process of transforming the problem into a solution; the description of a solution |
|
|
Term
| Conceptual (system) design |
|
Definition
| tells the customer exactly what the system will do |
|
|
Term
|
Definition
| allows the system builders to understand the actual hardware and software needed to solve the customer’s problems. |
|
|
Term
|
Definition
| based on assigning functions to components |
|
|
Term
| Data-oriented decomposition |
|
Definition
| based on external data structures |
|
|
Term
| Event-oriented decomposition |
|
Definition
| based on events that the system must handle and uses information about how events change the system’s state |
|
|
Term
|
Definition
| based on user inputs to the system |
|
|
Term
|
Definition
| identifies classes of objects and their interrelationships |
|
|
Term
|
Definition
| composite parts of design |
|
|
Term
|
Definition
| each activity of the system is performed by exactly one component, and when the inputs and outputs of each component are well-defined |
|
|
Term
|
Definition
| a system is well-defined if all inputs to it are essential to its functions, and all outputs are produced by one of its actions |
|
|
Term
|
Definition
| associates the system capabilities identified in the requirements specification with the system components that will implement them |
|
|
Term
|
Definition
| involves algorithms and data structures, and the components are programming language primitives such as numbers, characters, pointers, and control threads |
|
|
Term
|
Definition
| addresses the code design at a still lower level of detail |
|
|
Term
|
Definition
| input and output of a component |
|
|
Term
|
Definition
| the transformation of the data from input to output |
|
|
Term
|
Definition
| transactions, in the form of an input stream, trigger process execution |
|
|
Term
|
Definition
| the central store controls the triggering of processes |
|
|
Term
|
Definition
| top level is most abstract, and goes down |
|
|
Term
|
Definition
| each component hides a design decision from the others |
|
|
Term
|
Definition
| the fundamental terms, images, and concepts that can be recognized and learned |
|
|
Term
|
Definition
| organization and representation of data, functions, tasks and roles |
|
|
Term
| Navigation rules for the model |
|
Definition
| how to move among data, functions, activities, and roles |
|
|
Term
|
Definition
| the characteristics of the system’s appearance that convey information to the user |
|
|
Term
|
Definition
| the interaction techniques that provide an appealing experience for the user |
|
|
Term
|
Definition
| method for allowing two activities to take place concurrently without their interfering one another |
|
|
Term
|
Definition
| popular way to synchronize processes; it makes sure that when one process is accessing a data element, no other process can affect that element |
|
|
Term
|
Definition
| an abstract object or component that controls the mutual exclusion of a particular process |
|
|
Term
|
Definition
| a task that is always running; its only purpose is to control access to an encapsulated resource |
|
|
Term
|
Definition
| names, abstracts, and identifies the key aspects of a common design structure that make it useful for creating a reusable design |
|
|
Term
|
Definition
| when there is a great deal of dependence between two components |
|
|
Term
|
Definition
| when a couple has some dependence, but the interconnections among components are weak |
|
|
Term
|
Definition
| components have no interconnections at all |
|
|
Term
|
Definition
| when one component modifies an internal data item in the other |
|
|
Term
|
Definition
| data are accessible from a common data store |
|
|
Term
|
Definition
| when one component passes parameters to control the activity of the other |
|
|
Term
|
Definition
| when a data structure is used to pass information from one component to another and the data structure itself is passed |
|
|
Term
|
Definition
|
|
Term
|
Definition
| when a component whose parts are unrelated to one another |
|
|
Term
|
Definition
| where several logically related functions or data elements are placed in the same component |
|
|
Term
|
Definition
| functions are performed in a sequence, but the functions are related only by the timing involved |
|
|
Term
|
Definition
| functions are grouped together in a component just to ensure the order |
|
|
Term
| Communicationally cohesive |
|
Definition
| unrelated data are fetched together because the fetch can only be done with only one disk or tape access |
|
|
Term
|
Definition
| output from one part of a component is input to the next part |
|
|
Term
|
Definition
| every processing element is essential to the performance of a single function |
|
|
Term
|
Definition
| situations that we know are counter to what we really want the system to do |
|
|
Term
|
Definition
| the system addresses each exception in a satisfactory way that does not degrade system functions |
|
|
Term
|
Definition
| when a system waits until a failure occurs during execution |
|
|
Term
|
Definition
| check the system for symptoms of faults or try to anticipate when failures will occur |
|
|
Term
|
Definition
| each system component assumes that the other components contain faults |
|
|
Term
|
Definition
| two functionally equivalent systems are designed by two different design teams at two different times using different techniques...the chances of making the same error is very small |
|
|
Term
|
Definition
| technique that involves having the second system generate false but benign transactions in the first system in order to determine if the first system is working properly |
|
|
Term
|
Definition
| system’s compensation for a fault’s presence |
|
|
Term
|
Definition
| isolation of damage caused by a fault |
|
|
Term
|
Definition
| the minimum number of crossovers that must be used when drawing the graph on a piece of paper |
|
|
Term
|
Definition
| govern how the component is to interact with other components and systems |
|
|
Term
|
Definition
| client calls another component |
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
| development is intended only for identifying feasibility or a particular characteristic in a large design |
|
|
Term
|
Definition
| a method originally developed for the US minuteman missile program, helping us to decompose design and look for situations that might lead to failure |
|
|
Term
|
Definition
| set of leaf nodes of a cut-set tree, with duplicates removed |
|
|
Term
| Preliminary design review |
|
Definition
| examine conceptual design with customers and users |
|
|
Term
|
Definition
| we present the technical design to other developers to check its details before proceeding with implementation |
|
|
Term
|
Definition
| programmers get feedback on their designs before implementation |
|
|
Term
|
Definition
| outlining the critical issues and trade-offs that were considered in generating the design |
|
|
