IDEF4 Standard

The development of the object-oriented programming significantly facilitated the process of software development. Nevertheless the development of software with good design, reliability, modularity and usability is still problematic. IDEF4 standard was developed for correct usage of object-oriented technologies. Accordingly to IDEF4 standard, the object-oriented process is represented with the help of diagrams, which helps to analyze this process and to discover its key points. The particularity of IDEF4 standard is the representation possibility of the influence of classes’ heredity, objects composition, functional decomposition and polymorphism on the object projecting.

The process of object-oriented projecting by IDEF4 method is divided into separate blocks.
Each subrun has notations, which indicate which decision should be accepted during the projecting process and how it will influence on other subruns. By IDEF4 standard the common diagram, describing the whole project, is not developed. This allows to avoid confusion and quickly find the necessary information on the project. IDEF4 standard lets the planner easily find compromises between classes’ heredity, objects composition, functional decomposition and polymorphism in the project.

IDEF4 model consists of 2 submodels: model of classes and model of methods. These submodels are connected between each other with the help of a distribution scheme and contain the whole information on the project. Because of classes’ subruns sizes and methods the planner never uses them as a whole, using a set of simpler diagrams and specifications which contain the part of information.

A submodel of classes consists of the following diagram types:

  • Diagrams of heredity, which define the heredity of classes;
  • Diagrams of types, which define the composition of classes;
  • Diagrams of protocols, which define protocols of methods call;
  • Diagrams of objects creation (Instantiation), which describes the process of creation of exemplars of the preset classes’ objects.

A submodel of classes consists of following diagrams:

  • Diagrams of methods systematization (Method taxonomy), which classify methods by behavior similarity;
  • Diagrams of clients, which represent clients and operations suppliers, so that to define the functional decomposition.
IDEF4 model example

The diagram of heredity represents hereditary ties between classes. For example, at the picture below the structure of heredity and Filled Rectangle class behavior is shown.

Diagrams of protocols define arguments of classes for protocols call. At the picture below the diagram of a protocol for Fill-closed-object is shown.

It is obvious from the diagram that Fill-closed-object gets requests from Polygon object (primary argument) and Color object (secondary argument) and returns the request to Polygon object.

Diagrams of objects creation come into diagrams of types and describe possible situations at composition of ties between created objects..

The diagram of methods systematization describes specific type of system behavior at the influence on the set of methods. Arrows on the diagram point at additional influences, done at the sets of methods. The sets of methods are grouped accordingly to additional obligatory conditions. At the example given below the set of methods ‘Print’ has an obligatory condition that the object must be printed and the set of methods ‘Print-Text’ – that the printed object must be a text.

Diagrams of clients represent clients and operations suppliers. Double arrows on the diagram point from the called operation to the calling operation. At the example given below a diagram of clients is shown. On this diagram the Redisplay operation which belongs to Redisplayable-object class calls the Erase operation of the Erasable-object class and the Draw operation of the Drawable-object class.

IDEF4 standard implies not only graphical presentation but the additional information about diagrams of heredity, methods systematization and types which are contained in specifications. Accordingly to IDEF4 standard there are specifications of invariant classes and specifications of obligatory conditions. Specifications of invariant classes are connected with diagrams of heredity and define influences which form properties of each concrete class of objects. For each class there exists a separate specification. For instance, the properties “Each square has four sides” and “All square sides are equal” are the properties of specification of the Square class.

Specifications of obligatory conditions are connected with sets of methods in diagrams of methods systematization and define obligatory conditions, which influence on methods and which methods should satisfy. For each set of methods there is one specification of obligatory conditions. For example the set of methods ‘Pop’, which deletes values from the stack, as obligatory condition will have the absence of attempts to delete the value from the stack if the stack is empty.

IDEF 4 standard is developed by professional planners and programmers of the U.S. Air Force Armstrong Laboratory and is intended to facilitate the usage of object-oriented technologies at software development.



TEN RELATED HOW TO's:

LLNL Flow Charts

These flow charts help scientists analysts and other decision makers to visualize the complex interrelationships involved in managing our nation x2019.LLNL flow charts
Picture: LLNL Flow Charts

Chemistry Drawing Software

ConceptDraw PRO extended with Chemistry solution from the Science and Education area is a powerful chemistry drawing software that provides the useful tools to help you design all kinds of chemistry drawings and illustrations, chemical schemes and diagrams of formulas, reaction schemes and lab set-ups of any complexity.Chemistry Drawing Software
Picture: Chemistry Drawing Software
Related Solution:

UML Diagram for System

This sample shows the UML Class Diagram of delivery system. On this diagram you can see the classes that are connected with aggregation and composition associations indicated with the multiplicity. This sample can be used by delivery services, postal services.UML Diagram for System
Picture: UML Diagram for System
Related Solution:

Diagrama de Topologia

PRO is a powerful drawing tool that changes the way diagrams are produced. ConceptDraw Arrows10 Technology - This is more than enough versatility to draw any type of diagram with any degree of complexity. Diagrama de Topologia or Topology Diagram helps you see the big picture as you develop a service.Amazon Web Services (AWS) diagram - 3 Tier auto scalable Web application architecture
Picture: Diagrama de Topologia

Draw Fishbone Diagram on MAC Software

This method of problem analysis is widely used in IT, manufacture industries and chemical engineering. If you want to take a fresh look on your problem, you can draw a fishbone diagram with ConceptDraw PRO software, which supports both MAC OS and Windows. You can see and download fishbone diagram samples and templates in ConceptDraw Solution Park. This Fishbone (Ishikawa) diagram can be applied as template for performing the cause and effect analysis of a service industry problems. It can help to determine factors causing problems. Causes in this diagram are categorized according to the 4S’s principle that means Surroundings, Suppliers, Systems and Skills. Grouping causes allows to reveal main interactions between different events. This diagram was made using ConceptDraw Fishbone diagrams solution. It can help to reveal the causes effected a complicated issue. Of course it can be used together with other methods of approaching to the problem solving.Draw Fishbone Diagram on MAC Software
Picture: Draw Fishbone Diagram on MAC Software
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:

Accounting Flowchart Symbols

It doesn’t matter what kind of business you have, a bar or a gym, there are common concepts for any of them. One of those concepts is accounting, and to facilitate the work with the figures, you can use accounting flowchart symbols and create a clear and representative scheme. You can create flowchart for auditing, tax accounting and even for planning your own budget. A graphical tool for displaying successive processes is flowchart. This method is mostly suited to represent an accounting process. The sequence of steps in the accounting process usually consists of standard accounting procedures, that can be depicted by using a minimal number of symbols, applied for the basic flowcharting. The advanced opportunity to create professional Accounting Flow charts is provided by ConceptDraw Accounting Flowcharts solution. It includes contains a library of accounting flowchart symbols used when drawing the accounting process flow.Accounting Flowchart Symbols
Picture: Accounting Flowchart Symbols
Related Solution:

Types of Flowcharts

A flowchart is a simple but very functional tool when it comes to understanding a workflow or to removing unnecessary stages from a process. When drawing flowcharts, keep in mind that there are four common types of flowcharts, like document flowcharts and data flowcharts that show control over a data or document flow over a system. To show controls on a physical level, use system flowcharts. In addition, to show controls in a program, you can draw a program flowchart. This flowchart diagram represents the piece of an article editing process, that involves the author and editor. It was created using the Basic Flowchart notation that consists from the basic flowchart symbols. The start and the end of the process are indicated with "Terminator" symbols. The "Process" symbols show the action steps consisting from making edits and searching for a compromise, when the author does not agree with the suggestions of the editor . The "Process" symbol is the general symbol in process flowcharts. The "Decision" symbol indicates a branching in the process flow. There are two branches indicated by a Decision shape in the current flowchart (Yes/No, Disagree/Agree). This basic flowchart can be used as a repeating unit in the workflow diagram describing the working process of some editorial office.Types of Flowcharts
Picture: Types of Flowcharts
Related Solution:

Collaboration in a Project Team

Create with our data flow diagram software perfect data flow diagrams. Download data flow diagram software for FREE. Use hundreds of data flow diagram examples.Advantages of Team-Work: Project
Picture: Collaboration in a Project Team

Network Diagramming Software for DesignRack Diagrams

Rack Diagrams visualize the rack mounting of computer and network equipment as the drawing of frontal view of the rack with equipment installed. They are used for choosing the equipment or racks to buy, and help to organize equipment on the racks virtually, without the real installation. Network Diagramming Software - ConceptDraw PRO is perfect for software designers and software developers who need to draw Rack Diagrams.Network Diagramming Software, Design Elements — Network Layout (Windows, Macintosh)
Picture: Network Diagramming Software for DesignRack Diagrams
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