***Instructions to R2.0 Project Teams:***

***Writing \"Model Requirements Analysis\" documents***

This document is provided as a formatting template for the documentation
of you analysis of the information requirements for each of the tasks
you defined in your \"AEC Industry Processes and Usage Scenaria\". Note
that this document should reference these process tasks as already
defined and not include a redundant definition of process tasks.

The document is structured so that several process analyses can be
combined into a single integrated document for all R2.0 projects.

Therefore ***please do not modify the document structure***.

Document structure is roughtly:

Heading 1 1. Project Document TYPE header

Industry Domain

Heading 2 1.1 Project header

Heading 3 1.1.1 Process/Functionality header

Heading 4 1.1.1.3 Process Def, Process Diagram,

Process/Functionality Analysis, Model

Impact, Roadmap Issues, Review

Issues

Heading 5 1.1.1.3.1 Process task analysis (Mdl. Reqm\'ts)

Each process analysis is presented within a "Heading 3" block (listed as
"1.1.1 {{ Process Name }} ").

Below this, there are six \"Heading 4\" blocks, one each for Process
Definition (overall), Process diagram, Process analysis (step by step -
listed as \"1.1.1.3 Process Analysis\" ), IFC Model Impact, Roadmap
issues and review issues.

Within each process analysis section, each process task step is analyzed
in a \"Heading 5\" block (listed as \"1.1.1.3.1 {{Process Task A}} \").
This includes analysis of the information requirement for this task step
(from the IFC model) and information produced in this task for later use
in another process or task step (to be stored in the IFC model) and
concludes with definition of extensions to existing IFC classes or
proposed new object classes.

***Notes:***

1.  The process definitions in this document must be consistent with
    their presentation in the companion project document \"AEC Industry
    Processes and Usage Scenaria\"

2.  Note that anything enclosed in double curly braces {{ xxx }} are
    instructions to you (the writer). You must replace these with
    content as described in the instructions.

3.  We are using the TQM diagramming template in Visio 4.0 for the
    process diagrams. A sample Visio 4.0 TQM diagram is included just
    double-click to edit

4.  Note that you should include all of the primary tasks in your
    process and identify the informational requirements for each task.
    Details for these informational inputs/outputs are imperative to
    completion of the requirements definition to be used by the
    Information Modeler assigned to design the model extensions to
    support your project.

5.  Please see the example file sent with this template R2an_EX1.doc.

6.  Naming convention for your \"Model Requirements Analysis\" \--
    R2an_XXn.doc (where XXn is the Proj ID in the first column of the
    spreadsheet). Example: \"Completion of the Architectural Model\" has
    an ID of AR-1 \-\-- thus the filename will be \"R2an_AR1.doc\".

7.  This is a project \'working\' document. It will contribute content
    to the \"Model Requirements Analysis\" section of the Release 2.0
    Specifications volume II \-- IFC Object Model for AEC Projects.

8.  The process definition sections from this document must be
    consistent with those in the \"AEC Industry Processes and Usage
    Scenaria\" .

9.  This template extends previous versions of the template for this
    document in multiple ways, including:

-   Process Tasks are now \"Heading 5\" sections. This will enable cross
    document references to specific process tasks

-   Model Requirements Analysis sections for each process task expanded
    to include behavior.

10. 

11. If you have questions please send email!

12. 

13. Regards,

14. Richard See

15. 

# IFC Model Requirements Analysis

*{{AEC Domain or project grouping}}*

## {{ProjID}} - {{ Project Name }}

### {{ Process/Functionality name }}

{{ provide any explanation you think would help the reader understand }}

-   who performs this process

-   When in the project lifecycle it is performed

-   What other processes it relates to (input from/output to/controlled
    by) }}

#### Industry Process Definition

{{ provide a clear, concise definition of this process/functionality in
terms that other AEC industry professionals will understand }}

#### Process Diagram

![](media/image1.emf)

#### Process Analysis

{{ complete an outline of the tasks you envision in software supporting
this industry process }}

##### {{ Process task A }}

{{ description of this process task }}

-   **Input Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

-   **output Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

1.  Project Model Usage Requirements:

-   **Existing Classes:**

-   **{{ Object type name }}**

1.  **Data**

2.  \- {{ Data description type }}

3.  \- {{ notes }}

4.  **Behavior**

5.  \- {{ Behavior description }}

6.  \- {{ notes }}

-   **New Classes:**

-   **{{ Object type name }}**

7.  **Data**

8.  \- {{ Data description type }}

9.  \- {{ notes }}

10. **Behavior**

11. \- {{ Behavior description }}

12. \- {{ notes }}

##### {{ Process task B }}

