DOCUMENT REQUIREMENTS FOR QUICKBOOKS PROJECT
1. “Skeleton” descriptions of how each sub-problem is to be solved by the final system solution (describes the context for each solution to each sub-problem and when each solution would be theoretically applied). Remember that you should equally weight all of the 3 sub-problems in your design document and final system deliverables. Focus only on the system to address the sub-problems; do not create “scope creep” which involves deriving system solutions for items beyond the original 3 sub-problems. Yes, the company may have other related problems that need solving. But NO, it is not within the scope of the course project to address these. An example of a “skeleton description” would be a Powerpoint presentation without fancy graphics of backgrounds as the design for a training Powerpoint presentation.
2. Complete description of the COTS package proposed for the tracking subproblem including as much technical details as possible. Complete description of the logic, input screens, output screens, etc. for any application (in Excel or Access or other) developed as a whole or partial solution to one or more of the project sub-problems as demonstrated by flowcharts, data flow diagrams, and/or other technical descriptions of the functionality of the solution to a given sub-problem. Remember that the group will ultimately be building a system to address the problem of tracking the security of the data/files that are remotely handled by employees (which is one of the sub-problems of the project) from this design document.
3. Finalized protocols, rules or policies developed for any sub-problem (written out in plain language before conversion to a documentation, presentation, or training format). Finalized data dictionary for any application developed as a whole or partial solution to one or more of the project sub-problems
4. Finalized description of how security is to be maintained for each of the sub-problem solutions (in other words, how do you ensure that would-be hackers from inside or outside the company do not compromise each of the sub-problem solutions)
5. Complete description of the design for all training, advertising, websites, etc. proposed as part of the marketing plan for showing current and future customers that their information will be secure. (May want to have two sets, one of future and another for current customers).
6. These documents (in total) typically run 10 pages in length (or more). This is the most important deliverable of the semester. Another group should be able to take the design document and build/implement all of the solutions to the subproblems as your group envisioned it without any additional information. That is the level of detail and work required for this document.