Section 8. The Scope of the Product


8. The Scope of the Product

8a. Product Boundary

We have made much mention of the difference between the scope of the work and the scope of the product. We won't belabor the point by repeating it here.

You have several options for showing the product's scope. We suggest a model is markedly better than a text description at demonstrating your scoping intentions to your stakeholders. The UML use case diagram, while far from perfect, is a popular model to show product scope.

Alternatively, you can use another context model similar to the work context. This time the central bubble is the product, and the adjacent systems are the actors.

The kind of model you use here is less important than using a model and having a clear demonstration of the functionality contained in your product.

8b. Product Use Case List

The use case diagram is a graphical way of summarizing the product use cases that are relevant to the product. If you have a large number of product use cases (we find 1520 is around the limit), then a list of product use cases is more manageable than the use case diagram.

8c. Individual Product Use Cases

This section is where you keep details about the individual product use cases on your list. You can include a scenario for each product use case on your list or you might prefer to draw a sequence diagram. Also, here is where you keep any prototypes of the product use cases.




Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net