Getting the right user requirements in initial phase of software implementation is always a challenge. Poor requirements specifications can result in systems that do not meet user needs. In the most extreme case, incomplete or error-riddled requirements specifications result in both time and money wasted building the wrong system. Customer perception of past solution package, past software problems and past operation procedure often build a wrong way of providing the right business requirements. Other aspect in getting the right business requirement is also due to schedule pressure which cause oversight.
Some ways to having a better process are :
- Including Business Process Owners who runs day to day operation in the discussion
- Having a software business analyst to interview business process owners
- Understanding that business requirements might not be able capture 100% since day one, so several can be categorised as current business, new business req and potentially new requirements that are not foreseen
- Mapping requirements into software standard package features, package extentions, and non system solution such as adjustment in the system procedures
- Choosing from several System Development Life Cycle approaches which is fit for a complex implementation such as : Spiral Model, Incremental Development are found will reduce risk.
To support the above process, especially getting complete business requirements - a tool from ravenflow which help to give a visual requirement definition can be also useful to validate if you have missing requirements.
No comments:
Post a Comment