QUALITY REQUIREMENTS FOR INFORMATION SYSTEMS – PART 4 – ENSURING DETAILED REQUIREMENTS ARE SUFFICIENTLY DETAILED
About the Presentation
Audience:Business analysts and managers, project teams
Presented by:Dan Tasker, Senior Business Analyst, Author, Mentor
Having discussed Stakeholder (high-level) requirements in Part 2 of this series, and models representing the information component of an information system, that leaves Functional (detailed) requirements to be discussed. Quality functional requirements need to represent everything that is required from a business perspective.
An example of the level of detail necessary for a report taken from the Trips-R-You Case Study is discussed. The example utilizes visual representations of the report (i.e. a mock-up) as well as operational aspects. Ultimately, quality requirements are not complete until every data field and label that needs to be included in the report has been documented.
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..