What is Waterfall model The first Process Model

What is Waterfall model? The first Process Model to be introduced Diagram of Waterfall-model

Advantages of the Waterfall model Framework Type: Linear (linear-sequential life cycle model) Advantages: v Simple and easy to understand use v Easy to manage – each phase has specific deliverables and a review process to determine ü if the project is on the right path ü whether or not to continue or discard the project v Each phase must be completed fully before the next phase can begin v Phases do not overlap v Used for small projects with no uncertain requirements

Disadvantages of the Waterfall model Disadvantages: v Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage v No working software is produced until late during the life cycle v High amounts of risk and uncertainty v Not a good model for complex and object-oriented projects v Poor model for long and ongoing projects v Not suitable for the projects where requirements are at a moderate to high risk of changing

When to use the waterfall model v Waterfall model is used only when the requirements are very well known, clear and fixed v There are no ambiguous requirements v Product definition is stable v Technology is understood v Ample resources with required expertise are available freely v The project is short

Summary on waterfall model v Very less customer enter action is involved during the development of the product. v Once the product is ready then only it can be demoed to the end users. v Once the product is developed and if any failure occurs then the cost of fixing such issues are very high, because we need to update everywhere from document till the logic.

What is V-model (Verification and Validation model)? Diagram of V-model

What is V-model? Framework Type: Linear (linear-sequential life cycle model) Description: v Each phase must be completed before the next phase begins v But …. Testing of the product is planned in parallel with a corresponding phase of developments

What is V-model? The various phases of the V-model are as follows: v Business requirement specification (BRS) and System requirement specification (SRS) begin the life cycle model just like the waterfall model ü But, before development is started, a System test plan is created. ü The test plan focuses on meeting the functionality specified in the requirements gathering

What is V-model? The various phases of the V-model are as follows: v The high-level design (HLD) phase focuses on system architecture and design ü It provides overview of Ø solution Ø platform Ø system Ø product Ø service/process ü An integration test plan is created in order to test the pieces of the software systems ability to work together

What is V-model? The various phases of the V-model are as follows: v The low-level design (LLD) phase is where the actual software components are designed ü It defines the actual logic for each and every component of the system ü Class diagram with all the methods and relation between classes comes under LLD ü Component tests are created in this phase

What is V-model? The various phases of the V-model are as follows: v The implementation phase is where all coding takes place ü Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use v Coding. This is at the bottom of the V-Shape model. ü Module design is converted into code by developers

Advantages of the V-model Advantages: v Simple and easy to use v Testing activities like planning, test designing happens well before coding ü This saves a lot of time. Hence higher chance of success over the waterfall model v Proactive defect tracking – that is defects are found at early stage v Avoids the downward flow of the defects v Works well for small projects where requirements are easily understood

Disadvantages of the V-model Disadvantages: v Very rigid and least flexible v Software is developed during the implementation phase, so no early prototypes of the software produced v If any changes happen in midway, then the test documents along with requirement documents has to be updated

When to use the V-model v The V-shaped model should be used for small to medium sized projects where requirements are clearly defined and fixed v The V-Shaped model should be chosen when ample technical resources are available with needed technical expertise

Summary on V-model v High confidence of customer is required for choosing the VShaped model approach. v Since, no prototypes are produced, there is a very high risk involved in meeting customer expectations.

What is Incremental model? • The whole requirement is divided into various builds • Multiple development cycles take place here (“multi-waterfall” cycle) Ø Cycles are divided up into smaller, more easily managed modules Ø Each module passes through the ü Requirements ü Design ü Implementation ü Testing phases

What is Incremental model? • A working version of software is produced during the first module • Each subsequent release of the module adds function to the previous release • The process continues till the complete system is achieved

What is Incremental model? Diagram of Incremental -model

What is Incremental model? For example: When we work incrementally we are adding piece by piece but expect that each piece is fully finished Thus keep on adding the pieces until it’s complete From http: //istqbexamcertification. com/what-is-incremental-model-advantages-disadvantages-and-when-to-use-it/

Advantages of the Incremental model Advantages: v Generates working software quickly and early during the software life cycle v This model is more flexible – less costly to change scope and requirements v It is easier to test and debug during a smaller iteration v In this model customer can respond to each built v Lowers initial delivery cost v Easier to manage risk

Disadvantages of the Incremental model Disadvantages: v. Needs good planning and design v. Needs a clear and complete definition of the whole system before it can be broken down and built incrementally v. Total cost is higher than waterfall

