CS 461 / 462 / 463:

Career Preparation and Software Engineering Capstone Project

Fall-Winter-Spring Quarters 2009-2010

http://cs.oregonstate.edu/capstone

"You are always in your career." -- Matthew Moran

Class Organization


This page was last updated: September 28, 2009


Learning Objectives

On completion of the course, students will have been able to:

  1. Design, plan, organize, synthesize and complete a significant software project in three academic quarters (Level 5; ABET Outcomes: A, B, C, K, e).
  2. Apply all aspects of the software engineering process, including project planning, requirements documents, software design, coding, testing, walk-throughs, documentation, and delivery (Level 3; ABET Outcomes: A, B, c, I, j, K, l, n).
  3. Demonstrate good communication skills in the form of weekly reports, project talks, posters, and elevator talks (Level 3; ABET Outcomes: F, O).
  4. Participate effectively in a team environment (Level 3; ABET Outcomes: D, o).
  5. Analyze and organize their own career preparation (Level 4; ABET Outcomes: E, G, H, m).
  6. Evaluate the professional, legal, and/or social implications of software product development (Level 6; ABET Outcomes: E,H).
  7. Evaluate the contributions and importance of software projects to the broad user community (Level 6; ABET Outcomes: G, O).
  8. Explain the importance of software projects to people from other disciplines and the general public (Level 3; ABET Outcomes: F, o).

Credits

The three quarters will be worth 2, 2, and 2 credits, respectively.

Prerequisites

 FallWinterSpring
PrerequisitesCS 361CS 361CS 361, 362
Enforced PrerequisitesCS 361CS 361CS 361, 362
Co-requisites--CS 362--

What Will We Be Doing?

Over the next three quarters, we will be learning and discussing various aspects of Computer Science Career Preparation. We will be reading and discussing various topics from the book, as well as with guest speakers.

Also, you will be working in teams of 2-4 students to accomplish a significant project using good software engineering principles. Specifically, this includes:

  1. Requirements Analysis -- What does the client want? How are those requirements prioritized?
  2. The Plan -- How will the project team go about meeting the requirements? What are the milestones, deliverables, and tasks in producing the software?
  3. Design -- What will the project actually do? How will the project do it? How will the project be compartmentalized so that a team can work on it? How will the pieces be integrated?
  4. Risk Assessment -- In what ways could the project go wrong and how bad would they be?
  5. Review(s) -- How will we know if you are on course?
  6. Testing -- How will we know if the implementation satisfies the requirements?
  7. Documentation -- How will the client and support staff know how to use and maintain the product?
  8. Final Report -- What did we do? What went right? What went wrong? If you could do it all over again, what would you do differently?
  9. Sign-off by your project sponsor.

What is "CS Career Preparation"?

There is information all graduates should have, but has probably not been covered in any class. This information will really round out your skill set. The book calls such people Value-Added Technologists.

I am arranging for classes on these topics, sometimes from me, sometimes from others. Topics I am working on include:

This is meant to be more fun and useful than work. Feel free to make additional suggestions!

Book for the Class

Matthew Moran, "The IT Career Builder's Toolkit", Cisco Press, 2005.

The important phrase is right on the cover: "...building your information technology career in any economy."

The OSU bookstore has it.
Or, you can click here to buy it from Amazon. (New $32)
Or, you can look for it elsewhere online. Its ISBN number is: 1-58713-156-0

Yes, you need the book, but everyone doesn't need their own copy. You need to have easy access to one. It will work to share. There will be assigned readings from it, and some of you will volunteer or be volunteered to lead discussions from it.

Using Project Management Software

You are not required to use any specific project management software in this class, but you must use something that manages tasks and dependencies, and is capable of producing a Gantt chart.

If you have no other preference, Microsoft Project professional 2007 qualifies and you can get it for free by signing up for the MSDN Academic Alliance. To do that, go to the teach system,: http://engr.oregonstate.edu/teach. Under External Links, click MSDNAA Site Login. This will allow you to download Project, and a bunch of other packages, for free.

Weekly Reports

Each week, you are expected to submit both a team and an individual progress report. They are to be of the form known as a P3, which stands for Progress, Problems, Plans. Let me know what progress has been made since last week, what problems you are encountering or expect to encounter, and what the plan is for next week.

I have worked in industry, so I know what a BS P3 looks like. Don't do it! A P3 of the form "I had midterms this week, so didn't do much" is acceptable. Just don't submit such a P3 two weeks in a row.

You don't need to submit any P3s until Week #3 -- due Sunday October 18.

To make this easy on you, it can all be done as web forms:

These get re-formatted as simple HTML files before I see them, so feel free to embed HTML tags in them.

The "Clubhouse"

We have Kelley Room 2098 reserved for use by this class as our "Clubhouse". It has some dedicated PCs in it. You can each get a card key to get in to use this room for your CS 461/462/463 computer activities as well as team meetings. I'll let you know what that process is when it is ready.

Please keep the Clubhouse tiday. Making it look like slobs live there is the fastest way to get it taken away from us.

 

School of Electrical Engineering and Computer Science, 1148 Kelley Engineering Center
Oregon State University, Corvallis, OR 97331-5501
Send a comment about this web site | This page was last modified on Monday, September 28, 2009
Copyright © 2009 | Disclaimer | Committed to Diversity