OREGON INSTITUTE OF TECHNOLOGY
Computer Systems Engineering Technology Department
Junior Project I - CST 326
Winter 2014

James N. Long

Office:                              Purvine Hall #179
Office Phone:                   885-1580
Email:                               james.long@oit.edu          
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.

COURSE DESCRIPTION

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

EVALUATION METHODS:


Evaluation 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.


As 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:

  1. Refined Business Case
  2. Use Case Specification
  3. Use Case Architecture
  4. Use Case Model
  5. Software Requirements Specification
  6. Requirements to Use Case Map
  7. Use Case Associated Sequence Diagrams
  8. CRUD Matrix
  9. Refined Class Model
  10. Business Case Challenge
  11. Architechtral Prototype
  12. Gantt Chart
  13. Bi-Weekly Status Reoprts
  14. Gantt Chart Updates
Inidividual artifacts created in software development process are:
  1. Article Summaries - Agile Development, Technical Journal, Trade Journal
  2. Use Case Expansion
  3. Technical Demonstration
Team presentations that must be done are:
  1. Architectural Prototype Presentation
  2. Bi-Weekly Sprint Demonstrations
It is the responsibility of individual students and project groups to submit artifacts for feedback. Artifacts that have not had a feedback submission will not be included in the evalatuion protfolio. All artifacts must be submitted to continue on to the next course in the sequence.

GRADING:

To get an 'A' on the Project:

  1. Complete all project deliverables to a fine level of detail, producing all deliverable line-items.
  2. Fully implement all top priority requirements as determined by your team members and the instructor.
  3. Deploy the end project in a manner acceptable by your project sponsor.

To get an 'A' as a Group:

  1. Complete all of tasks accurately and to the highest level of detail. Leave no stone unturned.
  2. Prove the quality of your artifacts through a self audit.
  3. Attend all meetings, demos, and presentations.
  4. Keep project timeline and scrum boards up to date.
  5. Complete weekly progress reports.

To get an 'A' as an Individual:

  1. Attend all meetings, demos, presentations, etc.
  2. Complete all assigned tasks on time shwoing high quality effort.
  3. Attend lectures regularly.
  4. Actively support your group.
  5. Do more than assigned tasks.

Lab Attendance:

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.

Project Deliverables:

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:

  1. Email Subject Line must have: CST 326 - "Deliverable Name" - "Team Name" . Deliverable Name should be the name of the deliverable submitted - see Task Descriptions for details. Team Name should be the name of the team.
  2. The actual deliverable should be archived in a Zip file (...not rar...not sft....) and attached to the email. Attachments larger than 20Mbyts should written onto a CD and placed in a sealed envelope the instructors mailbox with a date and time stamp from the secretary.

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.

Reading:

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:

  1. Major topic(s) covered by the chapter/article.
  2. How the topics are relevant today in software engineering.
  3. How the topics will apply to software development in CST 326/326/336
  4. Agreemnt or disagreement explained ans supported.