Regardless of whether RUP, Agile, Waterfall or whatever is used, if the customer requirements are wrong, then failure will result. I think our quest for the "perfect" process to solve this problem will never happen ...until application incubation is embraced within them.
In reality today, the real customer requirements are not flushed out until a beta is delivered to the customer. The problem is considerable money has already been spent to produce this beta since production is now in mid-stream. Why not deliver the beta in the requirements phase!
Simunicator enables the development of rapidly designed, deployable prototypes so customers can incubate their application in "real life" before they sign off to production. Design our prototypes using visual design editors for ease & speed or plug in real code for power & flexibility such as for AJAX, DOM and dynamic data. For example, our web site is a prototype designed in Simunicator now being incubated.
There's no better way for a customer to understand and communicate their needs exactly. And, there's no better way to communicate to the dev team what they need to build. Not to mention incubated Simunicator prototypes allow for customer feedback capture, fast "final" tweaks and generation of technical documentation. And your requirements phase is not any longer that it was before.
This incubation feature is the biggest differentiator in the prototyping & simulation market. Draw screens and lower bad requirements with other tools or incubate applications and eliminate bad requirements with Simunicator.
(Thanks to Patrick J. Kerpan who gave us the "application incubation" term after he designed and incubated a prototype using Simunicator)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment