
Much energy has been spent over those years by ‘authorities’ and ‘experts’ trying to impress various audiences that their specific format/diagram was the one true way to document requirements heated arguments often between competing camps as to why ‘my way’ is better than ‘your way’. Given that straight prose writing was always going to be too ambiguous for common understanding, many different structured written formats and diagrams have been used over the decades in best attempts to capture the elusive Information System Requirement. How do you capture business requirements that reflect such potential diversity? Documenting Information System Requirements To support their communication and understanding, information system requirements must be documented this has usually meant they are written down in some way.

What this definition reminds us is that Information Systems are asked to do many different things perform calculations, edit and store data, produce reports, support business process, enforce rules, etc. They can be functions, constraints, or other properties that must be provided, met, or satisfied so the needs are filled for the system’s intended users (Roger Abbott 1986). Requirements vary (italics added) in intent and in the kinds of properties they represent. My favourite over time is: A requirement is a property that is essential for an IT system to perform its functions. What is an Information System Requirement? A standard definition of an Information System Requirement does not yet exist.

#MICROVELLUM TOOLBOX SYSTEM REQUIREMENTS HOW TO#
This article will be how to document Information System Requirements other aspects of Business Analysis (gathering, analyzing) will be the subject of another article. In the domain of Business Analysis, the ‘hard skill’ is writing (or modeling), documenting the Requirements so that they are recorded, communicated, and agreed to and it is this skill and related techniques that is the least well known of all skills/techniques employed in Information Systems development.
