Draft Federal Information Processing Standards …

1 IDraft Federal InformationProcessing Standards publication 1831993 December 21 Announcing the Standard forINTEGRATION DEFINITION FOR FUNCTIONMODELING (IDEF0) Federal Information Processing Standards Publications (FIPS PUBS) are issued by the NationalInstitute of Standards and Technology after approval by the Secretary of Commerce pursuant toSection 111(d) of the Federal Property and Administrative Services Act of 1949 as amended bythe Computer Security Act of 1987, Public Law of Definition for Function Modeling (IDEF0). of Standard, Modeling publication announces the adoption of the Integration DefinitionFunction Modeling (IDEF0) as a Federal Information Processing Standard (FIPS).

2 This standardis based on the Air Force Wright Aeronautical Laboratories Integrated Computer- AidedManufacturing (ICAM) Architecture, Part II, Volume IV - Function Modeling Manual (IDEF0),June standard describes the IDEF0 modeling language (semantics and syntax), andassociated rules and techniques, for developing structured graphical representations of a systemor enterprise. Use of this standard permits the construction of models comprising systemfunctions (activities, actions, processes, operations), functional relationships, and data( Information or objects)

3 That support systems standard is the reference authority for use by system or enterprise modelers requiredto utilize the IDEF0 modeling technique, by implementors in developing tools for implementingthis technique, and by other computer professionals in understanding the precise syntactic andsemantic rules of the of of Commerce, National Institute of Standardsand Technology, Computer Systems ICAM Architecture Part II-Volume IV - Function Modeling Manual (IDEF0),AFWAL-TR-81-4023, Materials Laboratory, Air Force Wright Aeronautical Laboratories, AirForce Systems Command, Wright-Patterson Air Force Base, Ohio 45433, June Information Resources Management Regulations Subpart , Standards , and Subpart , Federal Information Support System (IISS), Volume V - Common Data ModelSubsystem, Part 4 - Information Modeling Manual - IDEF1 Extended, December Architecture Part II, Volume V - Information Modeling Manual (IDEF1)

4 ,AFWAL-TR-81-4023, Materials Laboratory, Air Force Wright Aeronautical Laboratories, AirForce Systems Command, Wright-Patterson Air Force Base, Ohio 45433, June Configuration Management, Volume II - ICAM Documentation Standardsfor Systems Development Methodology (SDM), AFWAL-TR-82-4157, Air Force SystemsCommand, Wright-Patterson Air Force Base, Ohio 45433, October primary objectives of this standard are:a. To provide a means for completely and consistently modeling the functions (activities,actions, processes, operations) required by a system or enterprise, and the functionalrelationships and data ( Information or objects) that support the integration of thosefunctions;b.

5 To provide a modeling technique which is independent of Computer-Aided SoftwareEngineering (CASE) methods or tools, but which can be used in conjunction with thosemethods or tools; provide a modeling technique that has the following characteristics:-Generic (for analysis of systems of varying purpose, scope and complexity);-Rigorous and precise (for production of correct, usable models);-Concise (to facilitate understanding, communication, consensus and validation);-Conceptual (for representation of functional requirements rather than physical ororganizational implementations);-Flexible (to support several phases of the lifecycle of a project).

6 Use of this standard is strongly recommended for projects that:a. Require a modeling technique for the analysis, development, re-engineering,integration, or acquisition of Information systems;b. Incorporate a systems or enterprise modeling technique into a business process analysisor software engineering specifications of this standard are applicable when system or enterprise modelingtechniques are applied to the following:iiia. Projects requiring IDEF0 as the modeling technique;b. Development of automated software tools implementing the IDEF0 specifications of this standard are not applicable to those projects requiring afunction modeling technique other than features of the IDEF0 technique should be used only when the neededoperation or function cannot reasonably be implemented with the standard features nonstandard features can be very useful.

7 It should be recognized that the use of these orany other nonstandard elements may make the integration of models more difficult and standard adopts the Integration Definition for FunctionModeling (IDEF0) as a Federal Information Processing Standard (FIPS). implementation of this standard involves two areas ofconsideration: acquisition of implementations and interpretation of the Acquisition of IDEF0 publication (FIPS 183) iseffective June 30, 1994. For Federal acquisitions after this date, projects utilizing the IDEF0function modeling technique, or software implementing the IDEF0 modeling technique, shouldconform to FIPS 183.

8 Conformance to this standard should be considered whether the project orsoftware utilizing the IDEF0 modeling technique is acquired as part of an ADP systemprocurement, acquired by separate procurement, used under an ADP leasing arrangement, orspecified for use in contracts for programming transition period provides time for industry to develop products conforming to thisstandard. The transition period begins on the effective date and continues for one (1) yearthereafter. The provisions of this publication apply to orders placed after the date of thispublication; however, utilizing a function modeling technique that does not conform to thisstandard may be permitted during the transition Interpretation of this provides for the resolution of questionsregarding the implementation and applicability of this FIPS.

9 All questions concerning theinterpretation of this standard should be addressed to: Director, Computer Systems Laboratory ATTN: FIPS IDEF0 Interpretation National Institute of Standards and Technology Gaithersburg, MD certain exceptional circumstances, the heads of Federal departmentsand agencies may approve waivers to Federal Information Processing Standards (FIPS). Thehead of such agencies may redelegate such authority only to a senior official designated pursuantivto section 3506(b) of Title 44, United States Code.

10 Requests for waivers shall be granted onlywhen:a. Compliance with a standard would adversely affect theaccomplishment of the missionof an operator of a Federal computersystem, orb. Compliance with a standard would cause a major adverse financial impact on theoperator which is not offset by government-wide heads may approve requests for waivers only by awritten decision whichexplains the basis upon which the agency head made the required finding(s). A copy of eachsuch decision, with procurement sensitive or classified portions clearly identified, shall be sentto: Director, Computer Systems Laboratory ATTN.