Requirements Patterns via Events / Use Cases

Author: atlsysguild.com | Published: 12th Aug 2005 | Visited: 486 times | Add Comment
Filed in: Test Approach

This paper illustrates how event/use case modelling can be used to identify, define and access requirements patterns. Event/use case partitioning is widely used as a way of breaking a system into manageable, business-related chunks. Each event/use case is then the subject of detailed analysis, design and implementation. This paper illustrates how event/use case modelling can also be used as the basis for identifying and defining requirements process and data patterns. Given a book of requirements patterns, each project uses context analysis and event/use case partitioning as a way of accessing relevant patterns.

Read Article

Sponsored Links

• Fallback Patterns for Ajax No matter how much the developer ensures that the application goes smoothly something will go wrong eventually. It may not happen today or the next few months but certain conditions will happen such as hardware or update incompatibility. That will lead to errors in executing an Ajax based applicatio ...

• Requirements of Japanese Text Layout I've just caught up with this document from W3C which fills in a big gap in English-language technical material. Japanese typesetting technology has been very influential in the other Ideographic countries, and they share many commonalities (e.g. Japanese ruby tex ...

• Handling Html Events by .NET C# This article demonstrates a simple way to bind to any html document event from .NET Winform Application or BandObject or Browser Helper Ob ...

• Factory Patterns - Delphi OOP Chapter 26 in Delphi OOP :: This chapter explores the Factory patterns, which, instead of changing an object’s behaviour, provide ways of creating different objects to suit run time requirements. Read the ful ...

• EventyList: The List with Events Generic list class based on Microsoft's implementation with few additional events to handle like BeforeAdd, OnAdd, BeforeRemove, ...

• Tracking Events Using a Semi-Structured Repository Tracking the activities of a system and its users is too often not considered until the application is already deployed. Learn how to demonstrate an (almost) no hassle persistent bean pool that you can use to track the activities of an already developed system for later rev ...

• Sinking events from managed code in unmanaged C++ Raising event in managed code and sinking it in unmanaged ...

• Patterns for Varying Class Behavior - Delphi OOP Chapter 24 in OOP Course :: The structure of a class is fixed when the class is compiled. However, there are occasions when an operation may need to take on different characteristics a ...

• The Facade Patterns - Delphi OOP Chapter 23 in OOP Course :: Chapter summary: Using delegation (in the form of composition or association) in implementing patterns; Using the Adapter pattern; Object and class Adapters; Using the Facade pattern ...

• SQA Planning and Requirements SQA Planning and Requirements The scope of Software Quality Assurance or SQA starts from the planning of the application until it is being distributed for the actual operations. To successfully monitor the application build up process, the SQA team also has their written plan. In a regular SQA... V ...

Next: Improving Requirements Through Testing