Design

After the analysis and specification phases have been completed and signed off by  the Client, a detailed software system design document is presented to the client. This design document discusses any of the areas that have given cause for concern in the analysis phase, along with a range of possible solutions that can be developed and deployed. Formal software design documentation can also be produced in the form of use cases, data flow diagrams or object/entity relationships. Bubblelogic recommends the use of the UML software analysis and design notation and methodology for projects, however specific methodologies will be applied at the client's request.

We believe that in presenting real software designs in a non-technical manner we can bridge between the technical domain and the business domain in a language that can be understood by both parties. With a single design definition (for instance use-cases), we can be sure that the technical implementation will be exactly what our clients are expecting.