SlideShare une entreprise Scribd logo
1  sur  32
Télécharger pour lire hors ligne
In this Module, we look at
  • what we mean by a “process”
  • software development products, processes &
    resources
  • several models of the software development
    process
  • tools & techniques for process modeling

                                            Back   Next
- Process is a series of steps involving activities
  constraints and resources that produce an
  intended output of some kind.
- in building a software product, process is refer to a
  life cycle
- software development process is sometimes
called
- software life cycle than a procedure
  a process is more
- a process may require design to occur before
  coding, many different design may be used
- Process guides our actions by allowing use
  examine, control and improve that comprise the
  process.
Characteristics of a Process
- The process prescribes all of the major process
  activities.
- The process uses resources, subject to a set of
  constraints (such schedule) and produces
  intermediate and final product.
- The process may be composed that are linked in
  some way. The process may be defined as
  hierarchy of process, organized so that each sub-
  process has its own process models
- Each process activity has entry and exit criteria, so
  that when the activity begins and ends.
- The activities are organized in sequence, so that it
  is clear when one activity is performed relative to
  the other activities.
- Every process has a guiding principles that explain
  the goals of each activity.
- Constraints or controls may apply to an activity,
  resource or product.
Reasons for Modeling Process
 - It forms common understanding of the activities,
   resources and constraints involved in software
   development.
 - It helps the development team find
     inconsistencies, redundancies and omissions in
the
- process and in its constituent parts. such as
   It reflects the goals of development
   building high-quality software, finding faults in
   early development and meeting required budget
   and schedule constraints.
- It helps the development team understand where
  tailoring is to occur for the special situation.
- The waterfall model is a sequential software
  development model (a process for the creation of
  software) in which development is seen as flowing
  steadily downwards (like a waterfall) through the
  phases of software developmet.
- Winston W. Royce (1929–1995), present this
  model cited in his article published in 1970.
- It is very useful in helping the developers lay out
  what they need to do.
- The biggest problem with the waterfall model is
  does not reflect the way the code is really
  developed.
In Royce's original waterfall model, the following
phases are followed in order:

1.Requirements specification
2.Design
3.Construction (AKA implementation or coding)
4.Integration
5.Testing and debugging (AKA validation)
6.Installation
7.Maintenance
Requirement
   Analysis

        System
        Design

               Program
                Design


                     Coding

                             Unit &
                          Integration
                            Testing

                                   System
                                   Testing

                                         Acceptance
                                           Testing

                                                      Operation &
The Waterfall Model                                   Maintenance
The software development process in reality.
- The sashimi model (so called because it features
  overlapping phases, like the overlapping fish of
  Japanese sashimi) was originated by Peter
  DeGrace.
- also referred as the waterfall model with
  overlapping phases or with feedback
Instructor’s idea about the
                                                     Sashimi Model




     Requirement
       Analysis ystem
              S
               DesignProgram
                      Design
                           Coding Unit &
                                Integration
                                  Testing ystem
                                         S
                                         Testing
                                               Acceptance
                                                 Testing
                                                       Operation &
                                                       Maintenance




The Waterfall Model with overlapping phases / The Waterfall
Model with feedback
- Prototyping is a partially developed product that
  enables customers and developers to examine
  some aspect of the proposed system and decide if
  it is suitable or appropriate for the finished
  product.
- Design prototyping helps developers assess
  alternative design strategies and decide which is
  the best for a particular project.
Validation
 Requirement
   Analysis

        System
        Design             Verify

               Program
                Design


                     Coding

                               Unit &
                            Integration
                              Testing
 Prototyping
                                      System
                                      Testing

                                            Acceptance
                                              Testing

                                                         Operation &
The Waterfall Model                                      Maintenance
- The V-Model (or VEE model) is a systems
  development model designed to simplify the
  understanding of the complexity associated with
  developing systems
- a variation of the waterfall model that demonstrate
  how the activities are related to analysis and
  design
- the focus of the V-Model is on activity and
  correctness
The V-Model
- It requires investigation to ensure that the
  developer, user and customer have a common
  understanding both of what is needed and what is
  proposed.
- it reduce risk and uncertainty in development
- The process of prototyping involves the following
                                                steps:
       1. Identify basic requirements
        2. Develop initial prototype
        3. Review
        4. Revise and enhancing prototype
