Delivers software to end users and more adjustments can be made. This involves giving people who will use it training. After the system is placed in it's final environment

Tests for defects against the products specification so bugs and defects are detected and removed. This includes unit, system and user acceptance testing.

Involves building the software, distribution installing the software, configuring the software and testing the software

This involves breaking down the system pieces to analyse the situation, project goals in an attempt to engage users so that the definite requirements can be defined

Turns specifications into a design plan. All stake holders review the plan and offer feedback and suggestions. The output of this stage will describe the new system as a collection of modules

Involves building the software, distribution installing the software, configuring the software and testing the software

This step involves determining the costs, benefits, resource requirements and user needs required for completion

This involves breaking down the system pieces to analyse the situation, project goals in an attempt to engage users so that the definite requirements can be defined

Turns specifications into a design plan. All stake holders review the plan and offer feedback and suggestions. The output of this stage will describe the new system as a collection of modules

Involves building the software, distribution installing the software, configuring the software and testing the software

This step involves determining the costs, benefits, resource requirements and user needs required for completion

Delivers software to end users and more adjustments can be made. This involves giving people who will use it training. After the system is placed in its final environment

Involves building the software, distribution installing the software, configuring the software and testing the software

Turns specifications into a design plan. All stake holders review the plan and offer feedback and suggestions. The output of this stage will describe the new system as a collection of modules

This step involves determining the costs, benefits, resource requirements and user needs required for completion

Tests for defects against the products specification so bugs and defects are detected and removed. This includes unit, system and user acceptance testing.

Turns specifications into a design plan. All stake holders review the plan and offer feedback and suggestions. The output of this stage will describe the new system as a collection of modules

This involves breaking down the system pieces to analyse the situation, project goals in an attempt to engage users so that the definite requirements can be defined

Delivers software to end users and more adjustments can be made. This involves giving people who will use it training. After the system is placed in its final environment

Involves building the software, distribution installing the software, configuring the software and testing the software

This involves breaking down the system pieces to analyse the situation, project goals in an attempt to engage users so that the definite requirements can be defined

Delivers software to end users and more adjustments can be made. This involves giving people who will use it training. After the system is placed in its final environment

The software is improved and can be updated to fit new requirements.

Involves building the software, distribution installing the software, configuring the software and testing the software

An iterative approach to software development. It compromises various approaches to software development under which requirements and solutions evolve through collaborative efforts.

An iterative and incremental software development process framework. Each iteration is like a small project and with each iteration, new features arrive

The breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one. It is less iterative and flexible, as progress flows in one direction

Adapted from the Toyota production system, it offers a solid conceptual framework, values and principles as well as good practice.

An iterative approach to software development. It compromises various approaches to software development under which requirements and solutions evolve through collaborative efforts.

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

Intends to improve software quality, life quality for development team, and responsiveness to changing customer requirements

The breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one. It is less iterative and flexible. As progress flows in one direction

The breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one. It is less iterative and flexible. As progress flows in one direction

A risk driven model that guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

Adapted from the Toyota production system, it offers a solid conceptual framework, values and principles as well as good practice.

A risk driven model that guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process

Intends to improve software quality, life quality for development team, and responsiveness to changing customer requirements

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

An iterative and incremental software development process framework. Each iteration is like a small project and with each iteration, new features arrive

A risk driven model that guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

The breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one. It is less iterative and flexible. As progress flows in one direction

Adapted from the Toyota production system, it offers a solid conceptual framework, values and principles as well as good practice.

The breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one. It is less iterative and flexible. As progress flows in one direction

Adapted from the Toyota production system, it offers a solid conceptual framework, values and principles as well as good practice.

An iterative and incremental software development process framework. Each iteration is like a small project and with each iteration, new features arrive

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

A risk driven model that guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

Intends to improve software quality, life quality for development team, and responsiveness to changing customer requirements

An extension of waterfall and is based on each association of a testing phase for each corresponding development stage. The next phase starts when the previous one ends

A method for managing the creation of products with an emphasis on continual delivery while not overburdening the development team. It is defined to help teams work together more efficiently

