Activity 3.1: Identifying Data-Related Use Cases and Data Requirements In this activity, you will analyze a set of use cases derived from the Ferguson and Bardell, Inc.. case study and
Trang 1Activity 3.1: Identifying Data-Related Use Cases and Data Requirements
In this activity, you will analyze a set of use cases derived from the Ferguson and Bardell, Inc case study and determine data requirements, hidden data requirements, and nonfunctional data requirements from those use cases
Objectives
After completing this activity, you will be able to:
! Determine data requirements from the use cases
! Determine what nonfunctional requirements will affect the solution’s conceptual design
Before You Begin
Time to complete this activity: 20 minutes
Trang 2Exercise 1:
Identifying Use Cases that Require Data
In this exercise, you will identify data requirements from the provided use cases
! Determine data requirements from a set of current state use cases
1 Refer to the Ferguson and Bardell, Inc case study in Appendix A of this Activity Manual
2 Following are various use cases that capture the functionality of the existing system at Ferguson and Bardell, Inc Using both the case study and these use cases, identify the system’s data requirements and enter them in the grid below
The grid includes a few extra rows, in case you recognize use cases in addition to those listed below
Consultant submits timesheet Timesheet information
Administrative assistant prints timesheet Completed timesheet
Administrative assistant keys data into time and billing system
Completed timesheet, job numbers, categories
Administrative assistant runs reports Report criteria
System e-mails selected reports Addresses of managers,
administrative staff
Managers correct data Customer information, time
and billing information
Managers approve data corrections Managerial data, time and
billing information, customer information
Administrative assistant corrects data errors Managerial data
Managers print invoices Final time and billing
information
Trang 3Exercise 2:
Identifying Hidden Data Requirements
In this exercise, you will identify the hidden data requirements related to a set
of explicit data requirements
! Determine hidden data requirements
1 Refer to the use cases from the previous exercise
2 Review the case study again, looking for hidden data requirements identified in the case study Enter these requirements in the following table, together with the reason why the data should be tracked
Explicit data requirement (taken from use cases)
Hidden data requirement
Reason to track data
Timesheet information Customer
scheduling information
Consultant resources and availability
To check that customer is available
to accept consultant’s services
To check that consultant is available
to bill time to customer
Completed timesheet Resources
available to submit timesheet
Financial information
To allow timesheet data to be submitted
by consultant in a timely manner
To allocate expense reimbursements and commission payments
Completed time and billing information
Currency rates
Receivables
To allow for international customers who require currency exchange
To track customers who owe money
Managerial data Forecasting data
Profitability information
To predict future trends
To determine future directions and courses
of actions
Trang 4Exercise 3:
Identifying Nonfunctional Requirements
In this exercise, you will identify any nonfunctional data requirements that are present in the Ferguson and Bardell, Inc system
! Determine nonfunctional data requirements
1 Read the case study, referring to the section titled “Technology” if necessary
2 Use the categories listed below to help identify nonfunctional requirements from the case study
3 Record two to four nonfunctional requirements for each category in the table below (Some categories may have more or fewer requirements than others.)
Category Nonfunctional data requirements
Scalability System must work for existing main office and satellite
office personnel
System must leverage existing hardware and new software
to grow to meet additional users in new offices
Availability System must be available for consultants use at all times
System must allow for concurrent users in different modules, performing different tasks
Maintainability System must use industry-standard software for
implementation
In-house development staff must be able to maintain system easily
Managers and clerical staff must be able to do specific administrative functions within system without harm to system
Extensibility System must support current number of users and future
users easily
Add-on products must integrate with system
System must provide hooks to third-party software and utilities
Interoperability System must be able to communicate with other systems
via standard protocols (TCP/IP)
All modules of system must talk to each other to transfer necessary data
Support is necessary for different operating systems and Web browsers for client software