1. Roadmap and Feature Planning
...
A detailed description about the rules used to build the roadmap and platform functional requirement is in [xx]. These document need to be written in AGL confluence.
- T1-2 Lifecycle Life-cycle calendar.
The following milestones should be determined at this stage. In order to complete each milestone, each exit criteria must be achieved and the deliverable released.
...
- T2.1-1 Create/update diagram and description of software component from use case point of view
- Use case diagram and/or Use case description should be showed in design documents to help understand requirements and to help have common understanding for requirements and,
- Use case diagram and/or Use case description show necessity of software component to be developed.
- T2.1-2 Create/update software component interface description
- This is important information for the component users, so it shall be included in design documents or described as markdown
- Developer shall define and describe meaning, parameter and return value of each interface
- If the order of calling interface function/method is important, we recommend that developer create a sequence diagram.
- T2.1-3 Create/update software component activity diagram
- T2.1-4 Create/update software component state machine diagram and table
- If the software component to be designed has a state, state transition should be represented by state machine diagram and/or state machine table.
- To prevent omission of consideration during design process, we recommend that developer checks his design using state machine table.
- T2.1-5 Create/update deployment diagram
- Developer should clarify related and/or interfering other components or hardware devices to show necessity of these.
- T2.1-6 Create/update software component test specification
- To Design test cases to meet the requirement coverage and
- To describe these as specification document.
...
- V2.1-2 Review the interface description
- The method of providing an interface should use for standard method of the own architectural layer.
Interface spec shall describe by standard format of the method.
ex. In case of C functional interface should be use doxygen. In case of REST interface should be use OpenAPI.
...
- D2.1-1 The software component use case diagram and description, activity diagram and description, state machine diagram and description and interface description is published in AGL confluence.
- D2.1-2 All review record is published in AGL jirra/confluence.
2.2. Architecture Design for the reusing existing opensource software
...
- V2.2-1 Review the use case diagram and description
...
- Two or more reviewers must approve this definition.
- This document must be including description for tasks from T2.2-1.
- V2.2-2 Review the assessment result
...
- The selected OSS must meet the assessment criteria.
- Risk information for the selected OSS must be provided. It should be updated during the detailed design phase.
- V2.2-3 Review the test .
...
- .
Selected OSS have test suite that fit the use case is available.
and/or the test cases is defined based on the defined use case.
The performance requirements in the reference environment must be specified.- ex. Interface A : response tome less than 1ms in R-Car M3.
- The resource requirements in the reference environment must be specified with limitations.
- ex. Runtime memory usage less than 20MByte in R-Car M3 (at 2 Guest container).
Exit Criteria
- X2.2-1 TBDCompleted review and accepted the documents for software component.
Deliverable
- D2.2-1 TBDThe software component use case diagram and description is published in AGL confluence.
- D2.2-2 TBD2 Assessment documents published in AGL confluence.
- D2.2-4 All review record is published in AGL jirra/confluence.
3. Detail Design and Code Development/Certification for existing OSS
...