You are in the process of implementing a new release of information (ROI)/accoun

ID: 3604628 • Letter: Y

Question

You are in the process of implementing a new release of information (ROI)/accounting of disclosure system. You hae an existing computerized release of information system, so the employees are comfortable with the technology- they just have to learn how to use the new one.As part of the implementation plan for the new ROI/ accounting of disclosure system, you will need to develp a testing plan that should include the following:

1.Testing that needs to be conducted prior to implementation.

2. A minimun of 6 scenarios that you would encounter when using the system during testing.

3. List of resources needed to complete the testing

4. What to do when a problem is identified

5.How you will know the system is ready for implementation

6. Who Should be included in the implemetation of the testing plan.

Explanation / Answer

The below table describes all test cases that should be in the testing plan,

Each major function performs as specified in user manual.

Design changes/customizations are present and work as requested. Document all changes for future reference (2.1 Change Control).

Screens appear as expected, including content and placement of all fields, codes, drop down menus, and messages. See Screen Design section of 2.1 System Build.

No spelling errors or color changes. Icons are readable.

Appropriate representation of content can be printed if necessary for legal purposes.

Entries that have been corrected and their corrections are both displayed accurately.

Fields edits (e.g., valid values, optionality, defaults) function as expected.

Workflows send and/or receive data properly between systems (e.g., between EHR and pharmacy or billing, PMS messages and EHR). Use scripts to test various scenarios.

Interfaces between applications move data correctly and completely. Test both sending and receiving when interfaces are bi-directional.

Connectivity with external organizations is accurate and complete as authorized (e.g., portal access to/from hospital/clinic, continuity of care record to referrals, personal health records for patients, disease management to/from health plan).

System access is appropriate per assigned privileges. Test attempts to gain access when not authorized .

Data are processed accurately, in graphs, tables, claims, client summaries, reports, etc.

Data correctly populate registries, reporting warehouses, etc.

->People ( Normally a project team is a group of people)

->Capital (Your project needs money, because it will need to pay for things,)

->Material Good (Projects also use up assets. Assets, or goods, vary from project to project but it’s highly likely that your project will need some kind of tangible resource.)

Example:

Software licences

· Hardware like technical infrastructure such as cabling or switches for the IT equipment

· Equipment or machinery (which you might hire for the life of the project or buy)

· Property (again, it might be something you hire for the project such as a temporary cabin on a building site).

Bug Title title of bug help to identify bug in one line description

Bug identifier: It is auto generated unique ID helps to identify the bug.

Status: This field indicates the actual status of the bug in the Bug life cycle. LIke New, Assigned, Resolved, Reopened.

Bug Assignee: This is the name of the developer who is responsible to resolve the bug.

Reported On the date when bug is identified.

Bug Type: The bug is categories into different category like Functional, Navigational, GUI etc.

Environment: On which OS, platform this bug is occurred.

Component: This field indicates the sub modules of the product.

Priority: Necessarity to fix the bug?
Priority can be set as P1 to P5.
The P1 means “ i.e. priority is highest” and P5 means “Low priority, No urgent, when get time then fix it”.

Severity:This tells you about the impact of the bug.

When all test cases are performed.

Whole life cycle of testing are performed.

The performance of system is matched to bussiness requirement.

All high priority (risky) bugs are resolved

Alpha & Beta testing are performed.

Test Componont Timing Accepted Unit & Functional Testing