Usability in SW-Engineering-Prozessen und in CMMI

Transcription

1 Workshop USABILITY VDE Prüf- und Zertifizierungsinstitut Strategiekreis i-12 Usability in SW-Engineering-Prozessen und in CMMI Helmut Thoma Schweizer Informatik Gesellschaft Lehrbeauftragter Universität Basel Software Engineering Consultant 1

2 Übersicht! CMMI! Usability in " CMMI " Systems Engineering & Architecture " IBM Global Services Method " Rational Unified Process " V-Modell! Usability in XP 2

3 Application Management Services Software Engineering Institute Capability Maturity Model Integration The Software Engineering Institute (SEI) is a federally funded research and development center at the Carnegie Mellon University, Pittsburgh 3 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

4 4

5 Application Management Services Content of CMMI the CMMI Framework a set of integrated CMMI models a CMMI appraisal method supporting products developed by industry, government, SEI 5 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

6 Application Management Services What is the CMMI? - The CMMI is a collection of effective management practices proven through industry use grouped in Process Areas CATEGORY PROCESS AREA CATEGORY PROCESS AREA PROCESS MANAGEMENT Organizational Process Focus (OPF) Organizational Process Definition (OPD) Organizational Training (OT) PROJECT MANAGEMENT Project Planning (PP) Project Monitoring and Control (PMC) Supplier Agreement Management (SAM) Integrated Project Management (IPM) Organizational Process Performance (OPP) Organizational Innovation and Deployment (OID) Risk Management (RSKM) Quantitative Project Management (QPM) CATEGORY PROCESS AREA CATEGORY PROCESS AREA ENGINEERING Requirements Management (REQM) Requirements Development (RD) Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL) SUPPORT Configuration Management (CM) Process and Product Quality Assurance (PPQA) Measurement and Analysis (MA) Decision Analysis and Resolution (DAR) Causal Analysis and Resolution (CAR) CMMI-SW, V1.1 6 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

7 Application Management Services CMMI staged representation - The CMMI Maturity Levels Maturity Level 2 Maturity Level 3 Maturity Level 4 Maturity Level 5 CATEGORY PROCESS AREA CATEGORY PROCESS AREA PROCESS MANAGEMENT Organizational Process Focus (OPF) Organizational Process Definition (OPD) Organizational Training (OT) PROJECT MANAGEMENT Project Planning (PP) Project Monitoring and Control (PMC) Supplier Agreement Management (SAM) Integrated Project Management (IPM) Organizational Process Performance (OPP) Organizational Innovation and Deployment (OID) Risk Management (RSKM) Quantitative Project Management (QPM) CATEGORY PROCESS AREA CATEGORY PROCESS AREA ENGINEERING Requirements Management (REQM) Requirements Development (RD) Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL) SUPPORT Configuration Management (CM) Process and Product Quality Assurance (PPQA) Measurement and Analysis (MA) Decision Analysis and Resolution (DAR) Causal Analysis and Resolution (CAR) CMMI-SW, V1.1 7 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

8 Application Management Services Maturity Levels (staged representation) # Initial: At ML 1 the process is adhoc and informal # Managed: At ML 2 the focus is on disciplined management of projects # Defined: At ML 3 the focus is on the organization IBM Org. EUR CR 1999 (CMM) 2001 (CMM) # Quantitatively Managed: At ML 4 the focus is on product and process quality with quantitative measurements # Optimizing: At ML 5 the focus is on continuous process improvement 2004 (CMMI) ongoing 8 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

9 Application Management Services The Ultimate Goal... Measure Improve CMMI Maturity Level 5 Analyse 9 SEI Capability Maturity Model Integration EPG AMS EMEA Central Region Febr IBM Corporation

10 Usability of the product will be focused in the Engineering Process Areas (ML 2 + 3) of CMMI REQM Requirements Management RD Requirements Development TS Technical Solution PI Product Integration VER Verification VAL Validation 10

11 Requirements Development (ML 3) Specific Goals Generic Goals 11

12 Requirements Development (ML 3) SG 2 Develop Product Requirements SP 2.3 Indentify Interface Requirements 12

13 Technical Solution (ML 3) Specific Goals Generic Goals 13

14 Technical Solution (ML 3) SG 2 Develop the Design SP 2.3 Design Interfaces Using Criteria 14

15 Product Integration (ML 3) Specific Goals Generic Goals 15

16 Product Integration (ML 3) SG 2 Ensure Interface Compatibility SP 2.3 Review Interface Descriptions for Completeness 16

17 IBM Global Services Verification Validation PAs Verification and Validation are similar, but they address different issues Purpose: To ensure, that selected work products meet their specified requirements Purpose: To demonstrate that a product / p.-component fulfills its intended use when placed in its intended environment You built the work product right You built the right thing 17 Copyright IBM Corporation 2003

18 Validation 18 Quelle: Universität Zürich

19 Requirements Management (ML 2) Specific Goals Generic Goals 19

