Software Process Training

Transcription

1 Rule 15 Technical Solution Dr. Ernest Wallmüller Wolfgang Höh Qualität & Informatik Copyright Qualität & Informatik 2005

2 Context & Alternative solutions Requirements Product components Product components, work products, verification and validation reports Customer needs Product Customer Copyright Qualität & Informatik / 2

3 SW Development Overview: Rule 15 () Phase A Phase B Phase C Phase D Phase E Phase F P- Review 2 URS Handover of URS to PL-DP P- Review 3 Start Development KICK OFF SRS P- Review 4 (SRS- Review) DDS- Review Draft Architectural Design Complete Software Design Design- Review SDD- Review SW-Design Approval 15_ Impl. and Module Test Integration and Integration Test α n- Version Check Completeness of Deployments System Test Function Test Applic. Test P- Review 5 M Tryout Representative βa, β B, β C,.. GPM: Beta Version Release Review β1, β 2, β 3,.. Type Approval P- Review 6 Final Version Copyright Qualität & Informatik / 3

4 Technical Solutions Copyright Qualität & Informatik / 4

5 - Policy / Scope / Purpose! Policy AVL is dedicated to develop software with consistent and state of the art quality.! Scope All software producing units in AVL SBU MES.! Purpose The purpose of Technical Solution is to design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product-related life-cycle processes either singly or in combinations as appropriate. Copyright Qualität & Informatik / 5

6 Exercise: Familiarization! Method: Plenum! Timing: 10! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (Trainer)! Questions: I. What are your experiences with Technical Solution especially with design and implementation? II. What worked well in the past? III. What did not work so well? Copyright Qualität & Informatik / 6

7 Exercise: Roles, Activities, Work Products! Method: Individual! Timing: 15! Form: Individual elaboration! Documents: Rule 15; form: next foil! Deliverable: Filled in form Question: I. Based on your experience, the prior discussion and the process definition list the involved roles, the performed activities, and the produced work products. Copyright Qualität & Informatik / 7

8 Roles, Activities, Work Products Roles Activities Work Products Copyright Qualität & Informatik / 8

9 Roles, Activities, Work Products Roles SA SE TW PL-DP WPL RM Activities Develop Detailed Alternative Solutions and Selection Criteria and Select Product Component Solutions Design the Product or Product Component Establish a Technical Data Package Design Interfaces Using Criteria Perform Make, Buy, or Reuse Analysis Implement the Design Develop Product Support Documentation Work Products Technical Solution Decision Documentation DD WP chapter with Alternative Solutions Decision in DD System architecture SAD Subsystem SDD Documentation Design Document DDD Test Design Document TDD Source Code User Documentation Release Notes Train-The-Trainer Documentation Maintenance manual Copyright Qualität & Informatik / 9

10 with Practices 1/3 Validated Requirements Select Product Component Solutions Alternative Solutions Selection Criteria New Technology Evaluations Select Product Component Solutions Operational Scenarios Timeline Analysis Use Cases Evolve Operational Concepts & Scenarios Selection Decisions Compliance w/ Reqmts Copyright Qualität & Informatik / 10

11 with Practices 2/3 Design the Product or Product Component Design Methods Design Tools Design es Develop the Design Establish a Tech Data Package Tech Data Package Selection Criteria Make/Buy Analysis Perform Make, Buy, or Reuse Analyses I/F Design Documentation I/F Specification I/F Control Documents Design Interfaces Using Criteria Copyright Qualität & Informatik / 11

12 with Practices 3/3 Implement the Product Design Implement the Design Parts Fabricated Software Coded Data Documented es Documented Facilities Constructed Develop Product Support Documentation Manuals Users Manual Operator s Manual Maintenance Manual On-line Help Copyright Qualität & Informatik / 12

13 Tasks 1/2 Practice Task Work Products Select Product Component Solutions Evolve Operational Concepts and Scenarios Design the Product or Product Component Establish a Technical Data Package Design Interfaces Using Criteria Create DD Describe Decisions of Alternative Solutions related to Work Packages Evolve Operational Concepts and Scenarios Create System architecture SAD Create SDD Establish a Technical Data Package Create Interface descriptions in SDD Technical Solutions Decision Documentation DD Work Package Solutions Decision in DD SDD (Sequence Diagram, deployment, installation, operating environment) System architecture SAD Subsystem SDD Technical Data Package (Harvest) SDD (Interface descriptions) Copyright Qualität & Informatik / 13

