Avra Software CMPUT 770 - Process Quality and Software Assessment Case Study - slide#1©P. Sorenson and Amr Kamel Assessment Plan for Assessment Plan for.

Slides:



Advertisements
Similar presentations
Requirements Specification and Management
Advertisements

E-OCVM (Version 2) Explained Episode 3 - CAATS II Final Dissemination Event Alistair Jackson EUROCONTROL Episode 3 Brussels, 13 & 14 Oct 2009.
Software Quality Assurance Plan
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
ITIL: Service Transition
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Stepan Potiyenko ISS Sr.SW Developer.
WM Software Process & Quality SPiCE Requirements - slide#1 1  Paul Sorenson REQUIREMENTS FOR A SPiCE ASSESSMENT A set of defined input information.
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Software Engineering General Project Management Software Requirements
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
WM Software Process & Quality Generic Processes - Slide #1  P. Sorenson SPiCE Reference Model - how to read Chapter 5 Capability Levels (process.
WM Software Process & QualityAssessment Prep - slide# 1©P. Sorenson Assessment Process documented  The Assessment Process must be documented. -
(c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 1 Documenting Analysis and Test.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
Chapter 5: Project Scope Management
Systems Engineering Management
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Development plan and quality plan for your Project
Software Configuration Management
Chapter 24 - Quality Management
Fundamentals of ISO.
What is Business Analysis Planning & Monitoring?
Web Development Process Description
S/W Project Management
Introduction to Software Quality Assurance (SQA)
Software Testing Lifecycle Practice
Requirements Analysis
Software Quality Assurance Activities
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Project Planning QMS Training.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
INFO 637Lecture #51 Software Engineering Process II Defining Requirements INFO 637 Glenn Booker.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Process Assessment Method
Lecture 7: Requirements Engineering
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Systems Development Life Cycle
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Consultant Advance Research Team. Outline UNDERSTANDING M&E DATA NEEDS PEOPLE, PARTNERSHIP AND PLANNING 1.Organizational structures with HIV M&E functions.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 Community-Based Care Readiness Assessment and Peer Review Overview Department of Children and Families And Florida Mental Health Institute.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Introduction to ITIL and ITIS. CONFIDENTIAL Agenda ITIL Introduction  What is ITIL?  ITIL History  ITIL Phases  ITIL Certification Introduction to.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
AUDIT STAFF TRAINING WORKSHOP 13 TH – 14 TH NOVEMBER 2014, HILTON HOTEL NAIROBI AUDIT PLANNING 1.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Sample Fit-Gap Kick-off
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Project Charter START IT! By Catherine B. Calio, PMP
Software Reviews.
Presentation transcript:

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#1©P. Sorenson and Amr Kamel Assessment Plan for Assessment Plan for Advanced GUI Ltd. 1. General 1.1 Objectives. This plan provides the basis for an initial capability determination for Advance GUI Ltd. Up to an including capability level 3 under a SPICE V2 Assessment This plan provides the basis for an initial capability determination for Advance GUI Ltd. Up to an including capability level 3 under a SPICE V2 Assessment

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#2©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 1.2 Background This second-party assessment by Avra Software will determine the capability of Advanced GUI Ltd.in its Engineering practices, based on the SPICE V2 model (published in May 6, 1996). The scope of the assessment will only include process ENG.2 (Develop Software Requirements). This second-party assessment by Avra Software will determine the capability of Advanced GUI Ltd.in its Engineering practices, based on the SPICE V2 model (published in May 6, 1996). The scope of the assessment will only include process ENG.2 (Develop Software Requirements). 1.3 Acknowledgement This plan is based on one used for the assessment of NewCo developed by Amr Kamel on Oct. 22, This plan is based on one used for the assessment of NewCo developed by Amr Kamel on Oct. 22, References SPICE - Part 5: An assessment model and indicator guidance.

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#3©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 2. Assessment Inputs 2.1 Assessment Purpose To perform a capability determination of Advanced GUI Ltd in its Engineering process, based on the SPICE V2 model (published in May 6, 1996). To perform a capability determination of Advanced GUI Ltd in its Engineering process, based on the SPICE V2 model (published in May 6, 1996). 2.2 Assessment Scope Processes The assessment will assess the process ENG 2 “Develop Software Requirements” up to and including level 3. The assessment will assess the process ENG 2 “Develop Software Requirements” up to and including level Organizational Unit See description in Section 2.2 of the case study

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#4©P. Sorenson and Amr Kamel Size Criticality Complexity App. Domain Technology Assessment Plan for Advanced GUI Ltd Target Characteristics The organizational characteristics are: The product characteristics are: Size Location Experience Small (25 software experts) Imaginville, Saskatchewan 12 year old company Reliability Portability Efficiency Usability Maintainability medium ? moderate medium GUI. financial sw components mandatory desirable GUI builders mandatory

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#5©P. Sorenson and Amr Kamel Lifecycle Method Language Environment Assessment Plan for Advanced GUI Ltd. The process characteristics are: unknown Evolutionary component dev. unknown PC-based 2.3 Assessment Constraints Assessment is based on a brief case study description plus instructor’s interpretation. Only one instance of the process is assessed. Assessment is based on a brief case study description plus instructor’s interpretation. Only one instance of the process is assessed. 3. Assessment Outputs 3.1 Deliverables i) Process profiles, ii) Assessment context, iii) Assessment final report i) Process profiles, ii) Assessment context, iii) Assessment final report

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#6©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 4. Assessment Team Roles and Responsibilities 4.1 Assessment Team Leader Mr. Paolo Ferrari, ESI Assessor -- duties as on page Qualified Assessors Paul Sorenson (ISO 9001 trained), Amr Kamel (SPICE trained) -- duties as on page 3. Paul Sorenson (ISO 9001 trained), Amr Kamel (SPICE trained) -- duties as on page Project Controls 5.1 Document Controls All documents become the property of Advanced GUI Ltd. 5.2 Risk Management No participants will be interviewed from engineering staff

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#7©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 6.`Quality Plan Quality Criteria As on page Quality Method The assessment will follow the Assessment Model defined in Part 5 of the SPICE 2 document. The assessment will follow the Assessment Model defined in Part 5 of the SPICE 2 document Assessment Team Meetings As on page 5 7. Key Activities 7.1 Assessment Initiation As on page 5 -- replace with today’s date and in-class initiation meeting. As on page 5 -- replace with today’s date and in-class initiation meeting. review page 4

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#8©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 7.2 Process Instance Selection For ENG 2 (Develop Software Requirements). Sample size is limited to one instance. For ENG 2 (Develop Software Requirements). Sample size is limited to one instance. 7.3 Assessment Preparation Assessment team preparation Assessors (instructors) prepared for this class through training courses, doing assessments and reviewing SPICE materials Assessors (instructors) prepared for this class through training courses, doing assessments and reviewing SPICE materials Assessment Planning Jan.7, 1996, Ferrari visited Advanced GUI to explain the SPICE Assessment process. Outline for this Assessment Plan has been developed by Paul Sorenson and Amr Kamel and submitted for the class for review. Jan.7, 1996, Ferrari visited Advanced GUI to explain the SPICE Assessment process. Outline for this Assessment Plan has been developed by Paul Sorenson and Amr Kamel and submitted for the class for review.

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#9©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd Organizational Unit Briefing Taking place now -- should include the items given on page 6 in NewCo example. Taking place now -- should include the items given on page 6 in NewCo example Assessment Techniques As on page Assessment Instrument Checklists will be developed Facilities We will use this room as a meeting and interview room Participant Selection Similar to what’s given on page 6.

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#10©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd Supporting Documentation Only the case study description and dialog are available 7.4 Information Gathering Information will be gathered by reviewing the case study description and dialog. Information will be gathered by reviewing the case study description and dialog. 7.5 Determining and Validating Ratings Rating determination will be as described in Part 5 of SPICE V2. No validation is possible. Rating determination will be as described in Part 5 of SPICE V2. No validation is possible. 7.6 Assessment Output The detailed findings will include consolidated ratings, identified risks, and proposed action plan. The detailed findings will include consolidated ratings, identified risks, and proposed action plan.

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#11©P. Sorenson and Amr Kamel Assessment Plan for Advanced GUI Ltd. 7.7 Follow-up As on page 7 8. Schedule ActivityTimeAssessorsProcess addressed Checklist developmt.NowPaul&AmrENG2. Checklist developmtNextAllENG5.,SUP1.,MAN1 InterviewN+30Team1ENG5. InterviewN+45Team2SUP1. InterviewN+60Team3MAN1. 9. Version Version 1.0, May 22, 1998

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#12©P. Sorenson and Amr Kamel Checklist ENG.2 Develop Software Requirements Checklist purposeDevelopment software requirements The purpose of the Development software requirements process is to establish the requirements of the software components of the result system. As a result of successful implementation of the process: the requirements allocated to software components of the system and their interfaces will be defined to match the customer’s stated and implied needs; analyzed, correct and testable software requirements will be developed the impact of software requirements on the operating environment will be understood

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#13©P. Sorenson and Amr Kamel ENG.2 Checklist (continued) a relevant software release strategy will be developed that defines the priority for implementing software requirements; the software requirements will be approved and updated as needed; the software requirements will be communicated to all affected parties 1. What is your strategy for determining and analyzing requirements of the software components of the system? 2. How do you document these requirements? 3. How do you determine the interfaces between the software requirements and other components of the operating environment?

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#14©P. Sorenson and Amr Kamel ENG.2 Checklist (continued) 4. What is your method of communicating the software requirements to the customer? How are revisions to requirements handled? 5. How do you prioritize software requirements and map them to future releases? 6. How do you use preliminary or prototypical versions of the system to affect the next iteration of requirements? 7. How and to whom do you disseminate software requirements and software requirement updates?

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#15©P. Sorenson and Amr Kamel ENG.2 Associated Work Products Input 52) Customer requirements 52) Maintenance requirements 44) Product needs assessments 83) Customer request 94) Change request 53) System design/architecture 84) Problem reports 87) Communication mechanisms 101) Database designInput 52) Customer requirements 52) Maintenance requirements 44) Product needs assessments 83) Customer request 94) Change request 53) System design/architecture 84) Problem reports 87) Communication mechanisms 101) Database designOutput 52) Software requirements 21) Analysis resultsOutput 52) Software requirements 21) Analysis results

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#16©P. Sorenson and Amr Kamel Generic Process Assessment PA 2.1 Performance Management 1. How do you identify the resource requirements needed to capture and update software requirements? 2. Show me a plan for the performance of requirements analysis that identified the activities to be undertaken the resources involved. 3. Show me how this plan is effective. 4. How are the planned requirements activities managed so that they remain within stated time and resource requirements?

Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#17©P. Sorenson and Amr Kamel Generic Process Assessment (cont.) PA 2.2 Work Product Management 1. What procedures and checks do you have in place to ensure the quality and integrity of your system requirements documents? 2. How do you manage different versions of the requirements documents and other requirement work products to ensure their integrity? 3. How do you manage the quality of the requirements documents and associated work products? In particular, how and by whom are they reviewed?