1 reply
by oldefar
You have some excellent ideas, but it seems to me that you have rolled different aspects of system development together.
The business ogjectives and business requirements should come from business managers. This defines the overall parameters.
The user requirements and desires come into play as part of the technical objectives. It is important that these are linked to the business requirements, in turn linked to the business objectives.
The scope of documentation within ICT probably fits best within the technical requirements, while documentation for users is really a business requirement.
Communication between individuals involved at each level - business objective, business requirement, technical objective, technical requirement, technical design, and implementation ought to be part of the process. In general, the communication is specific to the level, and summary to the level other levels.
Where the biggest failure occurs is with a lack of linkage between levels. Too often, development begins without being grounded in business objectives, business requirements, and often technical objectives. Starting at the technical requirement level is where the problem lies, since communication will have no common point of reference between IT and other parties.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending