CSCI 150 Final

Waterfall

1st SDLC model

whole process of software development is divided into separate processes

Outcome of one phase acts as input for the next phase sequentially

Requirements

1st Phase of Waterfall

Concept, needs addressed, functionalities

Design

2nd Phase of Waterfall

Logical and physical design, inputs/outputs, dataflow, no changing after this phase

Implementation

3rd Phase of Waterfall

Build design into software, coding

Verfication

4th Phase of Waterfall

Testing software against requirements

Deployment

5th phase of Waterfall

Actual release into IT environment, goes to maintenance phase

understand implement

1st advantage of waterfall

Easy to ____ and _____

deliverables review process

2nd advantage of waterfall

Each phase has specific _____ and a _______

clearly defined

3rd advantage of waterfall

All the activities to be performed in each stage are ______

processed completed

4th advantage of waterfall

Phases are _____ and _____ one at a time

milestones tasks

5th advantage of waterfall

Well understood ______ and easy to arrange _____ and assign tasks

Process results

6th advantage of waterfall _____ and _____ are well documented

working software late

1st disadvantage of waterfall

No ____ is produced until _____ during the life cycle

risk uncertainty

2nd disadvantage of waterfall

High amounts of _____ and ______

complex object-oriented

3rd disadvantage of waterfall

Not a good model for _____ and _____ projects

long ongoing

4th disadvantage of waterfall

Poor model for ____ __and__ ____ projects

moderate to high risk

5th disadvantage of waterfall

Not suitable for the projects where requirements are at a ________ of changing.

difficult progress

6th disadvantage of waterfall

It is _____ to measure _____ within stages

changing requirements

7th disadvantage of waterfall

Cannot accommodate _______

scope end

8th disadvantage of waterfall

Adjusting _____ during the life cycle can _____ a project

"big bang" identifying

9th disadvantage of waterfall

Integration is done as a "_____” at the very end which does not allow for ______ any technological or business bottleneck or challenges early

not changing frequently

1st reason to use waterfall

Requirements are not ______

complicated big

2nd reason to use waterfall

Application is not ______ and _____

short

3rd reason to use waterfall

Project is _____

clear

4th reason to use waterfall

Requirement is _____

stable

5th reason to use waterfall

Environment is _____

dynamic stable

6th reason to use waterfall

Technology and tools used are not ____ and are _____

available trained

7th reason to use waterfall

Resources are _____ and _____

iterative model

Starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed

clearly easy

1st reason to use iterative model

When requirements are defined _____ and _____ to understand

large

2nd reason to use iterative model

When the software application is _____

requirement of changes

3rd reason to use iterative model

When there is a ________ in the future

Testing debugging

1st advantage of iterative model _____ and ______ during smaller iteration is easy

parallel

2nd advantage of iterative model

A _____ development can plan

acceptable ever-changing

3rd advantage of iterative model

It is easily ______ to ______ needs of the project

Risks during

4th advantage of iterative model

____ are identified and resolved ____ iteration

documentation designing

5th advantage of iterative model

Limited time spent on ______ and extra time on ______

smaller

1st disadvantage of iterative model

It is not suitable for ____ projects

More

2nd disadvantage of iterative model

____ resources may be required

changed imperfect

3rd disadvantage of iterative model

Design can be _____ again and again because of _____ requirements

over budget

4th disadvantage of iterative model

Requirement changes can cause ____

confirmed

5th disadvantage of iterative model

Project completion data not ______ because of changing requirements

Prototype

Simulation of the product created to test its UX/UI design concepts and functionality. Demonstrates the visual form of a final version of the product and implements select features. Used to identify users pain points and verify whether users have a positive experience navigating through a product or feature

Proof of Concept

Standalone project that validates a product idea. It is not a simplified version of the product with minimal features. Goal is to test the general assumptions inherent in the idea and verify that it can be executed from a technical point of view. Can take the form of a working part of the final product, developed with specific technology, to prove that the software can solve a particular business problem.

Is my idea technically feasible?

A POC answers the question

How will my product be used?

A prototype answers the question

tight show end-users

1st reason to use prototype

If you are on a _____ budget and need to ______ your product to the ______ or stakeholders

visualize know

2nd reason to use prototype

If you need to ______ your product and get to _____ how it would work

understand feel before

