1 Week 3 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

Figures-Chapter 2.
Software Development Life Cycle
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
CSE 470 : Software Engineering The Software Process.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
 © Ian Sommerville A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
Chapter 2 The Software Process
Chapter 2 Process Models
CH02: Modeling the process and life cycle Process of developing software (organization and discipline in the activities) contribute to the quality of the.
Feature Driven Development
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Process- Related Requirement Management By Viswaketan Reddy.
Fall 2007CS 225 Introduction to Software Design Chapter 1.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Spring 2009CS 225 Introduction to Software Design Chapter 1.
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Project Management Methodology More about Quality Control.
Chapter : Software Process
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
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)
PART ONE The Product and the Process Chapter 2 The Process  Software Engineering: A Layered Technology a “quality” focus process model methods tools.
Introduction to Software Design Chapter 1. Chapter Objectives  To become familiar with the software challenge and the software life cycle  To understand.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Software Process Models
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Software Engineering - I
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Systems Analysis and Design in a Changing World, Fourth Edition
Process: A Generic View
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
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.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
CMMI Certification - By Global Certification Consultancy.
School of Business Administration Chap 3 Engineering of Software;
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.
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
WE ARE HERE!.
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
PART I CLASSICAL SOFTWARE ENGINEERING
PART I CLASSICAL SOFTWARE ENGINEERING
CMMI Overview.
Teaching slides Chapter 1.
Chapter 2 Process Models
Chapter 2 Process Models
Chapter 2 Process Models.
Chapter 2 Process Models
Acknowledgment of achievement
Chapter 2 Process Models
Chapter 4: Software Process Models
Presentation transcript:

1 Week 3 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam

2 Review Case Study 1 Quiz Chapters 1-3 Chapter 4 Software Process Models Start Mini-Project 1 – create schedule in MS Visio

3

4

5

6

7

8 It is a description of : what tasks need to be performed in what sequence under what conditions by whom to achieve the “desired results.”

Do we need a process if the project requires just 1 person or at most two people? Why? -- Why not ?

11 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

12 We now need to “Define”: the set of tasks that need to be performed the sequence of flow of the tasks the input and the output from these tasks the pre-condition and post-conditions for each task The people & skills needed to perform the tasks

13  The earlier “simple” process was employed by many for years without formally embracing other important development activities such as requirements analysis, design, formal testing, or packaging.  The recognition of the need for formal processes was initially driven by failures in developing large complex software --- (later shown by Chaos reports) Waterfall : earliest process and coping with no process Incremental : coping with decomposing the large systems Spiral : coping with risk management Rational Unified Process : coping with different task and managing through project phases

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.

20 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

In 2001, CMM was upgraded to CMMI (CMM Integrated). Started with multiple, major aspects to CMMI: Systems engineering Software engineering Integrated product and process development Supplier sourcing

22 This is a start – there will be several subordinate tasks