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 example, idef diagram


Interior Design Piping Plan - Design Elements

When moving to a new apartment it is always pleasure to develop an interior design project. Nevertheless, another important part that should not be forgotten is the piping plan, because wrong piping system might ruin all the renovation. So, to avoid such problems, a stress analysis is performed. Plumbing and piping plans should be created for any premises. They are used to trace location of pipes, fixtures and valves in the house. This diagram presents a set of certified piping plan symbols for drawing plumbing and piping floor plans, diagrams and other technical drawings. Applying standard symbols when creating a piping plan is very important for creating a valid piping plan included into the building documentation pack. It is essential for any professional to be able to read and properly interpreted any piping plan.Interior Design .  Design Elements — Piping Plan
Picture: Interior Design Piping Plan - Design Elements
Related Solution:

Electrical Symbols — Electrical Circuits

A circuit diagram or wiring diagram uses symbols to represent parts of a circuit. Electrical and electronic circuits can be complicated. Making a drawing of the connections to all the component parts in the circuit's load makes it easier to understand how circuit components are connected. Drawings for electronic circuits are called "circuit diagrams". Drawings for electrical circuits are called "wiring diagrams". 26 libraries of the Electrical Engineering Solution of ConceptDraw PRO make your electrical diagramming simple, efficient, and effective. You can simply and quickly drop the ready-to-use objects from libraries into your document to create the electrical diagram.Electrical Symbols — Electrical Circuits
Picture: Electrical Symbols — Electrical Circuits
Related Solution:

ConceptDraw PRO Compatibility with MS Visio

If you ever wanted to try any diagramming tools except of Visio, but were afraid to lose existing documents, there’s good news for you. One of the most striking features of ConceptDraw PRO is it’s perfect compatibility with MS Visio, which guarantees that you won’t depend on operating system anymore, because another ConceptDraw PRO feature is that it’s cross-platform tool. Don’t waste your time looking for other options, you’ve found the solution already! Business professionals often utilize the MS Visio as a common tool for making various issues on business visualization. MS Visio is a strong software with good capacity to maintain complex business solutions. But there is no MS Visio for Apple OS X . This is a large invocation, and one would be pleased to recognize that ConceptDraw PRO is the ideal alternative to MS Visio. Primarily, because this software works natively on both Windows and Apple OS X platforms. if you have migrated from Windows to Mac, or need to communicate in a cross-platform conditions, you’ll search for MS Visio replacer. ConceptDraw PRO is the exclusive professional business diagramming application that runs on both Windows and Apple OS X. The opportunity exchange files between PC and Mac, as well as between ConceptDraw PRO and Visio is the significant advantage that permits you to display and to collaborate business information in effortless and cost-effective way.ConceptDraw PRO Compatibility with MS Visio
Picture: ConceptDraw PRO Compatibility with MS Visio

Types of Welding in Flowchart

This sample was created in ConceptDraw PRO diagramming and vector drawing software using the Flowcharts solution from the What is a Diagram area of ConceptDraw Solution Park. This sample shows the Flowchart that displays the solid-state welding processes, the types of welding.Solid-state welding processes
Picture: Types of Welding in Flowchart
Related Solution:

Campus Area Networks (CAN). Computer and Network Examples

If we divide computer networks by scale, we get several main categories. The smallest network is PAN, as it connects personal devices themselves, and as the number of users grows, a local area network can be recognized, and campus area networks (CAN) connects several local networks located within some area like a university or a corporation. Computers connected to CAN share public educational materials and list of CAN network examples includes such prestigious universities like Stanford and Carnegie Mellon. This is an example of a computer network diagram created for a campus area network. It was created using using ConceptDraw solution for the Computer and Network diagramming. The specific of this sample campus network is its distribution. It is rather broad to embrace a big campus territory. This diagram can be applied as a template for designing custom area network topology diagram for a particular educational institution.Campus Area Network
Picture: Campus Area Networks (CAN). Computer and Network Examples
Related Solution:

Windows Azure

