Module 3: Using a Conceptual Design for Data Requirements

Module 3: Using a Conceptual Design for Data Requirements Module 9: Data Storage Considerations Module 8: Designing Data Services Module 1: Course Overview Module 2: Solution Design Processes Module 7: Implementing Data Integrity Module 6: Deriving a Physical Data Design Designing Data Services and Data Models Module 3: Using a Conceptual Design for Data Requirements Module 4: Deriving a Logical Data Design Module 5: Normalizing the Logical Data Design Investigation Process Module 3: Using a Conceptual Design for Data Requirements Activity 3.2: Relating Data Requirements to Conceptual Design Activity 3.1: Identifying Data-Related Use Cases and Data Requirements Data Requirements Module 3: Using a Conceptual Design for Data Requirements 47 ! Overview Slide Objective To provide an overview of this module’s topics and objectives. ✂Investigation Process ✂Data Requirements ✂Activity 3.2: Relating Data Requirements to Conceptual Design ✂Review In thismodule... At the end of this module, you will be able to: ✂✁Describe the information investigation process. ✂✁Determine functional data requirements from use cases. ✂✁Identify nonfunctional requirements that will affect a solution’s design. 48 Module 3: Using a Conceptual Design for Data Requirements ! Investigation Process Slide Objective To introduce use cases and nonfunctional requirements that are used in the solution’s conceptual design. ✂Gathering Information ✂Analyzing Information ✂Creating Use Cases In thissection... Delivery Tip This section provides an overview of what students would normally do to get information about data and nonfunctional requirements. They will not actually do this in the course. If students want more information about this process, refer them to Course 1585: Gathering and Analyzing Business Requirements. In this section, the discussion will focus on the reasons for gathering and analyzing data, as well as the formulation of this data into use cases. Use cases will be the foundation for determining data requirements for the system. Module 3: Using a Conceptual Design for Data Requirements 49 Gathering Information Slide Objective To provide an understanding of the gathering phase as a part of the investigation process. Lead-in You will take a look at the gathering of information as it relates to the investigation process. ✂Identify necessary information ✂Identify sources for required information ✂Use perspectives when looking at source information ✂Gather information $Conduct interviews $Shadow $Collect artifacts To identify data requirements, the project team starts a process of investigation. This process involves gathering and analyzing data from users, systems, and documentation to determine the current state and desired future state of the solution. Gathering data involves: ✂✁Determining what information is needed to identify the data, functional requirements, and nonfunctional requirements. ✂✁Identifying sources from which to obtain relevant and supporting information. Sources can include people, systems, and systems-support documents. ✂✁Looking at source information from different perspectives to ensure that all the relevant information is gathered from a particular source. ✂✁Gathering the information needed to determine requirements from the identified sources. Information can be gathered in several ways: • Conduct interviews with users, managers, and other customers. • Shadow users, managers, and other customers to gain first-hand knowledge of the skills and experience necessary to perform a task. • Collect artifacts, such as printed documentation and manuals. ... - tailieumienphi.vn