Modeling and Simulation - Part 2How Simulation Addresses Each Root CauseIn Modeling and Simulation - Part 1, we described root causes of requirements problems. Here we describe how simulation addresses each one of these root causes. 1. Lack of User involvementUsers want to experience and play with what they're going to get. Simulations are accessible and boost morale because users can verify early in the project that they were heard and understood.2. Stakeholders Cannot Validate Requirements Until Application DevelopedA wider audience of users can interactively run the simulation to validate that requirements have been captured and interpreted correctly before any code is written.3. Requirements Discovered After Code WrittenThe simulation will call out missed requirements early. Instead of a specification-driven prototype, have a simulation-driven specification.4. Project Budgets InaccurateOnce the simulation is approved, it becomes part of the requirements. Scope is well documented and visible to all.5. Users Do Not Know What They WantUsers discover what is possible and request it early rather than during user acceptance testing or in a future release. It is impossible for clients to specify requirements completely before trying some version(s) of the software they are specifying.Users expectations are set realistically when they are involved early. The delivered business process or software application are much more likely to match their expectations. User satisfaction rises. New Capability: Discovering What Is PossibleSimulation enables analysts to help others discover what else might be possible. This opens up the possibility that a solution that addresses the underlying business problem might be discovered and implemented early in the project.See this
system simulation example
to see how simulation in and of itself enabled finding a solution to a long standing problem.
|
