Detailed Design

Step 3: Detailed Design

Once a final prototype design is approved, our team will gather the underlying details required by our engineering team to build the application.

The detailed design phase is less visible and seemingly less tangible than the prototype design phase.  In fact, it may seem like it is just slowing down the project.  However. this step is essential to uncover, communicate, and resolve any remaining unknowns.   It enables us to better align expectations on how the application is going to function, and ultimately, to insure that we are building a solution that meets your specific business and operational needs.

Gathering details at this early phase can pay off significantly by avoiding issues down the road and speeding up the development phase.  If necessary, we will update our estimate based upon the results of the detailed design phase.  Depending upon the nature of your application, detailed design requirements may include:

• Use cases and test cases that clarify how the application is expected to behave and perform specific tasks
• Business logic, algorithms, and calculations that support the visual design
• Input constraints and data validations to be performed as data is input by users
• Data schema diagrams that layout the tables and relational data model
• Third-party controls that Practical may wish to use in developing the application
• Low level functional specifications for tricky or more complex areas of the application
• A data migration plan to move your business data from your old system to the new application

Go to the next step: