Chapter 4 Review of Software Process Models Please answer the seven Blue Questions in the following slides. Bring the answers to class on Monday June 13.

Slides:



Advertisements
Similar presentations
Schedule and Effort. Planning Big Project: Waterfall-ish Style 1.Figure out what the project entails Requirements, architecture, design 2.Figure out dependencies.
Advertisements

CSC 532 Term Paper Process Models In Software Engineering By Xiancong Xiong Fall 2004.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Chapter 16: Analysis and Design (a short introduction) ● As engineers in other desciplines do, it necessary for real projects to “analyse” and “design”
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
 The Rise of Computer Science ◦ Machine Language (1 st Gen) ◦ Assembly Language (2 nd Gen) ◦ Third Generation Languages (FORTRAN, BASIC, Java, C++, etc.)
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Fall 2007CS 225 Introduction to Software Design Chapter 1.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Copyright © 2002 Pearson Education, Inc.
1 Info 1409 Systems Analysis & Design Module Lecture 8 – Modelling tools and techniques HND Year /9 De Montfort University.
Spring 2009CS 225 Introduction to Software Design Chapter 1.
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Personal software process Mohammed ahmed ali. What is psp The personal software process (psp) is a structured set of process descriptions, measurements.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Introduction to Software Design Chapter 1. Chapter Objectives  To become familiar with the software challenge and the software life cycle  To understand.
Software Life-Cycle Models Somnuk Keretho, Assistant Professor Department of Computer Engineering Faculty of Engineering, Kasetsart University
Software Process Models
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Effort.vs. Software Product “Quality” Effort Product “Quality” Which curve? - linear? - logarithmic? - exponential?
Click to add text SUITE SEM Implementation Process Training.
CPSC 871 John D. McGregor Process – an introduction Module 0 Session 3.
CPSC 372 John D. McGregor More EPF Module 2 Session 4.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
SOFTWARE PROCESS IMPROVEMENT
CMMI. Reference CMMI: Guidelines For Process Integration And Product Improvement by Mary Beth Chrissis, Mike Konrad, Sandy Schrum ISBN Copyright.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Week 3 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
Project and Project Formulation and Management
WE ARE HERE!.
Project Cost Management
Chapter 25 Process Improvement.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
School of Business Administration
CS4311 Spring 2011 Process Improvement Dr
CS 5150 Software Engineering
Introduction to Software Engineering: Second Edition
SUITE SEM Implementation Process Training
Process Models In Software Engineering
Database Actors Welcome : To the third learning sequence “ DB ACTORS “
Systems Analysis and Design
PART I CLASSICAL SOFTWARE ENGINEERING
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
PART I CLASSICAL SOFTWARE ENGINEERING
Constructive Cost Model
Teaching slides Chapter 1.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Software life cycle models
Chapter 2 Process Models
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Chapter 2 Process Models
Chapter 3 – Agile Software Development
Practical Software Engineering
CS385T Software Engineering Dr.Doaa Sami
Software Processes Process should be
Database Actors.
By The way, Why Groups? OK every student hates group work
Chapter 2 Process Models
Chapter 2: Building a System
Chapter 4: Software Process Models
Building a “System” Moving from writing a program to building a system. What’s the difference?! Complexity, size, complexity, size complexity Breadth.
SOFTWARE ENGINEERING CS-5337: Introduction
Presentation transcript:

Chapter 4 Review of Software Process Models Please answer the seven Blue Questions in the following slides. Bring the answers to class on Monday June 13

What is a Process Model ? It is a description of i) what tasks need to be performed in ii) what sequence under iii) what conditions by iv) whom to achieve the “desired results.” Blue Question 1. Is PSP a process model? Explain your answer.

Why Have A Process Model? Provide “guidance” for a systematic coordination and controlling of a) the tasks and of b) the personnel who perform the tasks Note the key words: coordination/control, tasks, people Blue Question 2. Who is the personnel?

A “Simple and Familiar” Process CodingCompiling Debugging Problem Statement Release problem 1. Most people performs and follow this simple process, but unfortunately some skips unit testing or debugging. 2. Also, some proceeds without thoroughly considering & understanding the “problem statement” ---- which is the requirement Unit Testing Blue Question 3. You followed this process… explain when.

Extending the “Simple” Process As projects got larger and more complex. (earlier, we introduced “simplification”, “better tools”, & “process”) –Needed to clarify and stabilize the requirements –Needed to test more functionalities –Needed to design more carefully –Needed to use more existing software & tools Database Network Code control –Needed more people to be involved Resulting in more tasks and more people

Waterfall Model Requirements Design Code Test Integrate and Package 1. Requirements must be specified. 2. Four main tasks must be completed in sequence: requirements, design, code, and test, followed by integration. 3. Output of one stage feeds into the next stage in sequence, and thus easily tracked (“controlled”) by management Plan Blue Question 4. This figured added an activity compared to the book. Which activity was added?

Incremental Model (A)– “Continuous Integration” Req. 1 Req.2 Req. n Des. code Integration Bucket Test code Test System Test 1. Each “major requirement/item” is further developed separately through the same sequence of : requirement, design, code, and unit test. 2. As the developed pieces are completed, they are continuously merged and integrated into a common bucket for integrated system test... Req. Analysis and Architecture Blue Question 5. Would you add the activity in Blue Question 4 to this process? Explain your answer.

Entry and Exit Criteria Process Activity Entry Criteria Met? Exit Criteria Met? Yes No In order for process models to be more than just a “guideline,” it must include a list of conditions or requirements that define the: - entry criteria prior to performing an activity in a process. - exit criteria before an activity in the process is deemed completed. Blue Question 6. For the Plan activity, explain the entry criteria and the exit criteria.

Assessment of Software Organizations Software Development and Software Support may be done with very little process or with very sophisticated, well defined, well organized and well executed processes. How mature is your software engineering organization and do you need to improve? ISO (ISO 9000 series) and SEI (Software Engineering Institute at Carnegie Mellon) are two leading organizations that help in the process assessment No Process Matured Process Where are you in this wide spectrum?? Blue Question 7. What are you using in your meetings that could point to your team’s maturity?