Herriman High Computer Programming 1A Software Development Cycle Things to Know.

Slides:



Advertisements
Similar presentations
P5, M1, D1.
Advertisements

25 February 2009Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Waterfall Model H.M.Shahzad MS(CS) from COMSATS Institute of Information Technology, Lahore.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
ICASAS305A Provide Advice to Clients
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
Software Configuration Management
Fundamentals of Information Systems, Second Edition
CHAPTER 19 Building Software.
Introduction to Computer Technology
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Appendix D McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
System Analysis and Design
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
Software Testing Life Cycle
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Understand Application Lifecycle Management
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
Systems development life-cycle Dr. Redekopp & Dr Kalanda.
Installation and Maintenance of Health IT Systems
End HomeWelcome! The Software Development Process.
Program Development Life Cycle (PDLC)
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
System Analysis (Part 3) System Control and Review System Maintenance.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
IFS310: Module 13 Implementation and Support - Construction, Conversion and Maintenance of the New System.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
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
Program Development Cycle
CS 1120: Computer Science II Software Life Cycle Slides courtesy of: Prof. Ajay Gupta and Prof. James Yang (format and other minor modifications by by.
Software Engineering Lecture # 1.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
1)History of water fall model. 2)Features of water fall model. 3)Phase of water fall model. 4)Brief description of phases. 5)Advantages. 6)Disadvantages.
The Importance of Control
Waterfall Model Software project Management. Waterfall Model  The Waterfall Model was first Process Model to be introduced. It is also referred to as.
Software Maintenance1 Software Maintenance.
MANAGEMENT INFORMATION SYSTEM
PROGRAMMING LIFE CYCLE. GROUP NAME:  RABIATUL ADAWIYAH BINTI MOHD NOOR 18ENS14F2001  KHAIRULAMIN ZAQUAN BIN AZHAM FUAD 18DNS14F2019  MUHAMMAD NAIM.
Methodologies and Algorithms
Software Configuration Management
Software Engineering (CSI 321)
Project life span.
Project Management Processes
Life Cycle Models PPT By :Dr. R. Mall.
Maintaining software solutions
Maintaining Quality Test Optimization with Increasing Software Complexity Ankit Goyal Software Engineer II Adobe Systems.
Chapter 1 (pages 4-9); Overview of SDLC
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
CS 1120: Computer Science II Software Life Cycle
Lesson 1 Understanding Software Quality Assurance
Applied Software Project Management
Project Management Processes
Software Requirement and Specification
CS 1120: Computer Science II Software Life Cycle
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Software Reviews.
Presentation transcript:

Herriman High Computer Programming 1A Software Development Cycle Things to Know

Herriman High Computer Programming 1A The Phases of Software Development

Herriman High Computer Programming 1A Analysis of Requirements A requirement is single aspect of what you want the software to do. A requirement is single aspect of what you want the software to do. Coming up with a clear, concise, set of requirements is the first (and often hardest) part of planning a software project. Coming up with a clear, concise, set of requirements is the first (and often hardest) part of planning a software project. Clients often have an abstract idea of what they want the end result to be, but little or no knowledge of what the software will actually do. Clients often have an abstract idea of what they want the end result to be, but little or no knowledge of what the software will actually do.

Herriman High Computer Programming 1A Analysis of Requirements Once a general set of requirements is obtained from the client – the of the development is outlined in writing. Once a general set of requirements is obtained from the client – the scope of the development is outlined in writing. This document helps both the developer and the client to understand what the software will and will not do. This document helps both the developer and the client to understand what the software will and will not do. The guiding parameters of this document are functionality and cost. The guiding parameters of this document are functionality and cost.

Herriman High Computer Programming 1A Design Once the requirements are established, a general outline of the project is created called a Once the requirements are established, a general outline of the project is created called a software design document. In the document the high level design or main modules of the program are laid out in a block diagram showing how they will all fit together. At this point the hardware requirements, computer language, and operating system should be decided. Once this is completed the lower level design work – the specific functions of each module can be outlined.

Herriman High Computer Programming 1A Development A.K.A. Coding After reviewing the design documents the work is divided in modules/units. After reviewing the design documents the work is divided in modules/units. Now actual coding is started. Now actual coding is started. Since, in this phase the code is produced, it is the main focus for the developer. Since, in this phase the code is produced, it is the main focus for the developer. This is the longest phase of the software development life cycle. This is the longest phase of the software development life cycle.

Herriman High Computer Programming 1A Testing Testing is an important phase coding/development process. Testing is an important phase coding/development process. This part of the process ensures that defects are recognized as soon as possible This part of the process ensures that defects are recognized as soon as possible Failure to rigorously test a software product at this point can lead to costly and time consuming “fixes” or updates. Failure to rigorously test a software product at this point can lead to costly and time consuming “fixes” or updates.

Herriman High Computer Programming 1A Documentation Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout the development/coding process. Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout the development/coding process. This may consist of both internal comments within the program and external documents like users guides. This may consist of both internal comments within the program and external documents like users guides.

Herriman High Computer Programming 1A Deployment/Release of the Software Deployment starts after the code is appropriately tested, approved for release, and sold. Deployment starts after the code is appropriately tested, approved for release, and sold. Deployment may involve installation, customization (setting up the software for a specific office or location), testing, and possibly an extended period of evaluation where the customer makes sure that the software meets their needs and works out the “bugs.” Deployment may involve installation, customization (setting up the software for a specific office or location), testing, and possibly an extended period of evaluation where the customer makes sure that the software meets their needs and works out the “bugs.” This is also the time when training is provided by the developer to the client’s employees. Software training and support is important, as software is only effective if it is used correctly. This is also the time when training is provided by the developer to the client’s employees. Software training and support is important, as software is only effective if it is used correctly.

Herriman High Computer Programming 1A Support/Maintenance Maintaining and supporting your product involves: Maintaining and supporting your product involves: Fixing faults or issues – “Bug fixing” Fixing faults or issues – “Bug fixing” Enhancing software to cope with newly discovered requirements or adding new features - “updating” Enhancing software to cope with newly discovered requirements or adding new features - “updating” These activities can take substantial time and effort and sometimes may even be extensive enough force redesign of the software in order to fix major problems or to stay competitive with other products. These activities can take substantial time and effort and sometimes may even be extensive enough force redesign of the software in order to fix major problems or to stay competitive with other products.