Course Syllabus (2005 Fall Term, Nov -
Feb)
Course Title: Senior Project
Course No: CIS433P Contact Hours: 3 Credit Hours: 3
Prerequisites: Upper-term standing
Course Instructor: Dr.
E-mail Address: [email protected]
Web Site: http://www.geocities.com/grg_lai
http://eclipse.fre.devry.edu/~glai
Office Hours: Tuesdays, Wednesdays, Fridays 10:001m – 11:00am
Thursdays,
Class Meetings: Wednesdays
Course Description
Working in teams, students
apply knowledge and mastered skills, including problem-solving techniques and
project-management methods, to an applications-oriented project. The project provides real-world experience by
integrating systems analysis, programming, testing, debugging, documentation
and user interfacing techniques.
Terminal Course Objectives
1. Given an outside-provided or alternative case project, practice the analysis, design, development, and implementation of a complete computer-based system.
2. Given a project, work in a project team of students to solve a business and information processing problem using project management’s organizational concepts, resource planning, and control (reporting).
3. Practice (or shared the practice) the leadership and interpersonal skills necessary to manage/supervise a team in accomplishing and completing a specified project objective.
4. Select, use a structured systems development process to accomplish the project.
5. Develop a team Planning/project Chart (time-scaled) using task identification and estimating skills, using such to successfully complete the business project within a term. Establish a time budget for the cost of the project.
6. Apply project status reporting, both oral and written, weekly using the Project Plan (Gantt, PERT, or other planning tools). Use a project management software package to assist in planning and reporting.
7. Present findings/recommendations/assignment deliverables orally and in writing to user or simulated user at an executive management level, using communication and presentation skills, seeking approval to proceed.
8. Develop alternative solutions for the defined problem including cost/benefit studies of each. Select a feasible solution using established feasibility analysis techniques.
9. Use specific documentation techniques to document the new system, programs, and user-oriented instruction manuals. Do same for existing system. Maintain a team Project Manual for all documentation including organizational and product flows, information flowcharts, data flow diagrams, process narratives, and system flowcharts.
10. Direct the planning, implantation of testing a system at unit, system, and user levels required by the project.
Approach
The class format will simulate working in a
professional, technical, project environment. At the beginning of the
term, class time will be used to provide introductory information. Afterwards,
the class time will be spent running project management meetings and project
status presentations. Communications between the professor and student
project teams will primarily be via group meetings, emails, and presentations.
Guidelines
and Schedule
1.
Project group meetings will be held every week during the term and will follow
a published Project Management Schedule. All team members must attend the
meetings and presentations. Each missed meeting will result in a zero for
the team member. Tardiness will be managed by each team leader and will
result in a reduction in the individual students’ score.
2.
The CIS Senior Project Review Board prior to the start of the class should have
approved the Project Proposal. However, if the project has not yet been
approved, the instructor should be notified immediately and an expedited
approval process should begin.
3.
All projects must have a written Letter of Engagement signed by the client and
a copy of such letter must be in the instructor’s file. Your
project will not be considered as approved until a signed Letter of Engagement
is filed with the instructor. A project without a Letter of Engagement
will not be accepted.
4.
The client must be sufficiently identified to allow open contact by the
instructor. Clients may be contacted by the instructor using the
telephone, email or with face-to-face meetings to monitor the progress of the
project.
5.
Each project team will maintain Weekly Status Reports to provide substantive
evidence of the project work performed and of each individual’s
contribution. A budget with codes for each type of work will be updated
on a weekly basis. A budget vs. actual report will be updated weekly, and
presented for review to the technical advisor.
6.
The professor will act as Senior Project Manager for the class. He/she will
assess the team’s progress on a weekly basis. However, project teams are
expected to communicate weekly with their technical advisor who will be
considered a Senior Project Consultant.
7.
On or before week 13 the team will meet with its client to deliver the Final
Report and the completed project. A copy of the Letter of Completion must
be attached to the Final Report. The client will sign this letter to
signify that material he/she expected as deliverables has been received.
This Letter must be handed in to the instructor.
8.
The client must also complete a Client Evaluation Form that is e-mailed to the
client by the instructor. The completed project belongs to the client and
your client has the right to further develop the project to suit his/her own
use.
9.
On week 13, the team will be required to present their project to the academic
community. In addition, all project teams are required to present their
projects during Technology Day.
10. The student project manager is responsible
for any changes in design and/or scope of the project. A Change Control
Form must be submitted and approved by the CIS Senior Project Review Board and
the client.
11. The project
Repository and all other required project materials will be submitted to the
University and retained for future use and reviewed by the University and its
students. The University will retain full rights to the retention and use of
these materials including the right to modify, revise, or change any portion or
component for the needs of the institution or its programs.
12. Additional information
regarding requirements, deliverables, roles, and responsibilities are
provided in the Senior Project Handbook.
Grading Policy
A
letter grade will be given to your final score that is based on the following
grading schemes and member evaluation:
|
Weekly Status Report |
20%
(Instructor) |
|
Final Project |
|
|
Industrial Assessments (Tech Day) |
10%
(Industrial Judges) |
|
Client Evaluation |
10%
(Client) |
|
Tech Judges Evaluations |
20%
(Judges) |
|
Tech Advisor Evaluation |
10%
(Tech Advisor) |
|
GE Advisor Evaluation (Final Report) |
10%
(GE Advisor) |
|
Total |
100% |
A for 90%
- 100%
B for 80% - 89%
C for 70% - 79%
D
for 60% - 69%
F for
< 60%
Class Change Policy
It
is essential that all members of a Senior Project Team be enrolled in the same
CIS 433 section. You will have one week to make class changes, if all
members are not in the same section. Otherwise, no changes from one
section to another will be allowed during the term.
|
Milestones |
Items / TCO |
Responsible Party |
Students Output |
|
Weekly |
Weekly Status Report / 6 |
Instructor/Tech Advisor |
Status of project |
|
Week
1-2 |
Concept Approval / 1, 2 |
Instructor/Tech Advisor |
See Concept Approval Form |
|
Week
3 |
Letter of Engagement |
Client |
See Letter of Engagement Form |
|
Week
4 |
Change of Design |
Instructor/Tech Advisor |
Include formal request |
|
Week
5 |
Planning Document / 2, 3 |
GE Advisor/Instructor |
Report Contents to GE
Advisor/Instructor |
|
Week
6 |
Analysis Document / 4, 5, 7 |
GE Advisor/Instructor |
Prelim Report to GE
Advisor/Instructor |
|
Week
7 |
Project Go or No Go |
Tech Advisor/Instructor |
Report to instructor |
|
Week
8 |
Complete PAD / 7, 8 |
GE Advisor |
See PAD Document, Report to
Instructor |
|
Week
9 |
Prepare Rough Demo |
Instructor |
Provide Rough Demo to
Instructor |
|
Week
10 |
Demo I |
Instructor |
Provide Demo I to Instructor |
|
Week
10 |
Project Go or No Go |
Tech Advisor/Instructor |
Report to Dean |
|
Week
10 |
Draft Final Report / 9 |
Tech & GE Advisors |
Report to instructor |
|
Week
11 |
Demo II |
Instructor/Tech Advisor |
Provide Demo II to Instructor |
|
Week
11 |
Final Report for Review / 10 |
Tech Judges |
Report to instructor |
|
Week
12 |
Dry Run |
Instructor |
Provide Presentation to
Instructor |
|
Week
12 |
Letter of Completion |
Client |
See Letter of Completion Form |
|
Week
13 |
Repository and Final Report |
Assessors |
Report to GE
Advisor/Instructor |
|
Week
13 |
Tuesday, Proj Presentation |
Instructor |
Final Presentations |
|
Week
13 |
Wednesday Tech Fair |
Industry Judges |
Formal Presentations |
According to DeVry policy, each student is required to attend every lecture in the course.
If a student misses a lecture, then it is the responsibility of the student to determine what work was missed.
Be aware that some exam
material may come from lectures, in-class assignments, and class discussion
that are not covered in your text.
You are responsible for notifying your instructor of planned absences,
and for fulfilling course requirements missed during an absence.
Working with your team members to discuss and solve the homework is strongly encouraged. However, the submitted solutions must be your team work, using your team words. Academic misconduct (i.e. cheating, plagiarism, etc.) will NOT be tolerated with regards to analysis, design and coding during the course! If your team violates the academic integrity policy by gaining advantage over others through unfair means, your team will earn a non-pass grade. All teams are expected to follow the academic honesty policy.
What IS cheating?
What is NOT cheating?
All
teams are expected to follow the academic honesty. Academic honesty is violated when teams gain
advantage over other teams through unfair means. When teams violate the
academic honesty, they get a non-passed grade.
For more details, refer to DeVry Student Handbook.