This assignment is about producing a feasibility study for your project!

Background:

Projects:

  The goal is to develop a software project for an actual client who
  would use it in the regular course of business or entertainment. We
  will ultimately be working through the beginning of the software
  development cycle, focusing mostly on the pieces required to make
  software successful more so than the actual coding and development
  aspect. Unfortunately, this means largely using a waterfall
  model. We'll investigate why this is perhaps not the most optimal
  throughout the semester as we use parts of this model.

Planned Deliverables:

   Feasibility Study
   Requirements
   Specification
   Prototype

In this assignment we will be focusing on the feasibility study and a
bare bones plan.

Feasibility Study:

  Your job is to write a feasibility study that describes your
  project. Remember that clarity is very important and thus a portion
  of your grade will depend on being clear and concise. This study
  should be 4-6 double-spaced pages when complete. Do not shoot for
  page count but rather focus on the details required of the
  feasibility study while being clear and concise. Your study should
  include the following elements:

 - The client - who, what, why

 - The client type

 - Visibility plan 
        - How to keep other teammates up to date?
	- How to keep in contact with the client?
     	- How to keep the professor up to date?

 - What are you doing? What is involved in the project. Be detailed
   here. Be sure to take into account scope. What are the boundaries
   or functions that will not be implemented? What will be
   implemented?

 - Preliminary requirements analysis. Some of this is flushed
   out by the previous bullet. However, you should examine the
   system's services, constraints and goals as viewed by the client in
   this step. Examine any licensing required.

 - Suggested deliverables - What will you be providing the client? A
   rough plan will follow later, so in this step you can just discuss
   the deliverables and then follow up with the plan.

 - Plan - Show main tasks, milestones and deliverables and their
   expected delivery dates. This should be a rough outline that
   includes this course and beyond assuming continued production.

 - Copyright and Licensing - Open source and other
   considerations. What licensing will your software follow. Give some
   description and explanation.

 - Risk. What can go wrong? How will problems be detected? How will
   problems be reported? What are the fall-back options? What
   obstacles might exist to prevent

 - Alternatives. What are the alternatives? Either to resources chosen
   or to the project as a whole. What already exists in the
   market/infrastructure? How could you modify the product to make it
   better than what is proposed or to solve problems differently than
   proposed.

 - General. A general guide to how the project will be completed must
   be offered. If you will use some hardware, you must include a
   plan. If you will use some data, you must provide a plan to
   acquire. If you will solve some problem, you must give one avenue
   of that solution.