DEFINE A TEST PLAN OR SCRIPT IDENTIFYING MAJOR SOFTWARE FUNCTIONALITY AND HARDWARE TO BE TESTED WITH REQUIRED OUTCOMES.

DEFINE A TEST PLAN OR SCRIPT IDENTIFYING MAJOR SOFTWARE FUNCTIONALITY AND HARDWARE TO BE TESTED WITH REQUIRED OUTCOMES.
Write a 1,400- to 2,100-word draft of the third section of your SDLC Final Project. Include the following:
• Testing process summary
o Define a test plan or script identifying major software functionality and hardware to be tested with required outcomes.
• Installation process and training plan summary
o Provide a timeline identifying specific steps, including training, and related resources required to implement the recommended system. Include a narrative explanation with a discussion of effects of project constraints—such as time, conversion method, and so forth—and a description of the recommended plan.
• Documentation plan summary
o Specify and explain each type of documentation, which is required for ongoing technical and user support of the proposed system.SDLC Project – Team CDwana Escourse, La Shauna Berry, Nicholas Felix, Rajesh ThakurBSA/376September 7, 2015Deborah MarshallSDLC Project – Team CThe process of determining requirements involves the analysts and other team members to gather information. This information is used to figure out exactly what the new system should do, and this information is obtained from as many sources as possible. Examples of these sources are: observing users, reports, previous analysis records, questionnaire forms, previous or current developers, present system procedures, and system administrators. There are several methods of determining requirements and some of those traditional techniques for collecting requirements are:Interviewing and actively listening to othersAdministering questionnaires to providers and end usersObserving system usersAnalyzing current system proceduresReviewing present and previous documentsAfter using these methods of determining the specific requirements for Patton-Fuller, the analysts on this project team were able to provide a list of confirmed requirements. Along with the list, the team has categorized each system requirement identified as either mandatory or optional. The list includes the following:Manage and track the appointments of patients – MandatorySchedule, reschedule, or cancel appointments – MandatoryCheck patients in and out – MandatoryView physician’s schedules for open appointments – MandatoryTrack patients for follow-ups and schedule those dates – OptionalReferrals – OptionalShare information (EHR) with other departments – optionalWeekly physician schedule report and comparative analysis report – OptionalPatient pre-op and post-op schedule report – MandatoryPatient to physician time ratio – OptionalMonthly billing report – MandatoryThe flow chart listed below reflects the proposed flow of the process upon completion of the project. The previous process from beginning to end consumed more time than it needed to. This document will identify a process, and the designed flowchart gives a graphic view into the process that the team is looking to perfect it to become. Designing a flowchart for the process should be completed in order to identify the amount of time, redundancy of calls made to and from the patient, and initiate ideas to make the process more efficient.

 
. .

The post DEFINE A TEST PLAN OR SCRIPT IDENTIFYING MAJOR SOFTWARE FUNCTIONALITY AND HARDWARE TO BE TESTED WITH REQUIRED OUTCOMES. appeared first on bestnursingtutor.com.