Analysts sometimes use the term business event to describe the triggering condition that launches execution of a use case. Perhaps a help desk receives a phone call from a user who needs assistance. This external event triggers the help desk staffer to create a problem report ticket. Create Problem Report Ticket is a good name for a use case. In other types of products, such as real-time control systems, use cases are not a valuable technique for understanding user requirements. An alternative approach is to identify the external events the system must detect. Then describe the appropriate system response, which depends on the state the system is in at the time each event is detected. See Chapter 11, for more about events.Most requirements discussions focus on functionality. However, a product’s nonfunctional characteristics also have a great impact on how users feel about the product. Questions such as the ones that follow help the analyst understand the user’s expectations about aspects of the product’s quality.
đang được dịch, vui lòng đợi..
