BIS 261 DeVry Week 3 I Lab Latest
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>BIS</strong> <strong>261</strong> <strong>DeVry</strong> <strong>Week</strong> 3 I <strong>Lab</strong> <strong>Latest</strong><br />
Downloading is very simple, you can download this Course here:<br />
https://www.mindsblow.com/product/bis-<strong>261</strong>-devry-week-3-ilab-latest/<br />
Or<br />
Contact us at:<br />
SUPPORT@MINDSBLOW.COM<br />
<strong>BIS</strong> <strong>261</strong> <strong>DeVry</strong> <strong>Week</strong> 3 i<strong>Lab</strong> <strong>Latest</strong><br />
<strong>BIS</strong><strong>261</strong><br />
<strong>BIS</strong> <strong>261</strong> <strong>DeVry</strong> <strong>Week</strong> 3 i<strong>Lab</strong> <strong>Latest</strong><br />
Scenario and Summary<br />
OfficeFix, Inc. provides onsite office equipment repair services. Customers call a toll-free number or visit a website to<br />
request a service call. OfficeFix dispatches a technician to the customer's location within two hours to perform the<br />
needed repairs. OfficeFix can repair most popular makes and models of office equipment, including photocopiers,<br />
scanners, fax machines, desktop computers, and printers.<br />
OfficeFix's customer base has been growing rapidly, and the company has been expanding the number of makes and<br />
models of equipment that can be serviced. As a result, it has become difficult for service technicians to carry printed<br />
repair manuals for all of the different types of equipment, and time-consuming for them to find the right manual and<br />
service procedure. OfficeFix has decided to address these problems by creating a Mobile Service Knowledge Base<br />
system that will allow service technicians to call up repair procedures on handheld devices, eliminating the need for the<br />
paper manuals.<br />
You are a business analyst for OfficeFix. You have been assigned to write the requirements specification document for<br />
the Mobile Service Knowledge Base system.<br />
While you were busy on a different project, another analyst met with OfficeFix's Field Service Manager and interviewed<br />
him regarding the project. You have been provided with a transcript of that interview. Based on this transcript, your<br />
manager has asked you to prepare a preliminary list of requirements for the project. This list will be expanded and<br />
revised as you gather requirements from other sources, but it will serve as a starting point for the project.<br />
<br />
<br />
<br />
<br />
Upon completing this lab, you will be able to:<br />
Extract business requirements from customer interviews,<br />
Document business requirements so that they are objective, measurable, and testable, and<br />
Identify requirements in multiple categories.<br />
Necessary materials:<br />
All materials marked with * are already installed in your lab environment.<br />
Background information (Scenario/Summary section above)<br />
Transcript of interview with Field Service Manager<br />
(<strong>BIS</strong><strong>261</strong>_W3_i<strong>Lab</strong>_Transcript.docx; download from i<strong>Lab</strong> files folder in Doc Sharing)<br />
Template for requirements list (<strong>BIS</strong><strong>261</strong>_W3_i<strong>Lab</strong>_Template.docx; download from i<strong>Lab</strong> files folder in Doc Sharing)<br />
Microsoft Word* for writing the requirements<br />
Deliverables
Prepare a list of business requirements for the Mobile Service Knowledge Base system.<br />
Grading rubric:<br />
Item<br />
Percentage<br />
Each requirement is individually numbered. 10%<br />
Each requirement is expressed in a clear and concise<br />
20%<br />
format, preferably as a single sentence.<br />
Requirements are stated so as to be objective, measurable,<br />
20%<br />
and testable.<br />
Requirements accurately reflect customer needs as<br />
20%<br />
expressed in the interview transcript.<br />
At least 10 requirements are provided. 20%<br />
At least one requirement is provided in each of the following<br />
categories:<br />
functional, technical, performance, usability, reliability, and<br />
security.<br />
10%<br />
100%<br />
i<strong>Lab</strong> Steps<br />
STEP 1: Review background information and interview transcript<br />
Review the available information about the OfficeFix Mobile Service Knowledge Base system.<br />
Review the Scenario/Summary section above.<br />
Download and review the interview transcript provided in the <strong>BIS</strong><strong>261</strong>_W3_i<strong>Lab</strong>_Transcript.docx file in the i<strong>Lab</strong> Files<br />
folder in Doc Sharing.<br />
STEP 2: Download and open Economic Feasibility Analysis workbook template<br />
Based on the information that you reviewed in Step 1, write at least 10 specific statements of business requirements<br />
for the Mobile Service Knowledge Base system. Make sure that each requirement statement expresses a single<br />
requirement in a way that is objective, measurable, and testable.<br />
Download the file <strong>BIS</strong><strong>261</strong>_W3_i<strong>Lab</strong>_Template.docx from the i<strong>Lab</strong> Files folder in Doc Sharing.<br />
In the Functional Requirements section, write at least one functional requirement for the system. (Each functional<br />
requirement states an activity or process that the system must perform.) In the Rqmt. No. column, assign each<br />
functional requirement a unique number starting with FR- such as FR-001, FR-002, and so on.<br />
In the Technical Requirements section, write at least one technical requirement for the system. (Each technical<br />
requirement states a characteristic that the system must have because of the organization's technological<br />
environment.) In the Rqmt. No. column, assign each technical requirement a unique number starting with TR-, such as<br />
TR-001, TR-002, and so on.<br />
In the Performance Requirements section, write at least one performance requirement for the system. (Performance<br />
requirements deal with the speed, capacity, response time, or throughput of the system.) In the Rqmt. No. column,<br />
assign each performance requirement a unique number starting with PR-, such as PR-001, PR-002, and so on.<br />
In the Usability Requirements section, write at least one usability requirement for the system. (Usability requirements<br />
are those that make the system easier to work with for users.) In the Rqmt. No. column, assign each usability<br />
requirement a unique number starting with UR-, such as UR-001, UR-002, and so on.<br />
In the Reliability Requirements section, write at least one reliability requirement for the system. (Reliability requirements<br />
specify how dependable the system must be, and how it should handle errors, failures, and outages.) In the Rqmt. No.<br />
column, assign each reliability requirement a unique number starting with RR-, such as RR-001, RR-002, and so on.
In the Security Requirements section, write at least one security requirement for the system. (Security requirements<br />
deal with how user access to information is controlled.) In the Rqmt. No. column, assign each security requirement a<br />
unique number starting with SR-, such as SR-001, SR-002, and so on.<br />
NOTE: You must write at least 10 requirements in total, with at least one in each category. To write 10 total<br />
requirements, you will need to write more than one requirement in some categories.<br />
STEP 3: Save and submit<br />
Save your requirements list as a Microsoft Word file using the following naming convention: LastName_w3_ilab.docx.