 | This article has multiple issues. Please help improve it or discuss these issues on the talk page . (Learn how and when to remove these template messages)
|
In organization development, the initial phase within the Cognitive work analysis (CWA) framework is Work Domain Analysis. It provides a description of the constraints that govern the purpose and the function of the systems under analysis.
The Abstraction Hierarchy[ clarification needed ] (Rasmussen, 1985; Vicente, 1999 [1] ) is used to provide a context-independent description of the domain[ clarification needed ]. The analyses, and resultant diagrams, are not specific to any particular technology; rather they represent the entire domain.
Through a series of ‘means-ends’ links, it is possible to model how individual components can affect the overall domain purpose. The abstraction hierarchy is constructed by considering the work system's objectives (top-down) and the work system's capabilities (bottom-up). The diagram is constructed based upon a range of data collection opportunities. The exact data collection procedure is dependent on the domain in question and the availability of data. In most cases, the procedure commences with some form of document analysis. Document analysis allows the analyst to gain a basic domain understanding, forming the basis for semi-structured interviews with domain experts. Wherever possible, observation of the work in context is highly recommended.
The abstraction hierarchy consists of five levels of abstraction, ranging from the most abstract level of purposes to the most concrete level of form (Vicente, 1999). The levels are normally called
The labels used for each of the levels of the hierarchy tend to differ, dependent on the aims of the analysis. Below, the labels used by Xiao et al. [4] are shown.
The structure of the abstraction hierarchy framework acts as a guide to acquiring the knowledge necessary to understand the domain. The framework helps to direct the search for deep knowledge, providing structure to the document analysis process, particularly for the domain novice. While the output may initially appear overbearing, its value to the analysis cannot be overstated. The abstraction hierarchy defines the systemic constraints at the highest level.
One of the advantages of the abstraction hierarchy model is that it can be used to explore the effect of new technology on the system values and purposes. Additional technologies can be modelled at the base of the model and their effect assessed through the mean-ends links to the top of the diagram.
In software engineering and computer science, abstraction is the process of generalizing concrete details, such as attributes, away from the study of objects and systems to focus attention on details of greater importance. Abstraction is a fundamental concept in computer science and software engineering, especially within the object-oriented programming paradigm. Examples of this include:
A data model is an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities. For instance, a data model may specify that the data element representing a car be composed of a number of other elements which, in turn, represent the color and size of the car and define its owner.
Software design is the process of conceptualizing how a software system will work before it is implemented or modified. Software design also refers to the direct result of the design process – the concepts of how the software will work which consists of both design documentation and undocumented concepts.
A modeling language is any artificial language that can be used to express data, information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure of a programming language.
Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model Driven Architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.
In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.
An entity–relationship model describes interrelated things of interest in a specific domain of knowledge. A basic ER model is composed of entity types and specifies relationships that can exist between entities.
Business process modeling (BPM), mainly used in business process management; software development, or systems engineering, is the action of capturing and representing processes of an enterprise, so that the current business processes may be analyzed, applied securely and consistently, improved, and automated. BPM is typically orchestrated by business analysts, leveraging their expertise in modeling practices. Subject matter experts, equipped with specialized knowledge of the processes being modeled, often collaborate within these teams. Alternatively, process models can be directly derived from digital traces within IT systems, such as event logs, utilizing process mining tools.
The term conceptual model refers to any model that is formed after a conceptualization or generalization process. Conceptual models are often abstractions of things in the real world, whether physical or social. Semantic studies are relevant to various stages of concept formation. Semantics is fundamentally a study of concepts, the meaning that thinking beings give to various elements of their experience.
Object-oriented analysis and design (OOAD) is a technical approach for analyzing and designing an application, system, or business by applying object-oriented programming, as well as using visual modeling throughout the software development process to guide stakeholder communication and product quality.
Integration DEFinition for information modeling (IDEF1X) is a data modeling language for the development of semantic data models. IDEF1X is used to produce a graphical information model which represents the structure and semantics of information within an environment or system.
Ecological interface design (EID) is an approach to interface design that was introduced specifically for complex sociotechnical, real-time, and dynamic systems. It has been applied in a variety of domains including process control, aviation, and medicine.
Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.
The DIKW pyramid, also known variously as the DIKW hierarchy, wisdom hierarchy, knowledge hierarchy, information hierarchy, information pyramid, and the data pyramid, refers to a class of models representing purported structural or functional relationships between data, information, knowledge, and wisdom. It claims that deep understanding of a subject emerges through four qualitative stages: data, information, knowledge, and wisdom
In systems engineering, software engineering, and computer science, a function model or functional model is a structured representation of the functions within the modeled system or subject area.
A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.
Analytica is a visual software developed by Lumina Decision Systems for creating, analyzing and communicating quantitative decision models. It combines hierarchical influence diagrams for visual creation and view of models, intelligent arrays for working with multidimensional data, Monte Carlo simulation for analyzing risk and uncertainty, and optimization, including linear and nonlinear programming. Its design is based on ideas from the field of decision analysis. As a computer language, it combines a declarative (non-procedural) structure for referential transparency, array abstraction, and automatic dependency maintenance for efficient sequencing of computation.
Cognitive work analysis (CWA) is a framework that was developed to model a complex sociotechnical system.
Multilevel Flow Modeling (MFM) is a framework for modeling industrial processes.
A function analysis diagram (FAD) is a method used in engineering design to model and visualize the functions and interactions between components of a system or product. It represents the functional relationships through a diagram consisting of blocks, which represent physical components, and labeled relations/arrows between them, which represent useful or harmful functional interactions.
