1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Process Models
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 2 Software Processes (1/2) Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
More CMM Part Two : Details.
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)
Difference between project and other assignments  real customer  before programming: negotiations with client to clarify requirements  often.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
School of Computing, Dublin Institute of Technology.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
The Waterfall Model A Case Study
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Difference between project and other assignments real customer before programming: negotiations with client to clarify requirements often changes.
Introduction to Software Testing
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Effective Methods for Software and Systems Integration
Introduction to Software Quality Assurance (SQA)
Dr. Tom WayCSC What is Software Engineering? CSC 4700 Software Engineering Lecture 1.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Software Engineering Term Paper
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Seattle Area Software Quality Assurance Group Release and Configuration Management, The Acceleration of Change and Its Contribution To Software Quality.
Software Configuration Management
Software System Engineering: A tutorial
CS3300 Fall 2015 Software Development Lifecycles.
1 Configuration Management “The Cookbook Approach”
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Jump to first page (c) 1999, A. Lakhotia 1 Software engineering? Arun Lakhotia University of Louisiana at Lafayette Po Box Lafayette, LA 70504, USA.
Acquiring Information Systems and Applications
Software Quality Assurance
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
ANKITHA CHOWDARY GARAPATI
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
1 12/5/2015ã 2007, Spencer Rugaber Software Engineering Software engineering is concerned with the production of large scale software artifacts by teams.
UNIT-1 SOFTWARE PRODUCT AND PROCESS: Introduction – S/W Engineering paradigm – Verification – Validation – Life cycle models – System engineering –
CISB113 Fundamentals of Information Systems IS Development.
SWE 513: Software Engineering
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Advanced Software Engineering Dr. Cheng
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
CS 389 – Software Engineering
Software Process Activities.
Lecture 1 What is Software Engineering? CSC 4700 Software Engineering
Software and Systems Integration
Software Planning Guidelines
Quality Management Perfectqaservices.
Introduction to Software Engineering
Retirement Information Online (RIO) Enhancement
Chapter 2 – Software Processes
Introduction to Software Testing
Software Development Process
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Rapid software development
ACSC 155 System Analysis and Design 4. Systems Design
Presentation transcript:

1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification Detailed design Verification Code Unit test Integration Product verification Implementation System test Operations and maintenance Revalidation (Source : Software Engineering Economics - Boehm)

2 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Entrance/advancement criteria for each phase Document driven  heavyweight Non-overlapping phases Product visibility only at end of process  lack of user feedback Brittle in the face of requirements change

3 10/14/2015ã 2007, Spencer Rugaber Waterfall Activity Definitions - 1 Requirements Analysis: determination, specification, review and update of software functional, performance, interface, and verification requirements Product Design: determination, specification, review and update of hardware-software architecture, program design, and data base design Programming: detailed design, code, unit test, and integration of individual computer program components. Includes programming personnel planning, tool acquisition, data base development, component level documentation, and intermediate level programming management (Source : Software Engineering Economics - Boehm)

4 10/14/2015ã 2007, Spencer Rugaber Waterfall Activity Definitions - 2 Test Planning: Specification, review, and update of product test and acceptance test plans. Acquisition of associated test drivers, test tools, and test data Verification and Validation: Performance of independent requirements validation, design V & V, product test, and acceptance test. Acquisition of requirements and design V & V tools Project Office Functions: Project level management functions. Includes project level planning and control, contract and subcontract management, and customer interface

5 10/14/2015ã 2007, Spencer Rugaber Waterfall Activity Definitions - 3 Configuration Management: configuration management includes product identification, change control, status accounting, operation of program support library, development and monitoring of end item acceptance plan Quality Assurance: Quality assurance includes development and monitoring of project standards, and technical audits of software products and processes Manuals: Development and update of users' manuals, operators manuals, and maintenance manuals

6 10/14/2015ã 2007, Spencer Rugaber Time Spent in Various Phases of the Waterfall Process Requirements analysis & design % Implementation & unit test % System (integration) test % Operation & maintenance yet another %