Posted: February 28th, 2023

Pilot Implementation Report

Create a 2–5-page pilot implementation report for your company’s IT executive that addresses the following:

Week 8 Assignment – Pilot Implementation Report

Overview

The prototype you created for the project app has been approved, and it’s now time to run a pilot test in the field to uncover potential issues. For this assignment, you will create a report describing the resources you’ll need to implement your test and a user acceptance checklist that ensures the app meets requirements.

Instructions

Now that your app has been prototyped, your team will host a live deployed test at the San Antonio, TX, field office that will validate the function, usability, accessibility, and security of the app. Fifty people will test it, including field agents and their managers.

Create a 2–5-page pilot implementation report for your company’s IT executive that addresses the following:

·
Craft an executive summary that states the purpose of the report, as well as a conclusion paragraph that ties everything together.

· Describe the resources necessary to validate the application in a functional environment not co-located with the production/testing facility but instead at an operational location elsewhere in the United States—in this case, the San Antonio field office.

2. Include all the human resources (support staff in addition to the testers) needed to implement this test.

1. Provide the rationale for needing these resources, supported by research.

2. Include the physical hardware and software you will need to provide for all 50 testers.

2. Provide the rationale for needing these resources, supported by research.

· Explain how long you will run the pilot test and why.

· Design a pass/no pass user acceptance checklist that validates functionality and features, per the specifications for the app. Use an Excel spreadsheet to create your checklist. You may either paste the checklist into your report or submit it as a separate document.

· Incorporate a minimum of three credible and relevant resources to support your plan.

Running head: PROTOTYPING PLAN 2

PROTOTYPING PLAN 2

Prototyping Plan

February 08, 2023

Prototyping Plan

Executive Summary:

This report outlines the plan for developing a Section 508-validated application for U.S. Department of Homeland Security field officers to check potential immigrants for connections to criminal or terrorist behavior. The application must conform to Section-508 accessibility guidelines, allow wireless real-time bidirectional data transfer, and have a secure login and autolocking feature. The officers work in various environments, including offices, vehicles, and on foot along the U.S. border and in cities across the country. The report provides details on the interface choices, input/output methods, supported devices, error processing, security implementation, software tools, automated tools, and UX prototyping techniques. Finally, the report includes two Visio drawings that depict the user display and the system processing flow.

Interface Choices:

For the interface of the application, we have decided to use a GUI (Graphical User Interface) interface. This choice was made based on research that shows that a GUI interface is easier for users to navigate, as it allows for the visual representation of options, reducing the likelihood of user error. Additionally, a GUI interface also provides a more visually appealing interface that is easier to understand, making it more user-friendly.

Methods for Input/Output:

The input and output methods for the application will include both mouse and keyboard inputs, as well as touch inputs for devices that support touch input. The output will be displayed on the screen, providing visual feedback to the user. This choice was made to support a variety of devices and to ensure that the application is accessible to users with different abilities.

Supported Devices:

The application will be supported on desktop computers, laptops, and mobile devices, including smartphones and tablets. This choice was made to accommodate the needs of officers who may work in different environments, including offices, vehicles, and on foot.

Error Processing:

To process user mistakes and errors, the application will use a combination of error messages and pop-up notifications. The error messages will be displayed in clear language and provide clear instructions on how to resolve the error. The pop-up notifications will be used to provide additional information or clarification to the user. This approach was chosen to ensure that errors are handled in a clear and user-friendly manner, reducing the likelihood of user frustration, and increasing user satisfaction.

Security Implementation:

To ensure the security of the application and the sensitive information it processes, the application will implement the following security measures:

· Secure login: The application will require a secure login with a strong password to access the application.

· Autolocking: After two minutes of non-use, the application will automatically lock, requiring a secure login to access it again.

· Data encryption: All data transfer and database queries will be encrypted to protect sensitive information from being intercepted during transfer.

· Regular software updates: Regular software updates will be performed to ensure that any security vulnerabilities are addressed.

TOOLS AND TECHNIQUES:

The DHS application will use a combination of software tools and techniques to ensure its development and deployment. The following tools will be used in the development process:

JIRA and Bugzilla: These software tools will be used to determine programming bugs in the DHS application. JIRA and Bugzilla were chosen based on research that indicates that they are effective tools for tracking and fixing bugs in software development.

Software Tools for Debugging:

· JSLint: JSLint is a popular JavaScript code quality tool that helps to detect potential programming bugs and coding errors. It checks for syntax and formatting issues, enforces coding standards, and identifies potential security risks.

· GDB (GNU Debugger): GDB is a powerful debugger tool that can be used to debug any application written in C, C++, Fortran, Ada, and other programming languages. GDB can help developers detect and correct errors in the code, making it a crucial tool for ensuring the reliability of the application.

Automated Tools for Accessibility Validation:

· NVDA (Nonvisual Desktop Access): NVDA is a free, open-source screen reader that helps to validate the accessibility of the application.

· WAVE: WAVE is a free online tool that helps to validate the accessibility of web pages.

UX Prototyping Techniques:

· Wireframing: Wireframing is a technique used to create a visual representation of the user interface (UI) of the application.

· User Testing: User testing is a crucial technique for evaluating the user experience (UX) of the application.

Diagrams:

Login Screen

Search Screen

Output Screen

Fig 1: User Screens

Fig 2: Flow Diagram

Sources:

1. Cooper, A. (2007). The essentials of interaction design. John Wiley & Sons.

2. Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design, Revised and Updated: 125 Ways to Enhance Usability, Influence Perception, Increase Appeal, Make Better Design Decisions, and Teach through Design. Rockport Publishers.

3. Blattner, M. M., Stuart, D. S., & Hu, Y. (2017). Human-computer interaction: Development process. Springer.

4. Molich, R. (2010). User testing. In Usability Evaluation in Industry (pp. 71-90). Springer, London.

image1