Axiomatic product sevelopment lifecycle (APDL), also known as transdisciplinary system development lifecycle (TSDL) and transdisciplinary product development lifecycle (TPDL), is a

systems engineering Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their Enterprise life cycle, life cycles. At its core, systems engineering uti ...

product development New product development (NPD) or product development in business and engineering covers the complete process of launching a new product to the market. Product development also includes the renewal of an existing product and introducing a product ...

model proposed by Bulent Gumus that extends the Axiomatic design (AD) method.Suh (1990). ''The Principles of Design'', Oxford University Press, 1990, APDL covers the whole

product lifecycle In Industry (economics), industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from its inception through the Product engineering, engineering, Product design, design, and Manufacturing, ma ...

including early factors that affect the entire cycle such as development testing, input constraints and system components. APDL provides an iterative and incremental way for a team of transdisciplinary members to approach

holistic Holism is the interdisciplinary idea that systems possess properties as wholes apart from the properties of their component parts. Julian Tudor Hart (2010''The Political Economy of Health Care''pp.106, 258 The aphorism "The whole is greater than t ...

product development. A practical outcome includes capturing and managing product design knowledge. The APDL model addresses some weak

patterns A pattern is a regularity in the world, in human-made design, or in abstract ideas. As such, the elements of a pattern repeat in a predictable manner. A geometric pattern is a kind of pattern formed of geometric shapes and typically repeated li ...

experienced in previous development models regarding quality of the design,

requirements management Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requ ...

change management Change management (CM) is a discipline that focuses on managing changes within an organization. Change management involves implementing approaches to prepare and support individuals, teams, and leaders in making organizational change. Change mana ...

project management Project management is the process of supervising the work of a Project team, team to achieve all project goals within the given constraints. This information is usually described in project initiation documentation, project documentation, crea ...

, and communication between stakeholders. Practicing APDL may reduce development time and project cost.

Overview

APDL adds the Test domain and four new characteristics to Axiomatic design (AD): Input Constraints in the Functional Domain; Systems Components in the Physical Domain; Process Variables tied to System Components instead of Design Parameters; and Customer Needs mapped to Functional Requirements and Input Constraints. APDL proposes a V-shaped process to develop the Design Parameters and System Components (detailed design). Start top-down with Process Variables (PV) and Component Test Cases (CTC) to complete the PV, CTC, and Functional Test Cases (FTC); And after build, test the product with a bottom-up approach.

APDL Domains

;Customer domain Customer Needs (CN) are elements that the customer seeks in a product or system. ;Functional domain

Functional Requirements In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a summary (or specification or statement) of behavior between inputs and outputs. Functiona ...

(FR) completely characterize the minimum performance to be met by the design solution, product etc. FR are documented in requirement specifications (RS). Input Constraints (IC) are included in the functional domain along with the FR. IC are specific to overall design goals and are imposed externally by CN, product users or conditions of use, such as regulations. IC are derived from CN and then revised based on other constraints that the product has to comply with but not mentioned in the Customer Domain. ;Physical domain The Design Parameters (DP) are the elements of the design solution in the physical domain that are chosen to satisfy the specified FRs. DPs can be conceptual design solutions, subsystems, components, or component attributes. System Components (SC) provide a categorical design solution in the DP, where the categories represent physical parts in the Physical Domain. The SC hierarchy represents the physical

system architecture A system architecture is the conceptual model that defines the structure, behavior, and views of a system. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the s ...

or product tree. The method for categorizing varies. Eppinger portrays general categories as system, subsystem, and component Eppinger (2001). NASA uses system, segment, element, subsystem, assembly, subassembly, and part (NASA, 1995). SC makes it possible to perform Design Structure Matrixes (DSM), change management, component-based cost management and impact analysis, and provides framework for capturing structural information and requirement traceability. ;Process domain Process Variables (PV) identify and describe the controls and processes to produce SC. ;Test domain A functional test consists of a set of Functional Test Cases (FTC). FTC are system tests used to verify that FR are satisfied by the system.

Black-box testing Black-box testing, sometimes referred to as specification-based testing, is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. This method of test can be applie ...

is the software analog to FTC. At the end of the system development, a functional test verifies that the requirements of the system are met. Component Test Cases (CTC) are a physical analog to

White-box testing White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of software testing that tests internal structures or workings of an application, as opposed to its functionality ...

. CTC verify that components satisfy the allocated FRs and ICs. Each system component is tested before it is integrated into the system to make sure that the requirements and constraints allocated to that component are all satisfied.

Overview

APDL Domains

See also

References

Further reading