A risk driven model that guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process

A good model for projects with no end date and unsure requirements. All resources go on the software development and code. it's used on small projects with small teams

An extension of waterfall and is based on each association of a testing phase for each corresponding development stage. The next phase starts when the previous one ends

Easy to manage

Client is involved in every stage

Fast delivery

Very flexible

Not ideal for small projects

It is a complicated model

Very difficult to move back to previous stage

unclear requirements makes it ineffective

Focused on client processed- client is involved in every stage

Very flexible due to iteration

implementation cost is cheap

Ideal for small projects

Very difficult to make back to previous stage

Can be excessive preparation and planning

Lack of test automation

Not ideal for large projects

predictable

Very easy to understand

Used a lot

Adaptable to changing requirements

Complicated to understand

Documentation isn't used

The development process is complex and disorganised

Doesn't adjust to changing requirements

Eliminates unnecessary activity

Doesn't require documentation

Team can be of any skill level

Streamlined approach allows more functionality to be delivered in less time

Development team has no power to make decisions

Needs skilled team

Can be very slow

Depends on strong documentation

Great for complex projects

Easy to manage

Cheap

Little resources required

Not good for complex or OOP projects

Can be expensive

Needs lots of planning

Difficult to manage

Encourages Teamwork

Small investment time

Uses continuous testing

Good with documentation

Slow

Code is more of a focus than design

Expensive

Lack of documentation

Can be done with any size of project

Additional functionality or changes can be done at a later stage

Good for complex customer requirements

Process is very simple

Needs to be followed strictly

Not good with customer feedback

development is very slow

Risk of not meeting budget or schedule

Simple and easy to understand

Software is produced early in the lifecycle

Good for changing requirements

Highly-disciplined model

Very hard to manage

Poor model for short projects

Difficult to add or change functionality once project has reached testing

No working software produced until very late into the life cycle

Easy to manage due to rigidity of the model

Good for long projects

Has timeframes associated with each phase

Accurately models how work is done

Doesn't show how work is done

If Kanban board becomes outdated, it can become over complicated

Poor model for short projects

Poor model for long projects

The team is expected to capture the system requirements. They should also know the risk factors and should establish and validate the system architecture. The design is also created.

The system is deployed to the target users. Feedback is also received and can result in refinement over several transition periods. This phase also incorporates user training and system conversions

Develops an approximate vision of the system, makes a business case and produces a rough estimate for the cost and schedule

The system is built on the foundations laid in the elaboration phase. User cases are created and each one signifies a new iteration. Each iteration results in a release of the software

The system is built on the foundations laid in the elaboration phase. User cases are created and each one signifies a new iteration. Each iteration results in a release of the software

The team is expected to capture the system requirements. They should also know the risk factors and should establish and validate the system architecture. The design is also created.

Develops an approximate vision of the system, makes a business case and produces a rough estimate for the cost and schedule

The system is deployed to the target users. Feedback is also received and can result in refinement over several transition periods. This phase also incorporates user training and system conversions

The team is expected to capture the system requirements. They should also know the risk factors and should establish and validate the system architecture. The design is also created.

Develops an approximate vision of the system, makes a business case and produces a rough estimate for the cost and schedule

The system is deployed to the target users. Feedback is also received and can result in refinement over several transition periods. This phase also incorporates user training and system conversions

The system is built on the foundations laid in the elaboration phase. User cases are created and each one signifies a new iteration. Each iteration results in a release of the software

The system is deployed to the target users. Feedback is also received and can result in refinement over several transition periods. This phase also incorporates user training and system conversions

The system is built on the foundations laid in the elaboration phase. User cases are created and each one signifies a new iteration. Each iteration results in a release of the software

Develops an approximate vision of the system, makes a business case and produces a rough estimate for the cost and schedule

The team is expected to capture the system requirements. They should also know the risk factors and should establish and validate the system architecture. The design is also created.

This helps see which part of the system needs to be tested

This helps to see the positives and negatives of the old system

This helps identify requirements that haven't been met

This helps identify future updates for the system

