Perspective (What) Inventory Definition (How) Process Definition (Where) Distribution Definition (Who) Responsibility Definition (When) Timing Definition (Why) Motivation Definition Architect Perspective (What) Inventory Representation (How) Process Representation (Where) Distribution Representation (Who) Responsibility Representation (When) Timing Representation (Why) Motivation Representation Engineer Perspective (What) Inventory Specification (How) Process Specification (Where) Distribution Specification (Who) Responsibility Specification (When) Timing Specification (Why) Motivation Specification Technician Perspective (What) Inventory Configuration (How) Process Configuration (Where) Distribution Configuration (Who) Responsibility Configuration (When) Timing Configuration (Why) Motivation Configuration Enterprise Perspective (What) Inventory Instantiations (How) Process Instantiations (Where) Distribution Instantiations (Who) Responsibility Instantiations (When) Timing Instantiations (Why) Motivation Instantiations Since the product development (i.e., architectural artifact) in each cell or the problem solution embodied by the cell is the answer to a question from a perspective, typically, the models or descriptions are higher-level depictions or the surface answers of the cell. The refined models or designs supporting that answer are the detailed descriptions within the cell. Decomposition (i.e., drill down to greater levels of detail) takes place within each cell. If a cell is not made explicit (defined), it is implicit (undefined). If it is implicit, the risk of making assumptions about these cells exists. If the assumptions are valid, then time and money are saved. If, however, the assumptions are invalid, it is likely to increase costs and exceed the schedule for implementation. Framework set of rules The framework comes with a set of rules: Rule 1 The columns have no order : The columns are interchangeable but cannot be reduced or created Rule 2 Each column has a simple generic model : Every column can have its own meta-model Rule 3 The basic model of each column must be unique : The basic model of each column, the relationship objects and the structure of it is unique. Each relationship object is interdependent but the representation objective is unique. Rule 4 Each row describes a distinct, unique perspective : Each row describes the view of a particular business group and is unique to it. All rows are usually present in most hierarchical organizations. Rule 5 Each cell is unique : The combination of 2,3 & 4 must produce unique cells where each cell represents a particular case. Example: A2 represents business outputs as they represent what are to be eventually constructed. Rule 6 The composite or integration of all cell models in one row constitutes a complete model from