Abstract:
A system level automation tool tracks allocatable requirements associated with a system design using a computer by generating a plurality of objects each defining a portion of the system. The objects may have a parent-child relationship wherein one or more of the child objects each define a portion of the parent object. The allocatable requirements may be apportioned and traced among the objects. Some allocated requirement are reallocated as some actual values are determined to differ from their allocated requirement.

Description:
RELATED PATENT APPLICATIONS 
     This application is a continuation of application Ser. No. 07/965,984, filed Oct. 23, 1992, now abandoned, which is a continuation of application Ser. No. 07/661,360, filed 02/26/91, now abandoned. This patent application is related to U.S. patent application Ser. No. 08/075,844, entitled &#34;Computer Tool For System Level Design&#34;; U.S. patent application Ser. No. 07/661,042, entitled &#34;Method and Apparatus for System Design&#34;; and U.S. patent application Ser. No. 07/966,128, entitled &#34;Method and Apparatus For Aiding System Design&#34;, all filed concurrently herewith. 
    
    
     TECHNICAL FIELD OF THE INVENTION 
     This invention relates in general to computers systems and more particularly, to a computer system automation tool for system level engineers. 
     BACKGROUND OF THE INVENTION 
     System engineering concerns the conceptualization and construction of complex systems. As such, it is an important part of any major project. The system engineering commences at the initial stages of a project, and continues throughout the project life cycle, thereby having a great impact on the successful completion of the project. 
     To aid the system engineer, a multitude of computer tools have been designed. One word which is the key to understanding these tools is &#34;system&#34;. Webster&#39;s generic definition describes a system as &#34;a regularly interacting or independent group of items forming a unified whole.&#34; &#34;Systems&#34; range from extremely high-level concepts such as &#34;a motorized vehicle for individuals&#34; to the low-level, such as &#34;a drive train.&#34; 
     Although the term &#34;system&#34; is an overloaded term which can have far-reaching implications, an important element to consider is the different types of support tools which are appropriate at different system levels. Current software (e.g., CASE--Computer Aided Software Engineering) and hardware (e.g., CAE--Computer Aided Engineering) design tools are directed toward efficiency of use in a specific environment, rather than over the broad range of system levels. As such, several different tools are necessary at the different system levels, which complicates communication of necessary information between system levels. Further, the specific tools place different operational requirements on the user, thereby reducing the efficiency of using the programs. 
     Therefore, a need has arisen in the industry for a system engineering tool which provides engineering support over a wide range of system levels. 
     SUMMARY OF THE INVENTION 
     In accordance with the present invention, a method and apparatus for tracking allocatable requirements associated with a system design is provided which substantially overcomes problems associated with prior system design tools. 
     Allocatable requirements associated with a system design are tracked by generating a plurality of objects, each object defining a portion of the system. Some of the objects may have a parent-child relationship wherein one or more child objects each define a portion of a parent object. The allocatable requirements are apportioned among the objects and may be traced through the parent-child relationships. In other aspects of the present invention, the user may apportion an allocatable requirement to an object as a fixed value, by reference to an equation, or in relation to child objects associated with the object. A confidence factor may be assigned to the apportionment. The designer may easily compare actual apportionments of the allocatable requirements with system goals and vary the apportionment according. 
     The present invention provides significant advantages over the prior art. A system designer may allocate requirements among subsystems to comply with system requirements and also detect and re-allocate requirements among subsystems which are above and below the stated goals. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: 
     FIG. 1 illustrates a block diagram of project functions performed by a system engineer; 
     FIG. 2 illustrates a more detailed block diagram of a typical system engineering cycle; 
     FIG. 3 illustrates a perspective view of a preferred hardware embodiment for the present invention; 
     FIG. 4 illustrates an abstract model of the engineering cycle to which the present invention applies; 
     FIG. 5 illustrates a system level abstraction block (SLATE); 
     FIG. 6 illustrates a user interface showing hierarchical decomposition of a requirements definition; 
     FIGS. 7a-b illustrate a use for defining a technical allocation budget (TAB); 
     FIG. 8 illustrates a block diagram of an executable SLAB; 
     FIGS. 9a-d illustrate menus used for text fragments and automatic document generation; 
     FIG. 10 illustrates a block diagram of a transitional mapping (TRAM); 
     FIGS. 11a-b illustrate common uses of TRAMs; and 
     FIG. 12 illustrates an implementation of a mapping of regional TRAMs and requirements (MORTAR). 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The preferred embodiment of the present invention and its advantages are best understood by referring to FIGS. 1-12 of the drawings, like numerals being used for like and corresponding parts of the various drawings. 
     FIG. 1 illustrates a block diagram showing the project functions performed by system engineers. The project 10 begins with concept definition stage 12, which broadly states the goals of the project. Based on the output from the concept definition stage 12, a functional design 14 is generated. From the functional design phase 14, a detailed design is developed in block 16. In block 18, a prototype is developed. After the prototype is developed, production of the units begins in block 20. After production 20, maintenance and field support continue in block 22. As can be seen by the block diagram of the project 10, there is continuous feedback from the prototype production and maintenance blocks 18-22 which is incorporated in the concept definition, functional design and detailed design blocks 12-16. 
     FIG. 2 illustrates a more detailed block diagram of a typical system engineering cycle. The system engineering cycle begins in block 24 with the identification and evaluation of the operational needs of the system under consideration. These needs are combined with the customer requirements in block 26 which are interpreted and prioritized in block 28. This interpretation may be validated with the customer, after which the system requirements are designed in block 30. 
     The system requirements defined in block 30 are used to develop a system design. The system design includes documentation on design tradeoffs, estimated performance, estimated costs, risks, maintenance plans, validation, and producibility. Further, the system design includes a proposed architecture, breaking down the system into logical groups. For example, in an electronics system, the architecture might be broken down into analog, digital and software groups. If applicable, interfaces to other components must be defined. The information generated in the system design block 32 is reviewed in the system design review block 34. This is an interactive process in which the system design is refined until an acceptable design has been generated. 
     Once an acceptable design is generated, a design requirements specification is generated in block 36. The design requirements specification is reviewed under a preliminary design review block 38. The specification 36 is refined until accepted. 
     After the preliminary design review 38, a detailed design is developed in block 40 and a detailed design verification plan is developed in block 42. The detailed design 40 is refined until accepted by a critical design review 44. After accepted, the detailed design 40 is taken to fabrication and assembly 46. The system is tested in block 48 for performance, maintenance, reliability and environmental factors. Information from the system testing 48 is used to refine the detailed design in block 40. 
     Once testing is complete, system integration and testing is performed in block 50, the system is demonstrated in block 52, an operational analysis is performed in block 54 and the operational need (block 24) is validated in block 56. 
     As the cycle progresses from the concept stage to the design stage, the numerous ancillary requirements often become apparent. These requirements are often written down in multiple places or carried in the heads of one or more people. Maintaining a consistent set of requirements among these documents and humans is a difficult problem. The system engineer continues to refine information, breakdown requirements and define the functional structure of the solution. System level requirements need to flow downward in the hierarchy to ensure that the delivered system meets its requirements. Likewise, implementation details need to flow upward in the hierarchy in order to allow the system engineer to further refine the definition of the functional structure of the solution. 
     REQUIREMENTS 
     A large part of the system engineer&#39;s job involves information management. System level requirements are some of the most important pieces of information to be managed. &#34;Requirements&#34; is a generalized term which is often loosely applied to a number of different types of system level issues. The present invention provides support for four basic types of Requirements: Structural, Compliancy, ALLO. &#34;Structural&#34; Requirements are statements in the specification which describe a functional structure that must be embodied in the final product. An example of a Structural Requirement would be &#34;the database receives information through a bank of twenty-four modems.&#34; 
     &#34;Compliancy&#34; Requirements are global compliancy statements relative to the system being specified. For example, a specification might require that &#34;all software development shall be done in Pascal,&#34; or &#34;all electronic hardware must be radiation hardened.&#34; 
     &#34;Allocatable&#34; Requirements are characterized by quantifiable measures. Quantities are typically described in such terms as weight, size, cost, pressure, temperature, speed, power, memory and process capacity and so on. These requirements typically impose limits on contributing components of the product. Each of these requirements may be thought of as part of the &#34;technical budget.&#34; For example, if a system is allotted &#34;twenty-five watts of power and must weigh no more than two pounds&#34; then the weight and power must be allocated in the work breakdown structure among all contributing components. 
     &#34;Supplemental&#34; Requirements are imposed on the system by virtue of specific implementation decisions. For example, the utilization of a particular integrated circuit might limit operating temperatures for the entire system, even though the original specification did not have a temperature limitation. Additionally, Supplemental Requirements may be internally imposed. For example, a particular company may have a policy against using parts made by a particular competitor, or may have additional requirements regarding documentation of the system development. It is important that the Supplemental Requirements be uniquely identified so that when alternative implementations are considered, it is possible to identify quickly which requirements might be relaxed or removed, and under what conditions this would occur. All Supplemental Requirements are further identifiable as Structural, Compliancy or Allocatable Requirements. 
     SYSTEM LEVEL AUTOMATION TOOL FOR ENGINEERS (SLATE) 
     FIG. 3 illustrates a perspective view of a preferred hardware embodiment for the System Level Automation Tool for Engineers (SLATE) of the present invention. The user 58 inputs and receives information to a workstation 60 having a monochrome or color monitor 62 and input devices such as a keyboard 64 and a mouse 66. The workstation should be able to operate a graphical windowing system, such as X-windows. The workstation 60 is connected to a network in order to share the information stored in its database with a plurality of users. 
     FIG. 4 illustrates an abstract model of the engineering cycle which SLATE aids in developing. The top level of this model is the Functional Requirement Definition (&#34;FRD&#34;) 68. The FRD is a problem statement where the operational and other customer needs are collected. These needs are refined into a set of system requirements. Each requirement can be categorized into one of the four types described hereinabove. Below the FRD level 68 is the Implementation Logically Mapped Alternatives (&#34;ILMA&#34;) group 70. Each ILMA 72 is a possible implementation of the FRD 68. ILMAs 72 are bound to the FRD through a Functional to Implementation Mapping (&#34;FIM&#34;) 74. There is only one FRD level 68 in a system, there may be many ILMAs 72, one for each possible implementation alternative. Each ILMA 72 may be divided into functional categories 74 shown in FIG. 4 as software, mechanical and hardware categories. The compliancy checklist 76 contains a list of compliancy requirements and is maintained separate from the functional structures in SLATE. 
     SLABS 
     The base object in SLATE is the decomposition of the system into &#34;System Level Abstraction Blocks&#34; (&#34;SLABs&#34;) 78, illustrated in FIG. 5. The SLABs 78 can be thought of as a basic element of a functional block diagram. Each SLAB 78 has a unique identifier, such as &#34;carburetor&#34;, supports &#34;upwards&#34; hierarchical links 80 to &#34;parent&#34; SLABs and &#34;downward&#34; hierarchical links 82 to &#34;children&#34; SLABs. Links between SLABs 78 on different hierarchical levels is illustrated in greater detail in connection with FIG. 6. Further, each SLAB supports functional links 84 and 86, to and from peer SLABs, respectively. Peer SLABs are SLABs on a common hierarchical level. The interrelation between peer SLABs is also shown graphically in connection with FIG. 6. Additionally, each SLAB 78 supports Technical Allocation Budgets (&#34;TABs&#34;) 88, Requirements Traceability Links (&#34;RTLs&#34;) 90, executable Functional Descriptions (&#34;FDs&#34;) 92 and text fragments 94. TABs 88 are used to maintain an account of quantifiable requirements which must be spread out among various SLABs in a hierarchical level. For example, if a system has a requirement that the weight should be no greater than seven pounds, then the weight tab associated with a single hierarchical level should not exceed seven pounds. 
     SLATE supports two types of RTLs 90--structural RTLs and allocatable RTLs. A structural RTL links a text fragment relating to a structural requirement to a SLAB. For example, a proposed system for a transmitter/receiver may have a requirement that encoding shall be performed using algorithm A and decoding shall be performed using algorithm B. An RTL would tie the text fragment containing the encoding/decoding requirements to a SLAB(s) which accommodates the requirement. 
     An allocatable RTL ties an allocatable requirement to a TAB definition. Allocatable RTLs are discussed further in connection with FIGS. 7a-b. 
     Text fragments 94 are one or more paragraphs of textual information associated with the SLABs 78. The text fragments 94 may be used for a variety of purposes, such as documentation, proposals, maintenance information, manuals, and so on. The text fragments 94 may have an associated description field identifying their purpose. 
     The executable functional descriptions 92 are used to compute outputs from inputs in order to test the functional operation of SLABs. Executable FDs are discussed in greater detail in connection with FIG. 8. 
     FIG. 6 shows an illustration of the preferred embodiment of the user interface for SLATE. The interface, referred to generally by reference numeral 96 provides menu areas 98 each comprising a plurality of keys 100 which may be selected using the mouse 66 or other input device. The function of each of these keys will be described in greater detail hereinbelow. The interface 96 further provides a viewing area 100 which may be subdivided into a plurality of windows, shown as 102 and 104. A message area 105 is used to display messages from the system to the user. 
     Window 102 illustrates the hierarchical decomposition of a concept into system components of increasing detail. The top level SLAB 106 has the ID &#34;Vending Machine.&#34; The vending machine concept has been broken down into six (6) children SLABs 108-118. Children SLABs for Coin Handling SLAB 114 are shown as SLABs 120-130. Changer SLAB 122 has two children SLABs 132 and 134. Change Supply SLAB 134 has four children SLABs 136-142. Viewing area 104 illustrates the peer to peer connection between the children SLABs 144-150 of the Product Handling SLAB 116. 
     TABS 
     An important aspect of the preferred embodiment is the TAB allocation function of SLATE. FIGS. 7a-b illustrate a pop-up menu used to configurate TAB for a particular SLAB. FIG. 7a illustrates a TAB 152 for the vending machine SLAB 106 and FIG. 7b illustrates a TAB 154 for the Product Inventory Chamber SLAB 110. 
     TABs 88 contain parametric information that describe the limits, goals, actual values and unit for quantifiable (allocatable) requirements. There are several pieces of information stored in a TAB, including: maximum parameter limit, minimum parameter limit, goal parameter value, actual (calculated) parameter value, parameter confidence factor, and the unit the parameter is expressed in (volts, amps, and so on). In many cases, only one of the maximum or minimum parameters will be used, for example, when a requirement sets forth a value which may not be exceeded. 
     SLATE design is built around hierarchical decomposition of system blocks, as shown in FIG. 6. Each system level provides increasingly detailed structures, until component level implementation detail is reached. System requirements normally mandate limits placed on higher levels of system architecture structures (e.g., a system must not weigh more than twelve pounds), while the physical aspects that constitute the actual make-up of the parametric data (e.g., the microprocessor weighs five ounces) normally are introduced at the lowest system design levels. Consequently, SLATE is designed to propagate the limits and goals for each parametric requirement downwardly via the TABs 88 while simultaneously constructing actual/realized values upwardly through the TABs by summarization of the contributions of the children SLABs. Some constraints, like reliability factors, require their own algorithmic calculations and cannot be derived by simple summation. 
     A major difficulty in complex systems is that a stated allocatable requirement is normally an aggregate limit placed on the overall system behavior and/or composition, and the system engineer lacks the ability to link the impact of design decisions made at lower levels, which are often orders of magnitude removed from the initial allocation. The problem is further complicated upon recognition that the design is constrained in multiple dimensions, i.e., one design parameter may act adversely upon another design parameter. For example, if a circuit needs to respond faster to meet a first requirement, one alternative may be to use higher powered components. However, more power consumption may require more thermal dissipation which might affect another constraint, and an increase in cooling capacity might increase weight. The TABs 88 associated with the various SLABs provide the ability to not only track complexities, but to supply enough additional information within the localized context to aid the designer in understanding the available options. In the previous example, it was stated that cooling capacity might increase weight. However, by having the ability to track weight throughout the SLABs, the system engineer may determine that another portion of the system has been allocated more weight (i.e., has a weight goal) which is unnecessarily high based on a particular implementation. This may allow the system engineer to use higher powered components without exceeding the weight constraint of the overall system. 
     The parameter value stored in each TAB must be recalculated whenever a variable (with regard to the equation field 188) or the Actual Value associated with a Child SLAB is changed, before contextual analysis can be valid. 
     The system designer has the ability in SLATE to distribute the local parametric budget to each subcomponent in a logical manner. For example, if a unit has a maximum weight of five pounds, and is composed of three subunits (each subunit represented on a SLAB), the designer might allocate the TAB limits as one pound for the first subunit, one pound for the second subunit and three pounds for the third subunit. Similarly, the designer might distribute the weight as two pounds for the first subunit, three pounds for the second subunit and zero pounds for the third subunit, if the third subunit has no weight, such as a software module. The designer also has the ability to hold some local limit and/or goal in judgment for later allocation if needed. Limits and goals are inserted for each SLAB and &#34;flow down&#34;; as a result, for each SLAB in the system, a comparison can be made algorithmically between goals, limits and realized actuals. Actual conditions exceeding or even approaching limits and/or goals can be flagged for special attention by the system engineer. Under-utilized allocations for certain SLABs may be redistributed to SLABs exceeding the lower goals, as can portions of the budget held in reserve (i.e., available but not allocated). 
     Each TAB 88 includes a confidence factor which indicates the degree of certainty that can be associated with the numeric quantity (estimated versus measured). Thus, during TAB redistribution, limits on precisely measured TABs may be trimmed closely, while a larger margin of error can be provided for TABs 88 with uncertain estimates, while still staying within the overall system limit. Table I provides the certainty categories from least certain (1) to most certain (10). 
     TABLE 1 
     Confidence Factors 
     1. Uninitialized 
     2. Global default 
     3. Partition default 
     4. Computed from lower hierarchy 
     5. Model specified 
     6. User specified 
     7. Special/other 
     8. Customer specified 
     9. Specified by standards 
     10. Physical Law 
     When calculating, the actual lowest valued confidence factor is propagated up the hierarchical TABs thereby indicating how much flexibility exists within or under a SLAB 78. 
     FIG. 7a and 7b illustrate pop-up menus 152 and 154 to define a TAB 88 for a SLAB 78. Menus 152 and 154 each include a TAB Name Field 156, a SLAB Name Field 158, a TAB Units Field 160, a Goal Value Field 162, a Minimum Field 164, a Maximum Field 166, a TAB RTL Field 168 (which points to an allocatable requirement) and an Actual Value Section 170. The Actual Value Section 170 allows the designer to select one of three methods for determining the actual value of the TAB for the associated SLAB. The designer may choose to determine the actual value through a mathematical operation on corresponding TAB values associated with the children SLABs by using fields 172, 174, 176 and 178. A second method for providing an actual value is to use an assigned value using fields 180 and 182. A third method is to determine the actual value by an equation using fields 184, 186 and 188. The chosen method is indicated by pointer 189. 
     Equation field 188 may be used to provide an equation by which the actual value may be determined. The actual value determined by the equation is output in field 184. Field 186 is a confidence value associated with the computed value. 
     The assigned value of field 180 may be input by the designer. The Confidence Field 182 provides a confidence level associated with the Assigned Value. 
     The actual value may be computed based on a computation of the TABs associated with the children SLABs. The designer enters the desired operation in field 174. Typically, the desired mathematical operation will be a summation; however, other operations may also be provided. For example, to determine a reliability factor, a multiplication operation on the actual value associated with the children SLABs may be necessary. The confidence factor in field 176 is computed from the confidence factors associated with the children SLABs. 
     FIG. 7a illustrates a menu which the designer has completed for the &#34;weight&#34; TAB. This TAB is associated with the vending machine SLAB 106, which is the top SLAB in the hierarchy. Therefore, the goal of 6,000 pounds for the Weight TAB is an overall system goal. A minimum weight of 5,000 pounds is specified and the maximum weight of 7,000 pounds is specified. An Actual Value of 5,550 pounds is computed using the sum of the children SLABs. Thus, SLABs 108-118 each have associated Weight TABs which total to 5,550 pounds. 
     FIG. 7b illustrates a &#34;capacity&#34; TAB associated with the Product Inventory Chamber SLAB 110. The goal is to provide a capacity of 550 cans, with a minimum of 400 and a maximum of 700. In this instance, the Actual Value of 545 cans is computed through an equation entered in field 188. 
     EXECUTABLE FUNCTIONAL DESCRIPTIONS (FDs) 
     FIG. 8 illustrates a block diagram showing the operation of an executable FD. As discussed in connection with FIG. 5, a SLAB 78 may have one or more executable FDs 92 which transform inputs into outputs. The executable FD 190 has two inputs &#34;i&#34; and &#34;X&#34; and two outputs &#34;o&#34; and &#34;Y&#34;. Y represents a group of output signals and X represents a group of input signals; Y=f(X) is the generalized functional description. The input, i, is a secondary input used to initialize the block, provide interim parametric storage, implement breakpoint capability, and so on. The secondary output, o, provides a reportable data path. The designer using SLATE is responsible for defining the executable FDs, the interconnections between host SLABs/FDs and the functional/process consistency between FDs and among their interconnections. The function f(X) may use local variables and parameters. 
     Text Fragments 
     FIGS. 9a-d illustrate the text fragments 94 and the automatic document generation functions provided by SLATE. As previously discussed, any number of text fragments 94 may be associated with each SLAB 78. FIG. 9a illustrates a text fragment associated with the Product Inventory Chamber SLAB 110. A Modify Text Fragment menu 192 is shown in FIG. 9a. The menu 192 provides a Name Field 194 for the name of the text fragment, a Numeric ID Field 196 for providing a numeric ID for the text fragment (an alternate name), a Description Field 198 for describing the text fragment, a Key Word Field 200 for listing key words associated with the text fragment, an Attachment Field 202 specifying the SLAB to which the text fragment is associated, a Referring Documents Field 204 listing documents which incorporate the text fragment and a Edit Field 206 displaying the content of the text fragment to be modified. 
     FIG. 9b is a Format Block menu for specifying parameters for a document comprising one or more text fragments 94. The menu 208 includes a Name Field 210 for entering the name of the document to be generated, a Title Field 212 for providing a title for the document, a Document Type Field 214 for specifying a document type (such as manual, statement of work, proposal, etc.), a Publisher Name Field 218, a Contract Name Field 220 for specifying a particular contract with which the document is associated, a Customer Field 222 for specifying the entity for which the document is being generated, a Revision Field 224 for specifying a revision identifier, a Date Field 226 for specifying the date of the revision, a Classification Field 228 for specifying a confidentiality classification for the document, Header and Footer Fields 230, and Document Support Fields 232 for whether the document contains a table of contents, index, acronym section, reference document section, list of appendices, list of figures, or lists of tables. 
     FIG. 9c illustrates an Editor Menu 234 for constructing a template for the document. A Name Field 236 provides the name of the document. Document Title Field 238, Revision Field 240, Date Field 242, and Classification Field 244 have the same functions as described in connection with FIG. 9b. The Structure Field 246 allows the user to provide a template describing the organization of the document and the referenced text fragments. For example, under section three (&#34;Product Inventory Chamber&#34;), the text fragment &#34;Chamber&#34; is referenced. This text fragment is shown in FIG. 9a. 
     In FIG. 9d, the merged output based on the document template is illustrated. The file name is provided in Name Field 248 and the text is provided in Text Field 250. As can be seen, various files have been merged into the template shown in FIG. 9c. The merged document provides a number of control commands such as &#34;/BEGIN&#34;, &#34;/DOCT&#34;, and &#34;/TITLE&#34;. In the preferred embodiment, however, the merged document may be formatted to be compatible with the file specifications of any one of a number of popular word processors. 
     TRAMs 
     As previously discussed in connection with FIG. 4, a design may be structured as a functional requirement definition (FRD) 68, separated from one or more implementation logically mapped alternatives (ILMAs) 70 by a functional-to-implementation mapping (FIM) 74. In practice, a number of FIMs may exist, not only between the FRD and the ILMA, but also between different levels of ILMAs. Anywhere there is a logical &#34;leap of intuition&#34; in synthesizing a solution, or anywhere an abstract concept (function, algorithm or need) is mapped onto a system resource (for example, by assignment of ports, interrupt handlers, scheduling of band width, etc.), a FIM exists, and the object for recording the mapping in SLATE is a TRAM (TRAnsitional Mapping). 
     FIG. 10 illustrates a TRAM 252. A TRAM 252 is a conduit to convey functionality, requirements traceability, and technical allocation budgets across FIMs 74 in the design structure. The TRAM 252 provides a special parent-child relationship, described herein as a &#34;foster parent-foster child&#34; relationship between SLABs. The TRAM 252 links one or more &#34;foster&#34; parent SLABs to one or more &#34;foster&#34; children SLABs. Each SLAB may be linked to one or more RTLs 90 and TABs 88 from the foster parent SLABs and may have associated text fragments 94 which describe the TRAM interlinks. 
     FIGS. 11a and 11b illustrate common uses of TRAMs 252. In FIG. 11a, a control hardware SLAB 254 and a process software SLAB 256 are coupled via TRAM 258 to a microprocessor with ROM SLAB 260. This 2:1 mapping of SLABs 254 and 256 to SLAB 260 could not be achieved using hierarchical decomposition, since SLATE allows any SLAB to have, at most, one parent. In the example of FIG. 11a, SLABs 254 and 256 are the foster parent SLABs and SLAB 260 is the foster child SLAB. 
     FIG. 11b illustrates a second example of a TRAM wherein a communications channel SLAB 262 is coupled to a queuing software SLAB 264, a queuing hardware SLAB 266, a protocol SLAB 268 and a bus hardware SLAB 270. The communications channel SLAB 262 includes an RTL 272 and a radiation TAB 274. The RTL 272 is transferred via the TRAM 276 to the foster children TABs 264-270. The radiation TAB 274 is allocated between the queuing hardware SLAB 266 and the bus hardware SLAB 270. The radiation TAB 274 may be allocated in any desired ratio; for example, one-third of the allowable radiation associated with the communications channel could be radiation TAB 274 associated with the queuing hardware SLAB 266 and two-thirds of the radiation could be allocated to radiation TAB 274 associated with the bus hardware SLAB 270. 
     In recording complex system designs, providing clear documentation of the thought processes behind the derivation of the details of an implementation from original requirements presents a major problem for the system engineer. Major portions of the system&#39;s design description can normally be represented by a top-down hierarchical decomposition. SLATE uses such a hierarchical detail decomposition paradigm, with standard SLAB parent-child relationship, to carry the bulk of most system design descriptions. The difficulty occurs when standard hierarchical structure is not adequate to explain the complexities involved in relationships that have resulted in the final design embodiment. Typically, it is these precise complexities that are most in need of explanation and supporting documentation, but for which designers have historically had no special documentation tools to work with. In the SLATE paradigm, the TRAM mechanism handles these complex relationships. 
     At least three categories of complexities necessitate the TRAM structure as a supplement to the standard hierarchical SLAB structure. The three categories are: 
     1. Mapping conceptual requirements onto implementable components and subsystems. (This is the original SLATE &#34;classic&#34; TRAM, sometimes referred to as &#34;bridging the FIM&#34;.) This involves a shift of perspective from a statement of need to a planned solution. Examples of the mapping of these conceptual requirements are shown in FIGS. 11a-b. 
     2. Mapping the merger of a secondary requirement onto an existing implementable component(s) and/or subsystem(s) that was previously designed to satisfy a different functional need. An example of this mapping is provided hereinbelow. 
     3. Remapping &#34;current&#34; perspective of a potentially implementable structure onto a different set of implementables that are &#34;closer to&#34; the final design implementation. This category is subtle to grasp, because it is natural in the SLATE paradigm to think about one hierarchical structure of implementables. In practice, a solution is formed by &#34;nibbling&#34; away at the total picture until it can be broken down into digestible bits and pieces. Thus, in the interim process of &#34;getting to a design solution&#34;, the system designer travels through many intermediate steps that help redefine the need in terms closer to what will finally be implemented. A common occurrence of this category involves gathering up multiple uses of shared resources and coalescing the need into a common design embodiment. Since the individual usage points are never implemented, it is not correct to think of the SLABs in which they are identified as &#34;implementables&#34; (even though they could have been implemented individually in place, and even if every other SLAB in the hierarchical structure is the final design embodiment) because, as used in context, these SLABs form a needs requirement that will be met in the final design by implementing a shared resource. 
     Much of what has previously been written about SLATE has postulated the existence of an extensive detailed requirements list. The example given below has been chosen to illustrate how the same process evolves even from loosely stated &#34;mission statements&#34; that are representative of commercial undertakings. The example selected involves designing an automobile. 
     A partial list of the rationale and requirements driving a commercial manufacturer in its design of automotive vehicles might be stated as: 
     &#34;We intend to offer a viable product for sale on the commercial market by: 
     * Meeting governmental requirements that allow the product to be sold. 
     * Meeting functional requirements and needs of our customer base. 
     * Appealing to the potential customers&#39; `care abouts`.&#34; 
     Such a requirements list can be mapped into a &#34;Functional Requirements Definition&#34; structure shown in TABLE 2, and broken down hierarchically into finer detail. Each hierarchical line entry in the following could correspond to a SLAB in SLATE. 
     
                       TABLE 2______________________________________Functional Requirements Definition______________________________________1.      Offer a viable product for sale on the   commercial market.1.1     Meet governmental requirements to allow product   to be sold.1.1.1   Meet Safety Standard.1.1.2   Meet Environmental Pollution Standards.. . .1.2     Meet functional needs of customer base.1.2.1   Cargo Capacity.1.2.2   Operational Speed.1.2.2.1 Horsepower of Engine.1.2.2.2 Weight of Vehicle.1.2.3   Operational Range on single tank of gas.. . .1.3     Appeal to customers&#39; &#34;care abouts&#34;.1.3.1   Supply Comfort.1.3.2   Supply &#34;Ease of Handling&#34;.1.3.3   &#34;Eye Catching&#34; Design.1.3.4   Minimize &#34;Cost of Operation&#34;.1.3.4.1 Maximize &#34;Miles per Gallon&#34;.. . .______________________________________ 
    
     Further breakdown might be done in any given area (for example, under 1.2.2 Operational Speed, further detailing down to mathematical relationships between weight, horsepower, aerodynamic quality of design, etc., might be comprehended). However, a tops-down refinement will not reach a design for an automobile, because the functional requirements definition hierarchy does not deal with &#34;implementables&#34;. No carburetors, no tires, no pistons, no windshield wipers or tail lights are provided for. Clearly a TRAM mapping must exist between the elements out of which the automobile is built and the functional requirements definition provided in Table 2. 
     The implementation can also be described in a similar hierarchical structure provided in TABLE 3. One such structure, in part, might be detailed as follows: 
     
                       TABLE 3______________________________________Implementation Hierarchical Structure______________________________________1.             Automobile.1.1            Structural Body/Chassis.1.2            Interior Passenger Chamber.1.3            Engine.1.3.1          Engine Block.1.3.2          Carburetor.1.3.3          Radiator/Cooling System.1.3.3.1        Fan.1.3.3.2        Water Pump.1.3.3.3        Heater.1.3.3.4        Defroster.1.3.3.5        Radiator1.4            Power Train.1.5            Exhaust System.1.5.1          Tail Pipe.1.5.2          Muffler.1.5.3          Catalytic Converter.1.6            Electrical System.1.6.1          Battery.1.6.2          Alternator.1.6.3          Lights.1.7            Optional Features.1.7.1          Power Steering.1.7.2          Cruise Control.1.7.3          Air Conditioner.. . .______________________________________ 
    
     As in the prior hierarchy, the choices are subjectively grouped, and no single embodiment of &#34;associations&#34; should be considered &#34;correct&#34;. Rather it should be regarded as a documented record of the perspective in which the designer viewed the system. 
     Within SLATE, the TRAM mechanism is used to construct the mapping between the functional requirements definition and the implementation hierarchy. For the automotive design example, the SLATE design scenario might be: 
     Construction of TRAMs 
     The user already has the two SLAB hierarchies illustrated above in Tables 2 and 3 to work with. The user then selects the &#34;Action/Object&#34; command &#34;Add/TRAM&#34;. A Pop-up Window opens that allows the user to specify the particulars of this TRAM. The TRAM will be given a name that the user can reference it by. The input side connections (foster parent SLAB(s)) from the Functional Requirements Definition hierarchy in this example) are specified. The output side connections (&#34;adopted child(ren)) SLAB(s)&#34; in the Implementation hierarchy in this example are specified. At this point, the new TRAM is established and &#34;lives&#34; in the Database in much the same manner as a normal SLAB does. 
     Having established the TRAM, the user is then free to &#34;enhance&#34; it in a manner very similar to what he/she would do if it were a standard SLAB. The user can &#34;Add/Text Fragment&#34; to explain the thought process behind the mapping carried via the TRAM. The user can &#34;reroute&#34; TABs that are attached to the TRAM&#39;s foster parents, to flow wholly or partially through the TRAM (by controlling TAB propagation at the foster parent SLAB) and then appropriately routing the portion of the TAB propagated into the TRAM, at the TRAM itself. &#34;Requirement Traceability Links&#34; can be either attached (mouse clicks tieing requirement to TRAM) or propagated through the TRAM (standard RTL propagation window usage on both the foster parent SLAB(s) and TRAM). 
     Using the automotive example, the user might call out the following: 
     
         ______________________________________ADD-TRAM....TRAM Name =             PASSENGER RESTRAINT             SYSTEMFoster Parent SLABs =         SAFETY STANDARD         XXX (1.1.1.8.4)         PASSENGER COMFORT (1.3.1.6)Adopted Child SLAB =         AIR BAG (1.2.8.3.9)______________________________________ 
    
     A text fragment might be placed on this TRAM explaining that the Air Bag is judged more comfortable than harnesses per a consumer survey. A different model car might have economy requirements outweighing comfort, and opt for shoulder harnesses. Still others might bring economy, safety and comfort together at this TRAM, and offer the customer a standard shoulder harness or optional air bag system. Whatever the structure or outcome, the TRAM documents the reasoning that lead to the design implementation, and provides traceability both to and from the factors that were considered in the design process. 
     The Passenger Restraint TRAM has a single adopted child, and multiple foster parents. It is referred to as an &#34;N-to-1&#34; TRAM because it maps a plurality of foster parents (Safety Standards and Passenger Comfort), transition mapping onto a single adopted child (Air Bag). The &#34;N-to-1&#34; TRAMs are the most obvious TRAMs in the design, because a SLAB, by definition, can have, at most, one parent. Therefore, if multiple concerns are focusing together to result in a single implemented entity, the SLAB is not just a detailed refinement of previously explained concepts, but instead constitutes a synthesis of multiple ideas that have been developed (a new perspective), and must be mapped via TRAM(s) to clearly delineate the intended relationships. The TRAM example above fits nicely into the category 1 TRAM rationalization. 
     Somewhat more subtle is the &#34;1-to-N&#34; TRAM, where a single foster parent&#39;s attributes are tied to numerous adopted children as shown in FIG. 11a. This is sometimes confused with the normal hierarchical parent-child relationship (as shown in FIG. 6), and at times spawns questions about the need-for a &#34;1-to-N&#34; TRAM. The answer lies in &#34;the Change of Perspective&#34; and can best be explained by example. Consider the following: 
     
         ______________________________________TRAM Name = CHOICE OF NON-TOXIC MATERIALSFoster Parent SLAB =         SAFETY REGULATION REQUIR-         ING NON-INFLAMMABLE         MATERIAL USAGE         (1.1.1.3.5)Adopted Children SLABs =           SEAT UPHOLSTERY           MATERIAL           (1.2.8.3.5.9)           RADIATOR HOSES (1.3.3.6)           EXTERIOR VINYL TRIM           (1.7.6.2)           . . . ETC. . . .______________________________________ 
    
     Clearly, the radiator hoses are not included &#34;just to have non-toxic material usage&#34;. Their primary function is to carry fluids in the cooling system (hence their direct ancestry passes through SLAB 1.3.3--Radiator/Cooling System). In this example, numeric technical budgets are not appropriate, as no numeric quantification is present, nor distributed. Attempting to relegate the Non-Inflammable Material Usage to a compliancy checklist would dilute the detail of this design structure, afforded by using a &#34;1-to-N&#34; TRAM. This is a category 2 utilization of TRAMs. 
     When both the driving needs and the resultant implemented structures are distributed, the TRAM becomes an &#34;N-to-M&#34; mapping. For example, the electronic systems in automobiles have grown in their sophistication, the need to communicate status information and commands throughout the automobile has become complex enough that some automobiles now have an internal &#34;data bus&#34; routed throughout the car. An associated &#34;N-to-M&#34; TRAM in the design of such an information bus might be described as: 
     
         ______________________________________TRAM Name = AUTOMOTIVE INFORMATION BUSFoster Parent SLABs =         Sensory data on air/fuel mix         Sensory data on engine timing         Sensory data on emissions         Sensory data from &#34;Gas Pedal           Position&#34;         Sensory data from &#34;Brake Pedal           Position&#34;         Sensory data from Speedometer         Sensory data about oncoming           lights         Sensory status of headlight           beams         Control Microprocessor           AlgorithmsAdopted Children SLABs =           Electrical Data Bus Cabling       Microprocessor (with software in         ROM)       Bus multiplexer hardware       various sensors . . . .       various actuators . . . .       . . . etc. . . .______________________________________ 
    
     There are many points to be made about this TRAM. The first is that it clearly constitutes &#34;an assemblage of components to perform several functional tasks&#34; a statement that is probably true of all &#34;N-to-M&#34; TRAMs. Since it is an &#34;assemblage of components&#34; it is conceivable that it could be thought of as a subsystem, contracted out, and become in essence, an &#34;off-the-shelf&#34; component. Such changes of perspective should not be surprising, since even the automobile itself could be viewed as a component in some higher level systems. Therefore, the TRAM documents the perspective being dealt within a relative context, and the information contained therein must be considered within that context to be properly understood. No value judgment is assigned to the perspective. 
     There is a commonly occurring theme in many system designs involving multiple usage of a reusable/shareable resource (such as a hardware bus, or a software subroutine). Implementing each occurrence separately (as would be demanded in the strictest sense under a tops-down hierarchical design structure) normally runs counter to the almost universal requirement of maximizing efficiency by minimizing cost. The gathering up of these multiple occurrences, and implementing a smaller number of resource suppliers (often just one), constitutes a change in perspective, and necessitates a TRAM. Significantly, it will appear that such a TRAM maps from one view of the implementation to another view of the implementation. In actuality, the first hierarchical structure is a mixture of implementables and &#34;functional needs&#34;. The remapping of the &#34;structural points needing usage of the functional resource&#34; to a perspective that will be implemented as a shared resource via a TRAM confirms that the intermediate hierarchical structure is not &#34;purely implementables&#34;, or at least not with relation to the final system design being implemented. 
     MORTAR 
     Once the FIM region has been traversed via TRAMS that computationally link allocatable requirements, structural requirements and implementation structures as well as documenting the underlying considerations, attention can then be paid to documenting the macro level synergistic effects that may occur at a FIM. The SLATE mechanism for explaining the macro synergistic considerations is MORTAR (Mapping Of Regional TRAMs and Requirements). 
     MORTAR provides the structure to bind together the synergistic relationships inherent in a set of TRAMs. The MORTAR is actually composed of supportive textual description and quantitative matrix descriptors that explain synergistic effects occurring between and among the TRAMs. These types of relationships are especially important to document when the FIM mapping is actually undergoing multiple constraints, and the resultant implementation choices are multiply bound in subtle, secondary manners, a condition that is at the heart and core of &#34;concurrent engineering&#34;. 
     An illustrative example at this point will clarify many points and offer a reference situation against which some of the concepts can be more fully elaborated. Consider the following example: 
     Needed Functionality: 
     Design a system that sorts, classifies and correlates &#34;items&#34;. 
     Constraints: 
     System cannot weight more than 70 oz. nor use more than 5 amps, and must process at least 6000 &#34;items&#34;/second. 
     Requirements List (derived from above): 
     R1--Sort 
     R2--Classify 
     R3--Correlate 
     R4--&lt;70 oz. 
     R5--&lt;5 amps 
     R6--6000 items/sec. 
     Potential &#34;System Components&#34; in implementing a solution: 
     
                       TABLE 4______________________________________Electronic ChipsTYPE          MIPS    WEIGHT    POWER  COST______________________________________Microprocessor XYZ         6.5     4.5 oz    400 ma $38.75Microprocessor RST         8.2     6.2 oz    750 ma $46.20Microprocessor JKL         3.5     3.4 oz    350 ma $14.50256 K DRAM    --      2.5 oz    160 ma  $1.381 Meg DRAM    --      4.9 oz    425 ma $12.42______________________________________ 
    
     
                       TABLE 5______________________________________Software Algorithmic Components           COM-      EXCLUSIVE INSTR           PATIBLE   MEMORY    EXECUTEDID   FUNCTION   WITH      NEEDS     PER ITEM______________________________________J14  Sort       RST       4     Meg    84J93  Sort       JKL       2     Meg   134J42  Sort       XYZ       1     Meg   272C15  Classify   JKL, XYZ  40    K      93C15  Classify   RST       58    K      75C88  Classify   XYZ       825   K      26S71  Correlate  JKL, RST  4     Meg   852S64  Correlate  XYZ       14    Meg   148______________________________________ 
    
     SLATE may accommodate numerous interpretations and approaches to each design, and there is not a single &#34;right&#34; approach. The definition of how TRAMs are defined and mapped reflect the individual design approach of the user, and must be complete and consistent within the framework that the design is viewed by the user. In essence, the TRAMs capture the perspective view that the designer intended. Alternate views may be equally valid. The example continues with one possible perspective that works. 
     Analysis: 
     Correlation function S64 consumes so much memory, that the power and weight limits are exceeded if it is used. Since S64 is the only correlation function compatible with XYZ, then XYZ is not a viable alternative. 
     The throughput requirement requires that if microprocessor JKL is utilized, at least two of them will have to work in parallel. 
     
         ______________________________________          Weight Power    Cost______________________________________Solution 1: (Least Expensive)Microprocessor - JKL, Qty 2             6.8 oz   0.7 a   $29.00DRAMs - 256 K, Qty 25            62.5 oz   4.0 a   $34.50Software - J93, C15, &amp; S71 Resulting Solution Processes 6481+ items per second.Solution 2: (More Expensive, but less power &amp;weight)Microprocessor - JKL, Qty 2             6.8 oz   0.7 a   $29.00DRAMs - 1 Meg., Qty 7            34.3 oz  2.975 a  $86.94Software - J93, C15, &amp; S71 Resulting Solution Processes 6481+ items per second.Solution 3: (Faster, better throughput at a highercost)Microprocessor - RST             6.2 oz   0.75 a  $46.20DRAMs - 1 Meg, Qty 9            44.1 oz  3.825 a  $111.78Software - J14, C15, &amp; S71______________________________________ Resulting Solution Processes 6923+ items per second. 
    
     There are a number of other potential solutions if we use a mixture of 256 k and 1 Meg DRAMs, that on a sliding scale would cut cost, but would also affect weight and power consumption. For example: 
     
         ______________________________________Solution 3A: (Same throughput, less weight, power &amp;expense)         Weight  Power    Cost______________________________________Microprocessor - RST           6.2 oz    0.75 a   $46.20DRAMs - 1 Meg, Qty 8           39.2 oz    3.4 a   $99.36DRAMs - 256 k, Qty 1           2.5 oz    0.16 a    $1.38Software - J14, C15 &amp; S71______________________________________ Resulting Solution Processes 6923+ items per second. 
    
     At this level of analysis Solution 3A appears superior to Solution 3, but in reality, the complications of mixing different sized memories and the resulting weight, power and expense of support circuitry might rule out 3A. Assuming that mixing memory sizes is acceptable, having seen across the board improvement in weight, power and cost, the natural inclination is to substitute the 256 k DRAMs for all the 1 Meg DRAMs. What worked nicely for a 1-to-1 chip substitution (because both the 1 Meg and 256 k DRAMs contain more than enough to cover the C15/58k need) breaks down when a 4-to-1 chip substitution is needed. The applicable deltas for each 1 Meg of substitution becomes: 
     Weight--Increases by 5.1 oz, 
     Power--Increases by 0.215 amps, and 
     Cost--Decreases by $6.90. 
     While the decreasing cost is desirable, the weight and/or power limits will soon prevent further substitution of 256 k DRAMs into an RST based solution. 
     Supplemental Requirements: 
     RS1--Need for a microprocessor to run all software 
     RS2--Memory requirements for SORT SW 
     RS3--Memory requirements for CLASSIFICATION SW 
     RS4--Memory requirements for CORRELATION SW 
     To carry through this example, one possible variation of the resultant TRAMs associated with ILMA 2 (Solution 2) are provided below: 
     T1 {(R1) →(J93)} Sort SW from requirement to sort 
     T2 {(R2) →(C15)} Classification SW from req. to classify 
     T3 {(R3) →(S71)} Correlation SW from requirement to corr. 
     T4 {(RS1) →(JKL)} Microprocessor from req. to run software 
     T5 {(RS2, RS3, RS4)→(DRAMs)} Total memory needs 
     There are still several questions unresolved with this TRAM mapping. First, the system engineer must instruct SLATE to deal with the dual architecture of the parallel JKL processors. Probably the simplest acceptable method would be to have a single SLAB (perhaps named &#34;JKL&#34;) that represented the &#34;complete&#34; microprocessor functionality. This SLAB (&#34;JKL&#34;) would then have children that would be the two instances of microprocessor occurrence (SLABs &#34;JKL1&#34; and &#34;JKL2&#34;), along with any other circuitry needed to distribute and balance the processing tasks between the twin processors. T4 would be pointing at the functional microprocessor SLAB (&#34;JKL&#34;). 
     The other logical question is how to tie in the allocatable requirements (R4, R5 and R6). It is not unreasonable to introduce a sixth TRAM to map the hardware requirements onto the hardware, e.g.: 
     
         T6 {(R4, R5)→(JKL, DRAMs)} HW constraints from req. limits 
    
     R6, the requirement that the system process 6000 items/sec., however, remains to be accounted for. An artificial &#34;System&#34; SLAB could be introduced at the highest level, just to map it out of the TAB Definition Table. However, it would be difficult to allocate this &#34;Throughput&#34; TAB to lower SLABs. This &#34;distributed allocatable&#34; (R6) is indicative that the &#34;whole picture&#34; is not yet present, because as was seen in the analysis portion, many subtle linkages are in effect between the TRAMs that must be balanced to reach this solution. The documentation of these TRAM linkages is provided for in MORTAR, and it is the MORTAR that should properly be the recipient of R6 in this case. It should be noted that each MORTAR must belong to an ILMA to reflect the unique sets of TRAMs within its implementation structure. 
     The core of the MORTAR is its matrix of TRAM relationships. The matrix is composed of all TRAMs within the set being described by the MORTAR, mapped against themselves. Thus, for a set of &#34;n&#34; TRAMS, the MORTAR matrix is &#34;n&#34;×&#34;n&#34; containing &#34;n&#34; squared elements. Any relational mappings are placed in appropriate elements of the matrix. Because such a matrix is mirrored along its diagonal (containing redundant information), only the diagonal and one of the remaining triangular areas need be specified. By convention, the lower triangular area is filled in for MORTAR matrices. MORTAR appears to the designer in a spreadsheet form shown in FIG. 12. 
     The MORTAR matrix concisely shows all the interdependencies that are applicable for a set of TRAMs selected by the designer. For the Sort SW (T1), it shows that the choice of J93 is tied to JKL microprocessor, it requires 2 Megs of memory, and it will consume 0.81 MIPS of processing. The JKL microprocessor (T4) is shown to have 3.5 MIPS and that a dual pair is used resulting in 67.8 oz of weight and 700 ma of power consumption. Likewise, it is shown that 7 1-Meg DRAMs (T5) are needed, and their contribution in weight and power consumption are listed. R6 can now be directly tied to this MORTAR. Text fragments supporting this MORTAR would expound upon the interdependencies and record details of alternatives considered, and why they were not chosen. 
     The MORTAR matrix is utilized whenever a change is to be considered. By scanning the row and column for any pertinent TRAM, all dependencies can be checked against for synergistic impact. For example, if someone were to propose using a new faster correlation software routine, the T3 column reveals that the appropriate questions to be considered are: 
     1. How many MIPS are needed to execute it to our basic R6 requirement? 
     2. Will it run on the JKL processor? 
     3. How much memory will it take? 
     No additional questions are generated by scanning the T3 row because the prior TRAMs (T1 &amp; T2) are not directly dependent on T3 (null entries). 
     By answering all of these questions, a correct analysis can be made of the overall impact introducing the new software will have. If the new software needed less MIPS, ran on JKL, and did not use much more memory then it would be a very interesting candidate for replacing S71. 
     In addition to illustrating all the dependencies between TRAMs, a MORTAR matrix is further capable of performing row, column and matrix operations on the various cells. For example, a cell providing a calculation for the needed MIPS according to TRAMs T1, T2 and T3 could be performed by calculating the sum of cells T1--T1, T2--T2 and T3--T3. A total weight cell could be provided by adding the weight specified in cells T6-T4 and T6-T5. These cells could be added to the matrix using conventional spreadsheet techniques. 
     Even more interesting, from the standpoint of understanding how MORTAR facilitates the analysis of design change impact, is the potential effect of new software that needs substantially less MIPS, less memory, but cannot run on JKL. This scenario would then force the designer to consider changing the microprocessor (T4), which sends him/her back to the MORTAR matrix to determine what needs to be considered when T4 is changed. That would generate the next set of questions, which are: 
     1. Does J93 run on the alternate processor? 
     2. Does C15 run on the alternate processor? 
     3. What MIP rate does the alternate processor run at? 
     4. What weight and power consumption will the alternate processor use? 
     The microprocessor change, by itself, does not affect the memory considerations. However, if these questions &#34;domino&#34; into considering further software changes (because either or both J93 and/or C15 do not run on the alternate processor), then memory considerations will reenter the analysis process when the next level of questions are generated from appropriate row/column entries under T1 and/or T2. 
     Finally, consider the potential impact if a new 4 Meg DRAM were to become available that effectively removed the original barriers (exceeding R4 and R5) that precluded using S64: 
     
         ______________________________________Type       MIPS    Weight     Power Cost______________________________________4 Meg DRAM --      6.3 oz     485 ma                               $28.00______________________________________Solution 4:          Weight     Power   Cost______________________________________Microprocessor - XYZ           4.5 oz     0.4 a  $38.75DRAMs - 4 Meg, Qty 4          25.2 oz    1.94 a  $112.00Software - J42, C88, &amp; S64______________________________________ Resulting Solution Processes 15695+ items per second.RESULTING POSSIBLE SOLUTIONS:Solution Number       Cost     Weight   Power Items/Sec.______________________________________1            $63.50  69.3 oz   4.7 a                               64812           $115.94  41.1 oz  3.675 a                               64813           $156.98  50.3 oz  4.575 a                               6923  3A        $146.94  47.9 oz   4.31 a                               69234           $150.75  29.7 oz   2.34 a                               15695______________________________________ 
    
     If all the above examples were documented in MORTAR, entries in the matrices would establish the relationship between the microprocessor, memory, and software routines that would not allow arbitrary changes to any of the components without appropriate analysis of the impact on the others. The entries in the matrices would indicate which parametric values were being balanced (e.g., board area occupied by chips would not be a constraint in this example) and only the relevant parameters would need to be analyzed. 
     In addition to the relationship matrix shown above, a shadow matrix could be implemented to carry the actual realized numeric values, allowing computation of the impact of substitutions across an entire system database, and load up analysis programs with libraries of alternative components for overnight batch analysis runs searching for more optimal alternatives. This concept is only possible if the MORTAR relationship are captured and structured, suitable for computational analysis. 
     The present invention provides numerous advantages over the prior art. Since SLATE handles a wide range of hierarchical levels, a consistent set of tools may be provided for the entirety of a project. Compliancy, structural and allocatable requirements may be carried through multiple levels to allow the system designer to identify problem areas and to identify over-allocated areas which may be used to solve allocation problems. SLATE allows requirements to flow down and implementation details to flow up, thereby providing the system designer with a broad understanding of the entire system. As implementations change, the accounting of the actual values for the technical allocatable budget may be automatically recalculated. 
     Further, the TRAM mechanism provided in SLATE encourages documentation of implementation complexities. The relations between TRAMs are documented in MORTAR matrices, providing a means for discerning the intricacies of a proposed implementation change. 
     Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.