OREGON INSTITUTE OF TECHNOLOGY
Computer Systems Engineering Technology Department
Junior Project I - CST 326
James N. Long
Purvine Hall #179
Office Phone: 885-1580
Web Page: http://www.jnltech.com
(If I am in my office, my door is usually open. You are welcome to drop by at other times.)
Class: 4 Credits
Winter Quarter Schedule
Text Books: UML Distilled,Third Edition., Addison Wesley, 2000
Agile Software Development , Addison-Wesley, 2002
Any student with a disability who anticipates a need for accommodation in this course is encouraged to talk with the instructor about his/her needs as soon as possible.
A second course in a three-term sequence that covers the design and implementation techniques used for large computer software systems. Each student is required to work on a project as a team member.
Course Overview and Objectives
Upon completion of this two-term course sequence, a student will be able to propose, design, document and implement a large software project using a software development team. To do this, you will become part of a team that will propose, design,document and implement a large software project.
NOTE: You must complete CST 316, CST 326 and CST 336 as a sequence. If you drop out of the sequence, the entire sequence must be repeated, with or without credits.
Upon completion of this course, the student will be able to:
As a team be able to:
PREREQUISITES: Successful completion of CST 316
for a final quarter grade will be based on quality of an accumulated
protfolio of artifacts resulting from class activities and project
develoment. The total grade will be split 1/3 group presentation, 1/3
group artifact, and 1/3 individual. Participation in class, lab, and
team project work will be considered as part if individual grade.
Project groups and individuals will assign themselves both a mid-term
and final term grade. These grade assignment will be presented to the
instructor in a scheduled meeting and must be supported through
portfolio artifacts, group based project development, and group based
presentations. The instructor has the right to raise or lower presented
grades as negotiated in the evaluation meeting.
the project teams advance toward the final goal of creating a fully
engineered enterprise software project solution, artifacts of the software development lifecyfcle will be generated.
For the first term, the follwoing project artifacts will be created:
To get an 'A' on the Project:
To get an 'A' as a Group:
To get an 'A' as an Individual:
The lab will consist of demonstrations and tutorials related to how to use the process tools and what will be expected in each of the deliverables. Failure to attend lab will weaken your team knowledge of deliverables and tools.ANY LAB THAT INVOLVES GROUP PRESENTATIONS MUST BE ATTENDED. Exceptions must be approved by the instructor. See course rules and regulations for further discussion.
When a team is ready to turn in a deliverable, they will inform the instructor and produce the artifacts for the deliverable. Deliverable will be turned in according to any rules that accompanied the task as specified when the task was assigned.
When the deliverable is submitted via email, it must be turned in according to the following:
Any submitted deliverable not following these requirements will be put into the recycle bin. Please QA your submissions. Poor QA is not an excuse for a faulty deliverable.
The assigned text books are an important part of the course sequence. The reading chapter/article will be accompanied by a write-up turned in after the reading is done.The write-up should explain: