Method Reports and White Papers Downloads 

IDEFØ Method Report

IDEFØ is a method designed to model the decisions, actions, and activities of an organization or system. IDEFØ was derived from a well-established graphical language, the Structured Analysis and Design Technique (SADT). The United States Air Force commissioned the developers of SADT to develop a function modeling method for analyzing and communicating the functional perspective of a system. Effective IDEFØ models help to organize the analysis of a system and to promote good communication between the analyst and the customer. IDEFØ is useful in establishing the scope of an analysis, especially for a functional analysis. As a communication tool, IDEFØ enhances domain expert involvement and consensus decision-making through simplified graphical devices. As an analysis tool, IDEFØ assists the modeler in identifying what functions are performed, what is needed to perform those functions, what the current system does right, and what the current system does wrong. Thus, IDEFØ models are often created as one of the first tasks of a system development effort.

IDEF1 Method Report

IDEF1 was designed as a method for both analysis and communication in the establishment of requirements. IDEF1 is generally used to 1) identify what information is currently managed in the organization, 2) determine which of the problems identified during the needs analysis are caused by lack of management of appropriate information, and 3) specify what information will be managed in the TO-BE implementation.

IDEF1X Method Report

IDEF1X is a method for designing relational databases with a syntax designed to support the semantic constructs necessary in developing a conceptual schema. A conceptual schema is a single integrated definition of the enterprise data that is unbiased toward any single application and independent of its access and physical storage. Because it is a design method, IDEF1X is not particularly suited to serve as an AS-IS analysis tool, although it is often used in that capacity as an alternative to IDEF1. IDEF1X is most useful for logical database design after the information requirements are known and the decision to implement a relational database has been made. Hence, the IDEF1X system perspective is focused on the actual data elements in a relational database. If the target system is not a relational system, for example, an object-oriented system, IDEF1X is not the best method.

IDEF3 Method Report

The IDEF3 Process Description Capture Method provides a mechanism for collecting and documenting processes. IDEF3 captures precedence and causality relations between situations and events in a form natural to domain experts by providing a structured method for expressing knowledge about how a system, process, or organization works.

IDEF4 Method Report

The intuitive nature of object-oriented programming makes it easier to produce code. Unfortunately, the ease with which software is produced also makes it easier to create software of poor design, resulting in systems lacking re-usability, modularity, and maintainability. The IDEF4 method is designed to assist in the correct application of this technology.

IDEF5 Method Report

Historically, ontologies arose from the branch of philosophy known as metaphysics, which deals with the nature of reality–of what exists. The traditional goal of ontological inquiry, in particular, is to divide the world “at its joints,” to discover those fundamental categories or kinds that define the objects of the world. So viewed, natural science provides an excellent example of ontological inquiry. For example, a goal of subatomic physics is to develop a taxonomy of the most basic kinds of objects that exist within the physical world (e.g., protons, electrons, muons). Similarly, the biological sciences seek to categorize and describe the various kinds of living organisms that populate the planet.

IICE White Paper

For all the rapid advances in computer hardware and specific software technology, enterprise engineering, reengineering, and enterprise integration efforts continue to lack effective, widely understood methods for engineering large-scale information systems. Diverse methods are needed to engineer systems that exhibit desirable life-cycle characteristics (e.g., flexibility, responsiveness, scalability, maintainability, ease of use, integration, performance) and for engaging teams of people in critical life-cycle system development activities. Integration Definition (IDEF) methods, a key product of the IICE program, provide easy-touse techniques and standard languages of communication that promote good engineering discipline. This report summarizes new IDEF developments toward establishing reliable methods for business constraint discovery (IDEF9), design rationale capture (IDEF6), humansystem interaction design (IDEF8), and network design (IDEF14). For each method, the conceptual foundations, relevance, issues, and recommended follow-on development activities are discussed.

BPR White Paper

This chapter presents an approach to BPR that is focused on achieving results from the first stages to implementation. The engineering approach presented utilizes an integrated set of methods applied incrementally. This allows BPR practitioners to more realistically approach a project; assess its impact, duration, and required budget; and mitigate the risks of failure. We present the approach as a phased BPR methodology along with methods, proven strategies, and tools we have worked with successfully at each phase. We present motivations for initiating a BPR effort that have been shown to result in successful cases for action. We present rationale for justifying change and a method for building a business case that includes the use of cost benefit analysis in formulating the justification rationale. An approach to planning for a BPR effort is presented that uses the same methods normally applied in the BPR process itself. We cover the issues associated with setting up a BPR project including: forming cross-functional teams, and selecting method and tool technology for the BPR project. A methodology is presented for base-lining the current business situation, identifying the current value delivery system and the processes that support that system along with problem-cause analysis. We describe eight general principles of business process design and conclude with an object centered technique for new process design. Finally this chapter addresses key issues in the implementation process starting with transition planning activities, model driven information system development, and initiation of a learning system that will carry the results forward in a continuous improvement manner.

IDEF9 Method Report

Policies, rules, conventions, procedures, contracts, agreements, regulations, societal and physical laws are the defining structure for an enterprise. These items forge relationships between people, information, material, and machines to make a system. In this report, we refer collectively to these items as constraints. Constraints initiate, enable, govern, and limit the behavior of objects and agents to accomplish the goals or purposes of a system. If we want to change the behavior of a system for whatever reason (e.g., improve its performance, efficiency, or effectiveness) we need to know what the relevant constraints are. However, the collection of constraints that forge an enterprise system is generally poorly defined. That is to say, the knowledge of what constraints exists and how those constraints interact is at best incomplete, disjoint, distributed, and often completely unknown. The IDEF9 Business Constraint Discovery method described in this report was designed to assist in the discovery and analysis of constraints in a business system. Once these constraints have been cataloged they can be systematically examined and, if necessary, tuned or replaced to improve the performance of the system.

IDFFAMI Method Report

In today’s environment, system implementors in Corporate Information Management (CIM), Concurrent Engineering (CE), and Computer Integrated Manufacturing face two overwhelming challenges. Besides their primary responsibility for introducing a new system into their engineering and manufacturing organizations, they also have an underlying need to introduce a new system of processes for developing these implementations. These new system development processes must employ an integrated framework of modeling methods. That is, the development process uses a structured collection of methods, rules, procedures, and tools to support the development and evolution of systems. The framework guides the user in applying the appropriate method within the system development life-cycle. The goal of this paper is to provide some insight into the purpose of modeling, particularly from the perspective of a CIM or CE project manager/engineer who must select, use, and evaluate the results of modeling efforts in support of systems development.