Tài liệu Module 6: Analyzing Information: Rationalizing Information doc

Module 6: Analyzing Information: Rationalizing Information THIS PAGE LEFT INTENTIONALLY BLANK Module 1: Course Overview Module 4: Gathering Information Module 5: Analyzing Information: Use Cases and Usage Scenarios Module 6: Analyzing Information: Rationalizing Information Module 7: Presenting Information Gathering and Analyzing Business Requirem ents Module 2: Identifying Business Pro cesses, Challenge s, and Vis ion Module 3: Characteristics of Information Organizing and Prioritizing the Current State Using Models Modeling Dynamic Behavior Review Module 6: Analyzing Information: Rationalizing Information Determining Requirements, Wants, and Constraints Module 6: Analyzing Information: Rationalizing Information 125 ! !! ! Overview " Organizing and Prioritizing the Current State " Determining Requirements, Wants, and Constraints " Using Models " Modeling Dynamic Behavior " Review In this module . In this module . In the first step of synthesizing information, you developed use cases and usage scenarios to begin describing the current state of the business. The use cases describe the primary functionality of the business processes within a business. The usage scenarios provide the detail that describes how the functionality occurs in a business process. The use cases and usage scenarios that you first develop originate from a large amount of information that you collect about the business, its processes, and the business challenge. Most likely, there will be redundant information that you will need to consolidate to describe the current state of the business in detail. The next step in analysis is to consolidate and prioritize the use cases and usage scenarios to determine requirements, wants, and constraints. In this module, you will learn how to organize and prioritize use cases and usage scenarios to describe the current state from the business and user perspectives. Then you will learn how to determine requirements, wants, and constraints from the business and user perspectives. Finally, you will learn how you can use models to describe the dynamic behavior of business processes. After completing this module, you will be able to: " Analyze use cases and usage scenarios to describe the current state of a business. " Determine requirements, wants, and constraints from user and business perspectives. " Explain how models can be used to describe behavior in a system. " Use models to describe dynamic behavior in the business environment. Slide Objective To provide an overview of the module topics and objectives. 126 Module 6: Analyzing Information: Rationalizing Information ! !! ! Organizing and Prioritizing the Current State In this section . In this section . " Grouping by Actors and Actions " Consolidating Redundancies " Activity 6.1: Organizing Use Cases and Usage Scenarios In this section, you will learn how to organize use cases and usage scenarios to eliminate any redundancies that may have resulted from the first pass at synthesizing information. Then you will analyze the existing use cases and usage scenarios to describe the current state of a business. In Activity 6.1, you will organize and prioritize the use cases and usage scenarios that you developed in Module 5. Slide Objective To provide an overview of the topics and activities in this section. Module 6: Analyzing Information: Rationalizing Information 127 Grouping by Actors and Actions " Actors $ Group use cases by identical actors $ Group actor use cases by similar organizational roles " Actions $ Group use cases by identical actions $ Group use cases by similar organizational processes When you gather information, you use different information-gathering techniques with a large number of sources in the business. Many of the sources you used had similar functions in the business. For example, you may have looked at different artifacts that documented the company’s intranet. Or using the Ferguson and Bardell, Inc. case study, you may have interviewed several consultants or managers. Each of these sets of sources can provide information that overlaps, resulting in duplication. When you are first gathering information, the duplication is normal, and it is part of ensuring that you collect all of the information that you need to describe the current state of the business. The duplicate information also helps to validate the information received from various sources. After you begin analysis, you need to eliminate redundancies to determine the most important information to the business and the business challenge. The analysis procedure performed in the previous module, in which you developed use cases and usage scenarios, represents the first step toward organizing information. The next step in organizing the information is to group the use cases and their usage scenarios by actors and by actions. For example, in a training center example, you might group by similar actors, such as sales representative or instructor. Individuals in a business may have different titles, but perform similar roles at different times. Make sure that you identify the roles and group them together. When grouping by actions, look across use cases for similarities, such as multiple use cases that involve processing payments. Different people will describe the same process differently. You can determine similar actions by looking for multiple usage scenarios that are describing the same process. Do not eliminate the redundancies at this point; just group the use cases so that you can determine what overlap you have among the total set. Again, you can also examine the redundancies to validate the information. Slide Objective To explain how to eliminate redundancies by grouping actors and actions. 128 Module 6: Analyzing Information: Rationalizing Information Consolidating Redundancies " Remove similar use cases from similar actors " Remove similar use cases from similar actions " Remove similar actor and action features After you have grouped use cases and usage scenarios by actors and actions, you can begin to eliminate redundancies. Identify each distinct actor in the business and eliminate any redundant use cases or usage scenarios. For example, for a sales representative in the training center, there may be use cases for processing a course payment by different credit cards, by debit cards, or by check. Each use case would have its own set of scenarios. However, each use case describes a payment processing function. To eliminate redundancies, you would create a primary use case called “Process Course Payment” and group all of the existing usage scenarios under the one use case. Next, analyze any similar usage scenarios to determine the complete set of tasks necessary to describe the usage scenario. Consolidate the tasks into one usage scenario to eliminate the redundant scenarios. As you are analyzing use cases and usage scenarios, you may find scenarios that describe instances of different use cases, but share a similar set of tasks. For example, when processing a student’s course payment, the sales representative may need to complete a process of recording the payment in a separate accounting database. The sales representative completes the process no matter what the payment method. Rather than repeat the process in each usage scenario, you may need to create a new use case, such as “Update Account Record,” that indicates the interaction of the actor with a different system. Slide Objective To explain how to eliminate redundancies among use cases and usage scenarios that are grouped by actors and actions. Module 6: Analyzing Information: Rationalizing Information 129 Activity 6.1: Organizing Use Cases and Usage Scenarios Organizing use cases and usage scenarios represents a necessary process of eliminating redundancies in large amounts of information. Analysis is an iterative process in which you gradually create structure in the information provided by different sources. In this activity, you will group the use cases that you created in Module 5 by actors and by actions. Then you will eliminate redundancies in both sets of use cases. Finally, you will review the usage scenarios to determine if there are task sequences that should be consolidated as usage scenarios under a new use case. After completing this lab, you will be able to: " Organize use cases and usage scenarios by actors and actions. " Eliminate redundancies among use cases and usage scenarios. Slide Objective To explain the activity. 130 Module 6: Analyzing Information: Rationalizing Information ! !! ! Determining Requirements, Wants, and Constraints " Identifying Requirements " Identifying Wants " Listing Requirements and Prioritizing Wants " Identifying Constraints " Activity 6.2: Determining Requirements, Wants, and Constraints Requirements tell the project team what the final solution must do to address the business challenge from the business and user perspectives. Wants tell the project team what improvements individuals in the business, from both the user and business perspectives, would like to see implemented in the final business solution. Constraints are aspects of the business environment that cannot or will not be changed. They indicate the parameters to which the final business solution must adhere. In this section, you will learn how to identify requirements, wants, and constraints. In Activity 6.2, you will prioritize the requirements and wants, and list constraints for the Ferguson and Bardell, Inc. case study. Slide Objective To provide an overview of the topics and activity in this section. Module 6: Analyzing Information: Rationalizing Information 131 Identifying Requirements " Examine use cases, usage scenarios, and business and user feedback to document: $ Inefficiencies, bottlenecks, and unnecessary steps $ Redundant and ineffective practices and processes $ Unnecessary paperwork $ Dysfunctional policies $ Undocumented new or changed business $ Transport and delay time The use case and usage scenarios that you organize and consolidate represent the current state of the business. You need to examine this set of information to determine the requirements and wants for any solution to the business challenge. Requirements are what the user or business need for the new solution. When analyzing usage scenarios, look for problems that contribute to the business challenge. For example, look at task sequences that contain duplication or unnecessary work. Compare task sequences that you observed during shadowing to the suggested task sequences that you find in artifacts such as user manuals or company policies. Discrepancies may indicate that users are following old policies that negatively impact performance. Conversely, users may discover more efficient task sequences that should become requirements in the new system. In addition to the usage scenarios, you will also obtain requirements by interviewing individuals or conducting focus groups. Participants will tell you what changes need to happen for business processes to be more effective and efficient. Slide Objective To explain how to identify requirements in use cases and usage scenarios. 132 Module 6: Analyzing Information: Rationalizing Information Identifying Wants " Capture what users or stakeholders want redesigned or built new to optimally support key processes $ Optimize the entire process $ Integrate processes where possible " Determine wants for the new system based on user and business perspectives $ Improved productivity $ Balance impact and technical feasibility " Build a preliminary list of wants Employees in a business work with business processes on a regular basis. They have a continual opportunity to think about how a process could be improved. The knowledge and experience that they develop provide both requirements and wants. The requirements indicate what characteristics of the process are essential to meet the goals of the business. The wants indicate characteristics or features that would be nice to have in the process. Wants are important, but not essential to achieving the business goals or resolving the business challenge. Wants are based on the actual day-to-day experiences of people, but they represent an ideal state of how people would like things to be in the business. Wants can indicate: " How a process can be done more efficiently. " How a process can integrate more efficiently with other processes. " How a process can be accomplished with less strain for the individuals involved in the process. While you are gathering information, you need to follow up with individuals to determine if a statement they make about improving the system is a requirement or a want. If the improvement is not essential for completing the process or does not address the business challenge and the core values and vision of the business, then list it as a want. Working with requirements and wants is an iterative process. During analysis, some requirements will become wants and some wants may better suit the business challenge and become requirements. The project team must often assume a leadership role in determining requirements and wants and present their results for validation by stakeholders and users. Do not discount wants. Though they may not have the same priority as requirements, they provide important information to the development team. Wants represent potential features that make tasks easier for employees. Slide Objective To explain wants as a result of the analysis process and to provide examples of these wants. [...]... complete 154 Module 6: Analyzing Information: Rationalizing Information Looking Forward Slide Objective To relate the current module to the next module and the course Module 7: Presenting Information Module 6: Analyzing Information: Rationalizing Information Module 1: Course Overview Gathering and Analyzing Business Requirements Module 5: Analyzing Information: Use Cases and Usage Scenarios Module 2:... 134 Module 6: Analyzing Information: Rationalizing Information Finally, validate the list of requirements and the prioritized list of wants with users When you organize information and present it to users to validate, you can make it easier for users to reflect on any information that they gave you, as well as offer them a second chance to correct or verify it Module 6: Analyzing Information: Rationalizing. .. note which topics you may need to review Finally, you will learn how this module relates to the next module and other information and skills that you encounter in this course Module 6: Analyzing Information: Rationalizing Information 151 Guidelines Slide Objective To present general guidelines related to the information in this module " Understand the user’s priorities " Fully describe high-priority... 150 Module 6: Analyzing Information: Rationalizing Information ! Review Slide Objective To provide an overview of the topics in this section " Guidelines " Review Questions " Looking Forward In this section In this section This section presents an opportunity to review the material in this module First, you will look at guidelines that you can use to adapt the information and skills in this module. .. transactions processed Credit card center approves charge and creates authorization number 148 Module 6: Analyzing Information: Rationalizing Information Modeling State Slide Objective To explain how to use state models to provide detailed information about usage scenarios Lead-in State models provide detailed information on the tasks within a usage scenario " Captures event-oriented dynamic behaviors... current state 142 Module 6: Analyzing Information: Rationalizing Information Dynamic Behavior with Use Cases and Usage Scenarios Slide Objective To explain how dynamic behavior is modeled between use cases and usage scenarios " Modeling behavior between use cases $ $ " Within systems Between systems Modeling behavior for usage scenarios tasks Modeling the behavior among use cases provides information about... cases, you can examine the usage scenarios to determine relationships, such as dependencies between task sequences Module 6: Analyzing Information: Rationalizing Information 143 Activity 6.3: Using Models Slide Objective To explain the activity Models are powerful tools for describing and analyzing business requirements You can develop extremely complex models that provide detail about how a system currently... as a user might describe it to another person 146 Module 6: Analyzing Information: Rationalizing Information Modeling Interaction Slide Objective To explain interaction models and provide an example " Lead-in Sequence $ " Captures time-oriented dynamic behaviors $ Interaction models can emphasize sequence or collaboration Identifies the life span of information Collaboration $ Captures message-oriented.. .Module 6: Analyzing Information: Rationalizing Information 133 Listing Requirements and Prioritizing Wants Slide Objective To explain how to prioritize wants " Review all information that addresses the business challenge $ Business processes $ Use cases and usage scenarios $ Requirements... business challenge and to determine what the requirements are and what information you might need to gather As the business processes are modeled and adapted to reflect the requirements, you can build a model of the final architecture that describes the application or final business solution Module 6: Analyzing Information: Rationalizing Information 139 Describing Models Slide Objective To describe different . Information Module 5: Analyzing Information: Use Cases and Usage Scenarios Module 6: Analyzing Information: Rationalizing Information Module 7: Presenting Information. Review Module 6: Analyzing Information: Rationalizing Information Determining Requirements, Wants, and Constraints Module 6: Analyzing Information: Rationalizing