The protodev approach is available to businesses seeking additional confidence and choice in the engineering of custom software applications.
The notion of software prototyping is not new ... the information technology industry has demonstrated a "hot" and "cold" stance toward prototyping for requirements gathering over the past two decades. In fact, many professionals acknowledge it is not until a client actually "test-drives" an application with "live" data that a business process is fully comprehended.
| Yet surprisingly, businesses are disappointed when new requirements are discovered late in the development cycle when a subject matter expert is (finally) able to fully exercise the application via a tactile (or kinesthetic) interaction with keyboard, mouse and monitor. |
In addition, many businesses want more effective in-sourcing, out-sourcing or off-shore options ... while increasing the velocity of development. But the real-world challenges of establishing and communicating requirements often drives an approach where the requirements gatherer is the most efficient entity to deliver a working application.
Confidence ... where does this feeling come from in the nebulas world of software engineering? Whether one is trying to determine quality, functional maturity, cost or schedule it is "predictability" that instills confidence. And it is the ability to effectively capture and analyze requirements that enables "predictability".
| So why hasn't prototyping "caught-on" in a big way? |
Two answers to the above question include process maturity and the existence of cost-effective tools . The protodev approach provides intentional focus on these two dimensions with the following set of assumptions:
If you are interested in growing your confidence in the systems engineering process, please contact GTC Group.
Copyright (c) 1999 - 2002 by GTC Group, Inc. at gtcGroup.com.
Use is authorized, provided the source is acknowledged by inclusion of this
copyright notice.