3rd reason to use prototype

If you want to ______ and _____ how your product works _____ developing it

technically feasible funding

1st reason to use POC

If you are not sure whether your idea is _____, need to prove technical feasibility, and need __________

explore technology

2nd reason to use POC

If you need to _____ the _____ used in your project

smoothly development

3rd reason to use POC

If you want to be sure that your project will run _____ before _____

investors seed-stage

When to choose either a POC or prototype

If you need to attract ____ or look for ____ funding at an early stage

Prove technical feasibility

Goal of POC

Days/weeks

Development time of POC

Researchers, developers

Audience of POC

Test technical aspects

Use case of POC

Reduces risks of technical problems

Risk evaluation of POC

Small budget

Investment of POC

Not for sale

Revenue of POC

Technical prototype or MVP development

Further use of POC

Demonstrate business concept

Goal of prototype

Weeks

Development time of prototype

Stakeholders, investors, focus groups

Audience of prototype

Fill gaps in a flow, pitch the product idea

Use case of prototype

Reduces risk of user dissatisfaction

Risk evaluation of prototype

Medium budget

Investment of prototype

Not for sale, generates further investment

Revenue of prototype

MVP development

Further use of prototype

Spiral

Combines elements of an iterative software development model with a waterfall method.

First step of spiral

Start with an idea

Phase when developers or entrepreneurs come up with new ideas so that they can create a new product or software. A team of skilled personals is also selected for executing this project effectively and efficiently

Second step of spiral

Feasibility study on the idea

Will help you in determining the cost of software development required to build it, the time is taken for developing it, and its functionality as well

Third step of spiral

Create a business plan based on feasibility study results

Should clearly define the target audience, market share, estimated cost of software development, etc.

4th step of spiral

Develop the initial prototype version for the product that will help you in proving the feasibility of your idea

5th step of spiral

Do User Acceptance Testing (UAT) on the prototype version

Should be performed by target users as well. If feedback from UAT is positive then the next step is identifying and resolving risks which we already discussed here

6th step of spiral

Once you are done with resolving risks then you can proceed to the final version of the software. This is the phase when you will work on adding more features as per your business plan or user requirements

7th step of spiral

Once this process is done then final testing should be performed and all defects if any should be fixed

8th step of spiral

Finally, the product will have to be deployed so that users can use it

9th step of spiral

User feedback on the final product should be collected and analyzed in order to identify any further enhancement required in the future. This is exactly where the spiral model comes into the picture, as you will go back to the first phase of this model whenever your customer wants to change something or add new features later on

10th step of spiral

The cycle can be closed when all user requirements are satisfied or the business model comes to an end

frequent

1st reason to use spiral model

When deliverance is required to be _____

large

2nd reason to use spiral model

When the project is _____

unclear complex

3rd reason to use spiral model

When requirements are ____ and ____

any time

4th reason to use spiral model

When requirements may change at ______

Large high

5th reason to use spiral method

____ and ___ budget projects

High risk

1st advantage of spiral model

____ amount of _____ analysis

large mission-critical

2nd advantage of spiral model

Useful for _____ and ______ projects

costly

1st disadvantage of spiral model

Can be _____ model to use

Risk expertise

2nd disadvantage of spiral model

_____ analysis needed highly particular ______

smaller

3rd disadvantage of spiral model

Doesn't work well for ______ projects

V-model

An extension of waterfall modelKnown as "Verification and Validation model"

Each phase of the development has its corresponding and testing activities performs together (planner parallel)

Next phase only occurs when the current phase is completed

well defined ambiguous

1st reason to use V-model

When the requirement is ______ and not _______

small medium fixed

2nd reason to use V-model

Used for _____ to _____ sized projects where requirements are clearly defined and ____

available technical

3rd reason to use V-model

When sample technical resources are _____ with essential _______ expertise

understand

1st advantage of V-model

Easy to ______

planning test

2nd advantage of V-model

Testing methods like _______ and _______ happen well before coding.

Saves higher

3rd advantage of V-model

_____ a lot of time, higher chance of _____

Avoid defects

4th advantage of V-model

____ the downward flow of _____

small easily

5th advantage of V-model

Works well for _____ plans where requirements are _____ understood

rigid least

1st disadvantage of V-model

Very _____ and ____ flexible