Software Process Training



Similar documents
Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Engineering. Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti

CMMI: Specific Goals and Practices

Requirements Definition and Management Processes

VAIL-Plant Asset Integrity Management System. Software Development Process

Project QA and Collaboration Plan for <project name>

Iterative Software Development -

Draft Requirements Management Plan

System Development Life Cycle Guide

Capability Maturity Model Integration (CMMI SM ) Fundamentals

CMMI KEY PROCESS AREAS

VALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

(Refer Slide Time: 01:52)

CMMI: What do we need to do in Requirements Management & Engineering?

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

Holistic PLM for the development of mechatronic systems Proof of concept: Synchronized Mechatronics Engineering enabled by SOA

Software Project Models

Time Monitoring Tool Software Development Plan. Version <1.1>

The Plan s Journey From Scope to WBS to Schedule

Requirements Engineering

Applying CMMI SM In Information Technology Organizations SEPG 2003

Software Requirements, Third Edition

Copyright 2013 wolfssl Inc. All rights reserved. 2

CMMI and IBM Rational Unified Process

RUP for Software Development Projects

Tools for Testing Software Architectures. Learning Objectives. Context

Supporting Workflow Overview. CSC532 Fall06

Systems Engineering Process

FSW QA Testing Levels Definitions

Requirements Management Practice Description

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

DO-178B compliance: turn an overhead expense into a competitive advantage

ITS Projects Systems Engineering Process Compliance Checklist

Software Configuration Management Plan

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997

Project Management Plan Template

PROJECT SCOPE STATEMENT

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

Chapter 3 The Integrated Requirements Management Framework (IREQM)

Requirements Elaboration

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

ISO/IEC Part 2 provides the following copyright release:

How To Understand The Software Process

Develop Project Charter. Develop Project Management Plan

How projects benefit from a full requirements lifecycle. Name : Nienke van den Brink, Leo Diepstraten, Capgemini NL Date: 6 October 2009

3C05: Unified Software Development Process

Safe Automotive software architecture (SAFE)

Short Guides to IDA Quality Assurance Guidelines. Development and Validation Phase. Issue 2.0

Project Lifecycle Management (PLM)

COMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES

USGS EOS SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP)

Agenda. 0 Agenda review 2 minutes. 0 Chapter of the week 50 minutes. 0 Q&A of chapter 10 minutes. 0 Break 10 minutes. 0 Exercises 25 minutes

Design Document Version 0.0

Industrialization software Engineering using CMMI Luc Quadflieg Atos Origin - Global System Integration

Chap 1. Introduction to Software Architecture

Managing Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI

Chapter 5: Project Scope Management. Information Technology Project Management, Fifth Edition

Syllabus. REQB Certified Professional for Requirements Engineering. Foundation Level

Business Analysis Standardization & Maturity

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK

G-Cloud Service Description. Atos: Cloud Professional Services: Requirements Specification

Introduction to OpenUP (Open Unified Process)

What is a life cycle model?

Software Requirements Engineering: What, Why, Who, When, and How By Linda Westfall

How To Model Software Development Life Cycle Models

Software Project Management and Support - Practical Support for CMMI -SW Project Documentation: Using IEEE Software Engineering Standards

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led

Module F13 The TOGAF Certification for People Program

ISO 9001/TL 9000 and CMMI Comparison

Microsoft SDL: Agile Development

Table of Contents. CHAPTER 1 Web-Based Systems 1. CHAPTER 2 Web Engineering 12. CHAPTER 3 A Web Engineering Process 24

Guidance document for EMIS Web EPS Release 2 deployment

Creating A Risk Management Plan

COMPANY LOGO. Project Charter Project Charter

This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed by the IIBA.

Revision History Revision Date Changes Initial version published to

Abstract. 1 Introduction

The Design and Improvement of a Software Project Management System Based on CMMI

Usability in SW-Engineering-Prozessen und in CMMI

A COMPARISON OF PRINCE2 AGAINST PMBOK

Classical Software Life Cycle Models

CDC UNIFIED PROCESS PRACTICES GUIDE

SOMA, RUP and RMC: the right combination for Service Oriented Architecture

CPET 545 SOA and Enterprise Applications. SOA Final Project Project Scope Management

Project Management Standards: A Review of Certifications/Certificates

PMI Fundamentals PMI Processes Project Organization. Initial documents. Functional, Project, Matrix Orgs. Statement of Work (SOW) Project Charter

The Software Lifecycle. Software Lifecycles

Charter & Scope Statement Web & Portal Redesign. Brookdale Community College

Transcription:

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

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

