This phase is essential to the success of the project. Expectations (whether from a client or from
your team) must be fleshed out in great detailed and documented information. He
is an iterative process with a lot of communication between stakeholders,
end users and the project team.
Analyze/Design
Technical design requirements are prepared during this phase by a team of
leading development which may include architects and developers. THE
Business requirements are used to define how the application will be written. Requirements
techniques will detail the database tables to add, the new transactions to
define, security processes and hardware and system requirements.
Development
This phase corresponds to the actual coding and unit testing of the process by the team
of development. After each step, the developer can demonstrate the work accomplished to the
business analysts and adjustments and improvements may be necessary. He is
It is important in this phase that developers are open-minded and flexible if
changes are introduced. This is normally the longest phase of the SDLC. The finished product
here has entered the testing phase.
Test
Once the application is migrated to a testing environment, different types of tests will be
carried out, including integration and system testing. Acceptance tests by
users constitute the last part of the tests and are carried out by the users
final results to ensure that the system meets their expectations. At this stage, defects may
be found and more work may be needed in analysis, design or
coding. Once approval is obtained by all parties involved, implementation and
deployment can begin.
Delivery
The size of the project will determine the complexity of the deployment. Training may be required
for end users, operations and on-call IT staff. THE
System deployment can be done in stages starting with a branch and then
slowly adding all locations or it can be a full implementation.