Skip to main content

Understanding the Overall Picture of the Process and Deliverables

To help you understand the overall picture of the software development process and deliverables (profile = metamodel + view definition) systematized in the embedded software development base package, we show representative screen images from a sample project.

Furthermore, as reference information for deeper understanding, we show document images of the expected target deliverables and the metamodel that defines their structure.

Supplement

This package targets the software development domain. Regarding "System Requirements Analysis," which is part of the system development domain, only the input information necessary for "Software Requirements Analysis" has been extracted and systematized. Accordingly, the testing process for system requirements analysis is not included.

Target V-Model Process and Main Deliverables​

V-Model Process

Process
OverviewMain Deliverables
SystemRequirementAnalysisDigitizes and makes traceable system requirements, which are inputs for software requirements analysis.・System Requirements (Input Information for Software Requirements Analysis)
SoftwareRequirementAnalysisBased on system requirements, analyzes the functional and non-functional requirements that the software must satisfy.Software Requirements
Software Architecture DesignDesign the component configuration, interfaces, and dynamic behavior to realize the software requirements.Component configuration and relationships
Interface design
Assignment of execution units (tasks/processes/interrupts, etc.) and interface functions
Dynamic design (sequence diagrams, state machine diagrams, DFDs)
Resource analysis
Software Component DesignDesign the internal unit configuration, interfaces, and dynamic behavior as a detailed design of the component.Component internal unit configuration and relationships
Interface design
Dynamic design (sequence diagrams, state machine diagrams, DFDs, flowcharts)
Software Component TestTest that the internal unit groups and individual components conform to the detailed design.Test execution plan and definition of scope
Test cases
Test results
Software Integration TestTest that each individual component, and the integrated component groups, conform to the architectural design.Same as above
Software TestTests that the entire software meets the software requirements.Same as above

Screen Images of Design Scenes in Each Process​

  • Software Requirements Analysis

Screen Image

  • Software Architecture Design

Screen Image

  • Software Component Design

Screen Image

  • Software Component Testing/Software Integration Testing/Software Testing

Screen Image

Document Images of Target Deliverables​

To view document images of target deliverables assumed in this package (sample documents for digitization by Next Design), please download the files from the following link.

Location: GitHub Repository ... Japanese version files only

  • Advanced Driving System Software Requirements Specification.docx
  • ADAS ECU Software Architecture Design Document.docx
  • ADAS ECU Software Component Design Document.docx
  • Advanced Driving System Software Test Report.xlsx (Test Specification and Report)
Please read carefully

The above samples are intended for your reference in order to effectively utilize the target product, and no warranty is provided.

These are treated as samples under the Next Design license agreement. For details, please refer to the Next Design End User License Agreement.

Metamodel Structure​

The metamodel defines the structure of the processes and deliverables systematized in this package.

To view the overall structure of the metamodel, please open the following class diagram (metamodel structure diagram) from the Profile Navigator. 1

  • [Class Diagram] Target Process ... Explanatory diagram of the target V-shaped process
  • [Class Diagram] Overall Structure ... Explanatory diagram of the class structure for each process and the relationships between processes
  • [Class Diagram] Trace Relationship Diagram ... Explanatory diagram focusing only on trace relationships between processes

Furthermore, please refer to the following class diagrams to see details of the metamodel for each process.

  • System Requirements Analysis/ [Class Diagram] System Requirements Analysis
  • Software Requirements Analysis/ [Class Diagram] Software Requirements Analysis
  • Software Architecture Design/ [Class Diagram] Software Architecture Design
  • Software Component Design/ [Class Diagram] Software Component Design
  • Software Component Test/ [Class Diagram] Software Component Test
  • Software Integration Test/ [Class Diagram] Software Integration Test
  • Software Test/ [Class Diagram] Software Test

Footnotes​

  1. A license for the Architect edition is required to view the Profile Navigator and class diagrams. ↩