1 / 5

Comprehensive Guide to I2RS Use Case Taxonomy and Requirements Understanding

This document outlines an approach to I2RS use case taxonomy by emphasizing the importance of thoroughly understanding the problem space and formalizing requirements. It explains the significance of identifying relevant use cases that extend the requirements meaningfully, discarding those with limited value. A structured process is proposed for gathering use cases, focusing on a broad range of scenarios linked to enterprise needs, service provision, and security considerations. By organizing use cases effectively, we aim to achieve optimal coverage and minimize redundancy.

oleg
Download Presentation

Comprehensive Guide to I2RS Use Case Taxonomy and Requirements Understanding

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. I2RS Use Case Taxonomy

  2. The Porpoise • Make certain we fully understand the problem space • Make certain we fully understand the requirements • We aren’t gathering use cases for fun.  • If a use case doesn’t really add to the requirements in some interesting way, we probably don’t need to document it

  3. The Process • Cast a wide net for every possible use case • Find the set of use cases that justify/support the widest set of requirements • These requirements are the “ultimate goal” • Not to be mistaken for any sort of immediate or intermediate goal • Narrow requirements to bite sized chunks • Kelp balls of the right size • Build the pieces needed to fulfill that set of requirements • Dip out the next set of requirements to work on

  4. Use Cases • Two ways to think about use cases • Enterprise verses service provider verses content provider • Security verses traffic engineering verses… • Data center verses campus verses core verses… • What is the “right” approach to organizing the use cases • Make certain we have most of the useful use cases • Without too much overlap

  5. Use Cases

More Related