20 Systems Engineering and Architecture, Global Services Requirements Traceability and Verification Matrix Created at the system level (based on systems requirements, traced to business requirements) Updated at the component level (tracing component Requirements to system requirements) Test and application information is added when known Test Types (examples): Functional / Component Verification Test Application system Control and Auditability System Integration Test Performance and Stress Test User acceptance Test System Engineering and Architecture Process Release /06/ IBM Corporation

21 RTVM (cut) Systems Engineering and Architecture, Global Services Requirements Traceability/Verification Matrix - <Project> Requirements Traceability Matrix Requirements Verification Matrix... Customer Test Type / Test Method System Component Requirements Affected Elements Design Documents Build Components Customer Acceptance Criteria FVT Test Method... R1 This is a customer requirement S1 This is a System requirement S1.1 C1.1 C1.2 This is a component requirement... R2 S2 S2.1 C System Engineering and Architecture Process Release /06/ IBM Corporation

22 SE & A Systems Engineering & Architecture The International Council on Systems Engineering IBM s Implementation 22

23 BASELINE NAME Systems Engineering and Architecture, Global Services Systems Engineering and Architecture Baseline Deliverables BASELINE DELIVERABLES BASELINE CREATED AT Customer Baseline System Baseline Component/ Application Baseline Customer Needs and Wants Test Architecture Business Requirements Specification (BRS) System Requirements Specification (SRS) Component / Application Requirements Specification (CRS) Architecture (System Level - what) Architecture (Component Level - how) Requirements Traceability Verification Matrix (RTVM) Component Requirements Traceability Verification Matrix Business Requirements Review (BRR) System Requirements Review (SRR) Preliminary Design Review (PDR) Component Test Plan Component Design Design Baseline Test Readiness System Test Strategy System Test Plan Test Cases (System and Component) System Test Data Test Traceability Matrix Critical Design Review (CDR) Test Readiness Review (TRR) LEGEND: Customer Provided Systems Engineering and Architecture Provided Component Developer Provided Testing organization Provided Production Readiness Review (PRR) 23 System Engineering and Architecture Process Release /06/ IBM Corporation

24 Systems Engineering and Architecture, Global Services Important Deliverables of the SE&A Process Business Requirements Specifications (optional) Business Requirements Review System Requirements Specifications System Requirements Review Component / Application Requirements Specification Preliminary Design Review Component Design, Component Test Plan Critical Design Review All reviews led by the Systems Engineer Test Readiness Review led by the Test Team Production Readiness Review led by the Project Manager Requirements Traceability/Verification Matrix SE&A Scorecards for all reviews 24 System Engineering and Architecture Process Release /06/ IBM Corporation

25 Systems Engineering and Architecture, Global Services Example: SE&A Scorecard template for SRR 25 System Engineering and Architecture Process Release /06/ IBM Corporation

26 IBM Global Services Method Custom Application Development 26

27 IBM Global Services Method Work Product Description APP 160: Usability Interactive Model IBM Global Services Interactive Model Work Product Description (WPD) Unique ID: APP 160 Copyright International Business Machines Corporation 1999, 2002 All Rights Reserved Version 4.1.1, August Description The Interactive Model is the blueprint for the user interface of an application. It illustrates the overall approach to a users experience with the application as it relates to navigation, content categories, grouping of functional elements, the logic of information layout, and high-level conceptual models of the application. Like architectural blueprints for a building, these work products provide an organizational framework that influences the technical architecture, and supports the appropriate media to enrich the users experience

28 Rational Unified Process 28

29 Rational Unified Process RUP Usability an important part of the process 29

30 V-Modell Struktur der Systemerstellung 30

31 V-Modell Ergonomieverantwortlicher 31

32 V-Modell Prüfspezifikation Benutzbarkeit Zu Usability-Tests: 32

33 Extreme Programming XP - one of several lightweight methodologies Flow chart 33

34 Extreme Programming XP Voraussetzungen für den Einsatz von XP Wechselnde Requirements in kurzen Zeitintervallen; kleine Programmiererteams mit zwei bis ca. 12 Personen; Entwicklerteam: Entwickler arbeiten mit Managern und Benutzern zusammen; Releaseplanung veranlasst von User Stories und explorativen Prototypen; quasi online mit häufigen und kleinen Releases, Iterationen etc. im Team; Units- und Funktions-Tests; Acceptance Tests (black box system tests) mit Test Szenarios aus User Stories; zusammen mit Benutzern Usability durch intensive Mitarbeit von Benutzern erreichen 34

35 Usability - in SW-Engineering-Prozessen - in CMMI Zusammenfassung Usability meist indirekt in allen Prozessen für die Entwicklung und Maintenance von Informationssystemen thematisiert Usability und Software-Ergonomie sind als wichtige Nichtfunktionale Eigenschaft eines Systems herausgearbeitet Deren Bedeutung ist hervorgehoben nicht wie eine gute Usability erreicht werden kann; vergleichbar mit der Beschreibung der Performance von Systemen Es ist sinnvoll, eine hohe Benutzbarkeit der Systeme durch das Arbeiten innerhalb von SW-Entwicklungs-Prozessen zu erreichen 35