- Policy / Scope / Purpose! Policy Produce and analyze customer, product and product-component requirements. Develop Customer Stakeholder needs, expectations, constraints and interfaces are collected and translated into customer requirements. Develop Product Customer requirements are refined and elaborated to develop product and productcomponent requirements. Analyze and Validate The requirements are analyzed and validated, and a definition of required functionality is developed.! Scope All SW producing units in AVL SBU MES. Affected projects are: Standard SW development projects (main releases as well as sub-releases) Customer-specific SW development Not affected projects are: Service Packs Hotfix packages, Patches Copyright Qualität & Informatik / www.itq.ch 3

- Policy / Scope / Purpose (cont.)! Purpose The purpose of Development is to produce and analyze customer, product, and product component requirements. Copyright Qualität & Informatik / www.itq.ch 4

Exercise: Familiarization! Method: Plenum! Timing: 20! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (trainer)! Questions: I. How do we know that the process is performing well? II. Who of you has experiences with this process? Which one? III. What are the most relevant work products? Copyright Qualität & Informatik / www.itq.ch 5

Exercise: Roles, Activities, Work Products! Method: Individual! Timing: 10! Form: Individual elaboration! Documents: Rule 6; 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 6

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

Roles, Activities, Work Products Roles PL-DP PL-CP GPM HOD STL SPL WPL RM Activities Develop Customer - Elicit Needs - Develop Customer Develop Product - Establish Product and Product Component Reqmts - Allocate Product Component - Identify Interface Analyze & Validate - Establish Operational Concepts and Scenarios - Develop architecture requirements - Establish a definition of required functionality - Analyze - Analyze to achieve balance - Validate with comprehensive methods Work Products CRS Document (for product dev. or customer specific dev.) URS SRS SAD Copyright Qualität & Informatik / www.itq.ch 8

with Practices 1/3 Collect Stakeholder Needs Develop Customer Elicit Needs Customer Develop the Customer Copyright Qualität & Informatik / www.itq.ch 9

with Practices 2/3 Customer Allocate Product and Product- Component Develop Product Establish Product & Product Component Identify Interface Product Copyright Qualität & Informatik / www.itq.ch 10

with Practices 3/3 Establish Operational Concepts & Scenarios Product Analyze and Validate Establish a Definition of Required Functionality Validate Analyze Analyze to Achieve Balance Validate with Comprehensive Methods Validated Copyright Qualität & Informatik / www.itq.ch 11

Tasks Practice Task Work Products Develop Customer Develop Product Analyze and Validate Product Development: Create a CRS Document and provide supporting details or Customer specific Development: Create CRS Create URS Create SRS Create SAD CRS CRS URS SRS SAD Copyright Qualität & Informatik / www.itq.ch 12

Exercise: Task Description! Method: Group work! Timing: 20 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 6:! Deliverable: Task description on flipchart! Question: I. Describe the selected task _T03 Create URS using the presented description technique ("next foil). Copyright Qualität & Informatik / www.itq.ch 13

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

Task Details Create URS Input CRS Rule 24: Review _T03 Roles PL-DP: GPM: Reviewer Tools ClearQuest Method/Technique not specified Create URS Description Analyze customer requirements Derive requirements from constraints, consideration, and issues Establish Product and Product Component Allocate Product Component (to Work Packages) Identify Interface Responsible for task T03 Responsible stakeholder Output URS URS acceptance protocol Copyright Qualität & Informatik / www.itq.ch 15

Rule 6: Work Products and Templates WP Id Type Description Task Id Resp. Link to Template _W01 M CRS _T01 GPM Template CRS.xls (product development) _W02 M CRS _T02 PLCP Template CRS.xls (customer specific development) _W03 M URS _T03 GPM Template URS.doc or Generated Output from requirements database (e.g. ReqPro, ClearQuest) _W04 M SRS _T04 PLDP Template SRS*.doc or Template SRS-SDD ( MO).dot _W05 O SAD _T05 PLDP Not yet defined Copyright Qualität & Informatik / www.itq.ch 16

Exercise: Manage Configuration! Method: Small groups! Timing: 10 group work, 10 discussion in plenum! Form: Group elaboration! Documents: none! Deliverable: Group notes! Question: Work products are often developed iteratively, have a life cycle status, or are changed caused by requirements changes. According to the importance of the work product the degree of configuration management has to be defined. I. What degrees of configuration management do you use? II. When do you define the configuration management for the work products? Copyright Qualität & Informatik / www.itq.ch 17

GP 2.6 for Manage Configurations GP2.7 NAGE CONFICURATIONS Place designated work products of the process under appropriate levels of configuration management. Purpose: Establish and maintain the integrity of the designated work products of the process (or their descriptions) throughout their useful life. Practice:! Identify the designated work products in the plan for performing the process, along with a specification of the level of configuration management (e.g.: version control, baseline configuration management). Copyright Qualität & Informatik / www.itq.ch 18

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

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