Is set over one day and is started whenever

Basic unit of work

Is an ordered list of what needs to be done

Can be various lengths and is started when the old sprint ends

Daily start-ups

Reviews with the stakeholders

Writes up backlog

Sprint planning and reviews

An ordered list of requirements

Customer reviews of the software

Special product backlog systems that don't just describe a feature, they say how a feature behaves and what is happening for the user

Ordered list of all the items a team should work on with the highest priority item on the top of the list.

Ordered lists of all the items a team may work on with the highest priority item on the top. The product owner should maintain the backlog.

Special product backlog systems that don't just describe a feature, they say how a feature behaves and what is happening for the user.

The basic unit of work that can be any length

All the versions the software has had

Eliminate waste, Amplifying learrning, Decide as late as possible, Deliver as slow as possible, Empower the team, build integrity in, optimise the whole

Eliminate waste, Amplifying learrning, Decide as early as possible, Deliver as slow as possible, Empower the team, build integrity in, optimise the whole

Eliminate waste, Amplifying learrning, Decide as early as possible, Deliver as fast as possible, Empower the team, build integrity in, optimise the whole

Eliminate waste, Amplifying learrning, Decide as late as possible, Deliver as fast as possible, Empower the team, build integrity in, optimise the whole

Respect, Cunning, Feedback, Communication, Simplicity

Respect, Courage, Feedback, Communication

Respect, Courage, Feedback, Communication, Simplicity

Respect, Courage, Feedback, Communication, Simplicity, Cunning

Evaluation of the software by the customer. Also includes identifying and monitoring risks such as schedule slippage and cost overrun

Includes testing, coding and deploying the software at the customer site

Identification of potential risks are done while risk mitigation strategy is planned and finished

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Evaluation of the software by the customer. Also includes identifying and monitoring risks such as schedule slippage and cost overrun

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Identification of potential risks are done while risk mitigation strategy is planned and finished

Includes testing, coding and deploying the software at the customer site

Includes testing, coding and deploying the software at the customer site

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Evaluation of the software by the customer. Also includes identifying and monitoring risks such as schedule slippage and cost overrun

Identification of potential risks are done while risk mitigation strategy is planned and finished

Includes testing, coding and deploying the software at the customer site

Identification of potential risks are done while risk mitigation strategy is planned and finished

Evaluation of the software by the customer. Also includes identifying and monitoring risks such as schedule slippage and cost overrun

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Coding the modules, code reviews and code optimisation happens. At the end the code is put in the repository

The testing phase. This includes user testing, integration testing, system testing and acceptance testing

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Includes the requirements analysis, and the design. System design, architectural design and module design all fall under this stage

The testing phase. This includes user testing, integration testing, system testing and acceptance testing

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

Coding the modules, code reviews and code optimisation happens. At the end the code is put in the repository

Includes the requirements analysis, and the design. System design, architectural design and module design all fall under this stage

Includes the requirements analysis, and the design. System design, architectural design and module design all fall under this stage

Estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customer

The testing phase. This includes user testing, integration testing, system testing and acceptance testing

Coding the modules, code reviews and code optimisation happens. At the end the code is put in the repository

Transparency, Balance, Collaboration, Customer focus, Flow, Leadership, Understanding, Agreement, Respect

Transparency, Balance, Collaboration, Customer focus, Flow, Leadership, Feedback, Agreement, Respect

Respect, Courage, Feedback, Communication, Simplicity

Eliminating waste, Amplifying learning, Decide as late as possible, Deliver as fast as possible, Empower the team, Build integrity in, Optimise the whole

Responsible for improving interactions in order to maximise productivity, arranges and facilitates start-ups, clears obstacles and protects the team from distractions

The voice of the customer, determines what the team works on based on priority, stake holders communicate with the product owner

Responsible for realising the stories identified by the customer.

Commits to finishing sprints and are flexible in what they can contribute Sprint goals are the most important and all team members should be able to perform the task

The voice of the customer, determines what the team works on based on priority, stake holders communicate with the product owner

