Spice4Cars

Specify, analyze and structure functional and non-functional system requirements according to defined characteristics for requirements. Prioritize system requirements according to schedule.
Note 1: System requirements can be structured, e.g., by categorizing, grouping, sorting, and prioritizing according to the context.
Note 2: For changes to the stakeholder’s requirements Technical Change Request Management (TCRM) may apply.
Note 3: The analysis of impact on effort and schedule supports the adjustment of estimates. Refer to Potential Management (POPM).

Linked Knowledge Nuggets:
arrow_forward "How do I bring levels to my requirement chaos?"

arrow_forward "INCOSE Guide to writing requirements v4 - Summary Sheet"

arrow_forward "Specifying behavior under all conditions"

arrow_forward "The role of assumptions in (system) requirements analysis"

arrow_forward "What is the difference between a functional system architecture, a logical system architecture and a physical system architecture?"

arrow_forward "What is the difference between a model, view and a diagram in (system) architecture?"

Specify and analyze the system architecture including and their interfaces. Specify static and dynamic views of .

Linked Knowledge Nuggets:
arrow_forward "Analysis of an architectural design"

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:

CSVV Cybersecurity Verification and Validation
PCOM Partner and Collaboration Management
REEL Requirements Elicitation
SWDI Software Requirements, Design and Implementation
SYRD System Requirements and Design

An expectation of functions and capabilities (e.g., non- (Functional requirement = A statement that identifies what a product or process must accomplish to produce required behavior and/or results.)), or one of its interfaces
from a black-box perspective
that is verifiable, does not imply a design or implementation decision, is unambiguous, and does not introduce contradictions to other requirements.
A requirements statement that implies, or represents, a design or implementation decision is called “Design Constraint”.
Examples for requirements aspects at the system level are thermal characteristics such as
- heat dissipation
- dimensions
- weight
- materials
Examples of aspects related to requirements about system interfaces are
- connectors
- cables
- housing
Examples for requirements at the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) level are
- lifetime and mission profile, lifetime robustness
- maximum price
- storage and transportation requirements
- functional behavior of analog or digital circuits and logic
- quiescent current, voltage impulse responsiveness to crank, start-stop, drop-out, load dump
- temperature, maximum (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) heat dissipation
- power consumption depending on the operating state such as sleep-mode, start-up, reset conditions
- frequencies, modulation, signal delays, filters, control loops
- power-up and power-down sequences, accuracy and precision of signal acquisition or signal processing time
- computing resources such as memory space and CPU clock tolerances
- maximum abrasive wear and shearing forces for e.g., pins or soldering joints
- requirements resulting from lessons learned
- safety related requirements derived from the technical safety concept

Used by these processes:

CSVV Cybersecurity Verification and Validation
REEL Requirements Elicitation
SWDI Software Requirements, Design and Implementation
SYRD System Requirements and Design

Meta-attributes that support structuring and definition of (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) scopes of requirements.
Can be realized by means of tools.
Note: usage of requirements attributes may further support analysis of requirements.

Used by these processes:

REEL Requirements Elicitation
SWDI Software Requirements, Design and Implementation
SYRD System Requirements and Design

A justifying rationale for the chosen architecture.
Individual behavior of
(System Element = System elements can be:
- Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
- Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
)
Interrelationships between
(System Element = System elements can be:
- Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
- Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
)
- Settings for system parameters (such as
  (Application parameter = An application parameter is a software variable containing data that can be changed at the system or software levels; they influence the system’s or software behavior and properties. The notion of application parameter is expressed in two ways:
  - The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
  - The actual quantitative data value it receives by means of data application.
  Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.)
  )
- Manual/human control actions, e.g., according to STPA
Interface Definitions:
- Technical characteristics of interfaces for relationships between two
  (System Element = System elements can be:
  - Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
  - Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
  )
Interfaces between
(System Element = System elements can be:
- Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
- Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
)
e.g.:
- bus interfaces (CAN, MOST, LIN, Flexray etc.)
- thermal influences
- (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)-software-interfaces (HSI), see below
- electromagnetic interfaces
- optical interfaces
- (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)-mechanical-interfaces (e.g., a cable satisfying both mechanical and electrical requirements, housing interface to a PCB)
- (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)-mechanical interconnection technology such as connectors, pressfit
- creepage and clearance distances
Fixations such as adhesive joints, screw bolts/fitting, riveted bolts, welding
System interfaces related to EE (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) e.g.:
- analogue or digital interfaces (PWM, I/O) and their pin configurations
- SPI bus, I2C bus, electrical interconnections
- placement, e.g., thermal interfaces between (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) (heat dissipation)
- soldering
- creepage and clearance distances
Interfaces for mechanical engineering e.g.:
- friction
- thermal influences
- tolerances
- clutches
- fixations such as adhesive joints, screw bolts/fitting, riveted bolts, welding
- forces (as a result of e.g., vibrations or friction)
- placement
- shape
- A (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)-software interface, e.g.:
  - connector pin configurations and floating IOs for μCs/MOSFETs
  - signal scaling and resolution to be reflected by the application software
Mechanical- (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) interfaces e.g.
- such as mechanical dimensioning
- positioning of connectors
- positioning of e.g., hall sensors in relation to the bus-bar
- tolerances
Dynamics of
(System Element = System elements can be:
- Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
- Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
)
and system states:
- Description of the system states and operation modes (startup, shutdown, sleep mode, diagnosis/calibration mode, production mode, degradation, emergency such as “limp-home”, etc.)
- Description of the dependencies among the system components regarding the operation modes
- Interactions between
  (System Element = System elements can be:
  - Logical and structural objects at the architectural and design level. System elements can be further decomposed into more fine-grained system elements of the architecture or design across appropriate hierarchical levels.
  - Physical representations of these objects, or a combination, e.g., peripherals, sensors, actuators, mechanical parts, software executables.
  )
  such as inertia of mechanical components to be reflected by the ECU, signal propagation and processing time through the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) and software and e.g., bus systems
Explanatory annotations, e.g., with natural language, for single elements or entire diagrams/models.

Used by these processes:

SYRD System Requirements and Design

SYRD System Requirements and Design