Full Syllabus Project Requirements
--> Spreadsheet & Database Projects
There are two student projects which you will complete. You will use both spreadsheet and relational database management system software to complete the project(s) based on a business scenario. This scenario can be from your current work place or some other management situation or based on a case study. A real world situation is required (case by case exceptions may be made.)
The projects involve using both spreadsheet and relational database software to improve management decision making and the automation of specific management tasks:
First, you need to decide upon suitable projects and scenarios. You may use a single scenario as the basis for your spreadsheet and your database projects or you may want to use different scenarios for each.
Second, submit your proposals in sufficient detail (see the course schedule), followed shortly thereafter by a more detailed outline/systems overview supported by sketches/diagrams for approval. You are then to submit a draft of your projects for my comments prior to final submission.
After the topic is approved, you will develop each project in four stages. The preliminary stages will be graded only for your information and to aid in your learning. The grade on the revised/final project will be the record grade. The following table shows several key components of your reports and the minimum level of detail/coverage at each stage of the project:
| Stages | 1. Proposal | 2. System Diagram/ Sketch w/narrative | 3. Draft & 4. Revision |
| Items to be covered. | |||
| Objectives | CCCATÜ | Visualize with sketches, diagrams, flowcharts; complement with words in outline or narrative | Programmed, Documented |
| Detailed Requirements | Summary | Visualize & complement | Programmed, Documented |
| Resources | Outline | Visualize & complement | Programmed, Documented |
| Users / Customers | Outline | Visualize & complement | Programmed, Documented |
| Assumptions | Outline | Visualize & complement | Programmed, Documented |
| Data (Input) | Outline | Visualize & complement | Programmed, Documented |
| Update Requirements | Outline | Visualize & complement | Programmed, Documented |
| Analytical Processes | Outline | Visualize & complement | Programmed, Documented |
| Queries (Repetitive) | Outline | Visualize & complement | Programmed, Documented |
| Reports & Other Outputs |
Outline | Visualize & complement | Programmed, Documented |
| Backup Strategy | Outline | Visualize & complement | Programmed, Documented |
| Audit & Test | Outline, Sample Data included | Visualize & complement | Programmed, Documented. Sample Data displayed, boundary & error conditions checked |
| ÜCCCAT= Clear, Concise, Complete, Accurate, Timely | |||
For excellent guidance on structured development of spreadsheet applications
see Senn, page 282, Figure 6.15, and the related discussion.
Similarly, for database applications see Senn, page 318, Figure 7.6,
and the related discussion.
You should also use the self-paced Cram text as a guide for techniques
and integration. Look also to the sample templates and 'Help' menus of your
software to aid you in constructing the screens and reports. Of course you have
a multitude of printed guides on microcomputer spreadsheet and relational database
programs.
Where to start? You will note that I have assigned Senn Chapters 6 &
7 out of order in Week 2. That will help some. Consider repetitive activities
in your workplace that could benefit from being automated. Look at Cram's project
text for ideas as well.
Unless otherwise excused, use the MS Office suite of programs to prepare
your report. Again, you will find that certain "reports" or products
cannot be viewed properly unless printed. You may print to file or to paper
(and then scan in the sheets) for these reports as I will need a copy of what
the customer will ultimately see. As required, follow an approved formatting,
presentation and documentation style.
Draft and Revision Stages: You should consider and address any comments
I have made on your prior submissions. Your objective is not to fully populate
either the spreadsheet or the database. You may if you wish, but the real objective
is to construct a tool with sufficient data to test its validity and reliability
for the purpose intended. So from an early stage pay close attention to your
test data, both in quality and quantity.
NOTE: If you use a program other than MS Excel or MS Access or FileMaker
Pro, please check with me to ensure I can read your files as you intended.
Use as many of the tools and strategies that you already know or will
learn in this course as possible. However, the intent of the project is for
you to demonstrate what you will have learned from the methods and techniques
presented in this course.
Where sources other than your texts are used, please include a complete
bibliographic reference and final summary of works cited. I should be able to
find any quote or paraphrase with relative ease in the original source. Just
as importantly, unless the idea, details, graphics, etc. are uniquely your own
(and presented for the first time in this report) or in that body of knowledge
termed 'general' by a non-specialist, make sure you cite your sources. If you
use some else's idea, exact words, graphics, etc., give them credit. If you
use a paper you or someone else has written for a prior class or purpose, include
it in your references. Be careful. Do not unintentionally plagiarize what has
been called 'intellectual property.'
| CAPP-340 Full Syllabus | Schedule & Assignments |
| WebTycho Guidance | CAPP-340 Index Page |
| CAPP-340 Locator Page | Phil's CAPP-340 Postings |
| Instructor Contact Information | |
| Phil Richardson; prichard@faculty.ed.umuc.edu |
Revised
8 June 2001
|