1 Advanced Computer Programming Project Management: Software Life Cycle Copyright © Texas Education Agency, 2013.

Slides:



Advertisements
Similar presentations
Chapter 7: Software production process Refers to the activities that are used for building, delivering, deploying, and evolving a software product, from.
Advertisements

CSC271 Database Systems Lecture # 18. Summary: Previous Lecture  Transactions  Authorization  Authorization identifier, ownership, privileges  GRANT/REVOKE.
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
Software Life Cycle Requirements analysis System design Program design Program implementation (coding) Unit testing Integration testing System testing.
MIS 2000 Class 20 System Development Process Updated 2014.
Chapter 4 Quality Assurance in Context
Copyright © Texas Education Agency, Computer Programming Software Life Cycle.
System Development Life Cycle Process of creating and altering systems or software by using methodologies or models to develop the systems in a logical.
Chapter 2 – Software Processes
Copyright  2002, Medical Present Value, Inc. All rights reserved. Copyright © 2010 Texas Education Agency. All rights reserved. TEA confidential and proprietary.
Computer Related Issues IC3 Chapter 5 Computer Fundamentals.
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
June 1, 2004Computer Security: Art and Science © Matt Bishop Slide #18-1 Chapter 18: Introduction to Assurance Overview Why assurance? Trust and.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Unit Five – Transforming Organizations
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
1 CMSC 132: Object-Oriented Programming II Software Development III Department of Computer Science University of Maryland, College Park.
CHAPTER 17 Building Software to Support an Agile Organization
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
CHAPTER 19 Building Software.
Software Life Cycle Model
Data Structures and Programming.  John Edgar2.
1 CMPT 275 Software Engineering Software life cycle.
Transforming Organizations
Business Driven Technology Unit 5 Transforming Organizations McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.
Appendix D McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
1 Advanced Computer Programming Project Management: Methodologies Copyright © Texas Education Agency, 2013.
Understand Application Lifecycle Management
End HomeWelcome! The Software Development Process.
Introduction to Java August 14, 2008 Mrs. C. Furman.
Project Life cycles BTEC National.
Software Engineering Chapter 3 CPSC Pascal Brent M. Dingle Texas A&M University.
Tutorial 1: Date: 19/09/2012 Instructor: Hanif Ullah
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Introduction to Testing. Topics Who are we? Who are we? Software Testing Definition and Goals Software Testing Definition and Goals Facts and Numbers.
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.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Software Life-Cycle and Models
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Software Engineering Lecture # 1.
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
KUFA UNIVERSITY Department of Computer Science. Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Lectures 2 & 3: Software Process Models Neelam Gupta.
C++ for Engineers and Scientists, Second Edition 1 Problem Solution and Software Development Software development procedure: method for solving problems.
Systems Development Life Cycle
Slide #18-1 Introduction to Assurance CS461/ECE422 Fall 2008 Based on slides provided by Matt Bishop for use with Computer Security: Art and Science.
1 Advanced Computer Programming Project Management: Basics Copyright © Texas Education Agency, 2013.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
MANAGEMENT INFORMATION SYSTEM
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
The DMAIC Method
Unit 6 Application Design KLB Assignment.
ICS 3UI - Introduction to Computer Science
Lecture 3 Prescriptive Process Models
SNS College of Engineering Coimbatore
Iterative Waterfall Model
System Development Life Cycle (SDLC)
Chapter 2 SW Process Models
Introduction to Software Engineering
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
Software life cycle models
CS101 Introduction to Computing Lecture 20 SW Development Methodology
Baisc Of Software Testing
Software Engineering Lecture 17.
Software Development Life Cycle Models
Presentation transcript:

1 Advanced Computer Programming Project Management: Software Life Cycle Copyright © Texas Education Agency, 2013

Overview Basics Requirements Design Implementation Verification Deployment Maintenance Waterfall Implementation Iterative Implementation 2Copyright © Texas Education Agency, 2013

Basics Software Design consists of five essential steps in the “life cycle” of development: Requirements Design Implementation Verification Maintenance 3Copyright © Texas Education Agency, 2013

Requirements The requirements phase is a period of collecting information from a user or customer on what they want a piece of software to do. It is critical to ensure you understand what the customer or client wants in order to provide the correct software solution. 4Copyright © Texas Education Agency, 2013

Requirements: Potential Pitfalls Things that can go wrong in requirements gathering: Client says one thing but means something else Not all requirements are specified (incomplete specification) Misunderstanding about what the client wants 5Copyright © Texas Education Agency, 2013

Design Design of a software product is the process of analyzing requirements provided by a customer or client and determining the most efficient and appropriate software solution. The level of detail in the design is dependent upon the type of software development methodology you are using. 6Copyright © Texas Education Agency, 2013

Design: Potential Pitfalls Things that can go wrong during design: Misinterpretation of requirements Inefficient or wrong solution to a problem Incomplete or over-complicated design 7Copyright © Texas Education Agency, 2013

Implementation Implementation is the process of turning the design of the software into a working program. 8Copyright © Texas Education Agency, 2013

Implementation: Potential Pitfalls Things that can go wrong during implementation: Implementing faulty or “buggy” code Misinterpretation of design Not following the design and “doing your own thing” Mismatched components preventing integration Lack of communication between developers Overwriting or deleting someone else’s work Not understanding someone else’s code and changing how it works 9Copyright © Texas Education Agency, 2013

Verification Verification is the process of testing software to ensure it meets the requirements presented by the user, as well as determining if the software is of high quality and relatively free of defects. This phase is also commonly called Testing or Quality Assurance. 10Copyright © Texas Education Agency, 2013

Verification: Potential Pitfalls Things that can go wrong during verification: Incomplete tests (not testing for something you should) Ignoring test results Misinterpreting test results 11Copyright © Texas Education Agency, 2013

Deployment Deployment is the delivery of functional software to the client or end user. In some methods of development, this is the last step in the actual development process leaving only maintenance of the product. In other methods, such as iterative, addition of new features continues until the user no longer wishes to continue the project. 12Copyright © Texas Education Agency, 2013

Maintenance Once a software solution is verified to be “correct,” it is deployed to the client and enters a stage of maintenance. During maintenance, the client will provide feedback on errors and changes they want in the system which must be corrected. It is not uncommon during maintenance to perform all of the steps of the Software Life Cycle. 13Copyright © Texas Education Agency, 2013

Maintenance: Potential Pitfalls Things that can go wrong during maintenance: Misinterpretation of requests from client “Fixing” something that isn’t broken Almost any of the concerns that may arise during the rest of the software life cycle 14Copyright © Texas Education Agency, 2013

Waterfall Model In the waterfall model, each step is performed in sequence. 15 Requirements Design Implementation Maintenance Verification Deployment Copyright © Texas Education Agency, 2013

Iterative Model In the iterative model, there is an initial planning phase, then a series of development iterations, each iteration adding functionality to the product. 16 Requirements Design Implementation Verification Deployment Maintenance Change Requirements Copyright © Texas Education Agency, 2013