AROBS Approach to Software Development

This section describes the internal processes followed while developing any outsourcing project.

We are guided by a customer-centered methodology which stood the test of time, consistently producing excellent results. By working together with our clients, we learn their needs and also help them understand their own customers. This combined effort brings forth solutions than exceed the expectations of both our customers and their clients.

Our internal product processes follow the same standard procedures regardless of the project type. The workflow is grouped is based on the life cycle phases of the software: requirement definition, requirement analysis, preliminary design, detailed design, implementation, system testing, acceptance testing.

1) The requirement definition stage.

A team of experts (from AROBS, our customer, or from both companies) prepares a document containing the requirements for the software and a draft of the functional specifications for the system. At the end of this phase the requirements for the system are evaluated.

2) The requirement analysis phase

The development team classifies and analyzes each specification and. Ambiguities, discrepancies, and to-be-determined (TBD) specifications are dealt with at this stage, whose outcome is the final version of the functional specifications document and a requirements analysis report.

3) The preliminary design.

During this phase, members of the development team produce a preliminary design report in which they define the software system architecture and specify the major subsystems, input/output (I/O) interfaces, and processing modes.

4) The detailed design stage.

All the components sketched during the previous phase get fully developed, in successively greater detail. Full descriptions of user input, system output, I/O files, and interfaces are produced at this stage, as well as an implementation plan describing a series of builds and releases and the software system to be delivered. The output of this stage is the detailed design document.

5) Implementation (coding, unit testing, and integration).

Coding takes place based on the guidelines from the detailed design document. The stage ends when all the code is integrated and supporting documents (the test plan for the system and the user's guide draft) are delivered.

6) System testing.

The functional testing of the system features and capabilities is done according to the system test plan. The system is validated and a preliminary system description document is produced. This stage ends when the tests required by the system test plan are completed.

7) Acceptance testing.

At this stage, the system is tested to find out if the original requirements have been met. To ensure an objective evaluation, we do not include any members of the software development team in the test team. The supporting materials delivered at this stage are the final versions of the user's guide and system description. Furthermore, an operational readiness review (ORR) is conducted to evaluate the system's readiness to begin operational support. Acceptance testing ends when all tests specified in the acceptance test plan have been run successfully.

8) Maintenance and operation

This is the last stage in the software life cycle. Hereafter, the maintenance and operation group takes charge of the system. The volume of work during this phase depends on the nature of the system being developed.


For additional information or a quote please contact us right away.