CS 487 488 Software Engineering Senior Capstone

1
CS 487 / 488 Software Engineering Senior Capstone

• Classes Monday evenings 640-920 pm, FAB 150
• Instructor Kal Toth, ktoth_at_cs.pdx.edu
• Coordinator Warren Harrison, warren_at_cs.pdx.edu
• Website http//www.cs.pdx.edu/ktoth/Capstone
• WebCT http//psuonline.pdx.edu/
• Skills Inventory Survey http//survey.oit.pdx.edu
  /ss/wsb.dll/ktoth/CScapstoneSkillsInventory.htm

2
Capstone Objectives

• Experience a team activity similar to industry
  practice
• Learn to work together towards common goals
• Integrate knowledge acquired from CS program
• Exercise the entire software engineering
  lifecycle
• Solve realistic customer problem, work w. the
  customer
• Understand needs, expectations, requirements
• Goal is successful completion
• Conduct a professional SE process
• Build confidence
• Enhance job opportunities

3
Approach

• Form Teams
• Inventory of skills in class -gt Instructor
  establishes teams
• Select Project from Projects Proposed by Sponsors
• Teams indicate references -gt instructor assigns
  projects
• Capture the requirements, manage scope
• Elicitation -gt feasibility -gt collaboration -gt
  negotiation
• Organize and produce an effective plan
• Organize team, define the work, schedule it
• Prepare the development environment
• Ensure tools, H/W, O.S., other support S/W in
  place
• Implement the plan
• Coordinate work, track progress, take corrective
  actions
• Close the project
• Deliver product, present results, discuss
  lessons-learned

4
Capstone Process
Acquired Undergrad Knowledge and Skills Sponsor
Presentations Customer Requirements Other
Documents Specs, Manuals
Requirements Project Plan Agendas Action
items Development Environment Software
Components Demonstration (s) Presentation
Slides Engineering Notebook
Team Process 1st Term
2nd Term Orient ? Mobilize ? Implement
PlanElicitDesignTest
Project Team
Individual Members
5
Logistics and Coordination

• Roles Instructor, Sponsor, Team Members
• Location of meetings class, team, instructor,
  sponsor
• Progress reviews with your instructor
• Progress reviews with your sponsor
• Internal team meetings
• WebCT collaboration, repository, resources
• E-mail among team members instructor
• Skills Inventory Survey
• Document Templates SPMP, SRS
• Engineering Notebooks (ENBs)
• Project Files (use binders)
• Sponsor Presentations
• Team Building Exercise
• Grading

6
Skills Inventory

• Rate your knowledge and experience
• Application / Domain Experience
• Architecture / Design
• Programming / Development
• Linux and MS Windows Administration
• Project Management / Soft Skills
• Other relevant knowledge and skills

7
Sponsor Proposals

• Project Title
• Sponsor name, company name
• Alternate personnel (if any)
• Contact information
• Purpose of Project
• Context Related to other systems?
• Application and usage of s/w to be developed
• Relevant assumptions, constraints, dependencies
• What are the risks, how mitigated?
• Resources Documentation, API specs, equipment,
  s/w components
• Any customer-provided equipment or documentation?
• Any agreements needed? (e.g. NDA?)

8
Roles

• Instructor Role Senior Management
• Team
• Management
• Team Leadership
• Organizing / Planning / Scheduling
• (SPMP)
• Coordinating / Directing
• Recording - Agendas, Action Items)
• Presenting
• Scope Control

• Sponsor Role Customer
• Roles
• Development
• Requirements (SRS)
• Architecture / Design
• Coding
• Integration
• Testing
• Quality Assurance
• Configuration Management
• Documentation

9
Engineering Notebook

• Scratch-pad memory, protect your assets (IP),
  reduce project risks, communicate, follow-up, .
• Permanent record of what you did and plan to do
• Permanently bound notebook dedicate for
  Capstone
• Numbered pages, ink, chrono order, dated, no
  blanks
• Key points and issues -gt meeting agenda items
• Key comments, decisions, follow-up actions
• Important ideas, references
• Will be reviewed by instructor and submitted at
  end
• Also -gt 3-ring binder of refs, papers, draft
  docs,

10
Evaluation and Grading

• Team Grades
• Teamwork 20
• Project Processes 20
• Project Outcomes 20
• Individual Grades
• Participation 20
• Engineering Notebook 20