When to use the Incremental model v This model can be used when the requirements of the complete system are clearly defined and understood v Major requirements must be defined; however, some details can evolve with time. v There is a need to get a product to the market early v A new technology is being used v Resources with needed skill set are not available v There are some high risk features and goals

What is Iterative model? • An iterative life cycle model does not attempt to start with a full specification of requirements • Instead, development begins by specifying and implementing just part of the software, which can then be reviewed in order to identify further requirements • This process is then repeated, producing a new version of the software for each cycle of the model

What is Iterative model? Diagram of Iterative -model

What is Iterative model? For example: When we work iteratively we create rough product or product piece in one iteration then review it and improve it in next iteration and so on until it’s finished • In the first iteration the whole painting is sketched roughly • Then in the second iteration colors are filled • In the third iteration finishing is done The whole product is developed step by step From http: //istqbexamcertification. com/what-is-iterative-model-advantages-disadvantages-and-when-to-use-it/

Advantages of the Iterative model Advantages: v In iterative model we ü create a high-level design of the application before we actually begin to build the product ü define the design solution for the entire product ü Later on we can design and built a skeleton version of that ü Then evolve the design based on what had been built v In iterative model we are building and improving the product step by step. Hence we can track the defects at early stages. This avoids the downward flow of the defects.

Advantages of the Iterative model Advantages: v In iterative model we can get the reliable user feedback. When presenting sketches and blueprints of the product to users for their feedback, we are effectively asking them to imagine how the product will work. v In iterative model less time is spent on documenting and more time is given for designing.

Disadvantages of the Iterative model Disadvantages: v Each phase of an iteration is rigid with no overlaps v Costly system architecture or design issues may arise because not all requirements are gathered up front for the entire lifecycle

When to use the Iterative model v. Requirements of the complete system are clearly defined and understood. v. When the project is big. v. Major requirements must be defined; however, some details can evolve with time.

What is Spiral model? • The spiral model is similar to the incremental model, with more emphasis placed on risk analysis. • The spiral model has four phases: ü Planning ü Risk Analysis ü Engineering ü Evaluation phases

What is Spiral model? • A software project repeatedly passes through these phases in iterations (called Spirals in this model) • The baseline spiral Ø starting in the planning phase Ø requirements are gathered Ø risk is assessed • Each subsequent spirals builds on the baseline spiral

Diagram of Spiral model

Phases of a Spiral model • Planning Phase: Ø Requirements are gathered ü BRS - Bussiness Requirement Specifications ü SRS - System Requirement specifications

Phases of a Spiral model • Risk Analysis: Ø A process is undertaken to identify risk and alternate solutions Ø A prototype is produced at the end of the risk analysis phase Ø If any risk is found during the risk analysis then alternate solutions are suggested and implemented

Phases of a Spiral model • Engineering: Ø In this phase software is developed Ø Testing is done • Evaluation: Ø Allows the customer to evaluate the output of the project to date before the project continues to the next spiral

Advantages of the Spiral model Advantages: v High amount of risk analysis Ø hence, avoidance of Risk is enhanced. v Good for large and mission-critical projects v Strong approval and documentation control v Additional functionality can be added at a later date v Software is produced early in the software life cycle

Disadvantages of the Spiral model Disadvantages: v Can be a costly model to use v Risk analysis requires highly specific expertise v Project’s success is highly dependent on the risk analysis phase v Doesn’t work well for smaller projects

When to use the Spiral model v When costs and risk evaluation is important v For medium to high-risk projects v Users are unsure of their needs v Requirements are complex v New product line v Significant changes are expected (research and exploration)

What is Prototype model? • The basic idea instead of freezing the requirements before a design or coding can proceed a throwaway prototype is built to understand the requirements • This prototype is developed based on the currently known requirements

What is Prototype model? • By using this prototype Ø the client can get an “actual feel” of the system Ø interactions with prototype can enable the client to better understand the requirements of the desired system

What is Prototype model? • Prototyping is an attractive idea for Ø complicated and large systems ü for which there is no manual process or existing system to help determining the requirements • The prototype are usually Ø not complete systems Ø many of the details are not built in the prototype • The goal is to provide a system with overall functionality

Diagram of Prototype model

