Selecting Software Development Life Cycles. Adapted from Chapter 4, Futrell
|
|
- Gabriella Ford
- 6 years ago
- Views:
Transcription
1 Selecting Software Development Life Cycles Adapted from Chapter 4, Futrell
2 Examples of Software Life Cycle Models Classical Waterfall Waterfall with feedback V-Shaped Prototyping Incremental Spiral Rapid Application Development Combination
3 Classic Waterfall Model Systems engineering Analysis Design Code Classical engineering approach Associated with DOD-STD-2167A Explicit start and end points to phases Clearly defined milestones Testing Maintenance
4 Waterfall Model with Feedback System Requirements V&V Activities Software Requirements V&V Activities Preliminary Design V&V Activities Detailed Design V&V Activities Code and Debug Developmental Test Test and Preoperations V&V Activities Operations and Maintenance V&V Activities
5 Strengths of the Waterfall Model It is easy to understand It is easy to use (when applied to a project for which it is suited) It is easy to track the progress of the project using a timeline or Gantt chart -- the completion of each phase is used as a milestone Allows for tight control -- defines quality control procedures The model is well known by non-software customers and end-users and is used by other organizations to track projects not related to software development
6 Weaknesses of the Waterfall Model It does not easily handle concurrent events -- development teams are delayed waiting on others It does not handle iterations among phases-- the sequential flow is not always realistic The user is involved only in the beginning of the process, while gathering requirements, and at the end, during acceptance testing Customers can rarely state all requirements at the beginning of the project The customer does not get to see the product until late in the life cycle The model is not equipped to handle dynamic changes in requirements over the life cycle -- deliverables are frozen
7 V-Shaped Model Project Requirements and Planning Production, Operation, and Maintenance Product Requirements and Specification Analysis System Testing Architectural or High-Level Design Integration and Testing Detailed Design Unit Testing Coding
8 Strengths of the V-Shaped Model The model is easy to understand It is easy to use (when applied to a project for which it is suited) It is easy to track the progress of the project using a timeline or Gantt chart -- the completion of each phase is used as a milestone The model emphasizes planning for verification and validation of the product in the early stages of product development The model encourages verification and validation of the requirements and design, not just the code of the product
9 Weaknesses of the V-Shaped Model The model does not easily handle concurrent events It does not handle iterations of phases The model is not equipped to handle dynamic changes in requirements throughout the life cycle The model is not equipped to handle dynamic changes in requirements over the life cycle The requirements are tested too late in the cycle to make changes without affecting the schedule for the project The V-Shaped model may be modified to overcome these weaknesses by including iteration loops to handle the changing of requirements beyond the Analysis phase.
10 Prototyping Model Plan to throw one away In most projects, the first system built is barely usable. It may be too slow, too big, awkward to use, or all three. There is no alternative but to start again, starting but smarter, and build a redesigned version The management question, therefore, is not whether to build a pilot system and throw it away. You will do that. The only question is whether to plan in advance to deliver a throwaway to customers. - Fred Brooks, The Mythical Man-Month, 1975 p. 116 Promising Attacks on the Conceptual Essence The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines, and to other software systems. No other part of the work so cripples the resulting system If done wrong. No other part is more difficult to rectify later. Therefore, the most important function that the software builder performs for the client is the iterative extraction and refinement of the product requirements. For the truth is, the client does not know what he wants. - Fred Brooks, No Silver Bullet, 1986
11 Evolutionary Rapid Prototyping Model Design Derivation Prototype Iteration User Approval Functions Rapid Analysis Project Plan Database Creation Tuning User Interface Operation and Maintenance
12 Strengths of the Rapid Prototyping Model The end user can see the system requirements as they are being gathered by the project team -- customers get early interaction with system There is less room for confusion, miscommunication or misunderstanding in the definition of the system requirements, leading to a more accurate end product -- customer and developer have a baseline to work against The model allows for flexible design and development
13 Weaknesses of the Rapid Prototyping Model If the users cannot be involved during the rapid prototype iteration phase of the life cycle, this can have adverse effects on the final product The rapid prototype is a partial system during the prototype iteration phase. If the project is risky and may not be completed, the end user will be left with only a partial system The customer may expect look and feel of the prototype The customer may want to have prototype delivered rather than waiting for full, well engineered version If the prototyping language or environment is not consistent with the production language or environment, there can be delays in full implementation of the production system Quality can suffer
14 Planning Spiral Model Risk analysis Initial requirements gathering and project planning Planning based on customer comments Risk analysis based on initial requirements Risk analysis based on customer reaction Go, no go decision Customer evaluation Customer evaluation Partitions process into four distinct quadrants Emphasizes evolutionary development Accommodates 1980s paradigms Stresses formal risk analysis Toward a completed system Initial software prototype Next level prototype Engineered system Engineering
15 Evolutionary Spiral Model Commit to Proceed 1. Understand Context Update Spiral Plan Review Progress 5. Manage and Plan Develop/Update Estimate of the Situation Define/Refine Approach - Stakeholders - Objectives - Alternatives - Constraints Place Product Under Change Control Review Context Review Technical Product Perform Risk Analysis Review Risk Analysis Source: Software Productivity Consortium Evolutionary Spiral Process Model Guidebook 2. Analyze Risks Plan Risk Aversion Evaluate Risk Aversion Develop and Verify Product Monitor and Review Review Alternative Plan and Schedule Commit to Risk Aversion Strategy Commit to Plan 4. Develop Product 3. Plan Development
16 Strengths of the Spiral Model The model embraces the waterfall model while allowing for iteration throughout the phases of that model It is driven by risk analysis and is ideal for those projects which represent a medium to high risk The users see the product early, via the proof of concept and rapid prototypes in the development life cycle The users are closely tied to the development efforts All of the money needed for the project need not be allocated up front The model handles changes in requirements by allowing for iteration through the Analysis & Design phase and Execute Phase
17 Weaknesses of the Spiral Model If the project is low risk, this model can be an expensive life cycle model -- much time is spent evaluating the risk after each iteration within the model and considerable risk assessment expertise is required It may require unrealistic overhead for small projects The creation of a prototype may not always be the appropriate type of product development It hasn t been used as widely as linear sequential The lack of a good prototyping tool or technique can make this model clumsy to use Adaptations of the model include: Replacement of the prototypes with an increment of a product Iteration within one of the spirals of the model illustrated by a two headed arrow Replacement of the prototypes with rapid application development product iteration
18 Rapid Application Development (RAD) Model User Community Development Effort Requirement s Planning User Description Construction Cut Over TIME
19 RAD Model TIME business modeling data data modeling process modeling Team 1 Deadline business modeling data data modeling process modeling Team 2 application application generation generation testing & testing & turnover turnover
20 Strengths of the RAD Model The model has shown reduced cycle time due to the use of powerful development tools The end user is involved throughout the life cycle The system is developed by a project team familiar with the problem domain; thus it continues to build upon this expertise can deliver a full product in a short time period
21 Weaknesses of the RAD Model If the users cannot be involved consistently throughout the life cycle, this can have adverse effects on the final product This model requires highly skilled and well-trained developers in the use of the chosen development tools to achieve the rapid turnaround time It can require more people It requires a system that can be properly modularized It can fail if reusable components are not available
22 Incremental Model One of the Evolutionary Models Combines elements of the linear sequential model and prototyping Requirements of the system are prioritized The first increment is the delivery of the core product, providing only the highest priority requirements Subsequent iterations expand on this core (enhancement maintenance)
23 Incremental Model System/information engineering analysis analysis design design code code test test delivery of 1st increment analysis analysis design design code code test test delivery of 2nd increment analysis analysis design design code code test test TIME delivery of 3rd increment
24 Strengths of the Incremental Model The costs of developing a system can be reduced by defining smaller incremental releases with reduced function The duration of the development cycle can be reduced with this model, allowing the product to be released quicker, perhaps in response to a market window Delivers a usable working product quickly Keeps all teams working The use of this model on a project with new technology can allow the user to adjust to the system in smaller incremental steps rather than leaping to a major new product This model is often combined with other models, such as the spiral model.
25 Weaknesses of the Incremental Model The model does not allow for iteration within each increment The definition of a complete, fully functional system must be done early in the life cycle to allow for the definition of the increments Allow you to design yourself into a corner It works best with an even distribution of different priority features It requires good planning and design
26 Microsoft Product Release using Combined Models Virus Backup Outside Procurement and Integration Fixes V-Shaped Disk Doublespace Waterfall File Recovery Spiral Memory Management Prototype Release Vxx.xx Incremental
27 Combination Model Preliminary requirements gathering Requirements analysis Prototyping 4GT Spiral model Design Prototyping: n-th iteration 4GT Coding Spiral model n -th iteration 4GT Testing Operational system Maintenance
28 Selecting a Life Cycle Model Examine project characteristic categories: Uncertainty of Requirements Requirements, Functional needs of the application Project Team, Availability of Resources User Community Project Type, complexity of project Cost of Application Cost of Future Upgrades Discrete / Gradual Requirements Change, Volume Ease of Use of life cycle, Reuse Longevity of the application Product technology Risk
29 Selecting a Life Cycle Model Project Characteristic Category Matrix Requirements Requirements Waterfall V-Shaped Prototype Spiral RAD Incremental Are the requirements easily defined and/or well known? Can the requirements be defined early in the cycle? Will the requirements change often in the cycle? Yes Yes No No Yes No Yes Yes No No Yes Yes No No Yes Yes No No Is there a need to demonstrate the requirements to achieve definition? No No Yes Yes Yes No Is a prrof of concept required to demonstrate capability? No No Yes Yes Yes No
30 Selecting a Life Cycle Model Project Characteristic Category Matrix Project Team Project Team Waterfall V-Shaped Prototype Spiral RAD Incremental Are the majority of team members new to the problem domain for the project? Are the majority of team members new to the technology domain for the project? Are the majority of team memebers new to the tools to be used on the project? Are the team members subject to reassignment during the life cycle? Is there training available for the project team if required? No No Yes Yes No No Yes Yes No Yes No Yes Yes Yes No Yes No No No No Yes Yes No Yes No Yes No No Yes Yes
31 Selecting a Life Cycle Model Project Characteristic Category Matrix User Community User Community Will the availability of the user representatives be restriced, or limited during the life cycle? Are the user representatives new to system definition? Are the user representatives experts in the problem domain? Do the users want to be involved in all phases of the life cycle? Waterfall V-Shaped Prototype Spiral RAD Incremental Yes Yes No Yes No Yes No No Yes Yes No Yes No No Yes No Yes Yes No No Yes No Yes No
32 Selecting a Life Cycle Model Project Characteristic Category Matrix Project Type and Risk Project Type & Risk Waterfall V-Shaped Prototype Spiral RAD Incremental Does the project identify a new product direction for the organization? Is the project a system integration project? Is the project an enhancement to an existing system? Is the funding for the project expected to be stable throughout the life cycle? Is the product expected to have a long life in the organization? No No Yes Yes No Yes No Yes Yes Yes Yes Yes No Yes No No Yes Yes Yes Yes Yes No Yes No Yes Yes No Yes No Yes
33 Selecting a Life Cycle Model Whole Class Exercise #1 A company is rewriting its payroll system to move it from an old batch-type mainframe to a distributed mini-computer/pc-based networked setup. No new functionality will be added. The statement of work calls for a conversion as is. Only the input and output subsystems will be altered for the new environment. Since it is a payroll application, testing and verification will be emphasized within the development activities. The schedule allows five months for the project, with two people working on it. What do you think is the most Appropriate Life Cycle Approach? What is the advantage of this approach for this project?
34 Selecting a Life Cycle Model Whole Class Exercise #2 A company, an electronics giant, has recently decided to venture into a related small business area developing wristwatch communicators. The device would be similar to a two-way radio and would be expected to work over a 50-mile radius. The company has considerable previous experience on product lines similar to this, and believes that a cheaper price could present a value-added challenge to the cellular market. It would like to have a working model to present at a national electronics fair coming up six months from now. What do you think is the most Appropriate Life Cycle Approach? What is the advantage of this approach for this project?
35 Selecting a Life Cycle Model Whole Class Exercise #3 A company has recently completed a 3-year process to develop a cellular infrastructure switching system to compete with industry leaders such as Motorola and Ericsson. It is now ready to move into the next phase where new releases will be issued approximately every four months. An average of 15 new features and an appropriate number of bug fixes will be included in each release spread across teams composed of one to three engineers. Development times for the new features can range from one to five months. Some features can require multiple releases for full implementation. What do you think is the most Appropriate Life Cycle Approach? What is the advantage of this approach for this project?
36 Selecting a Life Cycle Model Whole Class Exercise #4 A company has created a new small business division to develop a specialized communications system. Approximately 15 persons will be transferred from key areas of the company to form the base for the venture. Some 28 additional people will be hired from the outside, the bulk of which are engineers. It has already been decided that Object-Oriented tools and approaches will be used with C++ as the language. None of the participants has any prior knowledge of these techniques, but will go through ten days of training when they come on board. In addition, a consortium-partner of the company has just released a new workstation platform (its first). Due to these alliances, the consortium platform will be the development platform of choice. Training is also being scheduled for the new workstation. The primary satellite supplier, OO Aerospace, has been having major financial difficulties due to military cutbacks and has laid off about 35 percent of its work force. What do you think is the most Appropriate Life Cycle Approach? What is the advantage of this approach for this project?
37 Customizing the Life Cycle Model Become familiar with the various models Review, analyze the type of work: development, enhancement, maintenance, etc. Review project criteria Identify a minimum set of phases Identify phase activities Establish a minimum set of deliverables Define templates and content guides for deliverables Evaluate progress and effectiveness of the life cycle framework Implement improvements
38 Preliminary Object-Oriented Analysis Models Used to Develop Initial Prototype Demonstrate to User User Provides Feedback for Provides Feedback for Demo to Used to Develop Expanded & Refined Prototype Expanded & Refined OOA Models Latest Version Becomes Approves Used to Develop Final Requirements Specification Final Version of Prototype
39 Iterate More Specs Rapid OOA More Objects Create Services More Services Demo Feedback Create Controls Iterate Create Objects More Controls Feedback = Approval? No Yes User Operation & Maintenance Performance Testing & Tuning
40 Software Life Cycles Summary There are many models or representations of the software life cycle Each model has its peculiar strengths and weaknesses The model selected for a project or the models used by an organization should meet the needs of the organization, the type of work to be done, and the skills and tools of the software practitioners using the model(s)
Introduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More information03. Perspective Process Models
03. Perspective Process Models Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2017 Prescriptive Process Models advocates an orderly approach to software
More informationSDLC Models- A Survey
Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology IJCSMC, Vol. 2, Issue. 1, January 2013,
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationVolume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at
Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Study of Software Development Life Cycle Process Models
More informationPertemuan 2. Software Engineering: The Process
Pertemuan 2 Software Engineering: The Process Collect Your Project Topic What is Software Engineering? Software engineering is the establishment and sound engineering principles in order to obtain economically
More informationA New Divide & Conquer Software Process Model
A New Divide & Conquer Software Process Model First A. Hina Gull, Second B. Farooque Azam Third C. Wasi Haider Butt, Fourth D. Sardar Zafar Iqbal Abstract The software system goes through a number of stages
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationChapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More informationV Model material adapted from Steve Easterbrook. Waterfall Model material adapted from Steve Easterbrook. Lifecycle of Software Projects
Lifecycle of Software Projects ECE450 Software Engineering II Lifecycle models are useful to compare project management strategies in abstract terms Birds-eye view strategy Detect strengths and weaknesses...
More informationThe Top Thrill Dragster
EEC 421/521: Software Engineering The Software Process Prescriptive Process Models 1/22/08 EEC 421/521: Software Engineering 1 The Top Thrill Dragster 420 ft tall Max speed over 120 mph World s second
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationSoftware Life Cycle. Main Topics. Introduction
Software Life Cycle Main Topics Study the different life cycle models Study the difference between software maintenance and evolution Study product line engineering as a design methodology 2 Introduction
More informationMajor attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
More informationIntroduction to Software Project Management. CITS3220 Software Requirements & Project Management
Introduction to Software Project Management CITS3220 Software Requirements & Project Management "A project gets a year late one day at a time." "Anything that can be changed will be changed until there
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationIntroduction to Software Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016
Introduction to Software Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016 1 Goals Present an introduction to the topic of software life cycles concepts and terminology benefits
More informationInformation Systems Development
Information Systems Development Based on Chapter 3 of Whitten, Bentley, and Dittman: Systems Analysis and Design for the Global Enterprise (7th Ed). McGraw Hill. 2007 Wei-Tsong Wang 1 IIM, NCKU 3 Objectives
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationUC Santa Barbara. CS189A - Capstone. Christopher Kruegel Department of Computer Science UC Santa Barbara
CS189A - Capstone Christopher Kruegel Department of Computer Science http://www.cs.ucsb.edu/~chris/ Announcements Next Project Deliverable: Software Requirements Specifications (SRS) are due Wednesday,
More informationObject-Oriented and Classical Software Engineering
Slide 3.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 3 Slide 3.2 THE SOFTWARE PROCESS Overview Slide 3.3
More informationThe Basic Waterfall Model. Software Process Models. Concurrent Development. (Concurrent Development) The Agile Critique of the Waterfall
Software Process Models Critique & Defense of the Waterfall Issues in Waterfall Models concurrent development phase transitions and overlap Issues in Evolutionary Models incremental vs. iterative models
More informationContents. Today Project Management. What is Project Management? Project Management Activities. Project Resources
Contents Last Time - Software Development Processes Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software
More informationSoftware Engineering II - Exercise
Software Engineering II - Exercise April 29 th 2009 Software Project Management Plan Bernd Bruegge Helmut Naughton Applied Software Engineering Technische Universitaet Muenchen http://wwwbrugge.in.tum.de
More informationIntroduction to Software Life Cycles and Agile. CSCI 5828: Foundations of Software Engineering Lecture 03 09/02/2014
Introduction to Software Life Cycles and Agile CSCI 5828: Foundations of Software Engineering Lecture 03 09/02/2014 1 Goals Present an introduction to the topic of software life cycles concepts and terminology
More informationObject-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
More informationKINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK
KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK Subject Code & Subject Name: IT1251 Software Engineering and Quality Assurance Year / Sem : II / IV UNIT I SOFTWARE PRODUCT
More information18-642: Software Development Processes
18-642: Software Development Processes 9/6/2017 Without requirements and design, programming is the art of adding bugs to an empty text file. Louis Srygley Coding Is Essentially 0% of Creating Software
More informationSOFTWARE ENGINEERING
Page 1 MCA302 SOFTWARE ENGINEERING UNIT I - SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, object oriented)
More informationUser Involvement in Project Success
61-04-70 User Involvement in Project Success Stanley H. Stahl A basic principle for implementing a sustainable software productivity improvement program is to make everyone a winner. A systems project
More informationChapter. Redesigning The Organization With Information Systems
Chapter Redesigning The Organization With Information Systems 1 Objectives Demonstrate how building new systems produces organizational change Explain how a company can develop information systems that
More informationInformation Technology Services Project Management Office Operations Guide
Information Technology Services Project Management Office Operations Guide Revised 3/31/2015 Table of Contents ABOUT US... 4 WORKFLOW... 5 PROJECT LIFECYCLE... 6 PROJECT INITIATION... 6 PROJECT PLANNING...
More informationICS 52: Introduction to Software Engineering
ICS 52: Introduction to Software Engineering Fall Quarter 2004 Professor Richard N. Taylor Lecture Notes http://www.ics.uci.edu/~taylor/ics_52_fq04/syllabus.html Copyright 2004, Richard N. Taylor. Duplication
More informationFlexibility on what is delivered High
Flexibility on what is delivered level 1: Stakeholders are very comfortable with the fact that limited flexibility on budget and time may be necessary in order to deliver the full scope on quality, and
More information2 Why is systems development difficult and risky? 3 How do businesses use the systems development life cycle (SDLC) process?
1 What is systems development? 2 Why is systems development difficult and risky? 3 How do businesses use the systems development life cycle (SDLC) process? 4 How do businesses use the rapid application
More informationGUIDEBOOK CODE OF CONDUCT MANAGEMENT SYSTEMS
GUIDEBOOK CODE OF CONDUCT MANAGEMENT SYSTEMS 2005 Levi Strauss & Co. Page 1 of 57 Table of content SECTION I: INTRODUCTION... 3 1. Introduction... 3 2. How to use this Guidebook... 3 SECTION II: THE MANAGEMENT
More informationChapter 4 Software Process and Project Metrics
Chapter 4 Software Process and Project Metrics 1 Measurement & Metrics... collecting metrics is too hard... it's too time-consuming... it's too political... it won't prove anything... Anything that you
More informationAgile Project Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Agile Project Management Outline A mountaineering example Project context Goals, client types Environment, methods, tools, methodology
More informationAgile Tutorial for the Senior Project Class School of Computing and Information Sciences Florida International University
Agile Tutorial for the Senior Project Class School of Computing and Information Sciences Florida International University What is Agile? In simple terms, Agile is a collection of ideas to guide both the
More informationLIFE-CYCLE MODELS AND PROCESS. Software Engineering 1/9/2008. CHAPTER 1, 2, and 3. Stephen R. Schach
Slide 2.1 CHAPTER 1, 2, and 3 Slide 2.2 Object-Oriented Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach srs@vuse.vanderbilt.edu SOFTWARE LIFE-CYCLE MODELS AND PROCESS Overview Slide
More informationSAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS
SAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS AGILE AND SAP PROJECTS: FINDING THE FIT In a constantly changing business environment, enterprise systems and agile approaches are powerful allies. Enterprise
More informationEvolutionary Differences Between CMM for Software and the CMMI
Evolutionary Differences Between CMM for Software and the CMMI Welcome WelKom Huan Yín Bienvenue Bienvenido Wilkommen????S???S??? Bienvenuto Tervetuloa Välkommen Witamy - 2 Adapting an An Integrated Approach
More informationObjectives. Rapid software development. Topics covered. Rapid software development. Requirements. Characteristics of RAD processes
Objectives Rapid software development To explain how an iterative, incremental development process leads to faster delivery of more useful software To discuss the essence of agile development methods To
More informationChapter 2: The Project Management and Information Technology Context
Chapter 2: The Project Management and Information Technology Context TRUE/FALSE 1. Many of the theories and concepts of project management are difficult to understand. F PTS: 1 REF: 44 2. If project managers
More informationCommand and Control Software Development Lessons Learned. Lt Col Michael D. Sarchet Deputy Director, Space Systems Command and Control Division
Command and Control Software Development Lessons Learned Lt Col Michael D. Sarchet Deputy Director, Space Systems Command and Control Division 1 UNCLASSIFIED Agenda Two real world case studies Lessons
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationRequirements Basics. CSCE Lecture 4-09/02/2015
Requirements Basics CSCE 740 - Lecture 4-09/02/2015 This Week s Goals Understand the requirements problem Why are requirements so important? Get a feel for the structure of a requirements document What
More informationThe Product Creation Process
- 0. feasibility 1. definition 2. system 3. 4. integration & test 5. field monitoring needs verification core information Legend: in draft full under development most information 50% available in concept
More informationMINGGU Ke 1 Analisa dan Perancangan Sistem Informasi
MINGGU Ke 1 Analisa dan Perancangan Sistem Informasi Pokok Bahasan: A Framework for Systems Analysis and Design Tujuan Instruksional Khusus: Learn step by step building system analysis and design Referensi:
More informationReducing Business Risk
July 2005 Reducing Business Risk Through Agile Development Fred Tingey Head of Risk Systems BNP Paribas Introduction Context What is Agile Programming? Traditional vs Agile approach A New Way to do Things
More informationSome Well Known Software Development Life Cycle Models
Chapter 2 Some Well Known Software Development Life Cycle Models 2.1 Introduction It is really tough to draw a sharp line between software development approaches and Software Development Life Cycle (SDLC)
More information7. What is planning? It is an act of formulating a program for a definite course of action. Planning is to decide what is to be done.
UNIT I FUNDAMENTALS 2 MARKS QUESTIONS & ANSWERS 1. What is software project management? Software project management is the art and science of planning and leading software projects. It is sub discipline
More informationIMPLEMENTATION, EVALUATION & MAINTENANCE OF MIS:
IMPLEMENTATION, EVALUATION & MAINTENANCE OF MIS: The design of a management information system may seem to management to be an expensive project, the cost of getting the MIS on line satisfactorily may
More informationModel Driven Development Needs More Than Product Models
Model Driven Development Needs More Than Product Models Barry Boehm, USC USC-CSE Executive Workshop on MDA Mar. 16 th, 2005 3/16/2005 USC-CSE 1 Nature of Model Clashes Outline Among product, process, property,
More informationSE420 Software Quality Assurance
SE420 Software Quality Assurance Lecture 2 Software Specification Part-1 January 16, 2017 Sam Siewert SQA LO s (Learning Objectives) Theory and Principles 1. Coverage of Current SQA Theory and Practice
More informationAgile for Government Separating myth from reality. Open Webinar June 2, :00 pm EDT
Agile for Government Separating myth from reality Open Webinar June 2, 2016 2:00 pm EDT CGI Group Inc. 2013 Introductions Melissa Boudreault Vice President Consulting Services E-Mail: melissa.boudreault@cgi.com
More informationThe Agile PMP Teaching an Old Dog New Tricks
The Agile PMP Teaching an Old Dog New Tricks Why are we here today? What is Project Management? When will the project be done? How much will it cost? Do we all agree on what done looks like? What are the
More informationMULTI-USERS WORKSTATIONS. MICHAEL LING CHEE SlANG REPORT SUBMITTED IN FULFILMENT OF THE DEGREE OF COMPUTER SCIENCE (COMPUTER SYSTEM AND NETWORKING)
PERPUSTAKAAN UMP 1111111111111111111111111111111111111111111111 0000103096 MULTI-USERS WORKSTATIONS MICHAEL LING CHEE SlANG REPORT SUBMITTED IN FULFILMENT OF THE DEGREE OF COMPUTER SCIENCE (COMPUTER SYSTEM
More informationProject Management Context Outline
Project Management Context Outline Project Phases and the Project Life Cycle Product Life Cycles Project Stakeholders Understanding Organizational Influences Suggested Skills for a Project Manager 1 Project
More informationSoftware Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationTaking Control of Your Fuzzy
Taking Control of Your Fuzzy Front End MassMedic Presentation September 22, 2010 Sanjeev Wadhwani Project Management Consultant Integrated Project Management Company, Inc. Sanjeev Wadhwani Project Manager
More informationPassit4Sure.OG Questions. TOGAF 9 Combined Part 1 and Part 2
Passit4Sure.OG0-093.221Questions Number: OG0-093 Passing Score: 800 Time Limit: 120 min File Version: 7.1 TOGAF 9 Combined Part 1 and Part 2 One of the great thing about pass4sure is that is saves our
More informationIntroduction to Agile Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016
Introduction to Agile Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016 1 Goals Introduction to Agile Life Cycles The Agile Manifesto and Agile Principles Agile Life Cycles
More informationCustomer Profitability and Customer Value Models
Customer Profitability and Customer Value Models Sean McCall Vice President (713) 520-4204 sean.mccall@parivedasolutions.com Pariveda Solutions, Inc. Houston, TX Table of Contents Executive Summary The
More informationTECHNICAL REVIEWS AND AUDITS
Chapter 11 Technical Reviews and Audits CHAPTER 11 TECHNICAL REVIEWS AND AUDITS 11.1 PROGRESS MEASUREMENT The Systems Engineer measures design progress and maturity by assessing its development at key
More informationFactors to Consider When Implementing Automated Software Testing
Factors to Consider When Implementing Automated Software Testing By Larry Yang, MBA, SSCP, Security+, Oracle DBA OCA, ASTQB CTFL, ITIL V3 ITM Testing is a major component of the Software Development Lifecycle
More informationAn Oracle White Paper February Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions
An Oracle White Paper February 2014 Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions Executive Overview... 1 Introduction... 1 Standards Based...
More informationWHITEPAPER. Best Practices for Set-Top Box Product Development and Management
WHITEPAPER Best Practices for Set-Top Box Product Development and Management Contents Industry Landscape...3 The STB Lifecycle...4 In Conclusion...7 This paper was written by Robert Colbert, Software Architect,
More informationTOGAF - The - The Continuing Story Story
TOGAF - The - The Continuing Story Story The Open Group Framework (TOGAF) Presented by Chris Greenslade Chris@Architecting-the-Enterprise.com 1 of 53 TA P14 1 The questions to answer Who are we? What principles
More informationRedesigning the Organization with Information Systems
Chapter 14 Redesigning the Organization with Information Systems 14.1 2006 by Prentice Hall OBJECTIVES Demonstrate how building new systems produces organizational change Explain how a company can develop
More informationSession 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation
Session 11E Adopting Agile Ground Software Development Supannika Mobasser The Aerospace Corporation The Aerospace Corporation 2017 Overview To look beyond the horizon and to embrace the rapid rate of change
More informationProject Planning. COSC345 Software Engineering 2016 Slides by Andrew Trotman given by O K
Project Planning COSC345 Software Engineering 2016 Slides by Andrew Trotman given by O K Overview Assignment: The assignment sheet specifies a minimum Think about what else you should include (the cool
More informationAuditing Timeline. Top-Line Version
Auditing Timeline Top-Line Version As a complement to their book Agency Audits: How to Achieve Success, Joanne Davis and Jane Twyon have created a timeline that takes marketers through the auditing journey.
More informationSYSTEME ANALYSIS AND DESIGN
Ministry of Secondary Education Progressive Comprehensive High School & PCHS Mankon Bamenda Department of Computer Studies Republic of Cameroon Peace Work Fatherland School Year 2013/2014 SYSTEME ANALYSIS
More informationRequirements Engineering and Software Architecture Project Description
Requirements Engineering and Software Architecture Project Description Requirements Engineering Project Description This project is student-driven. There will be external sponsors, users, and others that
More informationValidation of NORM (Needs Oriented Framework for Producing Requirements Decision Material) Framework in Industry
Master Thesis Software Engineering Thesis no: MSE-2012:102 09 2012 Validation of NORM (Needs Oriented Framework for Producing Requirements Decision Material) Framework in Industry Salman Nazir Rizwan Yousaf
More informationSome Features of Project Management Using Dedicated Software in the Land Surveying Works
Some Features of Management Using Dedicated Software in the Land Surveying Works Lecturer Eng. BADEA ANA-CORNELIA, PhD badeacadastru@yahoo.com http://www.geodezie.utcb.ro/ Associate Professor Eng. BADEA
More informationContinuous Quality Assurance
White Paper Silk Central Connect Continuous Quality Assurance Deliver Great Software the Business Needs Table of Contents page Executive Summary...2 63% of All Software Projects Don t Succeed...2 40% of
More informationMicrosoft Office Project 2010 Basic Course 01: Getting Started
Microsoft Office Project 2010 Basic Course 01: Getting Started Slide 1 Topic A Project Management Concepts Slide 2 Project Constraints Slide 3 Phases of Project Management The initial Phase Initiating
More informationOn the management of nonfunctional requirements
- modulo B On the management of nonfunctional requirements Dr Tullio Vardanega European Space Research and Technology Centre and University of Padua TU Delft, 12 November 2001 Outline of the talk What
More informationRequirements Engineering. Andreas Zeller Saarland University
Requirements Engineering Software Engineering Andreas Zeller Saarland University Communication project initiation requirements gathering Planning estimating scheduling tracking Waterfall Model (1968) Modeling
More informationCase Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model
Case Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model Agile Waterfall Hybrid Model The Waterfall Model has been the ideal choice for software development.
More information2009 McGraw Hill Ryerson Limited. Kwantlen and Richardson Chpt 6 slide number 1
Chapter 6 Systems Development Phases, Tools, and Techniques Prof. Anita Beecroft, Kwantlen Polytechnic University (2009) Prof. Tim Richardson, University of Toronto (2011) 2009 McGraw Hill Ryerson Limited
More informationUnderstanding Business Requirements in terms of Components
Understanding in terms of Components Author: Richard Veryard Version: October 14 th 1998 richard@veryard.com http://www.veryard.com For more information about SCIPIO, please contact the SCIPIO Consortium.
More informationProject Management: As it ought to be!
Project Management: As it ought to be! Brian D. Krichbaum September 21, 2007 Process Coaching Incorporated Project Management As it ought to be! Most of us are beyond the point where we believe that successful
More informationApplying Lean Principles to Software Product Development
A TELLIANT SYSTEMS WHITE PAPER Applying Lean Principles to Software Product Development Intelligent Software. Delivered Applying Lean Principles to Software Product Development INTRODUCTION Lean Principles
More informationProduct Development & Entrepreneurship
Product Development & Entrepreneurship Design for Manufacturing and Assembly With input from the MIT-Portugal EDAM Post-graduate Program 1 2 Design for Manufacturing (DFM) Customer needs and product specs
More informationDRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors
1.1. Cost Estimation Models Parametric cost models used in avionics, space, ground, and shipboard platforms by the services are generally based on the common effort formula shown in Equation 1. Size of
More informationTenStep Project Management Process Summary
TenStep Project Management Process Summary Project management refers to the definition and planning, and then the subsequent management, control, and conclusion of a project. It is important to recognize
More informationSUSE Unified Delivery Process
Guide www.suse.com SUSE Unified Delivery Process What Is the SUSE Unified Delivery Process? The SUSE Unified Delivery Process is a solution delivery process based on the IBM* Rational Unified Process*
More informationComponent-based Development Process and Component Lifecycle
-based Process and Lifecycle Ivica Crnkovic 1, Michel Chaudron 2, Stig Larsson 3 1 Mälardalen University, Department of Computer Science and Electronics, Sweden 2 Eindhoven University of Technology, Dept.
More informationSE420 Software Quality Assurance
SE420 Software Quality Assurance Lecture 1 Introduction Part-2 January 16, 2017 Sam Siewert Course Learning Objectives Theory of Overall SQA Process Process Models (Waterfall, Spiral, XP) using Agile Strategy
More informationIntermediate Certificate in Software Testing Syllabus. Version 1.4
Intermediate Certificate in Software Testing Syllabus February 2010 Background This document is the syllabus for the intermediate paper which leads to the practitioner level of qualification, as administered
More informationInformation Technology. Project Management, Sixth Edition
Solutions to Accompany Information Technology Project Management, Sixth Edition ISBN-10: 0324786921 ISBN-13: 9780324786927 Course Technology MIS Series Companion Web Site: www.cengage.com/mis/schwalbe
More informationAgile Plus Comprehensive model for Software Development
Agile Plus Comprehensive model for Software Development Amit Juyal Umesh Kumar Tiwari Lata Nautiyal Shashidhar G. Koolagudi Assistant Professor Assistant Professor Assistant Professor Professor Graphic
More informationMINOTAUR - A VICTIM OF ITS OWN SUCCESS? ACCOMMODATING EVOLVING AND CONFLICTING SOFTWARE REQUIREMENTS
MINOTAUR - A VICTIM OF ITS OWN SUCCESS? ACCOMMODATING EVOLVING AND CONFLICTING SOFTWARE REQUIREMENTS Graeme Rainbird and Adam Pallant RM Consulting, The Post Office Technology Centre, Wheatstone Road,
More informationIntroduction to Project Management
Introduction to Project Management University Business Institute Amir Dabirian Vice President for Information Technology/CIO March 21 st, 2012 2 The Man Month Men and months are interchangeable commodities
More informationManagement of Projects
of Projects Giuseppe Lami Page 1 Course Outline! Part 1: The Project (PM) Framework! Part 2: The PM as a Process! Part 3: Techniques, Methods and Tools Supporting the PM! Part 4: Requirements Engineering
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More information