Commits to finishing sprints and are flexible in what they can contribute Sprint goals are the most important and all team members should be able to perform the task

Responsible for realising the stories identified by the customer.

Responsible for improving interactions in order to maximise productivity, arranges and facilitates start-ups, clears obstacles and protects the team from distractions

Responsible for realising the stories identified by the customer.

The voice of the customer, determines what the team works on based on priority, stake holders communicate with the product owner

Responsible for improving interactions in order to maximise productivity, arranges and facilitates start-ups, clears obstacles and protects the team from distractions

Commits to finishing sprints and are flexible in what they can contribute Sprint goals are the most important and all team members should be able to perform the task

Responsible for improving interactions in order to maximise productivity, arranges and facilitates start-ups, clears obstacles and protects the team from distractions

Responsible for realising the stories identified by the customer.

Help the team by trying to avoid making previously made mistakes

This keeps track of relevant metrics and also identifies areas for improvements

Help the team by trying to avoid making previously made mistakes

Responsible for realising the stories identified by the customer.

This keeps track of relevant metrics and also identifies areas for improvements

Commits to finishing sprints and are flexible in what they can contribute Sprint goals are the most important and all team members should be able to perform the task

This keeps track of relevant metrics and also identifies areas for improvements

Help the team by trying to avoid making previously made mistakes

The voice of the customer, determines what the team works on based on priority, stake holders communicate with the product owner

Responsible for realising the stories identified by the customer.

They monitor the project from a business standpoint and let the higher ups know about progress

Define and refine features often in conjunction with a technical lead. They also organise the requirements

Will use the system in their work. They will define requirements, review specifications, work with the developers to introduce the system, conduct acceptance tests

Leads and motivates the team. They track the development progress and are the link between the development team and the customer

Leads and motivates the team. They track the development progress and are the link between the development team and the customer

They monitor the project from a business standpoint and let the higher ups know about progress

Will use the system in their work. They will define requirements, review specifications, work with the developers to introduce the system, conduct acceptance tests

Define and refine features often in conjunction with a technical lead. They also organise the requirements

They monitor the project from a business standpoint and let the higher ups know about progress

The person who will use the system in their work. They will define requirements, review specifications, work with the developers to introduce the system, conduct acceptance tests

Leads and motivates the team. They also track the development progress and are the link between the development team and the customer

Define and refine features often in conjunction with a technical lead. They also organise the requirements

The person who will use the system in their work. They will define requirements, review specifications, work with the developers to introduce the system, conduct acceptance tests

Leads and motivates the team. They also track the development progress and are the link between the development team and the customer

Define and refine features often in conjunction with a technical lead. They also organise the requirements

They monitor the project from a business standpoint and let the higher ups know about progress

Analyses and plans the flow of data in a system and also looks at existing solutions. They write the technical requirements of the system and talk to the designers about ideas

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Creates code and does the initial testing. They work closely with the analysts and the designers

Responsible for creating test plans doing black/white box testing and documenting test results that inform developers of bugs to fix

Creates code and does the initial testing. They work closely with the analysts and the designers

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Analyses and plans the flow of data in a system and also looks at existing solutions. They write the technical requirements of the system and talk to the designers about ideas

Responsible for creating test plans doing black/white box testing and documenting test results that inform developers of bugs to fix

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Analyses and plans the flow of data in a system and also looks at existing solutions. They write the technical requirements of the system and talk to the designers about ideas

Creates code and does the initial testing. They work closely with the analysts and the designers

Responsible for creating test plans doing black/white box testing and documenting test results that inform developers of bugs to fix

Analyses and plans the flow of data in a system and also looks at existing solutions. They write the technical requirements of the system and talk to the designers about ideas

Responsible for creating test plans doing black/white box testing and documenting test results that inform developers of bugs to fix

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Creates code and does the initial testing. They work closely with the analysts and the designers

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Defines the structure of a program of system. They can act as Project Manager, overseeing IT assignments that are aimed at improving the business and ensuring all parts of the project runs

Analyses and plans the flow of data in a system and also looks at existing solutions. They write the technical requirements of the system and talk to the designers about ideas

