CET 4429 Project Information
Introduction
The CET 4429 project is a group project that should involve groups with 1-5 (max of 5) students per group. The project will involve the design of a database backend to support a set of supplied from end specifications.
Group Creation
Students may form groups during the frst two weeks of class. During this time any group consisting of the correct number of students may be mailed to the course instructor and the group will be setup inside WebCT. At the end of two weeks all students not assigned to a group will be assigned at that time.
Group Communication
The group will have a specific bulletin board set up within WebCourses for the group. The group should set up a communications plan to ensure that all group members are aware of all group deadlines and requirements. The final project turn-in will be a wiki (you may use PBwiki or any other wiki service) which contains all project documentation. Any wiki that you choose to use (and most have this feature) must allow me to make page level comments to the pages.
Project Requirements
All projects will have documented;
- Background requirements
- Who are the stakeholders?
- Why are you building this system?
- Who will use it?
- What does it do?
- Data Dictionary
- FIeld Name
- Field Description
- Data Type
- Data Lifecycle (where is data created? where does it end up? Who uses it?)
- Restricted access (role access) for read and write
- Database Schema Diagrams
- Database Schema Scripts
- Simple SQL Script for DB Creation
- Schema of all views (and diagrams)
- Script for any views
- Schema Diagram for any Views
- Documentation of all stored procedures
- Stored Procedure Code
- Purpose of stored procedure (can be included in document)
- Written by - can be comment in SP
- Documentation of coded fields and code plan
- Any fields stored codes, must include all codes and descriptions
- Ensure you double check against schema - I will look for coded fields
- Security plan (roles and acess levels to tables, views, stored procedures)
- List all roles and user types.
- Who has access to what? (roles accessing table, view, stored procedure)
- How will appropriate access be ensured?
- Indexing plan and maintenance plan
- What will be indexed?
- How will you monitor performance?
- Who will be responsible for maintaining?
- What access will Maintenance have?
- Proof of deployment in approved database product
- A simple capture of SQL server, Oracle, MySQL that shows DB
Where to get Ideas
It is recognized that not everyone in the class in groups will have access to specifications that will allow them to perform the design for this class. To help with this the class project groups are welcome to use any of the published specs from the SAGE project located at http://ucf-sage.pbwiki.com/ . At this site simply click on SAGE Methodology and you will have access to technical requirements for a number of government processes. Feel free to use any of these as your base for a database development.
Project Submissions
Submission 1 (P1)
- All groups will submit materials on the Group wiki page at http://ucf-ist-students.pbwiki.com/CET-4429-Spring-2009-Projects
- Your group wiki page should have (for P1)
- Your group members
- Title of Group Project
- Description of Group Project
- Duties of Group Project Members
Once completed, you will submit the link http://ucf-ist-students.pbwiki.com/CET-4429-Spring-2009-Projects in Web Courses (as a group) - I will find your information from there.
Submission 2 (P2)
This is the final submission. It will consist of 3 parts
1. Your completed project - this will be what you committed to in assignment 1. Web site, design, or what you were doing as your project.
2. Your documentation - can be submitted as a word doc, or a pdf, or a web site.
3. Presentation - You must have a (less than 10 minute) video submitted on Youtube (that will keep you under 10 minutes)
Other Project Ideas
These are ideas for project that I have developed that are about the correct scope for this class project.
Spring 2009 Groups
Spring 2008 Groups
Comments (0)
You don't have permission to comment on this page.