The Prototyping Model.
- The system requirments are evaluated or
executed
  in a way that demonstrates the behavior of the
- system. requirements are specified, it can be
  Once the
  enacted using the software package, so that their
  implication can be assess before design begins.
The Operational Specification Model
- It tries to reduce the opportunity for error by
  eliminating several major development steps.
- It uses automated support
- Sample transformation can include: (1) changing
  the data representation; (2) selecting algorithms;
 (3) optimizing; (4) Compiling.
The Transformational Model
- Cycle time is the time the documents are written
  and the time for the system was delivered.
- To reduce the cycle time is to use development
  phase , where two systems functioning in parallel.
- The Operational or Production System being used
  by the customer or user
- The Development System is the next version that
  is being prepared to replace the current production
  system.
The Phased Development Model
- The system as specified in the requirements
  documents are partitioned into subsystems by
  functionality.
- The releases are defined by beginning with one
  small, functional subsystem and then adding with
  each new releases.
- It delivers the full system at the very beginning
  and it changes the functionality of each subsystem
  with each new releases.
03 module2-090710094221-phpapp02
- The spiral model is a software development
  process combining elements of both design and
  prototyping-in-stages, in an effort to combine
  advantages of top-down and bottom-up concepts
 - also known as the spiral life cycle model
 - it is a systems development method (SDM) used
in
- Information technology (IT) Prototyping Model
   a combination of features of
   and Waterfall Model defined by Barry Boehm (1988)
- The spiral model is intended for large, expensive
   and complicated projects
The Spiral Model.
- It depicts the process, showing the inputs are
  transformed to outputs.
- See… A Toolset for Supporting Static and
Dynamic
  Model Checking
- It can enact the process, so that the user can see
  how intermediate and final products are
  transformed over time.
- See… A Toolset for Supporting Static and
Dynamic
  Model Checking
- Model Driven Development
- User Experience
- Top-Down to Bottom Design
- Chaos Model
- Evolutionary Prototyping
- ICONIX Process
- Unified Process
- Extreme Programming (XP)

Contenu connexe

Tendances

Visual Studio 2010 ALM Tools Overview
Visual Studio 2010 ALM Tools Overview Visual Studio 2010 ALM Tools Overview
Visual Studio 2010 ALM Tools Overview Ayman El-Hattab
 
5 sins of all hands ppt
5 sins of all hands ppt5 sins of all hands ppt
5 sins of all hands pptSpike Gu
 
Maintainanceandsupport
MaintainanceandsupportMaintainanceandsupport
Maintainanceandsupportvasuvvs
 
Initializing new project
Initializing new projectInitializing new project
Initializing new projectLai Ha
 
01 software test engineering (manual testing)
01 software test engineering (manual testing)01 software test engineering (manual testing)
01 software test engineering (manual testing)Siddireddy Balu
 
What is Rational CLM?
What is Rational CLM?What is Rational CLM?
What is Rational CLM?IBM Danmark
 
software construction modules,language,tools,design
software construction modules,language,tools,designsoftware construction modules,language,tools,design
software construction modules,language,tools,designnemali akhilesh
 
Automated software testing
Automated software testingAutomated software testing
Automated software testingMD ISLAM
 

Tendances (18)

Visual Studio 2010 ALM Tools Overview
Visual Studio 2010 ALM Tools Overview Visual Studio 2010 ALM Tools Overview
Visual Studio 2010 ALM Tools Overview
 
5 sins of all hands ppt
5 sins of all hands ppt5 sins of all hands ppt
5 sins of all hands ppt
 
02 software process_models
02 software process_models02 software process_models
02 software process_models
 
Final boss
Final bossFinal boss
Final boss
 
Lect3 ch15-unit2
Lect3 ch15-unit2Lect3 ch15-unit2
Lect3 ch15-unit2
 
SDLC
SDLCSDLC
SDLC
 
Manual Software testing - software development life cycle
Manual Software testing - software development life cycleManual Software testing - software development life cycle
Manual Software testing - software development life cycle
 
Maintainanceandsupport
MaintainanceandsupportMaintainanceandsupport
Maintainanceandsupport
 
Initializing new project
Initializing new projectInitializing new project
Initializing new project
 
01 software test engineering (manual testing)
01 software test engineering (manual testing)01 software test engineering (manual testing)
01 software test engineering (manual testing)
 
What is Rational CLM?
What is Rational CLM?What is Rational CLM?
What is Rational CLM?
 
