BIS 261 DeVry Week 3 I Lab Latest

Prepare a list of business requirements for the Mobile Service Knowledge Base system.
Grading rubric:
Item
Percentage
Each requirement is individually numbered. 10%
Each requirement is expressed in a clear and concise
20%
format, preferably as a single sentence.
Requirements are stated so as to be objective, measurable,
20%
and testable.
Requirements accurately reflect customer needs as
20%
expressed in the interview transcript.
At least 10 requirements are provided. 20%
At least one requirement is provided in each of the following
categories:
functional, technical, performance, usability, reliability, and
security.
10%
100%
iLab Steps
STEP 1: Review background information and interview transcript
Review the available information about the OfficeFix Mobile Service Knowledge Base system.
Review the Scenario/Summary section above.
Download and review the interview transcript provided in the BIS261_W3_iLab_Transcript.docx file in the iLab Files
folder in Doc Sharing.
STEP 2: Download and open Economic Feasibility Analysis workbook template
Based on the information that you reviewed in Step 1, write at least 10 specific statements of business requirements
for the Mobile Service Knowledge Base system. Make sure that each requirement statement expresses a single
requirement in a way that is objective, measurable, and testable.
Download the file BIS261_W3_iLab_Template.docx from the iLab Files folder in Doc Sharing.
In the Functional Requirements section, write at least one functional requirement for the system. (Each functional
requirement states an activity or process that the system must perform.) In the Rqmt. No. column, assign each
functional requirement a unique number starting with FR- such as FR-001, FR-002, and so on.
In the Technical Requirements section, write at least one technical requirement for the system. (Each technical
requirement states a characteristic that the system must have because of the organization's technological
environment.) In the Rqmt. No. column, assign each technical requirement a unique number starting with TR-, such as
TR-001, TR-002, and so on.
In the Performance Requirements section, write at least one performance requirement for the system. (Performance
requirements deal with the speed, capacity, response time, or throughput of the system.) In the Rqmt. No. column,
assign each performance requirement a unique number starting with PR-, such as PR-001, PR-002, and so on.
In the Usability Requirements section, write at least one usability requirement for the system. (Usability requirements
are those that make the system easier to work with for users.) In the Rqmt. No. column, assign each usability
requirement a unique number starting with UR-, such as UR-001, UR-002, and so on.
In the Reliability Requirements section, write at least one reliability requirement for the system. (Reliability requirements
specify how dependable the system must be, and how it should handle errors, failures, and outages.) In the Rqmt. No.
column, assign each reliability requirement a unique number starting with RR-, such as RR-001, RR-002, and so on.