Made with
ConceptDraw
DIAGRAM 15

IDEF9 Standard

IDEF9 method, as well as other IDEF methods, was developed in the framework of the BBC USA program on information integration for coordinated development (The Air Force Information Integration for Concurrent Engineering (IICE)). IDEF9 method is one of the methods, which constitute the technology of the work with existing information and knowledge. In particular, IDEF9 method (Business Constraint Discovery) is developed for calculation and analysis of conditions and limitations in business-systems. The main motivation for development of such method was the perception of the fact, that conditions and limitations, influenced on the enterprise structure, usually are poorly defined and studied. An organization can normally function (which frequently happens) without knowledge about conditions and limitations, which acts in its system, in other words, without knowledge about requirements of this system.
Nevertheless, if there is a task to improve the functioning of the production system, to increase its effectiveness and adapt the enterprise to new market conditions, the knowledge about the enterprise system requirements is critically significant.

Each object of the production system has its own requirements, and their fulfillment affect the execution of the production task in general. Accordingly, if there is a necessity to change the system behavior (to increase the effectiveness or production) it is necessary to know which requirements of the system objects must be satisfied for this. As a result of using IDEF9 method, system requirements are specified and cataloged. Thus, it is always possible to check easily how much system requirements are satisfied and correspondingly to change work conditions for gaining the necessary result. By knowing the system requirements it is also possible to explain why at the moment the system works this way and how to improve its work. IDEF9 method is an indispensable tool of a business-engineer, as with its help is it possible to define how the system will work and which requirements will have to be satisfied for the system work accordingly to the project.

Accordingly to IDEF9 method, requirement is a kind of a connection between system parts, which must obligatory exist at the given conditions set (context). The condition is considered as fulfilled if all conditions of its existence in the given context are fulfilled. Requirement is a connection type, which can be established between system objects, between processes, between objects and processes, between processes and objects properties, etc.

Requirements are described by statements. An example of the requirement statement to objects: “Only heads of departments are authorized to sign waybills.” An example of the requirement statement of the process to objects: “Transportations are only allowed in the presence of a signed waybill” or “Credit giving out is only possible at monthly paying off the percents on the credit.” An example of the requirement statement of the process to object properties: “Maximum carrying capacity of the elevator is 500 kg.”

In that way, the system is represented in the view of a set of objects and processes, which have definite requirements for system functioning. Also into the system description the purpose of the work of this system is usually included. This is necessary for definition of only those requirements of objects and processes, which are important for execution of the considered task.
At the system projecting the requirements define which rules, conditions, limitations and necessary connections the project must involve. The production system represents the set of objects, executing one or several functions under the influence of requirements for reaching the preset goal.

Requirements are divided into:

  • Inner (in), which influence inside the system;
  • Outer (on) which influence outside the system or which are managed outside the system;
  • Belonging to the system (of), which belong to the system and are controlled by it;
  • Intersystem (between), which connect systems between each other in the capacity of objects of a big system.

Also the requirements are divided into enabling and limiting in the context of the considered conditions. Surely, limiting requirements are more obvious and become apparent in the form of following problem symptoms: excess costs, low quality, terms increase, etc. Such symptoms are called evidence of existing of the requirements in a system.

The set of opinions, proving the necessity of definition and providing the requirement for system objects is called rationale for the requirement. The consequences of the influence of the requirement on the system are called effects of the requirements. Effects can be direct and indirect, intended and unintended, desirable and undesirable in the framework of the considered context.

It is necessary the sufficient number of evidence of requirements existence, otherwise the requirement will remain undefined. The effective definition of requirements and their management lets quickly identify requirements and react upon the typical industrial problems of requirements, listed below:

  • The cost of the requirement execution exceeds the requirement value;
  • An existing requirement does not correspond to the enterprise purposes anymore;
  • The requirement provokes unforeseen and undesired effects;
  • Objects of the system, responsible for the requirements fulfillment are incapable to provide the requirements fulfillment;
  • The requirement does not have an obvious mechanism of provision.

Also systems overloaded with outdated or inappropriate requirements lose productivity and waste resources on execution of these requirements.

Potential users of IDEF9 method are business owners, organization managers, system projecting and planning specialists and analysts. The knowledge of system requirements may help in Business Process Reengineering (BPR), Total Quality Management (TQM) and in strategic planning..

There is an example of the procedure of definition, confirmation and further improving of the requirement. The given procedure consists of following stages:

  1. Information collection (Collect) – implies the collection of data about the system and getting evidence of the requirement necessity.
  2. Classification (Classify) - definition of system conditions, objects, objects’ properties, processes and connection types.
  3. Hypotheses formation (Hypothesize) – selection of requirements-candidates, based upon received data and evidence.
  4. Requirement realization (Substantiate) – collection of examples for definition of the best requirement-candidate.
  5. Requirement check-up (Challenge) - checking-up of the requirement with the engagement of the interested persons.
  6. Requirement improvement (Refine) – modernizations, checkout, improvement of the requirement and adding details to the requirement characteristics.

Accordingly to IDEF9 method requirements are displayed in the form of visual schemes. Requirements on the schemes are displayed by way of rounded rectangles, objects and processes in the form of rectangles. Connections between objects of the scheme are represented by way of lines. The connection, indicating at obliging circumstances, is represented in the form of a line with the black little circle at the end. There are also used junctions, which are shown on the scheme in the form of squares with the definition of the junction type: &, O, X.

For example there is a following requirement: “An account for payment of consumed electricity must be signed by the head specialist of the power engineering, by the chief accountant and the head of the enterprise.” The corresponding scheme will have the following view:

Here the double-sided rectangle presents the context of a task, the rounded rectangle shows the requirement itself, and rectangles represent objects, which influence on the requirement execution. & junction shows that the requirement needs an influence of all objects, i.e. the account should be signed by each of the three faces.

Analogously it is possible to compose a scheme of the selection of requirements-candidates, a scheme, reflecting requirement effects and a scheme showing which requirements should be executed for reaching the general goal.

An effective management of changes is significantly facilitated by way of definition and documenting of business-requirements. The knowledge about the business-requirements which exist and how they interrelate between each other in the best way is insufficient sometimes. Nevertheless the requirements trigger, manage and bound the behavior of objects of the business-system and affect them so that the final goal is reached with more or less costs of resources and time. IDEF9 method is developed to help with definition and analysis of the requirements.

IDEF9 Standard *

TEN RELATED HOW TO's:

Auditing Process. Audit Planning Process →

Auditing Process, Audit Planning Process - The audit is complex process of independent examination of data, statements, operations, financial performances of an enterprise for a stated purpose. The auditing process consists of defined quantity of audit steps. Planning is fundamental stage of auditing process. The carefully thought-out audit planning process ensures the success of the business project.Auditing Process. <br> Audit Planning Process *
Picture: Auditing Process. Audit Planning Process
Related Solution:

UML Diagram Types List →

Two types of diagrams are used in UML: Structure Diagrams and Behavior Diagrams. Behavior Diagrams represent the processes proceeding in a modeled environment. Structure Diagrams represent the elements that compose the system.UML Diagram Types List *
Picture: UML Diagram Types List
Related Solution:

Flowchart. What is Flowchart →

The Flowcharts have one or more starting and ending points. The geometric figures on the Flowcharts represent the steps of the process and are connected with arrows that show the sequence of the actions. The Flowcharts can be orientated vertically or horizontally. ConceptDraw DIAGRAM is a powerful software for creating professional looking Flowcharts quick and easy. For this purpose you can use the Flowcharts solution from the Diagrams area of ConceptDraw Solution Park.Flowchart. What is Flowchart *
Picture: Flowchart. What is Flowchart
Related Solution:

Interior Design. Machines and Equipment — Design Elements →

Any factory needs a clear scheme of all the equipment used in the manufacture processes. So, if you want to place all your machines and equipment on one diagram, you need a good diagramming tool for that. For instance, you can find all the design elements you might need, such as lathes, milling machines or saws on ConceptDraw DIAGRAM Solution Park in Plant Layout Plans solution in appropriate libraries. This drawing represents the Machines and Equipment library delivered by ConceptDraw Plant Layout Plans solution. This vector library is supplied along with other libraries related to industrial architecture planning and interior design. Just planning the proper facilities in a proper right place, allows to manufacture a product in the most effective and economic way. Objects containing in these libraries will be helpful for architects and engineers dealing with industrial buildings design. They are intended to use for designing layouts of plants, warehouses, manufacturing workshop etc.Machines and Equipment — Design Elements
Picture: Interior Design. Machines and Equipment — Design Elements
Related Solution:

Basic Audit Flowchart. Flowchart Examples →

This sample shows the Audit Process Flowchart. It was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the Flowcharts solution from the Diagrams area of ConceptDraw Solution Park. The Audit Flowcharts are widely used in the financial management, accounting, money management and in many others fields.Basic Audit Flowchart. Flowchart Examples *
Picture: Basic Audit Flowchart. Flowchart Examples
Related Solution:

Account Flowchart. Flowchart Examples →

Create your own flow charts of computer or network system account processing using the ConceptDraw DIAGRAM diagramming and vector drawing software extended with the Cross-Functional Flowcharts solution from the Business Processes area of ConceptDraw Solution Park. The flow chart example shows the computer network system account processing.Account Flowchart. Flowchart Examples *
Picture: Account Flowchart. Flowchart Examples
Related Solution:

Audit Process Flowchart. Audit Flowchart →

Audit Process Flowchart, Audit Flowchart - Audit Flowcharts solution for ConceptDraw DIAGRAM Solution Park provides the Audit Flowcharts library with wide variety of predesigned audit flowchart symbols, and also the set of templates and samples allowing you design your own audit flowchart or audit process flowchart in one moment. Simply use any of offered samples and change it for your needs, or fill the desired template.Audit Process Flowchart. <br> Audit Flowchart *
Picture: Audit Process Flowchart. Audit Flowchart
Related Solution:

Flow Chart Online →

Flow Chart is a great visualization tool for the flow of a process, algorithm or procedure with a lot of benefits. It is convenient to use a powerful software for creating flow charts. Now we have the best flow chart maker online design software - ConceptDraw DIAGRAM enhanced with Flowcharts Solution from the "Diagrams" Area of ConceptDraw Solution Park.Flow Chart Online *
Picture: Flow Chart Online
Related Solution:

ConceptDraw DIAGRAM Comparison with Omnigraffle Professional and MS Visio →

ConceptDraw DIAGRAM Comparison with Omnigraffle Professional and MS Visio. All source ConceptDraw documents are vector graphic documents. They are available for reviewing, modifying, or converting to a variety of formats: PDF file, MS PowerPoint, MS Visio, and many other graphics formats.ConceptDraw DIAGRAM Presentation
Picture: ConceptDraw DIAGRAM Comparison with Omnigraffle Professional and MS Visio
Related Solution:
ConceptDraw
DIAGRAM 15