Has knowledge in a domain other than software development. They are often asked to review, improve and approve technical work

Creates code and does the initial testing. They work closely with the analysts and the designers

Designs solutions to solve business problems based upon the requirements specification provided. This includes software design, database design and the UI design

Defines the structure of a program of system. They can act as Project Manager, overseeing IT assignments that are aimed at improving the business and ensuring all parts of the project runs

Has knowledge in a domain other than software development. They are often asked to review, improve and approve technical work

The tester can see the code. They are aware of what the code should do and how it is done

The tester cannot see the code. They are aware of what the code should do but not how it is done

Tests coexistence and communication between modules

Tests individual modules for bugs

Checks the systems functionality and communication with other systems

Tests in the user environment where it can uncover compatibility issues and check non-functioning requirements

Tests in the user environment where it can uncover compatibility issues and check non-functioning requirements

Checks the systems functionality and communication with other systems

Tests individual modules for bugs

Tests coexistence and communication between modules

Tests individual modules for bugs

Checks the systems functionality and communication with other systems

Tests coexistence and communication between modules

Tests in the user environment where it can uncover compatibility issues and check non-functioning requirements

Tests individual modules for bugs

Tests coexistence and communication between modules

Tests in the user environment where it can uncover compatibility issues and check non-functioning requirements

Checks the systems functionality and communication with other systems

Implementation / Deployment

Requirements Analysis.

Testing

Feasibility Study

To provide a suitable framework for planning a software development project

To provide a set of steps to create a software end-product

To create a methodology for developing software code

To provide a consistent set of coding standards

b, d, a, c.

b, d, c, a

d, b, a, c

d, b, c, a

Waterfall

UP / RUP

Scrum

Spiral

Agile.

Unified Process (UP).

V-Model

Waterfall

To provide insight into business products and processes.

To specify functional requirements on behalf of the customer.

To identify non-functional requirements

To assess project risks and constraints

Feasibility study, code development

Requirements analysis, maintenance.

Design, testing.

Initiation, implementation / deployment

Software specification

Software code.

Use cases.

Test plans.

To assist in tracking project management issues

To ensure that deliverables are delivered in priority sequence

To determine which deliverables might be affected by a change request.

To identify requirements which have not been met

Analysis

Design.

Implementation (Deployment)

Code Development

The development project consists of a large distributed team

The customer has very few formally documented requirements

There are strict safety critical requirements.

The customer has a range of complicated contractual commitments that are linked to the planned development.

Prioritising items on the backlog.

Accepting stories as done.

Managing the execution stage of the project

Representing the customer to the Agile team

Help the development team to achieve their goals.

Remove impediments from the team

Shield the team from interruptions during the sprint

Lead the development team

Identify and fix bugs before software is implemented (deployed) so that they do not cause operational failures.

Adapt and modify the software as users’ needs change through time after implementation (deployment).

Complete any testing that could not be finished before implementation (deployment).

Fix bugs identified during live operation of the software.

The SDLC should be used only with sequential development methodologies

The SDLC contains detailed instructions that should be followed to develop any IT system.

The SDLC can be used to solve any business problem.

The SDLC is independent of the software development methodology used.

All seven stages of SDLC are performed for each iteration, with verification and validation performed in the final stage

Each of the seven stages are performed iteratively before moving onto the next stage with verification and validation performed in the testing stage.

The first three stages are performed once then verified and validated. The following four stages are iterative.

Each stage of the SDLC has a corresponding verification and validation stage.

Lean.

Unified Process (UP).

Scrum

XP

An audit trail of the reasons for change.

Traceability of the source of changes.

Keeping track of the details of the change

Providing information for stakeholders.

Software development teams must adopt a project structure in order to ensure that software is delivered to time, quality and cost.

Software development teams using waterfall methods of development should adopt a functional structure reporting to a software development manager.

Software development teams using agile methods should adopt a matrix structure that allows for complete flexibility of roles across the team

Software development teams should adopt a structure that is appropriate for their organisation, irrespective of whether project working is used.

The project planners

The software designers

The project manager

The software code development manager