software construction modules,language,tools,design
software construction modules,language,tools,designsoftware construction modules,language,tools,design
software construction modules,language,tools,design
 
Automated software testing
Automated software testingAutomated software testing
Automated software testing
 
Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011
Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011
Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011
 
Vaidyanathan Ramalingam Rca In Testing Conference Speech
Vaidyanathan Ramalingam Rca In Testing Conference SpeechVaidyanathan Ramalingam Rca In Testing Conference Speech
Vaidyanathan Ramalingam Rca In Testing Conference Speech
 
Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech
Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference SpeechVaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech
Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech
 
Vaidyanathan Ramalingam Agile Conference Speech
Vaidyanathan Ramalingam Agile Conference SpeechVaidyanathan Ramalingam Agile Conference Speech
Vaidyanathan Ramalingam Agile Conference Speech
 
Vaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech
Vaidyanathan Ramalingam Trade Off Economics In Testing Conference SpeechVaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech
Vaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech
 

En vedette

Session 33 2 maria melkersson
Session 33 2 maria melkerssonSession 33 2 maria melkersson
Session 33 2 maria melkerssonMariaMelkersson
 
Audience institutions and reader profiles
Audience institutions and reader profilesAudience institutions and reader profiles
Audience institutions and reader profilesspearmain123
 
Holistic Product Development
Holistic Product DevelopmentHolistic Product Development
Holistic Product DevelopmentGary Pedretti
 
Teaching Students with Emojis, Emoticons, & Textspeak
Teaching Students with Emojis, Emoticons, & TextspeakTeaching Students with Emojis, Emoticons, & Textspeak
Teaching Students with Emojis, Emoticons, & TextspeakShelly Sanchez Terrell
 
Study: The Future of VR, AR and Self-Driving Cars
Study: The Future of VR, AR and Self-Driving CarsStudy: The Future of VR, AR and Self-Driving Cars
Study: The Future of VR, AR and Self-Driving CarsLinkedIn
 
Hype vs. Reality: The AI Explainer
Hype vs. Reality: The AI ExplainerHype vs. Reality: The AI Explainer
Hype vs. Reality: The AI ExplainerLuminary Labs
 

En vedette (6)

Session 33 2 maria melkersson
Session 33 2 maria melkerssonSession 33 2 maria melkersson
Session 33 2 maria melkersson
 
Audience institutions and reader profiles
Audience institutions and reader profilesAudience institutions and reader profiles
Audience institutions and reader profiles
 
Holistic Product Development
Holistic Product DevelopmentHolistic Product Development
Holistic Product Development
 
Teaching Students with Emojis, Emoticons, & Textspeak
Teaching Students with Emojis, Emoticons, & TextspeakTeaching Students with Emojis, Emoticons, & Textspeak
Teaching Students with Emojis, Emoticons, & Textspeak
 
Study: The Future of VR, AR and Self-Driving Cars
Study: The Future of VR, AR and Self-Driving CarsStudy: The Future of VR, AR and Self-Driving Cars
Study: The Future of VR, AR and Self-Driving Cars
 
Hype vs. Reality: The AI Explainer
Hype vs. Reality: The AI ExplainerHype vs. Reality: The AI Explainer
Hype vs. Reality: The AI Explainer
 

Similaire à 03 module2-090710094221-phpapp02

03 module2-090710094221-phpapp02
03 module2-090710094221-phpapp0203 module2-090710094221-phpapp02
03 module2-090710094221-phpapp02Asadullah Tareen
 
Soft Eng - Software Process
Soft  Eng - Software ProcessSoft  Eng - Software Process
Soft Eng - Software ProcessJomel Penalba
 
Software Process in Software Engineering SE3
Software Process in Software Engineering SE3Software Process in Software Engineering SE3
Software Process in Software Engineering SE3koolkampus
 
software Processes
software Processessoftware Processes
software ProcessesSeif Shaame
 
Process model rup
Process model rupProcess model rup
Process model rupAryan Ajmer
 
Materi Testing dan Implementasi System
Materi Testing dan Implementasi SystemMateri Testing dan Implementasi System
Materi Testing dan Implementasi Systemdevinta sari
 
Software development models
Software development modelsSoftware development models
Software development modelsAzlan Nawawi
 
Software engineering 25 models details
Software engineering 25 models detailsSoftware engineering 25 models details
Software engineering 25 models detailsSamiul Hossaini
 
