Made with
ConceptDraw
DIAGRAM 16

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.



NINE RELATED HOW TO's:

UML Diagram of Parking →

This sample shows the Use Case Diagram of parking lot control system. On this sample you can see use cases represented as ovals and three actors represented as figures of persons that employ these use cases. Associations between actors and use cases are shown as lines. UML Diagram of Parking - This diagram can be used for understanding the process of working the car parking, at the projection and construction the parking by building companies and for automation the existing parkings.UML Diagram of Parking *
Picture: UML Diagram of Parking
Related Solution:

UML Class Diagrams. ConceptDraw DIAGRAM - Diagramming Software for Design UML Diagrams →

In software engineering, a UML Class Diagrams is a type of static structure diagram that is used both for general conceptual modeling of the systematics of the application, and for detailed modeling translating the models into programming code. Use ConceptDraw DIAGRAM with UML class diagram templates, samples and stencil library from Rapid UML solution to show the classes of system, their attributes, operations or methods, and the relationships among the classes.UML Class Diagrams. Diagramming Software for Design UML Diagrams *
Picture: UML Class Diagrams. ConceptDraw DIAGRAM - Diagramming Software for Design UML Diagrams
Related Solution:

Integration Definition →

Creation of various types of Integration DEFinition (IDEF) diagrams - IDEF0, IDEF1X, IDEF2, IDEF3 and many other is a sufficiently complex process that requires powerful automated tools. ConceptDraw DIAGRAM diagramming and vector drawing software offers you such tool - IDEF Business Process Diagrams solution from the Business Processes area of ConceptDraw Solution Park.Integration Definition *
Picture: Integration Definition
Related Solution:

Cloud Computing Architecture Diagrams →

For documenting the Cloud Computing Architecture with a goal to facilitate the communication between stakeholders are successfully used the Cloud Computing Architecture diagrams. It is convenient and easy to draw various Cloud Computing Architecture diagrams in ConceptDraw DIAGRAM software with help of tools of the Cloud Computing Diagrams Solution from the Computer and Networks Area of ConceptDraw Solution Park.Cloud Computing Architecture Diagrams *
Picture: Cloud Computing Architecture Diagrams
Related Solution:

Taxi Service Data Flow DiagramDFD Example →

This sample shows the Data Flow Diagram of the Taxi Service and interactions between the Clients, Operators and Divers, as well as Orders and Reports databases.Taxi Service Data Flow Diagram<br>DFD Example *
Picture: Taxi Service Data Flow DiagramDFD Example
Related Solution:

Metropolitan area networks (MAN). Computer and Network Examples →

A list of parameters on which networks differ is very long. A large network with a range up to 50 kilometers is called metropolitan area network (MAN), and this type of network can include several local area networks. Metropolitan networks in their turn connect into global area networks. Here you will see a Metropolitan Area Network (MAN). This is an extensive network which occupies a large territory including a few buildings or even the whole city. The space of the MAN is bigger than LAN, but lower than WAN. MAN comprise a lot of communication equipment and delivers the Internet connection to the LANs in the city area. Computer and Networks solution for ConceptDraw DIAGRAM provides a set of libraries with ready-to-use vector objects to design various kinds of computer networks.Metropolitan area networks (MAN). Computer and Network Examples
Picture: Metropolitan area networks (MAN). Computer and Network Examples
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 16