Chapter 2 October 14, 1997 1 Software as a Process zSoftware Engineering -- a definition: y[Software engineering is] the establishment and use of sound.

Slides:



Advertisements
Similar presentations
Departemen Ilmu Komputer IPB
Advertisements

SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
CS487 Software Engineering Omar Aldawud
TCS2411 Software Engineering1 Software Life Cycle “What happens in the ‘life’ of software”
CS3773 Software Engineering Lecture 01 Introduction.
More CMM Part Two : Details.
Chapter 2 The Software Process
Chapter 2 Process Models
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Software Development Process Models. The Waterfall Development Model.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SOFTWARE ENGINEERING LECTURE-3 CSE-477.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Capability Maturity Model
Chapter 1 The Systems Development Environment
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.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Chapter 2 The process Process, Methods, and Tools
Chapter 2 The Process.
Software Process and Models
N By: Md Rezaul Huda Reza n
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.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Chapter 2 The Process.
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 Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Chapter 2 Process: A Generic View
Lecture 1 Introduction to Software Engineering
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Jump to first page (c) 1999, A. Lakhotia 1 Software engineering? Arun Lakhotia University of Louisiana at Lafayette Po Box Lafayette, LA 70504, USA.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Chapter 4 프로세스 모델 Process Models
Process: A Generic View
1 Software Engineering Textbook:“Software Engineering -- A Practitioner’s Approach,” 5th Edition by Roger S. Pressman URL:
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Developed by Reneta Barneva, SUNY Fredonia The Process.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
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.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Chapter 2 A Generic View of Process Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
SOFTWARE PROCESS IMPROVEMENT
Software Engineering (CSI 321) Software Process: A Generic View 1.
Software Engineering Process Lecture -2:. –Software development life cycle –overview of software development process models.
The Software Process CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides are intended.
Done By: Asila AL-harthi Fatma AL-shehhi Fakhriya AL-Omieri Safaa AL-Mahroqi.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CMMI for Services, Version 1.3
Software Project Management Unit 1. Evolving role of software S/w now a days resides in the mobile, mainframes The main role of the s/w is to transform.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
Advanced Software Engineering Dr. Cheng
Software Life Cycle “What happens in the ‘life’ of software”
Software Engineering (CSI 321)
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Chapter 2 Process Models
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Chapter 2 Process Models.
Capability Maturity Model
Presentation transcript:

Chapter 2 October 14, Software as a Process zSoftware Engineering -- a definition: y[Software engineering is] the establishment and use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines. zSoftware Engineering is a layered technology.

Chapter 2 October 14, A Layered Technology zTools yEditors yDesign aids yCompilers yComputer Aided Software Engineering (CASE) zMethods yIncludes standards (formal or informal) yMay include conventions, e.g., low level such as naming, variable use, language construct use, etc. yMay involve design methodologies.

Chapter 2 October 14, Some Generic Engineering Phases zDefinition ySystem or information engineering (leading to requirements) ySoftware project planning yRequirements analysis zDevelopment ySoftware design yCoding yTesting

Chapter 2 October 14, Some Generic Engineering Phases zMaintenance yCorrection -- bugs will appear yAdaptation -- to changing operating systems, CPU’s, etc. yEnhancement -- changing customer needs yPrevention -- software reengineering

Chapter 2 October 14, Some Generic Engineering Phases zTypical activities in these phases yProject tracking and control yFormal reviews ySoftware quality assurance yConfiguration management yDocumentation yReusability management yMeasurement yRisk management

Chapter 2 October 14, SEI Software Maturity Model zLevel 1: Initial -- The software process is characterized as ad hoc, and occasionally even chaotic. Few processes defined. zLevel 2: Repeatable -- Basic project management processes established to track cost, schedule and functionality. zLevel 3: Defined -- Process for both management and engineering is documented, standardized and integrated. zLevel 4: Managed -- Detailed measures of the process and product quality collected. Both are quantitatively understood and controlled. zLevel 5: Optimizing -- Continuous process improvement enabled by quantitative feedback and testing innovative ideas.

Chapter 2 October 14, Key Process Areas zMaturity Level 2 ySoftware Configuration Management ySoftware Quality Assurance ySubcontract management yProject tracking and oversight ySoftware project planning yRequirements management

Chapter 2 October 14, Key Process Areas zMaturity Level 3 yPeer Reviews yIntergroup coordination yIntegrated software management yTraining program yOrganization process definition yOrganization process focus

Chapter 2 October 14, Key Process Areas zMaturity Level 4 ySoftware quality management yQuantitative process management zMaturity Level 5 yProcess change management yTechnology change management yDefect prevention

Chapter 2 October 14, Software Process Models

Chapter 2 October 14, Waterfall Model Requirements Analysis Design Code Test System/Information Engineering Maintain

Chapter 2 October 14, The Rapid Prototyping Model

Chapter 2 October 14, Evolutionary Process Models zThe Incremental Model

Chapter 2 October 14, Evolutionary Process Models zThe Spiral Model

Chapter 2 October 14, Evolutionary Process Models zThe Component Assembly Model

Chapter 2 October 14, Evolutionary Process Models zThe Concurrent Development Model

Chapter 2 October 14, Other Models zFormal Methods yRigorous mathematical representation of requirements yProvides basis for automatic verification test generation zFourth Generation Techniques yUse code generators to produce specific parts of product zProcess Technology yProvides a variety of tools to aid software developers, e.g., workload flow, configuration management, quality assurance management, etc.