14 Tasks 2/2 Practice Task Work Products Perform Make, Buy, or Reuse Analysis Implement the Design Develop Product Support Documentation Decide about Make, Buy, or Reuse Implement Source Code Create Documentation Create documentation design document DDD Create Test design document TDD Write Documentation Write Release Notes Write Maintenance manual DD (Make/buy/reuse Decision) sheet reference (opt) Source Code Documentation Documentation Design Document DDD Test Design Document TDD User Documentation Release Notes Maintenance Manual Copyright Qualität & Informatik / 14

15 Technical Data Package! A collection of items that may include the following if such information is appropriate to the type of product and product component (for example, material and manufacturing requirements may not be useful for product components associated with software services or processes): product architecture description allocated requirements product-component descriptions product-related life-cycle process descriptions if not described as separate product components key product characteristics required physical characteristics and constraints interface requirements materials requirements (bills or material and material characteristics) fabrication and manufacturing requirements (for both the original equipment manufacturer and field support) the verification criteria used to ensure requirements have been achieved conditions of use (environments) and operating/usage scenarios, modes and states for operations, support, training, manufacturing, disposal, and verifications throughout the life of the product rationale for decisions and characteristics (requirements, requirement allocations; design choices) ==> default documents or specifications that you need to implement a component Copyright Qualität & Informatik / 15

16 Exercise: Task Description! Method: Group work! Timing: 20 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 15:! Deliverable: Task description on flipchart! Question: I. Describe the selected task _T01: Create DD and task _T14: Establish a Technical Data Package using the presented description technique ("next foil). Copyright Qualität & Informatik / 16

17 Task Description Technique Input ID Task Name Description Roles Tools Method/Technique Output Copyright Qualität & Informatik / 17

18 Task Details Create DD Input Necessity for development of alternative solutions Set of relevant requirements Set of constraints ID _T01 Roles PL-DP RM Task Name Create DD Description Create the DD to describe the solution finding and decision process. For each work package inserted a chapter (document the selected solution and the process for the decision). Document global project decisions. Document details of the selected solutions (where appropriate) in URS, SRS, and SDD. Tools Template: Template DD.dot Rule 13: Method/Technique not specified Resp. for task _T01 Requirements Output Technical Solution Decision DD URS updated SRS updated SDD updated Copyright Qualität & Informatik / 18

19 Task Details Establish a Technical Data Package Input Work Package SRS for subsystem incl. product requirements DD ID _T14 Roles PL-DP, WPL, SA _T14 Task Name Establish Technical Data Package Description Describe the selected alternative solution for implementation: SRS Software requirement specification SDD of the product component Reference to the SAD Reference to the DD documentation Test design document Documentation Design Document DDD Resp. for task Tools Template: Template Project_WorkProduct_Plan.xlt Harvest Method/Technique not specified Output Technical Data Package (Harvest) Copyright Qualität & Informatik / 19

20 Rule 15: Work Products and Templates WP Id Type Description Task Id Resp. Link to Template? _W01 M Technical Solution Decision Documentation DD _T01 PL-DP Template DD.dot _W02 M WP chapter with Alternative Solutions Decision in DD _T02 WPL Template DD.dot _W03 M System architecture SAD _T03 SA _W04 M Subsystem SDD _T04 WPL Template SDD.dot _T08 _W05 O Documentation _T05 WPL n.a. _W06 O Documentation Design Document DDD _T06 WPL Template DDD.mmap _W07 O Test Design Document TDD _T07 WPL Template_VER_Master Testplan*.dot or Template_VER_TD.mmp _W08 M Source Code _T09 SE n.a. _W09 M User Documentation _T10 TW Not yet existing _W10 M Release Notes _T11 TW Not yet existing _W11 M Interface descriptions in SDD _T08 WPL Template SDD.dot _W12 O Maintenance manual _T12 TW Not yet existing _W13 M Make, Buy, or Reuse decision document in DD. sheet reference if necessary. _T13 WPL Template SDD.dot _W14 M Overview of a technical data package in the project work product plan _T14 WPL Template Project_Work Product_Plan.xlt Copyright Qualität & Informatik / 20

21 Rule 15: Concluding Discussion What was important for you concerning this Rule? Copyright Qualität & Informatik / 21

22 Any Questions Copyright Qualität & Informatik / 22