OSFA technologies

OSFA SOFTWARE DEVELOPMENT PHILOSOPY

Software Requirements volatility is one of the many reasons why software projects become a challenging undertaking. Software Developer need the Client and other stakeholders to obtain clear and complete requirements before the Project can begin. 

Now there are two Models in existence which are commonly used, one is the Waterfall model which is a sequential model whereby the complete requirements must be gathered from the client before proceeding to the next phases of the software development process. In this approach introducing changes later in the process can be very challenging or difficult and can have negative impact on the project success.

In the Agile Model, little requirements can be gathered from the client to begin with and series of iterations were made as new requirements emerges. Agile model is parallel in nature and changes can be introduced in any phase of the software process with ease.

Both Software Models needs requirements to be gathered from clients before  continuing  with the Software Project. And change in requirements means redesigning, re-coding, re-compiling and re-testing of source code.

CODING THE OSFA WAY

OSFA believes that the software Design should not be requirements driven but OSFA Patterns driven. This approach will allow isolate the Software Creator from the Client/Stakeholder (user) when creating the System. Therefore the Development team can go ahead with the project without the client /requirements.

In this approach the System is consist of two parts, The OSFA System and the Client System as shown below;