Articles and Posts Apr 13, 2020 8 mins 3187 Views 0 Comments 0 Likes Part 3 of Dan Tasker’s Requirements in Context series continues to look at high-level requirements, narrowing the context to that of a project charted to deliver an IT-bases solution. It discusses how scope statements that identify functional capabilities are a good source of HLRs. The article goes on to discuss how, when the scope is represented visually, either as a Level Zero Dataflow Diagram or a UML Use Case System Context diagram, those models can be used to derive functional HLRs. The following Use Case System Context diagram is presented as an example: Each use case is discussed and a corresponding example HLR is presented. “The system shall be able to identify the appropriate tax that applies to the purchase of a given product based on the product type and the tax authority(s) that have jurisdiction where the shipment is to be delivered.” Continue reading at ModernAnalyst.com Login or Register to download Related Content Keeping High-Level Requirements High-Level Dan Tasker 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 [email protected] Did you like this article? 0 Upvote High-Level Requirements UML Use Cases Context Diagram 2020-04-13 Requirements.com All about Requirements 2020-04-13 Dan Tasker Scope-based High-Level Requirements Contributor Dan Tasker Comments / Discussions Please login or register to post comments.