Feasibility Study - rabeeb909/WorldClassPrototypes GitHub Wiki

Link to feasibility report here: https://docs.google.com/presentation/d/1heJI6Fi5xHA3NoF70hgvqv0LmlzRCJf9ZwKWL9T3fsw/edit

Feasibility Report

Our project is to create a new CMS website for the company, World Class Prototypes. We will be developing this CMS web application using HTML/CSS and JavaScript for the frontend design and look, while the backend will be coded in PHP and store information in a MySQL database. For development purposes we most likely be using a similar type of text editor for development, but we are also looking into HTML/CSS specific text editors that aid in the development. For testing, we will be using our GVSU webpages that we get to test our code and determine if we want to push it to GitHub, or whether it still needs some work to be done with it. For the backend database, we are currently researching and trying to find a web hosting company that provides a database at a reasonable price along with the web hosting. That way we will be able to connect our web application with their database to store the order information when outside companies come to the store and want to order prototypes.
For frameworks, we have been researching these as well and haven’t came to a for sure decision. The PHP framework I have heard a lot of good reviews is CakePHP so our team will most likely use CakePHP as the framework for PHP. We have also been researching Bootstrap to integrate their templates in with our design that we want for the website. Bootstrap is a free software where it is pre-coded for you and you just have to download it and make it work with your website and it has really nice plug ins and other things you can use to make your website look and feel a lot more professional and clean. For interface considerations and the style of the website the owner has given us multiple examples of other big prototyping companies we can go off of for design. So we have some designs to work off of for our project. Next, and more of the final step in the process will be deployment and that’s why we were focused more on the languages, frameworks, and how we were going to develop our site first. But there are obviously many hosting services out there, we are just trying to research which one supports the languages we want to use and also can provide a database that we can connect to. Rabeeb and Casey have been researching this in depth and will hopefully come to a decision by the end of the week so we can use this hosting service to test our development. And that leads us into testing; we will be testing our code a lot throughout this process to make sure that everything is working properly and has no bugs. We plan to test our code on our school webpages, but soon as we pick a hosting provider we will move our testing platform to the hosting service so we can do live testing and make sure our code is truly working. For testing, we want as many eyes on it so before pushing it to GitHub we would like the developer and another set of eyes to look and agree its ready for go live and then can be sent to the GitHub repo.
Division of labor is what we have to work through the first sprint and will hopefully be able to nail it down in the second and third sprint. None of us has deployed a website before so we are planning on trying to dedicate the entire deployment to the last sprint so we will give ourselves enough time to make sure everything goes smoothly. Our plan is divide up the work using a point system where we all kind of agree on how much points a card will be worth and then everyone taking the same amount of points per sprint and that would be the best way. We should be able to work individually on the development but will come together weekly for integration and testing purposes. The GitHub repo will be used for deployment code for the most part. We will work individually on development and in our weekly meetings we will integrate any code that needs to be integrated and then testing it and if it passes our tests then one of us will be able to push it up to GitHub and then we know it is ready for deployment.

Design of Website Owner Sent Us (What we will go off of): https://midwestproto.com/