Dear All,
I am very new to SA. I need to present Business System Options to my senior PM for a information system he is designing for a library. He has given me a set of requirements. Now I need to prioritise them according to functional areas and the produce three BSO's. Please any suggestion from where I can get some help regarding presentation, some templates or on how to prioritise requirements and produce BSO's.
Many thanks for your time in advance,
any help much appreciated,
Regards,
Peter
Can you clarify what you mean by "Business Systems Options?"
What is the context of this report? Who will be using it? What decision are you seeking?
The set of Business System Options which is compiled so that a selection can be made. The selected Business System Option is a description of a chosen system development direction. The description documents the system boundary, inputs, outputs and the transformation taking place within the boundary.
Hi:
Are the description documents integrated? I will guarantee you that unless your input/process/output documentation is integrated (integrated input/process/output diagrams are called Data Flow Diagrams), then your requirements are incomplete. Chances are that incomplete requirements are your real issue. Once you have an integrated set of input/process/outputs, then you can systematically evaluate the requirements and prioritizing (by such things as interface complexity) is straight forward. So is evaluating automation alternatives.
Tony
Sounds like he is looking for 3 solution options i.e. 3 different ways to solve your requirements. Suggest you come up with descriptions for the 3 options and then make a recommendation. These options will often be costed to help with the decision making. You may need to involve an architect to help you define the system configurations for each option.
Your boss may simply be trying to get you as a newbie to think of multiple solutions. Probably a worthwhile exercise for you even if you only end up writing up your recommendation in the end.
In a previous job as part of scoping new projects we'd come up with mutliple costed solution options if the solution involved more than one system and could just be done more than one way easily. Didn't do it as a rule though.
Kimbo
brought to you by enabling practitioners & organizations to achieve their goals using: