Scribd
Upload
101 views6 pages

When Developing Any Type of Software Applications in A Business Environment, Typically There Will Be 5 Different Stages

The document discusses the typical 5 stages in the lifecycle management of software applications developed for business environments: 1) Planning, 2) Design, 3) Development, 4) Testing, and 5) Maintenance. Each stage is described briefly, with planning involving defining requirements, design determining inputs/outputs, development beginning coding, testing ensuring functionality, and maintenance updating the application over time.

Uploaded by

abdul shahid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
101 views6 pages

When Developing Any Type of Software Applications in A Business Environment, Typically There Will Be 5 Different Stages

The document discusses the typical 5 stages in the lifecycle management of software applications developed for business environments: 1) Planning, 2) Design, 3) Development, 4) Testing, and 5) Maintenance. Each stage is described briefly, with planning involving defining requirements, design determining inputs/outputs, development beginning coding, testing ensuring functionality, and maintenance updating the application over time.

Uploaded by

abdul shahid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Lifecycle Management

When developing any type of Plan


software applications in a business
environment, typically there will be 5
different stages.
Maintain Design

Test Develop
Lifecycle Management

Planning Plan

• What is the purpose of the script?


• What problem is it supposed to
solve? Maintain Design
• What language is the best to use?
• How long do we have to make it?

Test Develop
Lifecycle Management

Design Plan
• What input does the script need?
• What data does the script need to
access?
• How should it interact with other Maintain Design
systems or processes?
• What is the logical flow of the
script?
• Are there sections of code that
should only run under a certain
condition
• Should portions of code repeat Test Develop
• Would using functions simplify it
• Documentation of the function of
the script can begin at this phase
Lifecycle Management

Develop Plan

• At this stage, coding begins


• Comments should be used to
clarify the purpose of different Maintain Design
sections
• The development phase must keep
in mind the information gathered
during the previous two stages,
otherwise the script will not be fit
for purpose!
Test Develop
Lifecycle Management

Test Plan

• How can the script be tested


safely?
• Can it be run in a testing Maintain Design
environment, e.g. a VM or “model
computer”
• Does the script run without error?
• What debugging tools can be used
to troubleshoot errors?
• Does the script work as expected?
• Does the script run quickly Test Develop
enough?
Lifecycle Management

Maintain Plan

• Update / enhance the script over


time
• Keep track of version numbers and Maintain Design
changes
• Add comments to the top of the
script detailing important changes
• Document the functionality of the
script

Test Develop

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy