Made with
ConceptDraw
DIAGRAM 15

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.



TEN RELATED HOW TO's:

Wiring Diagrams with ConceptDraw DIAGRAM →

It is important to have an electrical circuits scheme, when you plan a renovation or move to a new apartment. You have to arrange interior according to that plan, and it’s trouble-free to create wiring diagrams with ConceptDraw DIAGRAM , furthermore, this software has all the features needed to create an interior plan as well. So, get inspired by tons of examples included to ConceptDraw DIAGRAM solutions, and start your diagramming experience! A wiring diagrams, that are represented on this drawing was created to depict the components of the electrical circuit schemes. These diagrams are created to depict the information about circuit arrangements and connections. Wiring diagrams, in contrast to physical drawings, use standard symbol's notation to depict different circuit devices and connections. That is why, wiring diagrams are applied to discover and repair electrical and electronic circuits. The vector graphic objects provided by ConceptDraw Electrical Engineering solution can help any specialist in electric engineering to design electrical schemes, circuit and wiring plans, power systems charts, and Maintenance and Repair diagrams.Wiring Diagrams with ConceptDraw DIAGRAM
Picture: Wiring Diagrams with ConceptDraw DIAGRAM
Related Solution:

Network Diagramming Software for Design Network Layout Diagrams →

ConceptDraw DIAGRAM is perfect for software designers and software developers who need to draw Network Layout Diagrams.Network Diagramming Software for Design  <br>Network Layout Diagrams *
Picture: Network Diagramming Software for Design Network Layout Diagrams
Related Solution:

Sales Process Flowchart. Flowchart Examples →

Process mapping helps with sharing business results and reorganizing workflow. In almost every case, after creating a sales process flowchart the steps that are redundant become obvious for a manager. It's easy to find a flowchart examples that will help in developing one for your business. This sales process flowchart consists of a sequence of steps that represent a simple sale process. Each step is shown graphically by a rectangle representing processing steps or an activity, or a diamond representing a decision. These rectangles are linked by arrows, that indicate the direction of the sales workflow. ConceptDraw Sales Flowcharts solution delivers a the full set of classical flowchart notation symbols, along with sales-related icons and pictograms.Sales Process Flowchart. <br>Flowchart Examples *
Picture: Sales Process Flowchart. Flowchart Examples
Related Solutions:

UML Use Case Diagram Example. Social Networking Sites Project →

UML Diagrams Social Networking Sites Project. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Use Case Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the Facebook Socio-health system and is used at the projection and creating of the social networking sites.UML Use Case Diagram Example. Social Networking Sites Project
Picture: UML Use Case Diagram Example. Social Networking Sites Project
Related Solution:

UML Use Case Diagram Example - Estate Agency →

UML Diagram Estate Agency. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Use Case Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the work of the estate agency and is used by the estate agencies, building companies, at the trainings of the estate agencies, for understanding the working processes of the estate agencies.UML Use Case Diagram Example - Estate Agency *
Picture: UML Use Case Diagram Example - Estate Agency
Related Solution:

Six Markets Model Chart →

This sample shows the Six Markets Model Chart. It was created in ConceptDraw DIAGRAM 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:

UML Diagram →

While developing software, it is very important to have a visual model, because it helps to represent the logic and the architecture of an application. Experienced engineers use UML diagrams to denote relationships between classes and their instances. UML is a general language for a set of diagrams like deployment diagrams, object diagrams or use case diagrams. This diagram represents UML class diagram used for a software system development using an object-oriented method. Class diagrams are categorized as static structure diagrams that depict the physical structure of a system. Class diagram divides a software system's structure into "classes". Classes are defined by the methods and variables of objects. UML Class diagram is used to depict relationships and source code dependencies between objects.UML Diagram *
Picture: UML Diagram
Related Solution:

ER Diagram Styles →

When creating ER diagrams, you can apply different color ER diagram styles and also notation styles. ConceptDraw DIAGRAM enhanced with Entity-Relationship Diagram (ERD) Solution gives the ability to draw visual and attractive ER Diagrams using the style icons from Crow’s Foot notation and Chen's notation professionally designed and offered by ERD Chen's Notation and ERD Crow’s Foot Notation libraries.ER Diagram Styles *
Picture: ER Diagram Styles
Related Solution:
ConceptDraw
DIAGRAM 15