Software Process Training



Similar documents
Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

VAIL-Plant Asset Integrity Management System. Software Development Process

Software Design Document (SDD) Template

Chap 1. Introduction to Software Architecture

ITS Projects Systems Engineering Process Compliance Checklist

Time Monitoring Tool Software Development Plan. Version <1.1>

Controlling Risks Safety Lifecycle

Project QA and Collaboration Plan for <project name>

INTRODUCTION: How to Develop Project Management Procedures and Skills. The Guideline Content Starts on the Following Page

Software Engineering. Objectives. Designing, building and maintaining large software systems

Project Implementation Process (PIP)

Iterative Software Development -

Applying CMMI SM In Information Technology Organizations SEPG 2003

(Refer Slide Time: 01:52)

Provision of an HR System, Implementation and Support Services

Abstract. 1 Introduction

USGS EOS SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP)

Appendix 2-A. Application and System Development Requirements

Draft Requirements Management Plan

IT Project: System Implementation Project Template Description

System Requirements Specification (SRS) (Subsystem and Version #)

QUALIFICATIONS PACK - OCCUPATIONAL STANDARDS FOR ELECTRONICS INDUSTRY. SECTOR: ELECTRONICS SUB-SECTOR: Semiconductor Design and Active Components

Project Plan for <project name>


ERP Implementation Methodology SAFAL ERP

Mastering Microsoft Project 2010

Software Project Models

Appendix <<1>> System Status Report for System template

CS6403-SOFTWARE ENGINEERING UNIT-I PART-A

Software Engineering. Software Engineering. Software Costs

INTRODUCTION: Plan and Schedule Development Create a Work Breakdown Structure (WBS) The detailed guidelines and examples start on the following page.

REQUEST FOR EXPRESSIONS OF INTEREST (CONSULTANT SERVICES)

Modelling the Management of Systems Engineering Projects

How To Write A Software Engineering Project Document Template

Sparx Systems Enterprise Architect for Team Players

Iterative Project Management 1

Enterprise Architecture 101. (Includes numerous samples/ templates produced using TOGAF methodology) Shail Sood

Classical Software Life Cycle Models

SCADE System Technical Data Sheet. System Requirements Analysis. Technical Data Sheet SCADE System

Project Managing Microsoft Dynamics CRM Implementations

Critical Path Method (CPM)

Unit 1 Learning Objectives

Product Lifecycle Management. Diane Ryan Siemens PLM Software

PHASE 5: DESIGN PHASE

Requirements engineering

1. Software Engineering Overview

System Development Life Cycle Guide

Software Project Management Plan (SPMP)

Modellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico

COMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES

Overview of the System Engineering Process. Prepared by

From the light to the full application form focus on work plan

Software Project Management

The Software Lifecycle. Software Lifecycles

Gantt Chart for Excel

Introduction to the ITIL Service Management Framework

Software Development: The Waterfall Model

Communications Software Engineering (Z01)

Software Test Plan (STP) Template

Project Lifecycle Management (PLM)

Project Scheduling & Tracking

Information Technology Security Certification and Accreditation Guidelines

Systems Engineering Process

Basic Unified Process: A Process for Small and Agile Projects

Cloud & Datacenter Monitoring with System Center Operations Manager

How To Model Software Development Life Cycle Models

Establishing Great Software Development Process(es) for Your Organization. By Dale Mayes

LR120 LoadRunner 12.0 Essentials

Software Project Management Part 2: Work Breakdown Structures

Software Development Standard Deliverables

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology

Software Processes. The software process. Generic software process models. Waterfall model. Waterfall model phases

Metrics in Software Test Planning and Test Design Processes

Minnesota Health Insurance Exchange (MNHIX)

The Impacts Of Agile Development On The System Engineering Process

How To Integrate Software And Systems

Mastering increasing product complexity with Collaborative Systems Engineering and PLM

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

Dependable (Safe/Reliable) Systems. ARO Reliability Workshop Software Intensive Systems

Software Process and Project Plan

Integration Test Plan

Business Process (BPMN) Course

Microsoft Infrastructure Assessment

Implementation of ANSI/AAMI/IEC Medical Device Software Lifecycle Processes.

CMMI KEY PROCESS AREAS

Software and Systems Engineering. Software and Systems Engineering Process Improvement at Oerlikon Aerospace

Project Type Guide. Project Planning and Management (PPM) V2.0. Custom Development Version 1.1 January PPM Project Type Custom Development

Health Information System Program Kick off

44-76 mix 2. Exam Code:MB Exam Name: Managing Microsoft Dynamics Implementations Exam

Decomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces

Revision History Revision Date Changes Initial version published to

Transcription:

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

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

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 / www.itq.ch 3

Technical Solutions Copyright Qualität & Informatik / www.itq.ch 4

- 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 / www.itq.ch 5

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 / www.itq.ch 6

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 / www.itq.ch 7

Roles, Activities, Work Products Roles Activities Work Products Copyright Qualität & Informatik / www.itq.ch 8

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 / www.itq.ch 9

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 / www.itq.ch 10

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 / www.itq.ch 11

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 / www.itq.ch 12

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 / www.itq.ch 13

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 / www.itq.ch 14

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 / www.itq.ch 15

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 / www.itq.ch 16

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

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 / www.itq.ch 18

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 / www.itq.ch 19

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 / www.itq.ch 20

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

Any Questions Copyright Qualität & Informatik / www.itq.ch 22