|
| Our Process |
 |
| Our process at Mullangi Technologies
comprises of the steps below to let the clients have a better
view of the flow of work done: |
|
| Investigation |
|
| This phase may begin with a phone call or
an email from a customer. The purpose of the Investigation is
not to develop a system, but to verify that a problem or deficiency
really exists, or to pass judgment on the new requirement. The
end result, or deliverable, from the Investigation phase is
either a willingness to proceed further, or the decision to
'call it quits'. |
|
| Analysis |
|
| In this phase, we study the project in detail.
At the end of this phase, we formalize the requirements of the
client. This provides details about what the program should
do. The Requirements Statement lists all of the major details
of the program. |
|
| Design |
|
| In this phase we take the formalized requirements
as inputs and frame up all the software and hardware needs.
Design encompasses many different elements. |
|
- Input
- Output
- Processing
- Files
|
| By the end of the design phase, we would hope
to have a formal Requirements Statement for the program, and
a rough sketch of the architecture and what the user interface
will look like. |
|
| Development |
|
| In this phase we take the sketch prepared
in the design phase as input and start coding the program. In
the Development phase, examination and re-examination of the
Requirements Statement is needed. |
|
| Developers use this stage to demo the application
to the customer as another check that the final software solution
answers the problem posed. When they are given the OK from the
customer, the final version code is written into this shell
to complete the phase. |
|
| Implementation & Testing |
|
| After the Development phase, the system is
implemented. Software, which was designed in phase 3, and programmed
in phase 4, will be installed on any PCs that require it. During
the Implementation phase, both the hardware and the software
is tested. Although the programmer will find and fix many problems,
almost invariably, the user will uncover problems that the developer
has been unable to simulate. |
|
| Maintenance |
|
| In this phase the client, studies the implemented
system to ensure that it actually fulfills the Requirements
Statement. The Maintenance portion deals with any changes that
need to be made to the system. Changes are sometimes the result
of the system not completely fulfilling its original requirements,
but they could also be the result of customer satisfaction.
Sometimes the customer is so happy with what they have got that
they want more. |
|