System models of sdlc- v model
System models of sdlc- v modelSystem models of sdlc- v model
System models of sdlc- v modelMinal Kashyap
 
TESTING IMPLEMENTATION SYSTEM
TESTING IMPLEMENTATION SYSTEMTESTING IMPLEMENTATION SYSTEM
TESTING IMPLEMENTATION SYSTEMPutri nadya Fazri
 
Chapter-2 ppt for the MBA 4rh seme6y.pdf
Chapter-2 ppt for the MBA 4rh seme6y.pdfChapter-2 ppt for the MBA 4rh seme6y.pdf
Chapter-2 ppt for the MBA 4rh seme6y.pdfVikasRai405977
 
Testing throughout the software life cycle (software development models)
Testing throughout the software life cycle (software development models)Testing throughout the software life cycle (software development models)
Testing throughout the software life cycle (software development models)tyas setyo
 

Similaire à 03 module2-090710094221-phpapp02 (20)

03 Modeling Process and Life Cycle
03 Modeling Process and Life Cycle03 Modeling Process and Life Cycle
03 Modeling Process and Life Cycle
 
03 module2-090710094221-phpapp02
03 module2-090710094221-phpapp0203 module2-090710094221-phpapp02
03 module2-090710094221-phpapp02
 
Introduction & Manual Testing
Introduction & Manual TestingIntroduction & Manual Testing
Introduction & Manual Testing
 
Manualtestingppt
ManualtestingpptManualtestingppt
Manualtestingppt
 
Soft Eng - Software Process
Soft  Eng - Software ProcessSoft  Eng - Software Process
Soft Eng - Software Process
 
Ch4
Ch4Ch4
Ch4
 
Ch4
Ch4Ch4
Ch4
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process Models
 
Software Process in Software Engineering SE3
Software Process in Software Engineering SE3Software Process in Software Engineering SE3
Software Process in Software Engineering SE3
 
software Processes
software Processessoftware Processes
software Processes
 
Process model rup
Process model rupProcess model rup
Process model rup
 
Materi Testing dan Implementasi System
Materi Testing dan Implementasi SystemMateri Testing dan Implementasi System
Materi Testing dan Implementasi System
 
Testing Throughout the Software Life Cycle - Section 2
Testing Throughout the Software Life Cycle - Section 2Testing Throughout the Software Life Cycle - Section 2
Testing Throughout the Software Life Cycle - Section 2
 
Software development models
Software development modelsSoftware development models
Software development models
 
Software engineering 25 models details
Software engineering 25 models detailsSoftware engineering 25 models details
Software engineering 25 models details
 
System models of sdlc- v model
System models of sdlc- v modelSystem models of sdlc- v model
System models of sdlc- v model
 
TESTING IMPLEMENTATION SYSTEM
TESTING IMPLEMENTATION SYSTEMTESTING IMPLEMENTATION SYSTEM
TESTING IMPLEMENTATION SYSTEM
 
Chapter-2 ppt for the MBA 4rh seme6y.pdf
Chapter-2 ppt for the MBA 4rh seme6y.pdfChapter-2 ppt for the MBA 4rh seme6y.pdf
Chapter-2 ppt for the MBA 4rh seme6y.pdf
 
Testing throughout the software life cycle (software development models)
Testing throughout the software life cycle (software development models)Testing throughout the software life cycle (software development models)
Testing throughout the software life cycle (software development models)
 
2. Software process
2. Software process2. Software process
2. Software process
 

