Scenario/Summary
OfficeFix, Inc. provides onsite office equipment repair services. Customers call a toll-free number or visit a website to request a service call. OfficeFix dispatches a technician to the customer's location within two hours to perform the needed repairs. OfficeFix can repair most popular makes and models of office equipment, including photocopiers, scanners, fax machines, desktop computers, and printers.
OfficeFix's customer base has been growing rapidly, and the company has been expanding the number of makes and models of equipment that can be serviced. As a result, it has become difficult for service technicians to carry printed repair manuals for all of the different types of equipment, and time-consuming for them to find the right manual and service procedure. OfficeFix has decided to address these problems by creating a Mobile Service Knowledge Base system that will allow service technicians to call up repair procedures on handheld devices, eliminating the need for the paper manuals.
You are a business analyst for OfficeFix. You have been assigned to write the requirements specification document for the Mobile Service Knowledge Base system.
While you were busy on a different project, another analyst met with OfficeFix's Field Service Manager and interviewed him regarding the project. You have been provided with a transcript of that interview. Based on this transcript, your manager has asked you to prepare a preliminary list of requirements for the project. This list will be expanded and revised as you gather requirements from other sources, but it will serve as a starting point for the project.
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.
1. Download the file BIS261_W3_iLab_Template.docx from the iLab Files folder in Doc Sharing.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. In the Security Requirements section, write at least one security requirement for the system. (Security requirements deal with how user access to information is controlled.) In the Rqmt. No. column, assign each security requirement a unique number starting with SR-, such as SR-001, SR-002, and so on.
Attachment:- Assignment.rar