QUALITY REQUIREMENTS FOR INFORMATION SYSTEMS – PART 2 – KEEPING HIGH-LEVEL REQUIREMENTS HIGH-LEVEL
About the Presentation
Audience:Business analysts and managers, project teams
Presented by:Dan Tasker, Senior Business Analyst, Author, Mentor
A generic functional model of an organisation is introduced that supports identifying contexts for information systems. An example of a context diagram representing the scope for an information system project is presented as the starting point for eliciting Stakeholder (high-level) requirements. Those requirements utilise the five fundamental capability types introduced in Part 1 of this series.
Each high-level requirement is seen to represent a unit of delivery within the project, expected to act as the context for eliciting functional (detailed) requirements. The BABOK® requirement quality characteristics are reviewed in relation to the overall set of requirements based on the project scope.
About the Speaker
The author of two books and numerous articles, Dan recently retired after working and consulting in the IT industry for the past 48 years.
He spent the first 10 years working as a developer (called ‘programmer’ back then) in the United States and Canada. This was followed by two years teaching computer programming, database design, and data modelling.
The remainder of his career was spent as a business analyst, in Canada, Australia, and New Zealand. He continues to be passionate about quality requirements and helping business analysts produce them. He can be contacted at firstname.lastname@example.org..