# PROCESS PURPOSE
The purpose is to provide an analyzed design, including dynamic aspects, that is consistent with the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) requirements and suitable for manufacturing, and to derive production-relevant data.
# PROCESS OUTCOMES
O1
A (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture and (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design is developed that identifies the elements of the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) and describes their behavior as well as their interfaces, and the dynamic interactions of the (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.).
O2
The (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture and the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design is analyzed, and special characteristics are identified.
O3
Consistency and bidirectional traceability are established between (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) requirements and (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) design.
O4 (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) production data is derived from the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design and communicated to all affected parties.
O5
Information for production test is derived from the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design and communicated to all affected parties.
O6
The (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture and (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design and the special characteristics are agreed and communicated to all affected parties.
# BASE PRACTICES
BP1
Specify the hardware architecture. (
O1, O4, O5 )
Develop the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture that identifies the (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.). Document the rationale for the defined (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture. Note 1: Examples for aspects reflected in the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture are ground concept, supply concept, EMC concept. Note 2: Examples for a design rationale can be implied by the reuse of a standard (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.), platform, or product line, respectively, or by a make-or-buy decision, or found in an evolutionary way.
Linked Knowledge Nuggets: arrow_forward "What is the difference between a model, view and a diagram in (system) architecture?"
personAuthor: Process Fellows
In model-based development, it's essential to distinguish between the concepts of "model", "view", and "diagram", as each serves a specific purpose.
A "model" is an abstraction of reality. It represents the complete system description, but only in terms of the essential elements that are relevant to the modeling context. Irrelevant details are deliberately excluded to maintain clarity and focus. The model is considered "complete" not because it includes every possible detail, but because it captures all significant influencing factors necessary for understanding and analysis within its intended scope. Remark: This definition is applicable as well for the various disciplines, e.g. in case a model is used to define a software architecture. If needed, different modelling techniques (e.g. SysML versus UML) might be used for different disciplines.
A "view" focuses on a particular aspect of the model, such as its structure or behavior. Views are tailored to the needs of specific stakeholders, which means that certain details may be intentionally omitted. However, a view never contains more information than the model itself—it is always a subset or projection of the model. The model remains the authoritative source of truth, while views help stakeholders concentrate on what matters most to them.
A "diagram" is a visual representation of a model with respect to a specific view. It helps communicate the model’s content in a clear and accessible way. Multiple types of diagrams can be used to illustrate different views, depending on the aspect being analyzed and the audience’s needs.
Based on components identified in the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture, specify the detailed design description and the schematics for the intended (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) variants, including the interfaces between the (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.). Derive the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) layout, the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) bill of materials, and the production data. Note 3: The identification of (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.) and their suppliers in the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) bill of materials may be subject to a pre-defined repository (see also IATF 16949:2016, clause 8.4.1.2.). Note 4: (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design may be subject to constraints such as availability of (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.) on the market, (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) design rules, layout rules, creepage and clearance distances, compliance of HW parts with industry standards such as AEC-Q, REACH.
Linked Knowledge Nuggets: arrow_forward "What is the difference between a model, view and a diagram in (system) architecture?"
personAuthor: Process Fellows
In model-based development, it's essential to distinguish between the concepts of "model", "view", and "diagram", as each serves a specific purpose.
A "model" is an abstraction of reality. It represents the complete system description, but only in terms of the essential elements that are relevant to the modeling context. Irrelevant details are deliberately excluded to maintain clarity and focus. The model is considered "complete" not because it includes every possible detail, but because it captures all significant influencing factors necessary for understanding and analysis within its intended scope. Remark: This definition is applicable as well for the various disciplines, e.g. in case a model is used to define a software architecture. If needed, different modelling techniques (e.g. SysML versus UML) might be used for different disciplines.
A "view" focuses on a particular aspect of the model, such as its structure or behavior. Views are tailored to the needs of specific stakeholders, which means that certain details may be intentionally omitted. However, a view never contains more information than the model itself—it is always a subset or projection of the model. The model remains the authoritative source of truth, while views help stakeholders concentrate on what matters most to them.
A "diagram" is a visual representation of a model with respect to a specific view. It helps communicate the model’s content in a clear and accessible way. Multiple types of diagrams can be used to illustrate different views, depending on the aspect being analyzed and the audience’s needs.
BP3
Specify dynamic aspects. (
O1 )
Evaluate and document the dynamic behavior of the relevant (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) and the interaction between them. Note 5: Not all (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) have dynamic behavior that needs to be described.
Linked Knowledge Nuggets: arrow_forward "What is the difference between a model, view and a diagram in (system) architecture?"
personAuthor: Process Fellows
In model-based development, it's essential to distinguish between the concepts of "model", "view", and "diagram", as each serves a specific purpose.
A "model" is an abstraction of reality. It represents the complete system description, but only in terms of the essential elements that are relevant to the modeling context. Irrelevant details are deliberately excluded to maintain clarity and focus. The model is considered "complete" not because it includes every possible detail, but because it captures all significant influencing factors necessary for understanding and analysis within its intended scope. Remark: This definition is applicable as well for the various disciplines, e.g. in case a model is used to define a software architecture. If needed, different modelling techniques (e.g. SysML versus UML) might be used for different disciplines.
A "view" focuses on a particular aspect of the model, such as its structure or behavior. Views are tailored to the needs of specific stakeholders, which means that certain details may be intentionally omitted. However, a view never contains more information than the model itself—it is always a subset or projection of the model. The model remains the authoritative source of truth, while views help stakeholders concentrate on what matters most to them.
A "diagram" is a visual representation of a model with respect to a specific view. It helps communicate the model’s content in a clear and accessible way. Multiple types of diagrams can be used to illustrate different views, depending on the aspect being analyzed and the audience’s needs.
BP4
Analyze the hardware architecture and the hardware detailed design. (
O2 )
Analyze the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture and (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design regarding relevant technical aspects, and support (Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources and requirements.) management regarding (Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources and requirements.) estimates. Identify special characteristics. Note 6: Examples for technical aspects are manufacturability for production, suitability of pre-existing (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.) to be reused, or availability of (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.). Note 7: Examples of methods suitable for analyzing technical aspects are simulations, calculations, quantitative or qualitative analyses such as FMEA.
Linked Knowledge Nuggets: arrow_forward "Analysis of an architectural design"
personAuthor: Process Fellows
The analysis of an architectural design is a substantive examination of the quality of an architecture.
It should never depend on the background knowledge or experience of a single person.
For this reason, the analysis must involve a (interdisciplinary) team of experts, be based on predefined criteria and the analysis method should be documented in a comprehensible manner.
Examples of analysis criteria can be found in the Automotive Spice Guideline, but please do not hesitate to define additional criteria that are appropriate to the task and the environment!
BP5
Ensure consistency and establish bidirectional traceability. (
O3 )
Ensure consistency and establish traceability between (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) and (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) requirements. Ensure consistency and establish traceability between the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design and components of the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture. Note 8: There may be non-functional (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) requirements that the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) design does not trace to. Examples are development process requirements. Such requirements are still subject to (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.). Note 9: Bidirectional traceability further supports consistency, and facilitates impact analysis of change requests, and demonstration of (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) coverage. Traceability alone, e.g, the existence of links, does not necessarily mean that the information is consistent with each other.
Linked Knowledge Nuggets: arrow_forward "Consistency vs. Traceability – What’s the Difference?"
personAuthor: Process Fellows
Consistency ensures that related content doesn’t contradict itself – e.g., requirements align with architecture and test. Traceability, in contrast, is about links: can you follow a requirement through to implementation and verification? Both are needed – consistency builds trust, traceability enables control. Typically, traceability strongly supports consistency review.
arrow_forward "The role of traceability in risk control"
personAuthor: Process Fellows
Traceability isn’t just about completeness — it’s about managing impact. When a requirement changes, trace links tell you what’s affected. That’s your early-warning system.
arrow_forward "The true benefit of traceability
"
personAuthor: Process Fellows
Sometimes the creation of traceability is seen as an additional expense, the benefits are not recognized.
Traceability should be set up at the same time as the derived elements are created. Both work products are open in front of us and the creation of the trace often only takes a few moments.
In the aftermath, the effort increases noticeably and the risk of gaps is high.
If the traceability is complete and consistent, the discovery of dependencies is unbeatably fast and reliable compared to searching for dependencies at a later stage, when there may also be time pressure.
It also enables proof of complete coverage of the derived elements and allows the complete consistency check.
Communicate the agreed (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture and the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) detailed design, including the special characteristics and relevant production data, to all affected parties.
# OUTPUT INFORMATION ITEMS
15-51
Analysis results (
O2 )
Identification of the object under analysis.
The analysis criteria used, e.g.:
selection criteria or prioritization scheme used
decision criteria
quality criteria
The analysis results, e.g.:
what was decided/selected
reason for the selection
assumptions made
potential negative impact
Aspects of the analysis may include
correctness
understandability
verifiability
feasibility
validity
Used by these processes:
ACQ.4 Supplier Monitoring
HWE.1 Hardware Requirements Analysis
HWE.2 Hardware Design
MAN.5 Risk Management
MAN.6 Measurement
MLE.1 Machine Learning Requirements Analysis
MLE.2 Machine Learning Architecture
PIM.3 Process Improvement
SWE.1 Software Requirements Analysis
SWE.2 Software Architectural Design
SYS.1 Requirements Elicitation
SYS.2 System Requirements Analysis
SYS.3 System Architectural Design
13-52
Communication evidence (
O6 )
All forms of interpersonal communication such as
e-mails, also automatically generated ones
tool-supported workflows
meeting, verbally or via meeting minutes (e.g., daily standups)
podcast
blog
videos
forum
live chat
wikis
photo protocol
Used by these processes:
ACQ.4 Supplier Monitoring
HWE.1 Hardware Requirements Analysis
HWE.2 Hardware Design
HWE.3 Verification against Hardware Design
HWE.4 Verification against Hardware Requirements
MAN.3 Project Management
MLE.1 Machine Learning Requirements Analysis
MLE.2 Machine Learning Architecture
MLE.3 Machine Learning Training
MLE.4 Machine Learning Model Testing
PIM.3 Process Improvement
REU.2 Management of Products for Reuse
SUP.1 Quality Assurance
SUP.11 Machine Learning Data Management
SWE.1 Software Requirements Analysis
SWE.2 Software Architectural Design
SWE.3 Software Detailed Design and Unit Construction
SWE.4 Software Unit Verification
SWE.5 Software Component Verification and Integration Verification
SWE.6 Software Verification
SYS.1 Requirements Elicitation
SYS.2 System Requirements Analysis
SYS.3 System Architectural Design
SYS.4 System Integration and Integration Verification
SYS.5 System Verification
VAL.1 Validation
Used by these process attributes:
PA2.1 Performance Management
13-51
Consistency Evidence (
O3 )
Demonstrates bidirectional traceability between artifacts or information in artifacts, throughout all phases of the life cycle, by e.g.,
tool links
hyperlinks
editorial references
naming conventions
Evidence that the content of the referenced or mapped information coheres semantically along the traceability chain, e.g., by
performing pair working or group work
performing by peers, e.g., spot checks
maintaining revision histories in documents
providing change commenting (via e.g., meta-information) of database or repository entries
Note: This evidence can be accompanied by e.g., Definition of Done (DoD) approaches.
Used by these processes:
HWE.1 Hardware Requirements Analysis
HWE.2 Hardware Design
HWE.3 Verification against Hardware Design
HWE.4 Verification against Hardware Requirements
MAN.3 Project Management
MLE.1 Machine Learning Requirements Analysis
MLE.2 Machine Learning Architecture
MLE.3 Machine Learning Training
MLE.4 Machine Learning Model Testing
SUP.8 Configuration Management
SUP.10 Change Request Management
SWE.1 Software Requirements Analysis
SWE.2 Software Architectural Design
SWE.3 Software Detailed Design and Unit Construction
SWE.4 Software Unit Verification
SWE.5 Software Component Verification and Integration Verification
SWE.6 Software Verification
SYS.2 System Requirements Analysis
SYS.3 System Architectural Design
SYS.4 System Integration and Integration Verification
SYS.5 System Verification
VAL.1 Validation
04-52
Hardware Architecture (
O1 )
Describes the initial floorplan and the overall (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) structure
Identifies the required (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.)
Includes the rationale for chosen options of (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) architecture
Identifies own developed and supplied (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.)
Identifies the required internal and external (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.) interfaces
Specifies the interfaces of the (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.)
Specifies the dynamic behavior
Identifies the relationship and dependency between (Hardware component = Logical (e.g., functional block) or physical group of hardware parts realizing a functionality, which
cannot be realized by any of its hardware parts alone, e.g., voltage monitoring, power supply.
may be organized hierarchically, i.e., a hardware component can contain lower-level hardware components.
Note: Depending on the application, e.g., the populated PCB, a system-on-chip, a microcontroller, or an SBC can be considered a HW component.)
Describes all (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) variants to be developed
Describes power supply, thermal and grounding concepts
Used by these processes:
HWE.2 Hardware Design
14-54
Hardware Bill of Materials (
O1, O4, O5 )
Uniquely identifies type, supplier, and amount of the complete set of all (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.) of the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)
Used by these processes:
HWE.2 Hardware Design
04-53
Hardware Detailed Design (
O1 )
Describes the interconnections between the (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.)
Specifies the interfaces of the (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.)
Specifies the dynamic behavior (examples are: transitions between electrical states of (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.), power-up and power-down sequences, frequencies, modulations, signal delays, debounce times, filters, short circuit behavior, self-protection)
Describes the conclusions and decisions based on e.g., analysis reports, datasheets, application notes
Describes the constraints for layout
Used by these processes:
HWE.2 Hardware Design
04-55
Hardware Layout (
O1, O4, O5 )
Specifies the placement of the (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.) and labels
Specifies manufacturing data e.g., circuit paths (width, routing), vias, testing points, number of layers, drillings, material of the PCB, shape, soldering resist mask, PCB coating
Specifies a unique layout identification
Used by these processes:
HWE.2 Hardware Design
03-54
Hardware Production Data (
O1, O4, O5 )
Consists of bill of materials
Consists of layout e.g, GERBER data
Specifies requirements for EOL test e.g.:
Test type (AOI, ICT, boundary scan)
Test coverage
Electrical loads
Acceptance criteria
In case of semiconductor development: mask data (GDS2)
Used by these processes:
HWE.2 Hardware Design
04-54
Hardware Schematics (
O1, O4, O5 )
Identifies the (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.)
Specifies the connections of the (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.)
Specifies the unique identification of all (Hardware part = Fundamental HW element the purpose and functionality of which cannot be further subdivided or separated.
Note: Examples are transistors, resistors, diodes, non-populated PCB
Note: Depending on the application, e.g., a system-on-chip, a microcontroller or an SBC can be considered a HW part.
Note: the term ‘unit’ is considered to apply to the software domain only. The term ‘hardware part’ can be viewed as the hardware counterpart of ‘software unit’.)
Specifies unique variant identification
Used by these processes:
HWE.2 Hardware Design
04-56
Hardware element interface
is defined by output, input, type, and electrical characteristics including signal tolerances.
Examples of interfaces are
high level interfaces like SPI, I2C, CAN, LIN, Ethernet
electrical interconnections
thermal interfaces between (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) (heat dissipation)
Used by these processes:
HWE.2 Hardware Design
17-57
Special Characteristics (
O2 )
Special Characteristics in terms of relevant standards such as IATF 16949, VDA 6.x Guidelines, ISO 26262.
Special Characteristics according to IATF 16949:2016-10 [15], Chapters 8.3.3.3, are product characteristics or production process parameters that may have an impact on safety or compliance with official regulations, the fit, the function, the performance or further processing of the product.
Special characteristics shall be verifiable according to VDA vol. 1
Note: A typical method for identifying and rate special characteristics is an FMEA.
HWE.2
Hardware Design