The Microsoft Windows Azure platform is a highly flexible cloud-based solution with variety of services which supports not only the execution of .NET applications, but also allows developers to use programming languages like Java, PHP, Node.js, or Python. ConceptDraw PRO diagramming and vector drawing software provides the Azure Architecture Solution from the Computer and Networks area of ConceptDraw Solution Park with a lot of useful tools which make easier: illustration of Windows Azure possibilities and features, describing Windows Azure Architecture, drawing Azure Architecture Diagrams, depicting Azure Cloud System Architecture, describing Azure management, Azure storage, documenting Azure services.Windows Azure
Picture: Windows Azure
Related Solution:

Process Flowchart

When trying to figure out the nature of the problems occurring within a project, there are many ways to develop such understanding. One of the most common ways to document processes for further improvement is to draw a process flowchart, which depicts the activities of the process arranged in sequential order — this is business process management. ConceptDraw PRO is business process mapping software with impressive range of productivity features for business process management and classic project management. This business process management software is helpful for many purposes from different payment processes, or manufacturing processes to chemical processes. Business process mapping flowcharts helps clarify the actual workflow of different people engaged in the same process. This samples were made with ConceptDraw PRO — business process mapping software for flowcharting and used as classic visio alternative because its briefly named "visio for mac" and for windows, this sort of software named the business process management tools. This flowchart diagram shows a process flow of project management. The diagram that is presented here depicts the project life cycle that is basic for the most of project management methods. Breaking a project into phases allows to track it in the proper manner. Through separation on phases, the total workflow of a project is divided into some foreseeable components, thus making it easier to follow the project status. A project life cycle commonly includes: initiation, definition, design, development and implementation phases. Distinguished method to show parallel and interdependent processes, as well as project life cycle relationships. A flowchart diagram is often used as visual guide to project. For instance, it used by marketing project management software for visualizing stages of marketing activities or as project management workflow tools. Created with ConceptDraw PRO — business process mapping software which is flowcharting visio alternative or shortly its visio for mac, this sort of software platform often named the business process management process flowcharts, flowchart symbols, process flow diagram, workflow diagram, flowchart maker
Picture: Process Flowchart
Related Solution:

Hotel Plan. Hotel Plan Examples

Solution Building Plans from ConceptDraw Solution Park provides vector stencils libraries with design elements of interior, furniture and equipment for drawing hotel plans and space layouts.

Use ConceptDraw PRO diagramming and vector drawing software enhanced with Building Plans solution to draw your own site and floor plans, design and layouts.Hotel Plan

Picture: Hotel Plan. Hotel Plan Examples
Related Solution:

Data Flow Diagram Software

When studying a business process or system that involves the transfer of data, it is common to use a data flow diagram (DFD) to visualize how that data is processed. While initially used exclusively in regards to the flow of data through a computer system, DFDs are now employed as a business modelling tool, describing business events and interactions, or physical systems involving data storage and transfer. ConceptDraw PRO is a powerful Data Flow Diagram Software thanks to the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park. You can use the predesigned DFD vector objects that are grouped in 3 libraries of Data Flow Diagrams solution: Data Flow Diagrams Library; Gane-Sarson Notation Library; Yourdon and Coad Notation Library.Data Flow Diagram Software
Picture: Data Flow Diagram Software
Related Solution:

Six Markets Model Chart

This sample shows the Six Markets Model Chart. It was created in ConceptDraw PRO diagramming and vector drawing software using the Marketing Diagrams Solution from the Marketing area of ConceptDraw Solution Park. The six markets model defines six markets that take the central place in the relationship marketing: internal markets, supplier markets, recruitment markets, referral markets, influence markets and customer markets. The six markets model allows the organization to analyze the stakeholders and key market domains that can be important to it.Six Markets Model Chart
Picture: Six Markets Model Chart
Related Solution:
1 Diagram Software
Professional business graphics tool for drawing schemes, diagrams and illustrating business documentation
1 Mind Map Software
Excellent tool for Mind Mapping, Planning, Brainstorming, and Building Processes
1 Project Management Software
The full complement of features needed to successfully plan and execute projects, including task and resource management, reporting, and change control