Traditional software development flow

When using a traditional software development process (waterfall or other common methodology), ALM Octane can help you plan and manage your development process.

The traditional development process typically follows a structure like this:

We recognize that not all traditional (non-Agile) software development models follow such a linear progression, but they all keep the generally rigid separation between development phases.

In traditional software development, you follow a number of steps:

  1. Requirements phase: The requirements for the product or release are clearly deliniated. This may or may not include specific features within a product, but just a list of what the product needs to do.

  2. Design phase: The requirements are turned into a functional product design. In addition, you define how these features are to be built inside the product.

  3. Implementation: Using the planned design, the product is developed.

  4. Testing/verification: The planned features are sent, in their entirety, to the quality assurance team for testing. Defects are opened for those problems encountered in testing.

  5. Release/maintenance: The finished and approved features or product is released, and maintained for its entire lifecycle.

ALM Octane helps you manage your development processes through each of these development stages:

Select an image to learn more.

Requirements

In traditional, software development, you define the requirements before beginning any work. This enables you to know exactly what your product needs to do for customers.

Furthermore, you need to know your exact timeline and manpower before beginning work on the requirements so you get an estimate if the plan is reasonable.

ALM Octane enables you to do this planning before beginning work on the release.

Back to top

Design

Once you have planned what the application should contain, when you should release product versions, and who is working on these releases, you can begin designing the application's development. This involves creating a backlog of work items and assigning these work items for development.

Back to top

Implementation

Once you have defined the requirements for your application and designed what, when, and who will implement these requirements, you are ready to work on developing the application.

Back to top

Testing/Verification

After you have developed the features in your application, you pass them off to a quality assurance team for verification and testing.

ALM Octane has a number of ways to help you with testing:

Back to top

Release/Maintenance

After you have completed the specified requirements according to the design, and had the developed application verified and tested, you release your application to customers.

After the release, it is common to continue maintenance of released versions (in addition to developing new features in other releases). To assist with maintenance, ALM Octane enables you to:

  • Run tests against any version of your application you want

  • Create a pipeline for previous versions which enable you to build and test additional fixes made for that version. For details on pipelines, see Pipelines: Integrate with your CI server

  • Create dashboard widgets for past releases of the product to see quality of that release.

Back to top