This document discusses software development lifecycles and modeling approaches. It describes the Capability Maturity Model which defines 5 levels of process maturity. It also describes the Waterfall model, V-shaped model, and prototyping approaches. The Waterfall model involves sequential phases of requirements, design, implementation, testing and deployment. The V-shaped model emphasizes testing in parallel with development phases. Prototyping can be used for requirements gathering and refinement through iterative development of prototype versions.
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, and spiral models. For each model, it describes the key steps, strengths, weaknesses, and scenarios where the model is best applied. The models range from sequential/linear to iterative/incremental approaches.
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, spiral, and agile models. It provides details on the key steps, strengths, weaknesses, and scenarios for using each model. Quality assurance is important for any SDLC and includes elements like defect tracking, unit testing, code reviews, and integration/system testing.
The document discusses several software development life cycle (SDLC) models:
- The waterfall model is a linear and sequential approach with distinct phases for requirements, design, implementation, testing, and deployment. It works well for projects with stable requirements.
- The V-shaped model emphasizes verification and validation testing at each phase. It is suited for projects requiring high reliability.
- Evolutionary prototyping involves building prototypes early and getting user feedback in iterations to refine requirements. It helps clarify unstable requirements.
- Rapid application development (RAD) emphasizes user involvement and productivity tools to reduce cycle times. It is suited when requirements are reasonably well known.
- Incremental development delivers partial systems in increments to get early benefits while allowing
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, spiral, and timeboxing. It provides descriptions of each model including typical steps, strengths, weaknesses, and when each model is best suited. It also discusses capability maturity model (CMM) levels and how changing the lifecycle model can impact development speed, quality, visibility, overhead, risk, and customer relations.
The document discusses several software development life cycle (SDLC) models:
- Waterfall model involves sequential phases of requirements, design, implementation, testing and deployment with defined deliverables for each phase. It works well for stable requirements but lacks flexibility.
- V-shaped model emphasizes verification and validation testing in parallel with development phases. It focuses on planning testing in early phases.
- Prototyping model involves building prototypes to clarify requirements with user feedback before final development.
- RAD model focuses on rapid delivery through time-boxed iterations with customer involvement.
- Incremental model prioritizes and implements requirements in groups to provide early functionality.
- Spiral model combines prototyping, risk analysis
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, and spiral models. For each model, it describes the key steps, strengths, weaknesses, and scenarios where the model is best applied. The models range from sequential/linear to iterative/incremental approaches.
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, spiral, and agile models. It provides details on the key steps, strengths, weaknesses, and scenarios for using each model. Quality assurance is important for any SDLC and includes elements like defect tracking, unit testing, code reviews, and integration/system testing.
The document discusses several software development life cycle (SDLC) models:
- The waterfall model is a linear and sequential approach with distinct phases for requirements, design, implementation, testing, and deployment. It works well for projects with stable requirements.
- The V-shaped model emphasizes verification and validation testing at each phase. It is suited for projects requiring high reliability.
- Evolutionary prototyping involves building prototypes early and getting user feedback in iterations to refine requirements. It helps clarify unstable requirements.
- Rapid application development (RAD) emphasizes user involvement and productivity tools to reduce cycle times. It is suited when requirements are reasonably well known.
- Incremental development delivers partial systems in increments to get early benefits while allowing
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, rapid application development (RAD), incremental, spiral, and timeboxing. It provides descriptions of each model including typical steps, strengths, weaknesses, and when each model is best suited. It also discusses capability maturity model (CMM) levels and how changing the lifecycle model can impact development speed, quality, visibility, overhead, risk, and customer relations.
The document discusses several software development life cycle (SDLC) models:
- Waterfall model involves sequential phases of requirements, design, implementation, testing and deployment with defined deliverables for each phase. It works well for stable requirements but lacks flexibility.
- V-shaped model emphasizes verification and validation testing in parallel with development phases. It focuses on planning testing in early phases.
- Prototyping model involves building prototypes to clarify requirements with user feedback before final development.
- RAD model focuses on rapid delivery through time-boxed iterations with customer involvement.
- Incremental model prioritizes and implements requirements in groups to provide early functionality.
- Spiral model combines prototyping, risk analysis
The document discusses several software development life cycle (SDLC) models:
1) The waterfall model is a linear model that progresses through requirements, design, implementation, testing, and deployment phases. It works well for projects with stable requirements but lacks flexibility.
2) The V-shaped model emphasizes testing at each phase. It is good for high reliability projects but does not handle changes well.
3) Prototyping models involve building prototypes early for user feedback to refine requirements. This improves accuracy but risks scope creep.
4) Incremental models prioritize requirements and implement them in phases to deliver working functionality early. This reduces risk but requires strong planning.
5) The spiral model incorporates risk analysis and protot
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, incremental, spiral, rapid application development (RAD), dynamic systems development method (DSDM), adaptive software development, and agile methods. It provides an overview of the key characteristics, strengths, weaknesses, and types of projects that each model is best suited for. Tailored SDLC models are recommended to customize processes based on specific project needs and risks.
Bba ii cam u iii-introduction to sdlc cycleRai University
This document discusses several systems development life cycle (SDLC) models: the waterfall model, V-shaped model, structured evolutionary prototyping model, and spiral model. The waterfall model involves sequential phases of requirements, design, implementation, and testing. The V-shaped model emphasizes verification and validation testing parallel to development phases. Structured evolutionary prototyping uses iterative prototyping and user feedback. The spiral model incorporates risk analysis and prototyping in iterative cycles like waterfall. Each model has strengths for certain projects but also limitations.
This document discusses different process models used in software development. It describes the key phases and characteristics of several common process models including waterfall, prototyping, V-model, incremental, iterative, spiral and agile development models. The waterfall model involves sequential phases from requirements to maintenance without iteration. Prototyping allows for user feedback earlier. The V-model adds verification and validation phases. Incremental and iterative models divide the work into smaller chunks to allow for iteration and user feedback throughout development.
This document discusses several software development models and practices. It describes the waterfall model which involves sequential stages of requirement analysis, design, implementation, testing, and maintenance. It also covers prototyping, rapid application development (RAD), and component assembly models which are more iterative in nature. The prototyping model involves creating prototypes to help define requirements, RAD emphasizes reuse and short development cycles, and component assembly focuses on reusing existing software components.
ISE_Lecture Week 2-SW Process Models.pptHumzaWaris1
The document discusses various software development processes. It begins by defining a software process as a framework that describes the activities performed at each stage of a project. It then categorizes common activities as software specification, development, validation, and evolution. The document goes on to describe plan-driven and agile processes, and notes that most practical processes include elements of both. It provides details on specific process models like waterfall, V-model, prototyping, incremental development, component-based development, and spiral model.
This document discusses systems analysis and the waterfall model of software development. It describes the stages of systems analysis including investigation, design, and implementation with user consultation. The design stage produces a system specification detailing materials, procedures, hardware requirements, and inputs/outputs. Systems are monitored after implementation for changes. The waterfall model stages are feasibility, requirements analysis, design specification, coding, testing, and maintenance. Prototyping is discussed as an alternative that involves users earlier to detect issues and ensure requirements are met.
Process models are not perfect, but provide road map for software engineering work. Software models provide stability, control, and organization to a process that if not managed can easily get out of control
Software process models are adapted to meet the needs of software engineers and managers for a specific project.
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations, such as with prototyping, the spiral model and concurrent development.
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments that build on each other. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations like prototyping, the spiral model and concurrent development.
The document describes several software development life cycle (SDLC) models, including the waterfall model, V-shaped model, prototyping model, rapid application development (RAD) model, incremental model, and spiral model. The waterfall model involves sequential phases of requirements, design, implementation, testing and deployment. The V-shaped model emphasizes verification and validation with testing planned in parallel with development phases. The prototyping model uses iterative prototypes to refine requirements with user feedback. RAD focuses on accelerated development through workshops, automated tools and time-boxed construction phases. The incremental model delivers functionality in increments, while the spiral model incorporates risk analysis and prototyping in iterative development cycles.
This document provides an overview of several software development life cycle (SDLC) models, including Waterfall, V-Shaped, Prototyping, Rapid Application Development (RAD), Incremental, Spiral, and Agile models. For each model, the key steps or phases are described, along with their strengths and weaknesses. The document also provides guidance on which types of projects each model would be best suited for. It emphasizes that the best model depends on the specific project and that aspects of different models can be combined as needed.
Introduction,Software Process Models, Project Managementswatisinghal
The document discusses different types of software processes and models used in software engineering. It defines software and differentiates it from programs. It then explains key concepts in software engineering including the waterfall model, prototyping model, incremental/iterative model, and spiral model. For each model it provides an overview and discusses their advantages and limitations.
Software development process models
Rapid Application Development (RAD) Model
Evolutionary Process Models
Spiral Model
THE FORMAL METHODS MODEL
Specialized Process Models
The Concurrent Development Model
The document discusses software development life cycles (SDLC). It describes the typical stages of an SDLC including feasibility study, requirements analysis, system design, development, testing, implementation, and maintenance. Several SDLC models are mentioned, including waterfall, spiral, iterative, prototyping, and RAD (rapid application development). The waterfall model is described as having distinct sequential stages with no overlap between phases. Prototyping and RAD methodologies are also explained in further detail.
The document discusses several system development life cycle (SDLC) models including waterfall, iterative, incremental, spiral, RAD, concurrent, and unified process models. The key phases of SDLC are defined as preliminary survey, analysis, design, implementation, post-implementation/maintenance, and project termination. Each model takes different approaches such as sequential, iterative, incremental, or concurrent development through the SDLC phases.
The document discusses key differences between software engineering and software programming. Software engineering involves teams developing complex, long-lasting systems through defined processes, with maintenance accounting for over 60% of costs. It addresses multiple stakeholders and separates roles like architect and developer. Software engineering is concerned with all aspects of production, adopting systematic approaches depending on constraints.
The document discusses several software development process models including waterfall, iterative development, prototyping, RAD, spiral, RUP, and agile processes. The waterfall model is a linear sequential process while iterative development allows for incremental improvements. Prototyping allows users to provide early feedback. RAD combines waterfall and prototyping and emphasizes rapid development. Spiral model iterates through risk analysis, development, and planning phases. RUP is object-oriented and divided into cycles. Agile processes emphasize working software, incremental delivery, flexibility, and customer involvement.
The document discusses several software development life cycle (SDLC) models: waterfall model, prototyping model, iterative enhancement model, spiral model, and object-oriented methodology model. It provides detailed descriptions of each model's phases, process, advantages, and limitations. The waterfall model is the simplest and involves sequential phases of requirements, design, implementation, testing, and maintenance. Prototyping and iterative enhancement models allow for more user feedback and flexibility. The spiral model is risk-driven and iterative. The object-oriented model focuses on identifying system objects and relationships.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
The document discusses several software development life cycle (SDLC) models:
1) The waterfall model is a linear model that progresses through requirements, design, implementation, testing, and deployment phases. It works well for projects with stable requirements but lacks flexibility.
2) The V-shaped model emphasizes testing at each phase. It is good for high reliability projects but does not handle changes well.
3) Prototyping models involve building prototypes early for user feedback to refine requirements. This improves accuracy but risks scope creep.
4) Incremental models prioritize requirements and implement them in phases to deliver working functionality early. This reduces risk but requires strong planning.
5) The spiral model incorporates risk analysis and protot
The document discusses several software development life cycle (SDLC) models including waterfall, V-shaped, prototyping, incremental, spiral, rapid application development (RAD), dynamic systems development method (DSDM), adaptive software development, and agile methods. It provides an overview of the key characteristics, strengths, weaknesses, and types of projects that each model is best suited for. Tailored SDLC models are recommended to customize processes based on specific project needs and risks.
Bba ii cam u iii-introduction to sdlc cycleRai University
This document discusses several systems development life cycle (SDLC) models: the waterfall model, V-shaped model, structured evolutionary prototyping model, and spiral model. The waterfall model involves sequential phases of requirements, design, implementation, and testing. The V-shaped model emphasizes verification and validation testing parallel to development phases. Structured evolutionary prototyping uses iterative prototyping and user feedback. The spiral model incorporates risk analysis and prototyping in iterative cycles like waterfall. Each model has strengths for certain projects but also limitations.
This document discusses different process models used in software development. It describes the key phases and characteristics of several common process models including waterfall, prototyping, V-model, incremental, iterative, spiral and agile development models. The waterfall model involves sequential phases from requirements to maintenance without iteration. Prototyping allows for user feedback earlier. The V-model adds verification and validation phases. Incremental and iterative models divide the work into smaller chunks to allow for iteration and user feedback throughout development.
This document discusses several software development models and practices. It describes the waterfall model which involves sequential stages of requirement analysis, design, implementation, testing, and maintenance. It also covers prototyping, rapid application development (RAD), and component assembly models which are more iterative in nature. The prototyping model involves creating prototypes to help define requirements, RAD emphasizes reuse and short development cycles, and component assembly focuses on reusing existing software components.
ISE_Lecture Week 2-SW Process Models.pptHumzaWaris1
The document discusses various software development processes. It begins by defining a software process as a framework that describes the activities performed at each stage of a project. It then categorizes common activities as software specification, development, validation, and evolution. The document goes on to describe plan-driven and agile processes, and notes that most practical processes include elements of both. It provides details on specific process models like waterfall, V-model, prototyping, incremental development, component-based development, and spiral model.
This document discusses systems analysis and the waterfall model of software development. It describes the stages of systems analysis including investigation, design, and implementation with user consultation. The design stage produces a system specification detailing materials, procedures, hardware requirements, and inputs/outputs. Systems are monitored after implementation for changes. The waterfall model stages are feasibility, requirements analysis, design specification, coding, testing, and maintenance. Prototyping is discussed as an alternative that involves users earlier to detect issues and ensure requirements are met.
Process models are not perfect, but provide road map for software engineering work. Software models provide stability, control, and organization to a process that if not managed can easily get out of control
Software process models are adapted to meet the needs of software engineers and managers for a specific project.
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations, such as with prototyping, the spiral model and concurrent development.
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments that build on each other. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations like prototyping, the spiral model and concurrent development.
The document describes several software development life cycle (SDLC) models, including the waterfall model, V-shaped model, prototyping model, rapid application development (RAD) model, incremental model, and spiral model. The waterfall model involves sequential phases of requirements, design, implementation, testing and deployment. The V-shaped model emphasizes verification and validation with testing planned in parallel with development phases. The prototyping model uses iterative prototypes to refine requirements with user feedback. RAD focuses on accelerated development through workshops, automated tools and time-boxed construction phases. The incremental model delivers functionality in increments, while the spiral model incorporates risk analysis and prototyping in iterative development cycles.
This document provides an overview of several software development life cycle (SDLC) models, including Waterfall, V-Shaped, Prototyping, Rapid Application Development (RAD), Incremental, Spiral, and Agile models. For each model, the key steps or phases are described, along with their strengths and weaknesses. The document also provides guidance on which types of projects each model would be best suited for. It emphasizes that the best model depends on the specific project and that aspects of different models can be combined as needed.
Introduction,Software Process Models, Project Managementswatisinghal
The document discusses different types of software processes and models used in software engineering. It defines software and differentiates it from programs. It then explains key concepts in software engineering including the waterfall model, prototyping model, incremental/iterative model, and spiral model. For each model it provides an overview and discusses their advantages and limitations.
Software development process models
Rapid Application Development (RAD) Model
Evolutionary Process Models
Spiral Model
THE FORMAL METHODS MODEL
Specialized Process Models
The Concurrent Development Model
The document discusses software development life cycles (SDLC). It describes the typical stages of an SDLC including feasibility study, requirements analysis, system design, development, testing, implementation, and maintenance. Several SDLC models are mentioned, including waterfall, spiral, iterative, prototyping, and RAD (rapid application development). The waterfall model is described as having distinct sequential stages with no overlap between phases. Prototyping and RAD methodologies are also explained in further detail.
The document discusses several system development life cycle (SDLC) models including waterfall, iterative, incremental, spiral, RAD, concurrent, and unified process models. The key phases of SDLC are defined as preliminary survey, analysis, design, implementation, post-implementation/maintenance, and project termination. Each model takes different approaches such as sequential, iterative, incremental, or concurrent development through the SDLC phases.
The document discusses key differences between software engineering and software programming. Software engineering involves teams developing complex, long-lasting systems through defined processes, with maintenance accounting for over 60% of costs. It addresses multiple stakeholders and separates roles like architect and developer. Software engineering is concerned with all aspects of production, adopting systematic approaches depending on constraints.
The document discusses several software development process models including waterfall, iterative development, prototyping, RAD, spiral, RUP, and agile processes. The waterfall model is a linear sequential process while iterative development allows for incremental improvements. Prototyping allows users to provide early feedback. RAD combines waterfall and prototyping and emphasizes rapid development. Spiral model iterates through risk analysis, development, and planning phases. RUP is object-oriented and divided into cycles. Agile processes emphasize working software, incremental delivery, flexibility, and customer involvement.
The document discusses several software development life cycle (SDLC) models: waterfall model, prototyping model, iterative enhancement model, spiral model, and object-oriented methodology model. It provides detailed descriptions of each model's phases, process, advantages, and limitations. The waterfall model is the simplest and involves sequential phases of requirements, design, implementation, testing, and maintenance. Prototyping and iterative enhancement models allow for more user feedback and flexibility. The spiral model is risk-driven and iterative. The object-oriented model focuses on identifying system objects and relationships.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
Physiology and chemistry of skin and pigmentation, hairs, scalp, lips and nail, Cleansing cream, Lotions, Face powders, Face packs, Lipsticks, Bath products, soaps and baby product,
Preparation and standardization of the following : Tonic, Bleaches, Dentifrices and Mouth washes & Tooth Pastes, Cosmetics for Nails.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
Executive Directors Chat Leveraging AI for Diversity, Equity, and InclusionTechSoup
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
SE_models_1.ppt
1. SOFTWARE DEVELOPMENT LIFE
CYCLE (SDLC)
“You’ve got to be very careful if you don’t know where
you’re going, because you might not get there.”
Yogi Berra
2. Capability Maturity Model
(CMM)
A bench-mark for measuring the maturity of
an organization’s software process
CMM defines 5 levels of process maturity
based on certain Key ProcessAreas (KPA)
4. SDLC Model
A framework that describes the activities
performed at each stage of a software
development project.
5. Waterfall Model
Requirements – defines needed
information, function, behavior,
performance and interfaces.
Design – data structures,
software architecture, interface
representations, algorithmic
details.
Implementation – source code,
database, user documentation,
testing.
6.
7. Waterfall Strengths
Easy to understand, easy to use
Provides structure to inexperienced staff
Milestones are well understood
Sets requirements stability
Good for management control (plan, staff, track)
Works well when quality is more important than
cost or schedule
8. Waterfall Deficiencies
All requirements must be known upfront
Deliverables created for each phase are
considered frozen – inhibits flexibility
Can give a false impression of progress
Does not reflect problem-solving nature of
software development – iterations of phases
Integration is one big bang at the end
Little opportunity for customer to preview the
system (until it may be too late)
9. When to use the Waterfall
Model
Requirements are very well known
Product definition is stable
Technology is understood
New version of an existing product
Porting an existing product to a new platform.
High risk for new systems because of specification and
design problems.
Low risk for well-understood developments using
familiar technology.
10. V-Shaped SDLC Model
A variant of the Waterfall
that emphasizes the
verification and validation
of the product.
Testing of the product is
planned in parallel with a
corresponding phase of
development
11. V-Shaped Steps
Project and Requirements
Planning – allocate resources
Product Requirements and
Specification Analysis –
complete specification of the
software system
Architecture or High-Level
Design – defines how
software functions fulfill the
design
Detailed Design – develop
algorithms for each
architectural component
Production, operation and
maintenance – provide for
enhancement and corrections
System and acceptance
testing – check the entire
software system in its
environment
Integration andTesting –
check that modules
interconnect correctly
Unit testing – check that each
module acts as expected
Coding – transform
algorithms into software
12. V-Shaped Strengths
Emphasize planning for verification and
validation of the product in early stages of
product development
Each deliverable must be testable
Project management can track progress by
milestones
Easy to use
13. V-Shaped Weaknesses
Does not easily handle concurrent events
Does not handle iterations or phases
Does not easily handle dynamic changes in
requirements
Does not contain risk analysis activities
14. When to use the V-Shaped
Model
Excellent choice for systems requiring high
reliability – hospital patient control
applications
All requirements are known up-front
When it can be modified to handle changing
requirements beyond analysis phase
Solution and technology are known
15. Protoyping: Basic Steps
Identify basic requirements
Including input and output info
Details (e.g., security) generally ignored
Develop initial prototype
UI first
Review
Customers/end –users review and give feedback
Revise and enhance the prototype & specs
Negotiation about scope of contract may be
necessary
16. Dimensions of prototyping
Horizontal prototype
Broad view of entire system/sub-system
Focus is on user interaction more than low-level
system functionality (e.g. , databsae access)
Useful for:
Confirmation of UI requirements and system scope
Demonstration version of the system to obtain buy-
in from business/customers
Develop preliminary estimates of development
time, cost, effort
17. Dimensions of Prototyping
Vertical prototype
More complete elaboration of a single sub-system
or function
Useful for:
Obtaining detailed requirements for a given
function
Refining database design
Obtaining info on system interface needs
Clarifying complex requirements by drilling down to
actual system functionality
18. Types of prototyping
Throwaway /rapid/close-ended prototyping
Creation of a model that will be discarded rather
than becoming part of the final delivered software
After preliminary requirements gathering, used to
visually show the users what their requirements
may look like when implemented
Focus is on quickly developing the model
not on good programming practices
CanWizard of Oz things
19. Fidelity of Protype
Low-fidelity
Paper/pencil
Mimics the functionality, but does not look like it
20.
21. Fidelity of Protype
Medium to High-fidelity
GUI builder
“Click dummy” prototype – looks like the system, but
does not provide the functionality
Or provide functionality, but have it be general and
not linked to specific data
http://www.youtube.com/watch?v=VGjcFouSlpk
http://www.youtube.com/watch?v=5oLlmNbxap4&fea
ture=related
22. Throwaway Prototyping steps
Write preliminary requirements
Design the prototype
User experiences/uses the prototype,
specifies new requirements
Repeat if necessary
Write the final requirements
Develop the real products
23. Evolutionary Prototyping
Aka breadboard prototyping
Goal is to build a very robust prototype in a
structured manner and constantly refine it
The evolutionary prototype forms the heart
of the new system and is added to and
refined
Allow the development team to add features
or make changes that were not conceived in
the initial requirements
24. Evolutionary Prototyping
Model
Developers build a prototype during the
requirements phase
Prototype is evaluated by end users
Users give corrective feedback
Developers further refine the prototype
When the user is satisfied, the prototype code
is brought up to the standards needed for a
final product.
25. EP Steps
A preliminary project plan is developed
An partial high-level paper model is created
The model is source for a partial requirements
specification
A prototype is built with basic and critical
attributes
The designer builds
the database
user interface
algorithmic functions
The designer demonstrates the prototype, the
user evaluates for problems and suggests
improvements.
This loop continues until the user is satisfied
26. EP Strengths
Customers can “see” the system requirements as
they are being gathered
Developers learn from customers
A more accurate end product
Unexpected requirements accommodated
Allows for flexible design and development
Steady, visible signs of progress produced
Interaction with the prototype stimulates
awareness of additional needed functionality
27. Incremental prototyping
Final product built as separate prototypes
At the end, the prototypes are merged into a
final design
28. Extreme Prototyping
Often used for web applications
Development broken down into 3 phases,
each based on the preceding 1
1. Static prototype consisting of HTML pages
2. Screen are programmed and fully functional
using a simulated services layer
Fully functional UI is developed with little regard
to the services, other than their contract
3. Services are implemented
29. Prototyping advantages
Reduced time and cost
Can improve the quality of requirements and
specifications provided to developers
Early determination of what the user really wants can
result in faster and less expensive software
Improved/increased user involvement
User can see and interact with the prototype, allowing
them to provide better/more complete feedback and
specs
Misunderstandings/miscommunications revealed
Final product more likely to satisfy their desired
look/feel/performance
30. Disadvantages of prototyping 1
Insufficient analysis
Focus on limited prototype can distract
developers from analyzing complete project
May overlook better solutions
Conversion of limited prototypes into poorly
engineered final projects that are hard to maintain
Limited functionality may not scale well if used as
the basis of a final deliverable
May not be noticed if developers too focused on
building prototype as a model
31. Disadvantages of prototyping 2
User confusion of prototype and finished
system
Users can think that a prototype (intended to be
thrown away) is actually a final system that needs
to be polished
Unaware of the scope of programming needed to
give prototype robust functionality
Users can become attached to features included in
prototype for consideration and then removed
from final specification
32. Disadvantages of prototyping 3
Developer attachment to prototype
If spend a great deal of time/effort to produce,
may become attached
Might try to attempt to convert a limited
prototype into a final system
Bad if the prototype does not have an appropriate
underlying architecture
33. Disadvantages of prototyping 4
Excessive development time of the prototype
Prototyping supposed to be done quickly
If developers lose sight of this, can try to build a
prototype that is too complex
For throw away prototypes, the benefits realized
from the prototype (precise requirements) may
not offset the time spent in developing the
prototype – expected productivity reduced
Users can be stuck in debates over prototype
details and hold up development process
34. Disadvantages of prototyping 5
Expense of implementing prototyping
Start up costs of prototyping may be high
Expensive to change development methodologies
in place (re-training, re-tooling)
Slow development if proper training not in place
High expectations for productivity unrealistic if
insufficient recognition of the learning curve
Lower productivity can result if overlook the need
to develop corporate and project specific
underlying structure to support the technology
35. Best uses of prototyping
Most beneficial for systems that will have
many interactions with end users
The greater the interaction between the
computer and the user, the greater the
benefit of building a quick system for the user
to play with
Especially good for designing good human-
computer interfaces
36. Spiral SDLC Model
Adds risk
analysis, and 4gl
RAD prototyping
to the waterfall
model
Each cycle
involves the
same sequence
of steps as the
waterfall process
model
37. Risk
analysis
Risk
analysis
Risk
analysis
Risk
analysis Proto-
type 1
Prototype 2
Prototype 3
Opera-
tional
protoype
Concept of
Operation
Simulations, models, benchmarks
S/W
requirements
Requirement
validation
Design
V&V
Product
design Detailed
design
Code
Unit test
Integration
test
Acceptance
test
Service Develop, verify
next-level product
Evaluate alternatives
identify, resolve risks
Determine objectives
alternatives and
constraints
Plan next phase
Integration
and test plan
Development
plan
Requirements plan
Life-cycle plan
REVIEW
38. Spiral Quadrant: Determine objectives,
alternatives and constraints
Objectives: functionality, performance,
hardware/software interface, critical success
factors, etc.
Alternatives: build, reuse, buy, sub-contract, etc.
Constraints: cost, schedule, interface, etc.
39. Spiral Quadrant: Evaluate alternatives,
identify and resolve risks
Study alternatives relative to objectives and
constraints
Identify risks (lack of experience, new
technology, tight schedules, poor process, etc.
Resolve risks (evaluate if money could be lost by
continuing system development
41. Spiral Quadrant: Plan next phase
Typical activities
Develop project plan
Develop configuration management plan
Develop a test plan
Develop an installation plan
42. Spiral Model Strengths
Provides early indication of insurmountable
risks, without much cost
Users see the system early because of rapid
prototyping tools
Critical high-risk functions are developed first
The design does not have to be perfect
Users can be closely tied to all lifecycle steps
Early and frequent feedback from users
Cumulative costs assessed frequently
43. Spiral Model Weaknesses
Time spent for evaluating risks too large for small or low-
risk projects
Time spent planning, resetting objectives, doing risk
analysis and prototyping may be excessive
The model is complex
Risk assessment expertise is required
Spiral may continue indefinitely
Developers must be reassigned during non-development
phase activities
May be hard to define objective, verifiable milestones
that indicate readiness to proceed through the next
iteration
44. When to use Spiral Model
When creation of a prototype is appropriate
When costs and risk evaluation is important
For medium to high-risk projects
Long-term project commitment unwise because
of potential changes to economic priorities
Users are unsure of their needs
Requirements are complex
New product line
Significant changes are expected (research and
exploration)
45. Role Playing Game for SE’s
http://www.youtube.com/watch?v=kkkl3Lucx
TY&feature=related
46. Housekeeping
Individual Assignment:
Post mortem + peer review
Final presentations/demos
July 26/28 - 25 minutes per
~8 minute presentation
~10 minute demo
~7 minutes questions
Course evaluations thisThursday (4:05 pm)
47. The Rise and Fall of
Waterfall
http://www.youtube.com/watch?v=X1c2--
sP3o0&NR=1&feature=fvwp
Warning: bad language at 3:50! (hands over
ears if easily offended!)
49. Agile SDLC’s
Speed up or bypass one or more life cycle
phases
Usually less formal and reduced scope
Used for time-critical applications
Used in organizations that employ disciplined
methods
50. Some Agile Methods
Rapid Application Development (RAD)
Incremental SDLC
Scrum
Extreme Programming (XP)
Adaptive Software Development (ASD)
Feature Driven Development (FDD)
Crystal Clear
Dynamic Software Development Method
(DSDM)
Rational Unify Process (RUP)
55. Rapid Application Model (RAD)
Requirements planning phase (a workshop
utilizing structured discussion of business
problems)
User description phase – automated tools
capture information from users
Construction phase – productivity tools, such
as code generators, screen generators, etc.
inside a time-box. (“Do until done”)
Cutover phase -- installation of the system,
user acceptance testing and user training
56. Requirements Planning Phase
Combines elements of the system planning
and systems analysis phases of the System
Development Life Cycle (SDLC).
Users, managers, and IT staff members
discuss and agree on business needs, project
scope, constraints, and system requirements.
It ends when the team agrees on the key
issues and obtains management
authorization to continue.
57. User Design Phase
Users interact with systems analysts and
develop models and prototypes that represent
all system processes, inputs, and outputs.
Typically use a combination of Joint Application
Development (JAD) techniques and CASE tools
to translate user needs into working models.
A continuous interactive process that allows
users to understand, modify, and eventually
approve a working model of the system that
meets their needs.
59. Construction Phase
Focuses on program and application
development task similar to the SDLC.
However, users continue to participate and
can still suggest changes or improvements as
actual screens or reports are developed.
Its tasks are programming and application
development, coding, unit-integration, and
system testing.
60. Cutover Phase
Resembles the final tasks in the SDLC
implementation phase.
Compared with traditional methods, the
entire process is compressed.As a result, the
new system is built, delivered, and placed in
operation much sooner.
Tasks are data conversion, full-scale testing,
system changeover, user training.
61. RAD Strengths
Reduced cycle time and improved productivity
with fewer people means lower costs
Time-box approach mitigates cost and schedule
risk
Customer involved throughout the complete
cycle minimizes risk of not achieving customer
satisfaction and business needs
Focus moves from documentation to code
(WYSIWYG).
Uses modeling concepts to capture information
about business, data, and processes.
62. RAD Weaknesses
Accelerated development process
must give quick responses to the user
Risk of never achieving closure
Hard to use with legacy systems
Requires a system that can be
modularized
Developers and customers must be
committed to rapid-fire activities in
an abbreviated time frame.
63. When to use RAD
Reasonably well-known requirements
User involved throughout the life
cycle
Project can be time-boxed
Functionality delivered in increments
High performance not required
Low technical risks
System can be modularized
64. Incremental SDLC Model
Construct a partial
implementation of a total
system
Then slowly add increased
functionality
The incremental model
prioritizes requirements of
the system and then
implements them in
groups.
Each subsequent release of
the system adds function
to the previous release,
until all designed
functionality has been
implemented.
65. Incremental Model Strengths
Develop high-risk or major functions first
Each release delivers an operational product
Customer can respond to each build
Uses “divide and conquer” breakdown of tasks
Lowers initial delivery cost
Initial product delivery is faster
Customers get important functionality early
Risk of changing requirements is reduced
66. Incremental Model Weaknesses
Requires good planning and design
Requires early definition of a complete and
fully functional system to allow for the
definition of increments
Well-defined module interfaces are
required (some will be developed long
before others)
Total cost of the complete system is not
lower
67. When to use the Incremental
Model
Risk, funding, schedule, program complexity,
or need for early realization of benefits.
Most of the requirements are known up-front
but are expected to evolve over time
A need to get basic functionality to the
market early
On projects which have lengthy development
schedules
On a project with new technology
70. Scrum in 13 seconds:
http://www.youtube.com/watch?v=9DKM9HcRnZ
8&feature=related
Scrum in 10 minutes:
http://www.youtube.com/watch?v=Q5k7a9YEoUI
More scrum slides:
http://www.mountaingoatsoftware.com/system/p
resentation/file/129/Getting-Agile-With-Scrum-
Cohn-NDC2010.pdf?1276712017
Scalability of scrum addressed on slides 33-35
71. Scrum advantages
Agile scrum helps the company in saving time
and money.
Scrum methodology enables projects where
the business requirements documentation is
hard to quantify to be successfully developed.
Fast moving, cutting edge developments can
be quickly coded and tested using this
method, as a mistake can be easily rectified.
72. Scrum advantages
It is a lightly controlled method which insists
on frequent updating of the progress in work
through regular meetings.Thus there is clear
visibility of the project development.
Like any other agile methodology, this is also
iterative in nature. It requires continuous
feedback from the user.
Due to short sprints and constant feedback, it
becomes easier to cope with the changes.
73. Scrum advantages
Daily meetings make it possible to measure
individual productivity.This leads to the
improvement in the productivity of each of
the team members.
Issues are identified well in advance through
the daily meetings and hence can be resolved
in speedily
It is easier to deliver a quality product in a
scheduled time.
74. Scrum advantages
Agile Scrum can work with any technology/
programming language but is particularly
useful for fast moving web 2.0 or new media
projects.
The overhead cost in terms of process and
management is minimal thus leading to a
quicker, cheaper result.
75. Scrum disadvantages
Agile Scrum is one of the leading causes of
scope creep because unless there is a definite
end date, the project management
stakeholders will be tempted to keep
demanding new functionality is delivered.
If a task is not well defined, estimating
project costs and time will not be accurate. In
such a case, the task can be spread over
several sprints.
If the team members are not committed, the
project will either never complete or fail.
76. Scrum disadvantages
It is good for small, fast moving projects as it
works well only with small team.
This methodology needs experienced team
members only. If the team consists of people
who are novices, the project cannot be
completed in time.
Scrum works well when the Scrum Master trusts
the team they are managing. If they practice too
strict control over the team members, it can be
extremely frustrating for them, leading to
demoralisation and the failure of the project.
77. Scrum disadvantages
If any of the team members leave during a
development it can have a huge inverse effect
on the project development
Project quality management is hard to
implement and quantify unless the test team
are able to conduct regression testing after
each sprint.
Editor's Notes
imeboxing is a planning technique common in planning projects (typically for software development), where the schedule is divided into a number of separate time periods (timeboxes, normally two to six weeks long), with each part having its own deliverables, deadline and budget. Timeboxing is a core aspect of rapid application development (RAD) software development processes such as dynamic systems development method (DSDM) and agile software development.
Timeboxes are used as a form of risk management, especially for tasks that may easily extend past their deadlines. The end date (deadline) is one of the primary drivers in the planning and should not be changed as it is usually linked to a delivery date of the product. If the team exceeds the deadline, the team failed in proper planning and / or effective execution of the plan. This can be the result of: the wrong people on the wrong job (lack of communication between teams, lack of experience, lack of commitment / drive / motivation, lack of speed) or underestimation of the (complexity of the) requirements.
When the team exceeds the deadline, the following actions might be taken after conferring with the Client:
Dropping requirements of lower impact (the ones that will not be directly missed by the user)
Working overtime to compensate for the time lost
Moving the deadline