Header image
Junior Project I
line decor
Jim's Schedule  :: Calendar  ::  
line decor


Writing code is just the beginning piece of building good, industrial strength, software. Software is complex, unmanageable, and constantly evolving according the desires of coders, users, and project fund providers. How can such a multi headed beast be tamed? A good sound process is required along with adaptive rules for building software systems. Most importantly, all parities involved need to agree on what is being created. Communication is key.

To set the stage...

You are standing on the edge of a vast sea of cubicles. You have nothing more than pencil and paper. There is the sound of keyboards clicking and the hushed drone of intermingled conversations. In the corner, there is an intimidating looking man with clipboard in his hand looking at you.....

Late Arrival Policy:

In a corporate environment, being late can be a serious offense. It can cost a company several thousands of dollars as engineers and resources sit idle waiting for you arrival. This term, showing up late to a scheduled meeting will result in the throwing of a dice to determine the outcome of your late arrival consequence (unexcused absence is considered really late - see rules and regulations for exceptions). Consider a scheduled meeting to be a regularly scheduled class time or lab time when there have been no special announcements related standard operations. The number of the thrown dice will correspond to the following outcomes:

  1. CEO has a personal emergency. Meeting is delayed.
  2. Your late arrival has caused assignment of an extra task to you. It is due at a time determined when the assignment is made. If you choose not to complete the task, 1 grade point will be deducted from your overall grade. You will present the results of the task at the meeting time following the due date.
  3. You are being put on time-clock probation. The next time you are late to a scheduled meeting, you will receive a .5 grade point deduction from your overall grade.
  4. You will be required to do a testing or a QA task for the team with the closest scheduled deliverable task. The team for which you are helping out will determine how fit your work is. Unsatisfactory work will result on a .5 grade point deduction based on final evaluation of the instructor.
  5. Meeting is canceled due to venue issues.
  6. Recite the agile manifesto for review of the rest of the class.

End of Term Dates:

3/12/2014 - Last Day to turn in any artifact for credit.

Artifact List

  1. Refined Business Case
  2. Use Case Specifications
  3. Use Case Architecture
  4. Use Case Model
  5. Use Case Associated Sequence Diagrams
  6. Class Model/Logical Architecture
  7. Requirements to Use Case Map
  8. CRUD Matrix

Personal Tasks for Winter 2014:

Article Summaries:

Do article summaries for chapters in the second section of the Agile Development book by Martin as well as three articles related to design patterns. Also find two articles from peer-reviewed journals or technical trade journals. The number of articles that may be turned in in any given week is equal to the number of weeks remaining before dead week.

Use Case Expansion:

Each person will be in responsible for at least two use cases. These use cases must be either high-architectural, high, or mid priority use cases. A use case expansion will include:

    1. Use Case Specification
    2. Associated Use Case Model
    3. Associated Sequence Diagrams
    4. Related Class Models
    5. Code generated from class models
    6. Full implementation of code base related to the use case
    7. Test generation rising from defined scenarios in use case specifications
    8. Proof of round trip engineering and impact analysis integrity

1 Technology Demonstration:

Each student in the class must complete one technology demonstration presentation. This is an individual effort.  The presentation must revolve around a technology that either will be used in your project or a technology that is related to your project. The presentation will involve a live demonstration  to show how to use the technology and how it works. Plan for 20 to 30 minutes to allow time for questions. Make sure the demonstration venue is able to support your presentation before attempting to present to the class. Presentation topics must be chosen and the presentation scheduled before February 10. Students that miss this deadline should need to have a drop slip signed by the following Friday.

Team Assignment - Due 1/8/2014:

  • For each task assigned this quarter, set a milestone that will determine when the task will be submitted for grading.
  • Milestone sequencing must take into account task precedence discussed in lecture.
  • Completion dates must be realistic.
  • Tasks must be distributed throughout the quarter. Dead week with all tasks set as completion milestones is not acceptable.