Homework 3.docx | bartleby

Homework 3- Continuing Case: Personal Trainer, Inc

A system requirements checklist is an attempt by the systems analyst to model the organization’s information system to meet the organization’s business requirements. As an analyst, the aim should be to comprehend the task given, and guarantee the checklist made will assist with the requirements of whatever the venture may be. The analyst will have to go through facts to recover the outcomes. For the case study of Personal Trainer Inc., below is the checklist system’s prerequisite: Outputs  A single report is prepared by the Bumblebee plan, additionally the headquarters prepares the following 3 reports: a report of member sales/month, report of members who remained inactive and those who didn’t make the payment on time, a report that will show quarterly gain and loss, revealing the loss of revenue and costs for each separate activity.  A report compromising of every sale transaction is generated daily by the Bumblebee plan.  Generate a report daily, for the consumers who have paid for their enrollment levels that can participate in the tasks. Inputs  Computer workstations at every site to help keep track of activity and fitness logs, fitness coaching for seniors; also, able to utilize email, fitness blogs, Facebook, and Twitter.  A PC workstation with software that would contain Bumblebee accounting information. For cash charges and sales documenting.  Scannable ID cards to capture data.

Processes  In Chicago is the HQ of personal trainer located, which receives receivable summary of the accounts, sent by using Bumblebee by the local manager, and to the HQ are the statements of the participants made and mailed.  The fees for commodities and services are input on a pay slip, which is marked by the member.  A local bank receives receipts of cash daily, and it is further referred to the joint account of personal trainer Performance Performance requirements would focus on the system's speed, volume handling, availability and reliability. The system should be able to process the locations inputs and outputs quickly. It’s expected to handle large volumes of data from the corporate and other location users, this would include data being stored or retrieved. Also, able to securely store the personal and financial data of the members. With that comes with need for a reliable back-up system, in the event the system goes down. The management team would need to document the stats and operations reports for the data. Controls A security or control system designed to safeguard and protect the system from both internal and external compromises would be required. The system should have several checks and controls in place to limit user access to required areas. Users would be required to enter passwords to gain access to the system. For members, the system should

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

be able to track their access to premium services and bill limited members when accessing those services. Member access would be required to check in and out of clubs with an ID card that would also be used to track their activities within the club. To safeguard against unforeseen events or malicious activities, the system would be regularly backed up to an offsite third-party location. Stored data would be required to be encrypted with a high security algorithm to prevent unlawful access to data. Conclusion Incorrectly interpreting system requirements can create critical issues for the system analyst and the organization when developing a new system. Most miscalculations are created by a misinterpretation of system processes by the user, the requirement involved within the project, or from a lack of involvement from participants in the process. To correct for such inaccuracies, the project manager/analyst should actively monitor all stages of the process. This could be achieved through using project models that require iteration cycles that are actively monitored for progress and end user acceptance before moving on to the next stage.

References Tilley, S., & Rosenblatt, H. J. (2023). Systems Analysis and Design (11th ed.). Cengage Learning US. https://mbsdirect.vitalsource.com/books/9798214354095