Business System Options (BSO)
Once the current system is documented and the requirements of the new
are understood, there are usually a range of different ways that the
requirements can be met, variations in the extent and shape of the area that is
to be provided with automated support and the area that is to remain as
manual.
This includes a possible range of technical options as well - things
like the following may need to be considered: operating system version, web or
traditional client /server, web-services, thin/thick client, content management
system, call centre telephony integration, customer relationship management
system, pdas / handhelds, mobiles.
Each overall option considered will result in full or partial fulfilment
of the high level requirements. For those still covered, a new DFM and LDM is
often needed to show the area in scope for this option, the requirements
covered and the elements impacted by the option.
Depending on size and complexity of the business need, at least three
options for moving forward are developed. Of course, the users help and guide
their development for the to-be system, with you as a guide and scribe.
Together you will build a definition of each option, with supporting material
that will allow its assessment.
This will usually consist of a summary of the option and a financial
appraisal and cost benefit analysis. It will usually be supported by a
high-level DFM and LDM to show the scope of automation, and both a business and
technical impact analysis. Finally you will need, still in conjunction with the
users, to develop a set of risks and assumptions and a high-level plan for
taking that option forward to delivery.
Business Systems Options are developed during Feasibility Study and
Requirements Analysis.
The usual route is:
Business: Feasibility Study -> BSOs -> Selected BSO ->
Feasibility Report -> Supplier: Bid / Impact Assessment -> Business:
Requirements Analysis -> BSOs -> Supplier: Bid / Impact Assessment ->
Business: Selected BSO -> Requirements Specification.
|