Team-Fly |
Requirements Analysis: From Business Views to Architecture By David C. Hay | |
Table of Contents | |
[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X] [Y] [Z] IBM San Jose Laboratory ICAM Program IDEF methods IDEF0 and data-flow diagrams context diagram rules IDEF0 diagram 2nd activity limit IDEF1 IDEF1X 2nd 3rd 4th 5th identifying source discovering rules identity of the enterprise impact value Business Rules Group definition inclusive or ORM notation inclusive or (relationships) The UML incomplete (sub-types) IDEF1X notation independent set of dependencies 4th normal form InductionAboutData industry jargon inference rule class 2nd information definition information engineering 2nd 3rd 4th Information Engineering 2nd Information Engineering, a Technical Report, by Clive Finkelstein and James Martin information overload information resource manager information services department infrastructure, technical INGRES inheritance 2nd 3rd initial state initial value The UML innovation input transaction structure inputs in IDEF0 inside and now instance verifier in the Ronald Ross notation 2nd Integrated Computer Aided Manufacturing Program integrated computer-aided manufacturing definition) methods (IDEF) integrity constraint in the Ronald Ross notation intellectual capital Interactive Graphics and Retrieval System interest in a use case internal influence Business Rules Group definition internal organization data model pattern internal schema internal validity check intransitive ring constraint in ORM inventory data model pattern sample entity life history IRM irreflexive ring constraint in ORM item data model pattern item structure element data model pattern item type data model pattern 2nd item type structure element data model pattern 2nd iteration in a structured natural language in an entity life history ITT |
Team-Fly |
Top |