Advantages of the Prototype model v Users are actively involved in the development v Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed v Errors can be detected much earlier v Quicker user feedback is available leading to better solutions v Missing functionality can be identified easily v Confusing or difficult functions can be identified v Quick implementation of incomplete, but functional application

Disadvantages of the Prototype model Disadvantages: v Leads to implementing and then repairing way of building systems v Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans v Incomplete application may cause application not to be used as the full system was designed v Incomplete or inadequate problem analysis

When to use the Prototype model v When the desired system needs to have a lot of interaction with the end users v Online systems, web interfaces have a very high amount of interaction with end users - are best suited for Prototype model. v Prototyping ensures that the end users constantly work with the system and provide a feedback which is incorporated in the prototype to result in a useable system. They are excellent for designing good human computer interface systems.

What is Rapid Application Development model? • It is a type of incremental model. • In RAD model the components or functions are developed in parallel as if they were mini projects. • The developments are Ø time boxed Ø delivered Ø assembled into a working prototype • The customer provides feedback regarding the delivery and requirements

Diagram of RAD model

Phases of a RAD model • Business modeling phase Ø The information flow is identified between various business functions

Phases of a RAD model • Data modeling phase Ø Information gathered from business modeling is used to define data objects that are needed for the business

Phases of a RAD model • Process modeling phase Ø Data objects defined in data modeling are converted to achieve the business information flow to achieve some specific business objective. Description are identified and created for CRUD of data objects

Phases of a RAD model • Application generation phase Ø Automated tools are used to convert process models into code and the actual system

Phases of a RAD model • Testing and turnover phase Ø Test new components and all the interfaces

Advantages of the RAD model Advantages: v Reduced development time. v Increases reusability of components v Quick initial reviews occur v Encourages customer feedback v Integration from very beginning solves a lot of integration issues.

Disadvantages of the RAD model Disadvantages: v Depends on strong team and individual performances for identifying business requirements. v Only system that can be modularized can be built using RAD v Requires highly skilled developers/designers. v High dependency on modeling skills v Inapplicable to cheaper projects as cost of modeling and automated code generation is very high

When to use the RAD model v RAD should be used when there is a need to create a system that can be modularized in 2 -3 months of time. v It should be used if there’s high availability of designers for modeling and the budget is high enough to afford their cost along with the cost of automated code generating tools. v RAD SDLC model should be chosen only if resources with high business knowledge are available and there is a need to produce the system in a short span of time (2 -3 months).

What is Agile model? • Software is developed in incremental, rapid cycles • This results in small incremental releases with each release building on previous functionality • Each release is thoroughly tested to ensure software quality is maintained. • It is used for time critical applications. • Extreme Programming (XP) is currently one of the most well known agile development life cycle model

Diagram of Agile model

Advantages of the Agile model v Customer satisfaction by rapid, continuous delivery of useful software. v People and interactions are emphasized rather than process and tools. Customers, developers and testers constantly interact with each other. v Working software is delivered frequently (weeks rather than months). v Face-to-face conversation is the best form of communication.

Advantages of the Agile model v Close, daily cooperation between business people and developers. v Continuous attention to technical excellence and good design. v Regular adaptation to changing circumstances. v Even late changes in requirements are welcomed

Disadvantages of the Agile model Disadvantages: v In case of some software deliverables, especially the large ones, it is difficult to assess the effort required at the beginning of the software development life cycle. v There is lack of emphasis on necessary designing and documentation.

Disadvantages of the Agile model Disadvantages: v The project can easily get taken off track if the customer representative is not clear what final outcome that they want. v Only senior programmers are capable of taking the kind of decisions required during the development process. Hence it has no place for newbie programmers, unless combined with experienced resources.

When to use the Agile model v When new changes are needed to be implemented. The freedom agile gives to change is very important. New changes can be implemented at very little cost because of the frequency of new increments that are produced v To implement a new feature the developers need to lose only the work of a few days, or even only hours, to roll back and implement it

When to use the Agile model v Unlike the waterfall model in agile model very limited planning is required to get started with the project. Agile assumes that the end users’ needs are ever changing in a dynamic business and IT world. Changes can be discussed and features can be newly effected or removed based on feedback. This effectively gives the customer the finished system they want or need

When to use the Agile model v Both system developers and stakeholders alike, find they also get more freedom of time and options than if the software was developed in a more rigid sequential way. Having options gives them the ability to leave important decisions until more or better data or even entire hosting programs are available; meaning the project can continue to move forward without fear of reaching a sudden standstill