2.2 Type of Document 2. 3 Definitions of Concepts and Special Terms 2.4 Expected Relationship with Approved Reference Models, Frameworks, Architectures, etc. Business Case for Developing the Proposed Standard or Technical Report 3.1 Description 3.2. Existing Practice and the Need for a Standard 3.3. 3.3.4 Return on Investment 3.4 Legal Considerations 3.4.1 Patent Assertions 3.4.2 Dissemination of the Standard or Technical Report 4.
Title Provide a descriptive subject matter title.
2.4 Expected Relationship with Approved Reference Models, Frameworks, Architectures, etc. Identify relevant reference models, frameworks, architectures, etc., that are being used to conceptualize the relationships among the various information technologies and this project, and any known or anticipated areas of conformance or conflict. Creation of a new TC must include the rationale. 2.6 Anticipated Frequency and Duration of Meetings Estimate of the anticipated frequency and duration of meetings. 2.8 Estimated Useful Life of Standard or Technical Report Estimate the useful life of the document.