{{ description of this process task }}

-   **Input Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

-   **output Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

2.  Project Model Usage Requirements:

-   **Existing Classes:**

-   **{{ Object type name }}**

13. **Data**

14. \- {{ Data description type }}

15. \- {{ notes }}

16. **Behavior**

17. \- {{ Behavior description }}

18. \- {{ notes }}

-   **New Classes:**

-   **{{ Object type name }}**

19. **Data**

20. \- {{ Data description type }}

21. \- {{ notes }}

22. **Behavior**

23. \- {{ Behavior description }}

24. \- {{ notes }}

##### {{ Process task C }}

{{ description of this process task }}

-   **Input Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

-   **output Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

3.  Project Model Usage Requirements:

-   **Existing Classes:**

-   **{{ Object type name }}**

25. **Data**

26. \- {{ Data description type }}

27. \- {{ notes }}

28. **Behavior**

29. \- {{ Behavior description }}

30. \- {{ notes }}

-   **New Classes:**

-   **{{ Object type name }}**

31. **Data**

32. \- {{ Data description type }}

33. \- {{ notes }}

34. **Behavior**

35. \- {{ Behavior description }}

36. \- {{ notes }}

##### {{ Process task D }}

{{ description of this process task }}

-   **Input Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

-   **output Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

4.  Project Model Usage Requirements:

-   **Existing Classes:**

-   **{{ Object type name }}**

37. **Data**

38. \- {{ Data description type }}

39. \- {{ notes }}

40. **Behavior**

41. \- {{ Behavior description }}

42. \- {{ notes }}

-   **New Classes:**

-   **{{ Object type name }}**

43. **Data**

44. \- {{ Data description type }}

45. \- {{ notes }}

46. **Behavior**

47. \- {{ Behavior description }}

48. \- {{ notes }}

##### {{ Process task E }}

{{ description of this process task }}

-   **Input Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

-   **output Information:**

-   {{ object type 1 }}

-   {{ object type 2 }}

5.  Project Model Usage Requirements:

-   **Existing Classes:**

-   **{{ Object type name }}**

49. **Data**

50. \- {{ Data description type }}

51. \- {{ notes }}

52. **Behavior**

53. \- {{ Behavior description }}

54. \- {{ notes }}

-   **New Classes:**

-   **{{ Object type name }}**

55. **Data**

56. \- {{ Data description type }}

57. \- {{ notes }}

58. **Behavior**

59. \- {{ Behavior description }}

60. \- {{ notes }}

61. 

#### IFC Model Impact 

This section summarizes the model requirements from all the process
tasks analyzed above into two groups Extensions to R1.0 model object
types and proposed new object types for R2.0.

-   *Usage/Extensions to R1.0 object types*

-   **{{ Object type name }}**

62. **Data**

63. \- {{ Data description type }}

64. \- {{ notes }}

65. **Behavior**

66. \- {{ Behavior description }}

67. \- {{ notes }}

-   **{{ Object type name }}**

68. **Data**

69. \- {{ Data description type }}

70. \- {{ notes }}

71. **Behavior**

72. \- {{ Behavior description }}

73. \- {{ notes }}

74. 

-   *New object types required*

-   **{{ Object type name }}**

75. **Data**

76. \- {{ Data description type }}

77. \- {{ notes }}

78. **Behavior**

79. \- {{ Behavior description }}

80. \- {{ notes }}

-   **{{ Object type name }}**

81. **Data**

82. \- {{ Data description type }}

83. \- {{ notes }}

84. **Behavior**

85. \- {{ Behavior description }}

86. \- {{ notes }}

#### RoadMap Issues

-   Interoperability Issues

-   Applications from which information is needed:

-   {{ application 1 }}

-   {{ application 2 }}

-   **Applications for which information is produced:**

-   {{ application 1 }}

-   {{ application 2 }}

-   

-   Value of software supporting this process

-   {{In this section, please allow for the other domains to rank your
    process in order of precedance for their domain, this allows us to
    examine the issue on a group as well as an individual level}}

-   {{ discipline 1 }} - {{value from 1-10, 1 being the highest value,
    10 being the lowest\]\]

-   {{ discipline 2 }} - {{value from 1-10\]\]

-   Sponsor Software Companies

-   Software Companies that have shown an interest in developing
    applications which implement the process

-   {{ company 1 }}

-   {{ company 2 }}

#### Issues idendified in reviews

-   {{ Reviewing group - Reviewed for: }}

1.  Issues:

2.  {{ Proposed resolution }}

-   **{{ Issue 1 }}**

1.  {{ Proposed resolution }}

-   **{{ Issue 2 }}**

1.  {{ Proposed resolution }}