Chapter 3 Review Questions

1) 1. Identify the problem or need and obtain approval to proceed. 2. Plan and monitor the project—what to do, how to do it, and who does it. 3. Discover and understand the details of the problem or the need. 4. Design the system components that solve the problem or satisfy the need. 5. Build, test, and integrate system components. 6. Complete system tests and then deploy the solution. The activity being discussed in the beginning of the chapter is define functional requirements. Core process 3.

2) A use case is an activity the system performs, usually in response to a request by a user.3) Two techniques used for identifying use cases are the user goal technique and the event

decomposition technique.4) The user goal technique is to ask users to describe their goals for using the new or updated

system. Where the analyst will then identify all the users and then conduct a structured interview with each user. By focusing on one type of user at a time, the analyst can systematically address the problem of identifying use cases.

5) An example of users with different functional roles are shipping, marketing and sales users. Operational levels could be clerks, supervisors and executives.

6) Find course, Register for selected course, drop selected course.7) The overarching objective is to identify and document all use cases.8) Many types of users can have the same user goals. People from different departments can

share user goals9) The event decomposition technique begins by identifying all the business events that will cause

the information system to respond, and each event leads to a use case. Starting with business events helps the analyst define each use case at the right level of detail. For example, an entire process of adding a new customer is the right level of analysis for a use case.

10) The event decomposition technique also looks at temporal and state events making it more comprehensive then the user goal technique.\

11) An elementary business process is a task that is performed by one person in one place in response to a business event, adds measurable business value, and leaves the system and its data in a stable and consistent state.

12) The event decomposition technique helps identify use cases at the right level of detail by focusing on EBPs. An analyst will look for an example that defines a complete user goal. For example, the entire process of adding a new customer is a complete user goal.

13) An event is something that occurs at a specific time and place, and can be precisely identified, and must be remembered by the system.

14) The 3 types of events are temporal events, internal events (state), and external events.15) An external event is an event that occurs outside the system, usually initiated by an external

agent (customer). An external event that can apply to a checking account system would be when a customer (user) processes a charge with his debit card that uses his checking account.

16) A temporal event is an event that occurs as a result of reaching a point in time. A temporal event that applies to a checking account system would be the bank sending the customer (user) his monthly statements.

17) System controls are checks or safety procedures that protect the integrity of the system and the data. This is not considered part of the functional requirements because the functional requirements model does not need to indicate how the system is actually implemented.

18) The perfect technology assumption is the assumption that a system runs under perfect operating and technological conditions.