Made with

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 Standard *

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.


Biology Symbols →

ConceptDraw DIAGRAM diagramming and vector drawing software extended with Biology solution from the Science and Education area offers a set of useful tools for fast and easy drawing of various biology illustrations and drawings.

Biology solution provides 3 libraries with large quantity of vector biology symbols: Biochemistry of Metabolism Library, Carbohydrate Metabolism Library, Citric Acid Cycle (TCA Cycle) Library.Biology Symbols *

Picture: Biology Symbols
Related Solution:

DFD Flowchart Symbols →

A Data Flow Diagram (DFD) is a graphical technique which allows effectively model and analyze the information processes and systems. The ability to fast and easy create the DFDs is made possible with Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park. For designing the Data Flow Diagrams are used simple DFD flowchart symbols which are connected each other by arrows depicting the data flow from one step to another.DFD Flowchart Symbols *
Picture: DFD Flowchart Symbols
Related Solution:

Financial Comparison Chart →

This sample shows the Bar Chart of the leverage ratios for two major investment banks. The leverage ratio is the ratio of the total debt to the total equity; it is a measure of the risk taken by the bank. The higher of the leverage ratio denotes the more risk, the greater risks can lead to the subprime crisis.Financial Comparison Chart *
Picture: Financial Comparison Chart
Related Solution:

Basketball Court Dimensions →

Outdoor activities are a very important part of leisure. Although standard basketball court dimensions are strict, you can do something to set a court even in your yard. With ConceptDraw DIAGRAM you can develop a plan to see how a basketball court is going to fit in your yard. The favorite method of basketball coaches is visualization. For learning, for disassembly of played matches or for planning the strategy of the coming games - they always use a picture of basketball courts. Such schematically picture should have scale and should depict precisely standard equipment and dimensions of the basketball court. The Basketball solution for ConceptDraw DIAGRAM was developed as a tool for drawing different basketball schemes and illustrations.Basketball Court Dimensions
Picture: Basketball Court Dimensions
Related Solution:

Stakeholder Onion Diagrams →

The Stakeholder Onion Diagram is a popular and widely used way to view the relationships of stakeholders to a project goal. The Onion Diagram focuses on the project goal, most of other diagram styles focus on the project, stakeholders, and timeline. This difference favorably distinguishes and separates the Onion Diagram from other types of diagrams. Design fast and easy Stakeholder Onion Diagrams of any complexity in ConceptDraw DIAGRAM diagramming and vector drawing software using the powerful tools of Stakeholder Onion Diagrams Solution from the Management Area of ConceptDraw Solution Park.Stakeholder Onion Diagrams *
Picture: Stakeholder Onion Diagrams
Related Solution:

Hybrid Network Topology →

Every corporate network is unique, though there are guidelines and best practices in developing networks. As it is quite difficult to implement a pure topology within a company, using a hybrid network topology is considered a better solution. As a rule, such network assembles advantages and features of source topologies. This diagram is an example of the Hybrid network. This type of network topology means a conjunction of other network topologies. Such as star-bus, ring-mesh topologies, etc. It should be obviously diverse networks. The final computer network inherits both advantages and disadvantages of its ingredients. Using the ConceptDraw Computer and Networks solution including vector graphic libraries and templates one can develop professional custom network diagrams of any topology and complexity.Hybrid Network Topology *
Picture: Hybrid Network Topology
Related Solution:

Onion Diagram as Stakeholder Mapping Tool →

Stakeholders are the groups of people or organizations whose contribution matters to the organization's success, this can be labour participation, financial participation, dissemination of information about organization, etc. So, the employees of the company, its suppliers, customers, media, public organizations, state authorities, all they are stakeholders of the company. ConceptDraw DIAGRAM diagramming and vector drawing software extended with Stakeholder Onion Diagrams Solution from the Management Area of ConceptDraw Solution Park is a powerful stakeholder mapping tool which allows easy create Stakeholder Onion diagrams and maps depicting the layers of a project, relationships of stakeholders to a project goal, and relationships between stakeholders.Onion Diagram as Stakeholder Mapping Tool
Picture: Onion Diagram as Stakeholder Mapping Tool
Related Solution:

Basic Diagramming. Flowchart Software →

Create flowcharts, flow charts, and more with ConceptDraw flowchart software.Basic Diagramming *
Picture: Basic Diagramming. Flowchart Software
Related Solution:

Network Topologies →

When describing any computer network, we imagine a set of devices and nodes, arranged in some way. Talking about network structures, we should distinguish physical and logical network topologies, as physical topology is about devices location and logical topology illustrates data flow. In the same time, they do not have to match, and some devices, such as repeaters, may have a physical star layout, but a bus logical topology. There are two main types of computer network topologies: Physical topology that show the physical organization of a network - equipment and types of connections. Star network topology involves a set of devices that is connected to a single hub (router). Ring network topology means that, devices connected according this topology have two connections, connecting with nearby devices to make a loop. Bus network topology is the topology presented at the current diagram. It is similar to a ring topology. The difference is that data moves up and down a linear connection, copying itself where network equipment works as bus-stations along the way. This network topology can be used for small network, or when adding an extra device into a network.Network Topologies
Picture: Network Topologies
Related Solution: