| Initial Analysis |
![[Phase 1 Image]](phase1.gif) |
GOAL During this
phase, the goal is to arrive at a set of high level objectives as to how
the new system should perform and what functions it will carry out and
to raise issues that will need attention during the design phase. |
| COMPANY INVOLVEMENT
The analyst for Didelot Consultants will meet with various end users of
the system who will use it for its intended purpose. Discussion will
center around how the current system works, who uses the system and how,
and the system's shortcomings and strengths with regard to your business
needs. |
| END RESULT Once
the objectives and issues are outlined and reviewed for accuracy, the
analyst will prepare and deliver an Analysis Summary. |
| Business Design |
![[Phase 2 Image]](phase2.gif) |
GOAL
The Business Design phase will address the issues raised in the Initial
Analysis and outline how the analyst intends to build the new system so
it satisfies the objectives of the analysis. |
| COMPANY INVOLVEMENT
The analyst will sit down with end users to discuss one or more possible
solutions regarding how the new system will conform to your
expectations. The application is always designed with the end user in
mind and is based on the initial analysis. |
| END RESULT Upon
completion of this phases, Didelot Consultants will deliver a Business
Design packet which will list by name the screens, reports, and
processes the proposed system will include and a brief description of
each. |
| Construction |
![[Phase 3 Image]](phase3.gif) |
GOAL In the
construction phase, the analyst will use the tools and methods described
in the Software Overview section to develop the new system. Design
continues at a more detailed level incorporating the objectives and
solutions from the previous two phases. The analyst writes the computer
codes that make up the new system. Test cases are created using the
business knowledge gained, and then run through the program to ensure
reliability. |
| COMPANY INVOLVEMENT
Interaction with the end user at this is generally light. However, as
new ideas and issues surface the analyst may request additional meetings
with the users to get information, feedback, and approval. |
| END RESULT When the
construction phase is completed the new system is ready for installation
and testing. |
| System Testing |
![[Phase 4 Image]](phase4.gif) |
GOAL System testing
involves sending actual business data through the entire system to
verify that the individual components interact as expected and that the
results meet the stated objectives and requirements. |
| COMPANY INVOLVEMENT
Any differences between expected outcome and actual results that may
appear at this stage are noted and either corrected or discussed with
the end users to arrive at a resolution. |
| END RESULT The new
system is installed in a testing environment at the customer's site. |
| User Acceptance
Testing/Training |
![[Phase 5 Image]](phase5.gif) |
GOAL The new system
is released to the end user for their training and testing. |
| COMPANY INVOLVEMENT
End users will be trained on the new system by the analyst who designed
the product. The analyst will provide general assistance during the
conversion to the production environment. |
| END RESULT The new
system will be installed and productively used by the end user in the
business setting. Didelot Consultants will be available for a wrap-up
meeting with the company to review the completed system development
process. |