03 module2-090710094221-phpapp02

  • 1. In this Module, we look at • what we mean by a “process” • software development products, processes & resources • several models of the software development process • tools & techniques for process modeling Back Next
  • 2. - Process is a series of steps involving activities constraints and resources that produce an intended output of some kind. - in building a software product, process is refer to a life cycle - software development process is sometimes called - software life cycle than a procedure a process is more - a process may require design to occur before coding, many different design may be used
  • 3. - Process guides our actions by allowing use examine, control and improve that comprise the process. Characteristics of a Process - The process prescribes all of the major process activities. - The process uses resources, subject to a set of constraints (such schedule) and produces intermediate and final product. - The process may be composed that are linked in some way. The process may be defined as hierarchy of process, organized so that each sub- process has its own process models
  • 4. - Each process activity has entry and exit criteria, so that when the activity begins and ends. - The activities are organized in sequence, so that it is clear when one activity is performed relative to the other activities. - Every process has a guiding principles that explain the goals of each activity. - Constraints or controls may apply to an activity, resource or product.
  • 5. Reasons for Modeling Process - It forms common understanding of the activities, resources and constraints involved in software development. - It helps the development team find inconsistencies, redundancies and omissions in the - process and in its constituent parts. such as It reflects the goals of development building high-quality software, finding faults in early development and meeting required budget and schedule constraints.
  • 6. - It helps the development team understand where tailoring is to occur for the special situation.
  • 7. - The waterfall model is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of software developmet. - Winston W. Royce (1929–1995), present this model cited in his article published in 1970. - It is very useful in helping the developers lay out what they need to do. - The biggest problem with the waterfall model is does not reflect the way the code is really developed.
  • 8. In Royce's original waterfall model, the following phases are followed in order: 1.Requirements specification 2.Design 3.Construction (AKA implementation or coding) 4.Integration 5.Testing and debugging (AKA validation) 6.Installation 7.Maintenance
  • 9. Requirement Analysis System Design Program Design Coding Unit & Integration Testing System Testing Acceptance Testing Operation & The Waterfall Model Maintenance
  • 10. The software development process in reality.
  • 11. - The sashimi model (so called because it features overlapping phases, like the overlapping fish of Japanese sashimi) was originated by Peter DeGrace. - also referred as the waterfall model with overlapping phases or with feedback
  • 12. Instructor’s idea about the Sashimi Model Requirement Analysis ystem S DesignProgram Design Coding Unit & Integration Testing ystem S Testing Acceptance Testing Operation & Maintenance The Waterfall Model with overlapping phases / The Waterfall Model with feedback
  • 13. - Prototyping is a partially developed product that enables customers and developers to examine some aspect of the proposed system and decide if it is suitable or appropriate for the finished product. - Design prototyping helps developers assess alternative design strategies and decide which is the best for a particular project.
  • 14. Validation Requirement Analysis System Design Verify Program Design Coding Unit & Integration Testing Prototyping System Testing Acceptance Testing Operation & The Waterfall Model Maintenance
  • 15. - The V-Model (or VEE model) is a systems development model designed to simplify the understanding of the complexity associated with developing systems - a variation of the waterfall model that demonstrate how the activities are related to analysis and design - the focus of the V-Model is on activity and correctness
  • 17. - It requires investigation to ensure that the developer, user and customer have a common understanding both of what is needed and what is proposed. - it reduce risk and uncertainty in development - The process of prototyping involves the following steps: 1. Identify basic requirements 2. Develop initial prototype 3. Review 4. Revise and enhancing prototype
  • 19. - The system requirments are evaluated or executed in a way that demonstrates the behavior of the - system. requirements are specified, it can be Once the enacted using the software package, so that their implication can be assess before design begins.
  • 21. - It tries to reduce the opportunity for error by eliminating several major development steps. - It uses automated support - Sample transformation can include: (1) changing the data representation; (2) selecting algorithms; (3) optimizing; (4) Compiling.
  • 23. - Cycle time is the time the documents are written and the time for the system was delivered. - To reduce the cycle time is to use development phase , where two systems functioning in parallel. - The Operational or Production System being used by the customer or user - The Development System is the next version that is being prepared to replace the current production system.
  • 25. - The system as specified in the requirements documents are partitioned into subsystems by functionality. - The releases are defined by beginning with one small, functional subsystem and then adding with each new releases.
  • 26. - It delivers the full system at the very beginning and it changes the functionality of each subsystem with each new releases.
  • 28. - The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts - also known as the spiral life cycle model - it is a systems development method (SDM) used in - Information technology (IT) Prototyping Model a combination of features of and Waterfall Model defined by Barry Boehm (1988) - The spiral model is intended for large, expensive and complicated projects
  • 30. - It depicts the process, showing the inputs are transformed to outputs. - See… A Toolset for Supporting Static and Dynamic Model Checking
  • 31. - It can enact the process, so that the user can see how intermediate and final products are transformed over time. - See… A Toolset for Supporting Static and Dynamic Model Checking
  • 32. - Model Driven Development - User Experience - Top-Down to Bottom Design - Chaos Model - Evolutionary Prototyping - ICONIX Process - Unified Process - Extreme Programming (XP)