Creating the proto type Skrill online payment service for an online casino
This consists of two parts:
Part 1: Overview
When the requirements and design are completed for a project, the coding can begin. A good first step in development is to use the design to create a prototype, or proof of concept for the system. The prototype helps ensure the validity of the design and demonstrates that the basic concepts in the design will provide the desired solution. Use the Design Document to guide the creation of a prototype for the integrated system.
Part 1 Expectations
The Prototype should address the following requirements:
• The prototype should match the overall design created in the attached business project document and should provide evidence that the intended design will work.
• A basic visual interface to support navigation of the program and identify the future functionality of the application.
• No subsystem functionality is required but stubs to connectivity points for subsystems should be identified and have the ability to perform basic functionality tests.
• All code should be well-documented with comments.
• The program should run without significant errors.
• Include a document called operation.docxthat describes how to operate the application.
This document should provide sufficient information to allow anyone to set up and operate the application.
Identify any external system requirements
Key parts of the application should be identified (i.e., tell where to find the important parts of the application).
This document should also provide a summary of how the prototype shows proof-of-concept for the project.
Part 2: Overview
Provide the Alpha version of the project. An alpha version of an application will have the major functionality operational but not fully completed. The purpose of the Alpha version is to ensure the major functional components of the application will work as intended. The alpha version should have connections established to all outside components and internally developed functionality should be operational at least at a fundamental level.
Part 2 Expectations
The Alpha version should address the following requirements:
• The application should match the design created earlier (See attachment) with the exception of any changes required to address problems or conform to a revised timeline.
• All major functionality should be operational at least at a minimal level.
• Connections to outside components should be functioning at a basic level to prove they will work for the final version of the application.
• The visual interface should provide access to all major functions of the application.
• There should be a demonstrable, functional connection to the required database for the project.
• All code should be well-documented with comments.
• The program should run without significant errors.
• Include a document called operation.docxthat describes how to operate the application.
This document should provide sufficient information to allow anyone to set up and operate the application.
Identify any external system requirements
Key parts of the application should be identified (i.e., tell where to find the important parts of the application and changes that have been made since the last submission).