Chapter 12 Evaluating Products, Processes, and Resources.

Slides:



Advertisements
Similar presentations
Project Quality Management
Advertisements

Chapter 24 Quality Management.
© LOUIS COHEN, LAWRENCE MANION & KEITH MORRISON
© 2006 The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Validity and Reliability Chapter Eight.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Ch 3 System Development Environment
Introduction to Research Methodology
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
Chapter 15 Application of Computer Simulation and Modeling.
Stepan Potiyenko ISS Sr.SW Developer.
Software Testing and Quality Assurance
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
Fundamentals of Information Systems, Second Edition
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Overview of Software Requirements
Minnesota Manual of Accommodations for Students with Disabilities Training Guide
SOFTWARE PROJECT MANAGEMENT Project Quality Management Dr. Ahmet TÜMAY, PMP.
Software Process and Product Metrics
Project Documentation and its use in Testing JTALKS.
Validity Lecture Overview Overview of the concept Different types of validity Threats to validity and strategies for handling them Examples of validity.
Customer Focus Module Preview
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
Measurement and Data Quality
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
Chapter 10 Architectural Design
Introduction to Software Quality Assurance (SQA)
Chapter 1: Introduction to Statistics
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 2 The process Process, Methods, and Tools
Chapter 8: Systems analysis and design
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Teaching material for a course in Software Project Management & Software Engineering – part II.
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.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
CHAPTER 12 Descriptive, Program Evaluation, and Advanced Methods.
Chap. 5 Building Valid, Credible, and Appropriately Detailed Simulation Models.
Chapter 3: Software Project Management Metrics
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Sociological Research Methods. The Research Process Sociologists answer questions about society through empirical research (observation and experiments)
CS211 Slide 3-1 ADCS 21 Systems Analysis Phase Overview Systems Requirements Checklist Fact-Finding techniques Documentation (Chapter 3) SYSTEMS ANALYSIS.
CHAPTER 2 Research Methods in Industrial/Organizational Psychology
OPERATING SYSTEMS CS 3530 Summer 2014 Systems and Models Chapter 03.
Software Engineering Issues Software Engineering Concepts System Specifications Procedural Design Object-Oriented Design System Testing.
1-1 Copyright © 2014, 2011, and 2008 Pearson Education, Inc.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Selecting Research Design   The overall plan made by the researcher to get answers to research questions and for testing the hypothesis.   It is the.
Requirements Analysis
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
Chapter 4 Test Design Techniques MNN1063 System Testing and Evaluation.
Open Forum: Scaling Up and Sustaining Interventions Moderator: Carol O'Donnell, NCER
© 2006 by The McGraw-Hill Companies, Inc. All rights reserved. 1 Chapter 1 Introduction to Research in Communication Research: –Process of asking questions.
Software Engineering Lecture 9: Configuration Management.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
SCIENTIFIC METHOD RESEARCH METHODS ETHICS PSYCHOLOGICAL RESARCH.
Copyright © 2014 Wolters Kluwer Health | Lippincott Williams & Wilkins Chapter 11 Measurement and Data Quality.
Emilia Mendes1 Professora Visitante CAPES/ Associate Professor Univ. Auckland, NZ. Introdução a Métricas, Qualidade e Medição de Software.
SOFTWARE TESTING AND QUALITY ASSURANCE. Software Testing.
Software Configuration Management
OPERATING SYSTEMS CS 3502 Fall 2017
CS4311 Spring 2011 Process Improvement Dr
CHAPTER 2 Research Methods in Industrial/Organizational Psychology
CHAPTER 2 Testing Throughout the Software Life Cycle
Software metrics.
Requirements Document
Chapter 22, Part
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

Chapter 12 Evaluating Products, Processes, and Resources

Review  Software engineering provides a large variety of methods and tools for use by software developers throughout the software life-cycle.  What are some of them?

Review of S.E. Methods and Tools 1.Project Management 2.Requirements Engineering 3.Architectural Design 4.Implementation 5.Testing 6.Maintenance

Discussion Question  In a given situation, how do developers decide which method or tool is the most appropriate to use?

Discussion Question  How can developers tell if a change to the development process actually results in improvement?

Discussion Question  How can developers evaluate the effectiveness and efficiency of what they are already doing, so that they can tell if a change to the development process actually results in improvement?

Discussion Question  Once a change has been made, how can developers demonstrate that the products, processes and resources have the desired characteristics (such as improved quality)?

Chapter 12 Contents  Approaches to Evaluation  Selecting an Evaluation Technique  Assessment vs. Prediction  Evaluating Products  Evaluating Processes  Evaluating Resources

Approaches to Evaluation  Measure key aspects of product, processes, and resources and use this information to  Determine whether we have met goals for productivity, performance, quality, and other desire attributes

Four Categories of Evaluation Techniques  Feature analysis rate and rank attributes  Surveys document relationships and outcomes  Case studies compare with situation with another  Formal experiments rigorous, controlled investigation

Feature Analysis Example:  Buying a Project Scheduling Tool List five key attributes that the tool should have Identify three possible tools and rate each on the criterion Examine the scores, creating a total score based on the importance of each criterion Based on the score, select the tool with the highest score

Buying a Project Scheduling Tool FeaturesTool 1: MS Project Tool 2: Visio Tool 3: Rational Rose Importance Good user interface4543 Easy to learn5555 Consistency checking5313 Report Generation4442 Cost5455 Score857773

Surveys  Retrospective  Record data to determine how project participants reacted to a particular method, tool, or technique Compare data with other similar situations

Case Studies  Compares one situation with another Projects chosen for case study must be typical within the organization or company  Identify key factors that may affect an activity’s outcome and then document them

Case Studies  Involve sequence of steps: conception hypothesis setting design preparation execution analysis dissemination decision making

Case Study Types  Sister projects each is typical and has similar values for the independent variables  Baseline compare single project to organizational norm  Random selection partition single project into parts

Formal Experiments  Control variables  Uses methods to reduce bias and eliminate confounding factors  Often replicated

Evaluation Steps  Setting the hypothesis deciding what we wish to investigate, expressed as a hypothesis we want to test  Maintaining control over variables: identify variables that can affect the hypothesis, and decide how much control we have over the variables  Making investigation meaningful: the result of a formal experiment is more generalizable, while a case study or survey only applies to certain organization

Short answer question  How does feature analysis, surveys, case studies, and controlled experiments  differ?

Selecting An Evaluation Technique  Formal experiments: research in the small  Case studies: research in the typical  Surveys: research in the large

Key Selection Factors  Level of control over the variables  Degree to which the task can be isolated from the rest of the development process  Degree to which we can replicate the basic situation

Short answer question  Under which circumstances are feature analysis, surveys, case studies, and controlled experiments  appropriate?

Real-world example  Hypothesis: Extreme programming is more effective than the waterfall model for student capstone S.E. projects  Variables that can affect outcome?  Evaluation Technique?

Assessment vs. Prediction  Assessment system examines an existing entity by characterizing it numerically  Prediction system predicts characteristic of a future entity; involves a model with associated prediction procedures deterministic prediction (we always get the same output for an input) stochastic prediction (output varies probabilistically)