Rapid prototyping
Prototyping to validate functional requirements
You have strategic needs regarding software development. You acknowledge that prior to the implementation a formalizing step is necessary to ensure that budgets can be estimated and validated. But you find the time to formalize long and the overall result still frustrating and unreliable.
You feel that the paper, whether written or drawn, easily withstands anything. You're not alone. Nearly half of the bugs are associated with the formalization or lack of formalization of requirements. And over 80% of the time required to correct the bugs involves these same requirements.
Mockup is therefore a hope. But the user inability to directly manipulate the realistic use cases, still leaves room for too many gaps and inconsistencies, with a significant impact on overruns in time and on budget.
Because it puts users in a position to use real life cases, prototyping remains the safest way to validate the requirements. These users can enter their data, run their calculations and verify the relevance of results in real time. Unfortunately, a Web-based prototype manipulating rich data usually requires advanced technical skills and a significant time.
- MyDraft to build prototype with agility
MyDraft offers two major advances :
• Drastic reduction of the usual prerequisites (technical skills, tools, delays and budgets) by merging the lifecycles of business and software, which allows the modification of the application during its execution.
• Regulatory compliance, auditability and complete responsibility protected by full traceability at both runtime and design time.
The prototypes were built within 5 to 10 minutes cycles. The user or the subject matter expert can evolve the prototype on the fly, safely. What about specifications ? Two ways to answer : on one hand, the specification is the application, ie a living specification; on the other hand, the detailed specification documents can be easily generated.
- Illustration (see below)
• Definition of Business entities : classes, attributes and associations
• Definition of instances
• Diagrams display
• Definition of screen fragments : updatable grids, forms, master-details, composites, charts,.
• Preview
• Definition of roles, rights, user invite
• Need for complementary code ? Definition of operations and integrated unit testing
• Actions and controllers.
• Agile follow-up : ScrumBar.
![Image1\](http://www.karmicsoft.com/images/sliderDemo/p9e.jpg "\")
