SDLC
SDLC
2. Plan. “What do we want?” In this stage of SDLC, the team defines the
requirements of the new software and determines the cost and
resources required. It also details the risks involved and provides sub-
plans for softening those risks. In this stage, a Software Requirement
Specification document is created.
3. Design. “How will we get what we want?” This phase of SDLC starts by
turning the software specifications into a design plan called the Design
Specification. All stakeholders then review this plan and offer feedback
and suggestions. It’s crucial to have a plan for collecting and
incorporating stakeholder input into this document. Failure at this stage
will almost certainly result in cost overruns at best and total collapse of
the project at worst.
4. Build. “Let’s create what we want.” This SDLC stage develops the
software by generating all the actual code. If the previous steps have
been followed with attention to detail, this is actually the least
complicated step.
5. Test. “Did we get what we want?” In this stage, we test for defects and
deficiencies. We fix those issues until the product meets the original
specifications.
6. Deploy. “Let’s start using what we got.” Often, this part of the SDLC
process happens in a limited way at first. Depending on feedback from
end users, more adjustments can be made.
7. Maintain. “Let’s get this closer to what we want.” The plan almost
never turns out perfect when it meets reality. Further, as conditions in
the real world change, we need to update and advance the software to
match.
Agile Model. The Agile SDLC model separates the product into cycles
and delivers a working product very quickly. This methodology
produces a succession of releases. Testing of each release feeds back
info that’s incorporated into the next version. According to Robert Half,
the drawback of this model is that the heavy emphasis on customer
interaction can lead the project in the wrong direction in some cases.
Spiral Model. The most flexible of the SDLC models, the spiral model
is similar to the iterative model in its emphasis on repetition. The spiral
model goes through the planning, design, build and test phases over
and over, with gradual improvements at each pass.
Benefits of SDLC
SDLC done right can allow the highest level of management control and
documentation. Developers understand what they should build and why. All parties
agree on the goal up front and see a clear plan for arriving at that goal. Everyone
understands the costs and resources required.
Financial Management
Financial management is more of a general term used to describe an
array of finance-based systems developed in many organizations. Companies
rely on integrated financial software tools to join activities in purchasing,
accounting and finance departments. In essence, the computer tools allow
each purchase and revenue transaction to get recorded once, yet appear in
the records and reports used in each of these finance-related departments.
The goal is to optimize record-keeping efficiency and to avoid redundant
transaction entries. Often, accounting software provides the foundation for
data entered and used across the company.
Source: Stackify. (2019). What is SDLC? Understand the Software Development Life Cycle. [online] Available at:
https://stackify.com/what-is-sdlc/ [Accessed 25 Jan. 2019].
Smallbusiness.chron.com. (2019). Examples of System Development in a Company. [online]
Available at: https://smallbusiness.chron.com/examples-system-development-company-79419.html
[Accessed 27 Jan. 2019].
Software
Development
Life
Cycle
Marasigan, Joycee B.
BS Accountancy IV-A