Software Engineering II - Exercise
|
|
- Maria Wilson
- 1 years ago
- Views:
Transcription
1 Software Engineering II - Exercise April 29 th 2009 Software Project Management Plan Bernd Bruegge Helmut Naughton Applied Software Engineering Technische Universitaet Muenchen 1
2 Date for the final exam To be determined next week 2
3 Decision time Can we reschedule exercises for WBS and Scheduling? Change 1: WBS Exercise Wednesday May 27 -> Friday May 29, 14:00-15:30 Change 2: Scheduling Exercise Wednesday June 3 -> Friday June 5, 14:00-15:30 3
4 Basic Definitions: Project and Project Plan Software Project: All technical and managerial activities required to turn over the deliverables to the client A software project has a specific duration, consumes resources and produces work products Management categories to complete a software project: Tasks, Activities, Functions Software Project Management Plan (SPMP): The controlling document for a software project Specifies the technical and managerial approaches to develop the software product Companion document to requirements analysis document: Changes in either may imply changes in the other document Also interdependent with the system design document The SPMP may be part of the project agreement. 4
5 Project: Functions, Activities and Tasks A project has a duration and consists of project functions, activities and tasks Project Function Function Activity Activity Activity Activity Activity Activity Task Task Task Task UML 5
6 Tasks, Activities and Project Functions (UML Class Diagram) duration Project duration Work * Task Activity Project Function «invariant» duration = project.duration 6
7 Project Function Definition Project Function: An activity or set of activities that span the duration of the project (called Workflow in the Unified Process model) Project Function Function Activity Activity Activity Activity Activity Activity Task Task Task Task 7
8 Examples of Project Functions Configuration Management Documentation Quality Control (V&V: verification and validation) Training Testing Project management activities UML Project functions in the IEEE 1058 standard (IEEE Standard for Software Project Management Plans) are called Integral processes in the IEEE 1074 standard (IEEE Standard for Developing a Software Project Life Cycle Process). Sometimes also called cross-development processes. 8
9 Tasks Project Function Function Activity Activity Activity Activity Activity Activity Task Task Task Task Smallest unit of work subject to management Small enough for adequate planning and tracking Large enough to avoid micro-management 9
10 Tasks Smallest unit of management accountability Atomic unit of planning and tracking Tasks have finite duration, need resources, produce tangible result (documents, code, models) Specification of a task: Work package Name, description of work to be done Preconditions for starting, duration, required resources Work product to be produced, acceptance criteria for it Risk involved Completion criteria Includes the acceptance criteria for the work products (deliverables) produced by the task. 10
11 Heuristics for Determining Task Sizes Finding the appropriate task size is problematic Todo lists from previous projects During initial planning a task is necessarily large You may not know how to decompose the problem into tasks at first Each software development activitity identifies more tasks and modifies existing ones Tasks must be decomposed into sizes that allow monitoring Depends on nature of work and how well task is understood. Work package should corresponds to a well defined work assignment for one participant for a week 11
12 Action Item Definition Action Item: A task assigned to a person (or in certain cases a role) to be done by a certain time What?, Who?, When? Heuristics for Duration: be done within two week or a week Definition Todo: An action item that is missing either the person/role or the deadline Examples of todos: Unit test class Foo, Develop the project plan for our project. Example of action items: Bob posts the next agenda for the context team meeting before May, 12 th, noon The test team develops the test plan by Sep 18 th Action items should be reviewed regularly (at least once a week) Status section in the meeting agenda. 12
13 Activities Project Function Function Activity Activity Activity Activity Activity Activity Task Task Task Task Major unit of work with precise dates Consists of smaller activities or tasks Culminates in project milestone. 13
14 Activities Major unit of work Culminates in major project milestone: Internal checkpoint (not be externally visible) External checkpoint, synchronization with the client Scheduled event used to measure progress A milestone often produces a project baseline: Formally reviewed work product Under change control (change requires formal procedures) Activitites may be grouped into larger activities: Establishes hierarchical structure for project (phase, step,...) Allows separation of concerns Precedence relations often exist among activities 14
15 Work package, Product, Baseline, Deliverable Work Package: A specification for the work to be accomplished in an activity or task Work Product: Any tangible item that results from a project function, activity or task. Project Baseline: A work product that has been formally reviewed and agreed upon. A project baseline can only be changed through a formal change procedure Project Deliverable: A work product to be delivered to the customer 15
16 Project Agreement (in traditional management approaches) Project Agreement: In traditional management, the document written for a client that defines: the scope, duration, cost and deliverables for the project. the exact items, quantities, delivery dates, delivery location. Client: Individual or organization that specifies the requirements and accepts the project deliverables. Deliverables: Work Products to be delivered to the client Documents Demonstrations of functions Demonstration of nonfunctional requirements Demonstrations of subsystems The form of a project agreement can be a contract, a statement of work, a business plan, or a project charter. 16
17 IEEE Std : Standard for Software Project Management Plans (SPMP) What it does: Specifies the format and contents of software project management plans. It provides a standard set of abstractions for a project manager or a whole organization to build its set of practices and procedures for developing software project management plans Abstractions: Project, Function, Activities, Tasks What it does not do: It does not specify the procedures or techniques to be used in the development of the plan It does not provide examples 17
18 Project Agreement, Problem Statement, SPMP Client (Sponsor) Project Manager Project Team Problem Statement Project Agreement Software Project Management Plan (SPMP) 18
19 Pros and Cons of Project Plans Advantages: Very useful to kick off a software project (to establish the goals, organize the teams, and start with development) Useful also for software projects if the outcome is predictable or when no major change occurs. Disadvantages: Of limited value to control software project when the outcome is unpredictable or when unexpected ( unusual ) events occur in the project that change the project context. Examples of unexpected events: Appearance of new technology which was unknown at project start. A visionary scenario turns out to be not implementable Company is merged with another one during the project 19
20 Project Documentation Even in modern, agile project management styles, project documentation is important Beneficiaries of well written documentation: The customer has a reference detailing the project to be used for reviews or further projects The developing company can also use old project documentation for planning future projects Best practice: The Software Project Management Plan IEEE Standard
21 Structure of a Software Project Management Plan (*) Front Matter 1. Overview 2. References 3. Definitions 4. Project organization 5. Managerial process plans 6. Technical process plans 7. Supporting process plans 8. Additional plans Back Matter (*) The template in figure in the textbook is out of date 21
22 SPMP: Front Matter Title page Signature page Change history Preface Table of contents List of figures List of tables 22
23 SPMP Clause 1: Overview 1.1 Project Summary Purpose, scope and objectives Concise summary of purpose, scope and objectives, integration with other projects, reference to requirements etc Assumptions and constraints Schedule, budget, resources, software to be reused/incorporated, technology to be employed, interfaces to other products Project deliverables List of work items with delivery dates, locations and quantities (also includes delivery media and packaging & handling) Schedule and budget summary Only itemization of major work activities here 1.2 Evolution of the SPMP Plans for anticipated and unanticipated change 23
24 SPMP Clause 2 + 3: References + Definitions 2. References Complete list of all documents and other sources of information references in the SPMP (has to include author, title, report number, date, author, path/name for electronic access and publisher etc.) 3. Definitions Define all terms and acronyms required to properly understand the SPMP 24
25 SPMP Clause 4: Project organization 4.1 External interfaces Organizational boundaries between project and external entities (parent, subcontractor, others ) 4.2 Internal structure Interfaces among the units of the software development team. Interfaces between project and supporting entities. Lines of authority, responsibility and communication within a project. 4.3 Roles and responsibilities State and nature of major work activities and support processes and organizational units responsible for them. Often depicted in matrix form. 25
26 SPMP Clause 5: Managerial process plans 5.1 Start-up plan Estimation plan Cost and schedule with estimation methods, tools and techniques Staffing plan Number of staff by required skill level, phase, duration. Staff sources Resource acquisition plan Resource acquisition process for equipment, training, transportation, facilities etc Project staff training plan Types of training, number of personnel to be trained, entry and exit criteria for training, training method. Both for technical and managerial training. 26
27 SPMP Clause 5: Managerial process plans 5.2 Work plan Work activities Work breakdown structure with work packages detailing needed resources, estimated duration, work products to be produced, predecessor, successor, etc Schedule allocation Depicts time-sequencing constraints and opportunities for concurrency. Techniques include Gantt and PERT charts etc Resource allocation Detailed itemization of resources allocated to each major work activity. This includes personnel, tools, facilities, administrative support etc Budget allocation Breakdown of necessary resource budgets for each major work activity. Costs for personnel, travel, meetings, tools, etc. 27
28 SPMP Clause 5: Managerial process plans 5.3 Control plan Requirements control plan Controls changes to project requirements Schedule control plan Measure progress of work completed and corrective measures Budget control plan Measure cost of work completed and comparison with budget Quality control plan Quality control mechanisms (v&v, reviews, audits, etc.) Reporting plan Reporting mechanisms, format, information flows Metrics collection plan Methods, tools and techniques for collecting and retaining project metrics. 28
29 SPMP Clause 5: Managerial process plans 5.4 Risk management plan Identify, analyze and prioritize project risk factors. Describe procedures for contingency planning and methods for tracking risk factors. 5.5 Closeout plan Staff reassignment, archiving project materials, post-mortem debriefing plan, preparation for lessons learned and analysis of project objectives archived. 29
30 SPMP Clause 6: Technical process plan 6.1 Process model Flow of information and work products among activities and functions. Timing of deliverables, reviews, milestones etc. 6.2 Methods, tools and techniques Development methodologies, programming languages, tools and techniques etc. to be used in the project. 6.3 Infrastructure plans Development environment (workstations, LAN, software tools etc.). Also includes policies, procedures, standards etc. 6.4 Project acceptance plan Objective criteria for determining acceptability of deliverables. 30
31 SPMP Clause 7: Supporting process plans 7.1 Configuration management plan Configuration accounting, control, status accounting, evaluation, release management, change management etc. 7.2 Verification and validation plan Traceability, milestone review, progress review, peer review, prototyping, simulation, modeling 7.3 Documentation plan Deliverable and non-deliverable documentation products 7.4 Quality assurance plan Analysis, inspection, review, audit, assessment 31
32 SPMP Clause 7: Supporting process plans 7.5 Reviews and audits Schedule, resources, methods and procedures 7.6 Problem resolution plan Reporting, analyzing, prioritizing and processing software problems 7.7 Subcontractor management plan Selecting and managing subcontractors 7.8 Process improvement plan Periodical assessment of the project to determine areas for improvement and implementing improvement plans. 32
33 SPMP: Clause 8 & Back Matter 8. Additional plans Plans required to satisfy product requirements and contractual terms (safety, privacy, security requirements, user training, integration, data conversion, system transition, maintenance etc.) Back Matter Annexes Includes directly or by reference provided supporting details that could detract from the SPMP if included in its body. Index Index of key terms and acronyms. 33
34 Observations about planning What type of model does the template defined by IEEE represent? Object model (UML class diagram) What is missing from an object model for planning? Dynamic behavior - when do we do planning? (UML sequence diagrams, activity diagrams and state machine diagrams) Different approaches to planning: Traditional: Plan at the start of a project, then the plan is fixed (at least for an iteration) [Royce, 1998] Transitional: Plan in parallel with the system design (evolution of the architecture) [Paulish, 2002] Agile: Plan continuously during the project duration (incremental and iterative refinement) [Cohn, 2006] 34
35 Readings Information on topics covered today Bruegge/Dutoit, Chapter 14: Project Management Standard for Software Project Management Plans [IEEE Std ] Walker Royce, Software Project Management: A Unified Framework, Addison-Wesley, 1998 Daniel J. Paulish, Architecture-Centric Software Project Management: A Practical Guide, Addison-Wesley, 2002 Mike Cohn, Agile Estimating and Planning, Prentice Hall,
36 Homework Task: Choose a large software project and write an SPMP for that project based on IEEE Find (write) an (idealized) plan Do post-mortem analysis using information available on the internet if necessary You can work in teams with up to 6 participants Submission date is July 1 st 2009, 2PM 36
37 If you cannot think of a suitable project Organizing a hiking trip Organizing a wedding Organizing a reunion with your classmates Celebrating the end of SE II POM All of these are acceptable (even though they do not have anything to do with software engineering) Or maybe you would like to take up a bigger challenge 37
38 Example 1: Heathrow Terminal 5 38
39 Example 2: Airbus A380 39
40 Example 3: Toll collect 40
41 Example 4: Dolli (2) 41
42 Homework Task: Choose a large software project and write an SPMP for that project based on IEEE Find (write) an (idealized) plan Do post-mortem analysis using information available on the internet if necessary You can work in teams with up to 6 participants Submission date is July 1 st 2009, 2PM Oral presentation of these plans on July 1 st 2009 in the exercise session 42
43 Summary Software engineering is a problem solving activity Developing quality software for a complex problem within a limited time while things are changing The system models addresses the technical aspects Object model, functional model, dynamic model Other models address the management aspects WBS, Schedule Task models, Issue models, Cost models Important terms Software lifecycle, Project, Activity, Function, Task, WBS, SPMP This was an introduction to the managerial issues in software engineering We will elaborate on many of these concepts in more detail as we go along through the lectures. 43
PRINCESS NOURA UNIVESRSITY. Project Management BUS 302. Reem Al-Qahtani
PRINCESS NOURA UNIVESRSITY Project BUS 302 Reem Al-Qahtani This is only for helping reading the PMBOK it has our notes for focusing on the book Project Framework What is PMBOK? o PMBOK= Project Body of
PMBOK Guide Fifth Edition Pre Release Version October 10, 2012
5.3.1 Define Scope: Inputs PMBOK Guide Fifth Edition 5.3.1.1 Scope Management Plan Described in Section 5.1.3.1.The scope management plan is a component of the project management plan that establishes
PMI Scheduling Professional (PMI-SP)
PMI Scheduling Professional (PMI-SP) E X A M I N AT I O N CO N T E N T O U T L I N E Project Management Institute PMI Scheduling Professional (PMI-SP) Exam Content Outline Published by: Project Management
Project Plan. CxOne Guide
Project Plan CxOne Guide CxGuide_ProjectPlan.doc November 5, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 DELIVERABLE PURPOSE... 1 1.2 LIFECYCLE...
Object-Oriented Software Engineering! Using UML, Patterns, and Java! Chapter 3, Project Organization and Communication
Object-Oriented Software Engineering! Using UML, Patterns, and Java! Chapter 3, Project Organization and Communication How it should go Requirements! Analysis! Design! Implementation! System Testing! Delivery
Agile Project Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Agile Project Management Outline A mountaineering example Project context Goals, client types Environment, methods, tools, methodology
PROJECT PLAN. LCG Software Process & Infrastructure ( SPI )
PROJECT PLAN Organization: Project name ( SPI ) Document Revision #: 1.0 Date of Issue: 11.10.2002 Project Manager: Alberto Aimar Approval Signatures Approved by: Business Project Leader Approved by: Project
PART THREE: Work Plan and IV&V Methodology (RFP 5.3.3)
PART THREE: Work Plan and IV&V Methodology (RFP 5.3.3) 3.1 IV&V Methodology and Work Plan 3.1.1 NTT DATA IV&V Framework We believe that successful IV&V is more than just verification that the processes
MBP1123 Project Scope, Time and Cost Management Prepared by Dr Khairul Anuar
MBP1123 Project Scope, Time and Cost Management Prepared by Dr Khairul Anuar L2 Project Scope Management www.notes638.wordpress.com Project Scope Management Scope initiation/planning Scope definition Issue
A Primer for the Project Management Process by David W. Larsen 1. Table of Contents
A Primer for the Project Management Process by David W. Larsen 1 Table of Contents Description... 2 STAGE/STEP/TASK SUMMARY LIST... 3 Project Initiation 3 Project Control 4 Project Closure 6 Project Initiation...
The 9 knowledge Areas and the 42 Processes Based on the PMBoK 4th
The 9 knowledge Areas and the 42 Processes Based on the PMBoK 4th www.pmlead.net PMI, PMP, CAPM and PMBOK Guide are trademarks of the Project Management Institute, Inc. PMI has not endorsed and did not
National Aeronautics and Space Administration Washington, DC 20546
Technical Standards Division Publication NASA-STD-2100-91 NASA Software Documentation Standard Software Engineering Program NASA-STD-2100-91 -91 Approved: July 29, 1991 National Aeronautics and Space Administration
Management of Projects
of Projects Giuseppe Lami Page 1 Course Outline! Part 1: The Project (PM) Framework! Part 2: The PM as a Process! Part 3: Techniques, Methods and Tools Supporting the PM! Part 4: Requirements Engineering
1.Which of the items listed below is not one of the software engineering layers?
1.Which of the items listed below is not one of the software engineering layers? Process Manufacturing Methods Tools 2.The software quality assurance activity which is performed to check errors in logic,
CSU Project Management Certificate Program. Project Scope Management
CSU Project Management Certificate Program Project Scope Management Instructor: George Angel eaglebusiness@hotmail.com 303-678-9466 1 Scope gone wild! client wants what? 2 Project Scope Management Agenda
CHAPTER 2: IMPLEMENTATION PHASES AND OFFERINGS
CHAPTER 2: IMPLEMENTATION PHASES AND OFFERINGS Objectives Introduction The objectives are: Describe the purpose of the phase planning activity, preconditions, and deliverables in the implementation methodology.
7.11b: Quality in Project Management: A Comparison of PRINCE2 Against PMBOK
by Peter Whitelaw, Rational Management Pty Ltd, Melbourne Introduction This comparison takes each part of the PMBOK and provides comments on what match there is with elements of the PRINCE2 method. It's
Requirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
Project Report Template (Sem 1)
1. Introduction & Problem Statement Project Report Template (Sem 1)
Software Lifecycle Models
Software Lifecycle Models Introduction into Software Engineering Lecture 18 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Definitions Software life cycle Set of activities
Project Organization Software Engineering II
Object-Oriented Software Engineering Using UML, Patterns, and Java Project Organization Software Engineering II 23 June 2009 Bernd Bruegge Technische Universität München Department of Informatics Chair
Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
Object-Oriented and Classical Software Engineering
Slide 3.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 3 Slide 3.2 THE SOFTWARE PROCESS Overview Slide 3.3
Number: DI-IPSC-81427B Approval Date:
DATA ITEM DESCRIPTION Title: Software Development Plan (SDP) Number: DI-IPSC-81427B Approval Date: 20170313 AMSC Number: N9775 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity:
Project Origination: Item Description (Origination) Comments (or reasons for NOT completing)
Project Origination: (Origination) Develop Project Proposal: 24 Formulate business need/problem and 24 anticipated benefits to all parties Review project s fit with organization s mission 24 Identify project
Lesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence,
Lesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence, Instructors YOU ARE HERE Analysis and the Decision to
INFORMATION TECHNOLOGY PROJECT MANAGEMENT. Fourth Edition. International Student Version. Jack T. Marchewka WILEY. John Wiley & Sons, Inc.
INFORMATION TECHNOLOGY PROJECT MANAGEMENT Fourth Edition International Student Version Jack T. Marchewka WILEY John Wiley & Sons, Inc. PREFACE xvii ABOUT THE AUTHOR xxiii CHAPTER 1 An Overview of IT Project
Project Management Context Outline
Project Management Context Outline Project Phases and the Project Life Cycle Product Life Cycles Project Stakeholders Understanding Organizational Influences Suggested Skills for a Project Manager 1 Project
CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide
processlabs CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide CMMI-DEV V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAR - Causal Analysis and Resolution...
PMI-001 Questions & Answers
PMI-001 Questions & Answers Number: PMI-001 Passing Score: 700 Time Limit: 137 min File Version: 21.2 http://www.gratisexam.com/ PMI-001 Questions & Answers Exam Name: Project Management Professional v5
S O Seminar Objective
Introduction to Project Management Welcome! Presenter: Bob Hull CalACT Conference September 202 S O Seminar Objective To provide an overview of project management processes and provide some skills, tools
Introduction to Software Project Management. CITS3220 Software Requirements & Project Management
Introduction to Software Project Management CITS3220 Software Requirements & Project Management "A project gets a year late one day at a time." "Anything that can be changed will be changed until there
Integration Mgmt / Initiating Process Group 4.1 Develop Project Charter
1 Mgmt / Initiating Process Group 4.1 Develop Project Charter Project statement of work Business Case Contract Enterprise environmental factors Project charter Expert judgement 26/02/2013 18:22:56 1 2
For the PMP Exam using PMBOK Guide 5 th Edition. PMI, PMP, PMBOK Guide are registered trade marks of Project Management Institute, Inc.
For the PMP Exam using PMBOK Guide 5 th Edition PMI, PMP, PMBOK Guide are registered trade marks of Project Management Institute, Inc. 1 Contacts Name: Khaled El-Nakib, MSc, PMP, PMI-RMP URL: http://www.khaledelnakib.com
Contents. Today Project Management. What is Project Management? Project Management Activities. Project Resources
Contents Last Time - Software Development Processes Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software
VC SOFTWARE PROJECT MANAGEMENT PLAN
VC SOFTWARE PROJECT MANAGEMENT PLAN Supporting Process Plan This part will contain plans for the supporting processes that span the duration of the software project. Team #4 Members: Yazeed Al-Swailem
Project Cost Management
PMBOK Overview A Guide to the Body of Knowledge (PMBOK), created by the Institute (PMI), is the sum of knowledge within the profession of project management. The complete Body of Knowledge includes proven
CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide
processlabs CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide CMMI-SVC V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAM - Capacity and Availability Management...
Defining Project Scope
Defining Project Scope Casey Ayers PMP MBA CaseyAyers.com @caseyayers linkedin.com/in/caseyayers PMP is a registered mark of the Project Management Institute, Inc. Module Overview Overview Project Scope
Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
Initiation Group Process. Planning Group Process
Initiation Group Process Develop Project Charter Project statement of work Expert judgment Project charter Business case Contract (if third party project) EEF: government/industry standards, organizational
Redesigning the Organization with Information Systems
Chapter 14 Redesigning the Organization with Information Systems 14.1 2006 by Prentice Hall OBJECTIVES Demonstrate how building new systems produces organizational change Explain how a company can develop
Content Break-up & Methodology for awarding Contact Hours / PDUs
N.I.T.E - Project Management Professional (PMP) Exam Prep Course Content Break-up & Methodology for awarding Contact Hours / PDUs This course is based on Project Management Book of Knowledge PMBOK Guide
This resource is associated with the following paper: Assessing the maturity of software testing services using CMMI-SVC: an industrial case study
RESOURCE: MATURITY LEVELS OF THE CUSTOMIZED CMMI-SVC FOR TESTING SERVICES AND THEIR PROCESS AREAS This resource is associated with the following paper: Assessing the maturity of software testing services
Estimating Project Schedule-Time and Cost
Estimating Project Schedule-Time and Cost Chapter 5 5 1 Where We Are Now 5 2 1 Overview Seminar Agenda What is involved in schedule and cost management? In-depth Determining the sequence of activities
Evolutionary Differences Between CMM for Software and the CMMI
Evolutionary Differences Between CMM for Software and the CMMI Welcome WelKom Huan Yín Bienvenue Bienvenido Wilkommen????S???S??? Bienvenuto Tervetuloa Välkommen Witamy - 2 Adapting an An Integrated Approach
PMP Sample Questions Click here for PMP Questions. Question No : 1 Which of the following is an output of Define Scope?
PMP Sample Questions www.techfaq360.com Click here for 1600+ PMP Questions Question No : 1 Which of the following is an output of Define Scope? A. Accepted deliverables B. Change Requests C. Project document
PROJECT SCOPE MANAGEMENT PLAN TEMPLATE
PROJECT SCOPE MANAGEMENT PLAN TEMPLATE This template guides you through each stage of preparing an effective scope management plan that ensures success. With this plan you clearly state the exact work
CMMI for Technical Staff
CMMI for Technical Staff SES CMMI Training Series April 7, 2009 Audio Conference #: Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM
Total Questions: 370 MODULE QUIZ ANSWER KEY. Fundamentals 1 & 2
Fundamentals 1 & 2 1. Answer: B Process Group. Each project management knowledge area is subdivided into specific process group, each of which is characterized by their inputs, tools and techniques, and
Copyright 2013 Pearson Education, Inc. Publishing as Prentice Hall 5-1
Copyright 2013 Pearson Education, Inc. Publishing as Prentice Hall -1 Learning objectives Manage the planning process of a project Understand the work breakdown structure of a project Understand different
AUTOMOTIVE SPICE v3.1 POCKET GUIDE
EXTENDED VDA SCOPE ASPICE v3.1 AUTOMOTIVE SPICE v3.1 POCKET GUIDE 4 5 6 7 8-9 10 11-13 14-15 16-19 20-43 44-49 50-51 52-69 70-93 94-103 104-105 106 Automotive SPICE at a glance Automotive SPICE application
Introduction to Project Management
Introduction to Project Management University Business Institute Amir Dabirian Vice President for Information Technology/CIO March 21 st, 2012 2 The Man Month Men and months are interchangeable commodities
Selecting Software Development Life Cycles. Adapted from Chapter 4, Futrell
Selecting Software Development Life Cycles Adapted from Chapter 4, Futrell Examples of Software Life Cycle Models Classical Waterfall Waterfall with feedback V-Shaped Prototyping Incremental Spiral Rapid
Agenda. PMBOK Guide Third Edition. PMI Standards Background. PMI Life Cycle Plan for Standards. Presented by Kevin Chui, PMP. How Did We Get Here?
Agenda PMBOK Guide Third Edition Presented by Kevin Chui, PMP Vice President, PMI Hong Kong Chapter Background PMBOK Guide 2004 Update Project Structural Changes to the Standard Process Group Changes Knowledge
Integration and Testing
Integration and Testing 1 Today Software Quality Assurance Integration Test planning Types of testing Test metrics Test tools 2 Deliverables by Phase Possible Deliverables by Phase Concept Document Statement
17/12/1437. Lecture. Project Scope Management. Lecture 4. Project Management Knowledge Areas Section 3 Chapter 5. Project Scope Management.
17/12/137 Project Management Knowledge Areas Section 3 Chapter 5 Project Scope Management 2 of 33 1 17/12/137 Quick Re-cab Plan Scope Management Collect Requirement Define Scope Create WBS Validate Scope
V&V = the Verification and Validation of Deliverables
V&V = the Verification and Validation of Deliverables Verification and validation (V&V) are separated in the PMBOK Guide, but should be viewed as two integrated elements in the process of creating value
The Agile PMP Teaching an Old Dog New Tricks
The Agile PMP Teaching an Old Dog New Tricks Why are we here today? What is Project Management? When will the project be done? How much will it cost? Do we all agree on what done looks like? What are the
Advantages and Disadvantages of. Independent Tests. Advantages. Disadvantages
8.0 Test Management Outline 8.1 Test organisation 8.2 Test planning and estimation 8.3 Test program monitoring and control 8.4 Configuration management 8.5 Risk and testing 8.6 Summary Independent Testing
Factors to Consider When Implementing Automated Software Testing
Factors to Consider When Implementing Automated Software Testing By Larry Yang, MBA, SSCP, Security+, Oracle DBA OCA, ASTQB CTFL, ITIL V3 ITM Testing is a major component of the Software Development Lifecycle
Requirements Gathering using Object-Oriented Models
Requirements Gathering using Object-Oriented Models roject Management roject project is a temporary venture decided to create a single product, service or outcome. 1 rojects Vs Operations (services) rojects
Project Management Professional (PMP) Boot Camp
Project Management Professional (PMP) Boot Camp According to the Project Management Institute, the world's leading association for the project management profession: "PMP Certification is the profession's
Chapter 3 Managing the Information Systems Project
Princess Noura University Computer Science and Information Faculty Information Systems Department IS321 Chapter 3 Managing the Information Systems Project Learning Objectives Discuss skills required to
GAIA. GAIA Software Product Assurance Requirements for Subcontractors. Name and Function Date Signature 15/09/05 15/09/05 15/09/05 15/09/05 15/09/05
Title Page : i Software Product Assurance Requirements for Subcontractors Name and Function Date Signature Prepared by D.MUNCH Prime Contractor SPA Manager 15/09/05 Verified by D.PERKINS E-SVM PA Manager
WORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B
1. Work Plan & IV&V Methodology 1.1 Compass Solutions IV&V Approach The Compass Solutions Independent Verification and Validation approach is based on the Enterprise Performance Life Cycle (EPLC) framework
Standards Harmonization Process for Health IT
Evaluation of Standards Harmonization Process for Health Information Technology Contract HHSP23320054105EC Standards Harmonization Process for Health IT Document Number: HITSP 06 N 89 May 30, 2006 Date:
Project Management Professional (PMP)
Project Management Professional (PMP) E X A M I N AT I O N CO N T E N T O U T L I N E Project Management Institute Project Management Professional (PMP) Examination Content Outline June 2015 Published
Requirements Engineering Best Practices
White Paper Requirements Engineering Best Practices July 2015 by Kevin Parker, Vice President of Worldwide Marketing, Serena Software (Now Part of Micro Focus ) Table of Contents Are Requirements Still
SUSE Unified Delivery Process
Guide www.suse.com SUSE Unified Delivery Process What Is the SUSE Unified Delivery Process? The SUSE Unified Delivery Process is a solution delivery process based on the IBM* Rational Unified Process*
Scrum, Creating Great Products & Critical Systems
Scrum, Creating Great Products & Critical Systems What to Worry About, What s Missing, How to Fix it Neil Potter The Process Group neil@processgroup.com processgroup.com Version 1.2 1 Agenda Scrum / Agile
CMMI Project Management Refresher Training
CMMI Project Management Refresher Training Classifica(on 2: Foxhole Technology Employees Only RMD 032 Project Management Refresher Training Course September 21, 2017 Version 1.0 The Process Approach The
Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at
Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Study of Software Development Life Cycle Process Models
Requirements Elicitation
Requirements Elicitation Software Engineering I Lecture 4 14. November 2006 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline Motivation Requirements elicitation challenges
Project Management Institute (PMI) Practice Standard for Configuration Management
Project Configuration Management Project Management Institute (PMI) Practice Standard for Configuration Management Project Configuration Management What we will cover: Introduction Relationship with other
Chapter. Redesigning The Organization With Information Systems
Chapter Redesigning The Organization With Information Systems 1 Objectives Demonstrate how building new systems produces organizational change Explain how a company can develop information systems that
Scope Management 3/11/2015. Chapter 5 Learning Objectives. Project Scope. 1) Conceptual development. Problem Statements. Statement of Work (SOW)
Chapter 5 Learning Objectives Scope Management 05-01 Project Scope 05-02 Conceptual Development The process that addresses project objectives by finding the best ways to meet them. Project scope is everything
CHAPTER 1 Introduction
CHAPTER 1 Introduction The Standard for Program Management provides guidelines for managing programs within an organization. It defines program management and related concepts, describes the program management
Software Engineering Fall 2014
Software Engineering Fall 2014 (CSC 4350/6350) Mon.- Wed. 5:30 pm 7:15 pm ALC : 107 Rao Casturi 11/05/2014 Student Registration System (SRS) RC University Management Board approved a new Student Registration
Testkings PMP 705q. PMI PMP. Project Management Professional v5
Testkings PMP 705q Number: PMP Passing Score: 800 Time Limit: 120 min File Version: 14.5 PMI PMP Project Management Professional v5 This is my first share of braindumps questions. Very helpful study center
CERTIFIED SOFTWARE QUALITY ENGINEER
CSQE CERTIFIED SOFTWARE QUALITY ENGINEER Quality excellence to enhance your career and boost your organization s bottom line asq.org/cert Certification from ASQ is considered a mark of quality excellence
Chapter 2: The Project Management and Information Technology Context
Chapter 2: The Project Management and Information Technology Context TRUE/FALSE 1. Many of the theories and concepts of project management are difficult to understand. F PTS: 1 REF: 44 2. If project managers
TECHNICAL REVIEWS AND AUDITS
Chapter 11 Technical Reviews and Audits CHAPTER 11 TECHNICAL REVIEWS AND AUDITS 11.1 PROGRESS MEASUREMENT The Systems Engineer measures design progress and maturity by assessing its development at key
A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0 Skillport
A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0 by The International Institute of Business Analysis (IIBA) International Institute of Business Analysis. (c) 2009. Copying
An Oracle White Paper February Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions
An Oracle White Paper February 2014 Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions Executive Overview... 1 Introduction... 1 Standards Based...
Criteria for Method Selection and Process Design of a Technical Development Strategy
Criteria for Method Selection and Process Design of a Technical Development Strategy Suja Joseph-Malherbe CSIR sjoseph@csir.co.za sjosephmalherbe@gmail.com Copyright 2012 by Suja Joseph-Malherbe. Published
CMMI and FPA. the link and benefit of using FPA when rolling out CMMI. Christine Green IFPUG - Certified Function Point Specialist EDS
CMMI and FPA the link and benefit of using FPA when rolling out CMMI Christine Green IFPUG - Certified Function Point Specialist EDS and the EDS logo are registered trademarks of Electronic Data Systems
Introduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
GUIDE TO THE CHANGES IN PMP simpl learn i
GUIDE TO THE CHANGES IN PMP- 2015 simpl learn i Table of contents Introduction the purpose of this manual 1 New Tasks: Initiating 3 New Tasks: Planning 4 New Tasks: Executing 6 New Tasks: Monitoring and
[Name] [ ID] [Contact Number]
[Name] [Email ID] [Contact Number] THIS IS ONLY MODEL RESUME - DO NOT COPY AND PASTE INTO YOUR RESUME. PROFILE SUMMARY 15+ years of IT experience in Consulting and worked with the Major clients for the
TAMING COMPLEXITY ON MAJOR RAIL PROJECTS WITH A COLLABORATIVE SYSTEMS ENGINEERING APPROACH
TAMING COMPLEXITY ON MAJOR RAIL PROJECTS WITH A COLLABORATIVE SYSTEMS ENGINEERING APPROACH Chris Rolison CEO, Comply Serve Limited The Collaborative Systems Engineering Approach Collaboration A system
SEI Architecture Techniques complementary to the RUP Stuart Kerrigan, Richard van Schelven Principal Engineers Data Networks
SEI Architecture Techniques complementary to the RUP Principal Engineers Data Networks SATURN 14 th -16 th May 2007 Agenda Setting the scene SEI & the RUP Summary Future Work Q&A SATURN 14 th -16 th May
DATA ITEM DESCRIPTION
DATA ITEM DESCRIPTION Title: HUMAN SYSTEMS INTEGRATION PROGRAM PLAN Number: Approval Date: 20070404 AMSC Number: N7716 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: N/A Office of Primary Responsibility:
Software Engineering Fall 2014
Software Engineering Fall 2014 (CSC 4350/6350) Mon.- Wed. 5:30 pm 7:15 pm ALC : 107 Rao Casturi 09/17/2014 What is next Deliverable? Due: 09/19/2014 1. Problem Statement with Shall statements 2. RTM (4
Project Management Overview 4/17/2013 1
Project Management Overview 4/17/2013 1 Without Project Management 4/17/2013 2 Without Project Management 4/17/2013 3 What is a Project? A temporary and one-time endeavor undertaken to create a unique
INTEGRATED SOFTWARE QUALITY MANAGEMENT (ISQM)
Guide for Integrated Software Quality Management (ISQM) GUIDE FOR INTEGRATED SOFTWARE QUALITY MANAGEMENT (ISQM) SEPTEMBER 2012 (Updated February 2016 see next page) American Bureau of Shipping Incorporated
7/26/2016 ARETE-ZOE, LLC 1
Registered address: 1334 E Chandler Blvd 5 A-19, Phoenix 85048 Arizona, USA T: +1-480-409-0778 Skype: arete-zoe veronikav@arete-zoe.com Website SlideShare 7/26/2016 ARETE-ZOE, LLC 1 RISK MANAGEMENT PROCESS
CONTENTS PART ONE FOUNDATIONS FOR SYSTEMS DEVELOPMENT. Preface 21
CONTENTS Preface 21 PART ONE FOUNDATIONS FOR SYSTEMS DEVELOPMENT AN OVERVIEW OF PART ONE :»o SYSTEMS DEVELOPMENT IN AN ORGANIZATIONAL CONTEXT 31 Learning Objectives 31 Introduction 31 A Modern Approach
Introduction to Software Engineering
Introduction to Software Engineering 2. Requirements Collection Mircea F. Lungu Based on a lecture by Oscar Nierstrasz. Roadmap > The Requirements Engineering Process > Functional and non-functional requirements