Scope of Work
The following scope of work is what we have envisioned for this web application.
The Creation Process.
The purpose of this document is to describe the essentials of our vision as well as to provide the goal and scope of the project. The document contains a high-level technical aspects of the project. For practical purposes, we’ll code name the project “eWIZARD.”
eWIZARD is a piece of software that would basically update and add a proprietary file to a very popular, open source software platform. We are envisioning an automatic script capable of performing several independent steps with a current platform already on the users device. For instance, the eWIZARD would be able to open the platform program. Then, make the appropriate clicks within the residing platform and install a file that is within the eWIZARD package. After successfully installing the related file, the eWIZARD would perform a “clean up” operation and delete the related file installed on the platform from the users device. Then user would then need to power down the device and restart. On restart the platform would show the effects of the downloaded file.
Legality and Non-Compete.
eWIZARD is a pseudonym for the official product and is NOT the end product the development team will be working on. We have created this scope of work to clearly define the software we are looking to produce. Our company shall provide a standard Non-Compete Agreement to be signed by both parties for legal framework establishment to protect both our company and your company. The contract provisions additional agreements and appendices, which specify the details and address project specifics like cooperation model chosen, project plan and schedule, project scope, acceptance criteria and so on. We cannot discuss the official product with you or your team unless we have an executed Non-Compete Agreement. After both parties have signed the agreement, a kick-off meeting shall be held via Skype and resource situation will be established.
User Stories: The following are user stories created on the envisioned functionality of the end product.
1.0 AS A PAID USER I CAN:
1.1 Have access to more content that the standard platform allows.
Purchase Flow: The Purchase
We envision these would be the steps from purchase to installation. The customer would see the product featured on our website. Make the decision to purchase a copy of the software. Pay for it online via our credit card gateway. Once approved the gateway would send the end user to a one-time valid URL to download the software. After downloading it the URL would be invalid and unusable to retrieve future copies.
Purchase Flow: The Installation
Once the user downloads the software to the device they would execute the eWIZARD. The eWIZARD would open the residing open source platform (program) and proceed to run a script that would perform 8 to 10 clicks from within the software platform. Upon completed installation the eWIZARD would self delete removing itself and the proprietary file along with it. This way, the software could not be shared with non-paid users.
Assumptions and Constraints: All proposals on this project are based on the following assumptions:
• The “residing platform” program is open source and easy to get
• Ability to work with our credit card gateway to help with the one time download URL
• It assumes the end user has the residing platform pre installed on their device
Reporting and Tracking Process: Reporting and Progress Tracking are implemented on daily and weekly basis by email and with the help of online collaboration tools such as; Basecamp. The Weekly Report details project progress since previous week, lists current issues that needs to be addressed.
• Each week our company shall receive a summary of work done report via eLance