CS 577b: Software Engineering II

1
CS 577b Software Engineering II

• Overview

2
CS 577b Course Objective

• Learn how to go
• From successful LCA package
• To successfully delivered software system
• Main elements
• Coping with devils in the details
• Understanding how stakeholders will operate
  maintain system
• Using MBASE project guidelines

3
Who Am I?

• Ed Colbert, ecolbert_at_usc.edu

• SR. Research Associate with Center for SW
  Engineering
• A MBASE developer
• Lead researcher on COCOMO Security Extension
• 20 years industrial teaching consulting on
  objectoriented methods, software engineering,
  programming languages
• Consultant on definition of Architecture Design
  Language (ADL) for realtime, safetycritical
  systems
• Based on Unified Modeling Language (UML)
  Honeywells MetaH
• To be proposed as standard of Society of
  Automotive Engineers (SAE) 
• Created Colbert ObjectOriented Software
  Development method (OOSD)
• Noted for strength in realtime software
  development
• NASA Langley Research Center used for software
  engineering process manual
• Founded Absolute Software Co., Inc. in 1986

4
Course Etiquette

• Observe normal rules of classroom etiquette
• Be on time
• If you are late, dont slam the door
• (Tell your friends)
• 1 conversation at a time
• 1 topic at a time
• Direct all comments to instructor
• Encourage (rather than criticize) other students
• E-mail browsing at breaks or after class
• Turn off/silent cell phones pagers

5
Course Etiquette (cont.)

• Respect others yourself
• Cheat
• Dont!
• Be ready to learn.

6
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

7
Challenge IOC vs. LCA Client Evaluations
8
Software Engineering Education Stakeholders Win
Conditions
9
Software Engineering Education Stakeholders Win
Conditions (cont.)
10
Software Engineering Education Stakeholders Win
Conditions (cont.)
11
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

12
Staff

• Instructors
• Ed Colbert (lead instructor)
• Winsor Brown
• Dr. Barry Boehm
• TAs
• Alex Lam
• Mayurkumar Patel

13
Grading

• Individual Homework Quizzes 20
• Project 60
• SE Research Presentation 5
• Critique 12
• Individual Contribution 3
• Client Evaluation 2

14
Grading Philosophy

• Hard
• I like large distribute
• Better feedback
• Adjust when assigning final grades

15
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

16
Course Schedule

• See http//sunset.usc.edu/classes/cs577b_2005/sche
  dule/index.html
• Some Friday classes
• Student Presentations
• Staff will propose topics
• By 18 Feb
• Students must select topic get approval
• By 28 Feb
• Each student most cover a different aspect of a
  topic

17
Project Schedule
Subject to client 577 staff availability
18
Main Challenge for Clients

• Products are delivered on May 2
• Students disappeared by May 10

19
Selected Projects

• 577a projects selected for continuation should be
  finalized this week
• Students not on selected project need to join one
• New students need to fill out a capabilities
  questionnaire

20
Office Hours

• Ed
• Monday Wednesday 1-3 PM
• Some exceptions (this week weeks of 24 31
  Jan)
• Or by appointment
• Winsor
• By Appt (usually Wed before class)
• Dr. Boehm
• By Appt
• Alex Mayur
• Tuesday Wednesday 2-315 PM
• Or by appointment

21
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

22
Top 10 Risk Items 1989 1995
1989 1. Personnel shortfalls 2. Schedules
budgets 3. Wrong software functions 4. Wrong user
interface 5. Gold plating 6. Requirements
changes 7. Externally-furnished components 8.
Externally-performed tasks 9. Real-time
performance 10. Straining computer science
1995 1. Personnel shortfalls 2. Schedules,
budgets, process 3. COTS, external components 4.
Requirements mismatch 5. User interface
mismatch 6. Architecture, performance, quality 7.
Requirements changes 8. Legacy software 9.
Externally-performed tasks 10. Straining computer
science
23
Primary CS577b Risk Items

• Personnel
• Commitment
• Compatibility
• Ease of communication
• Skills (management, web/java, Perl, CGI, data
  compression, )
• Schedule
• Project scope
• IOC content
• Critical-path items (COTS, platforms, reviews, )
• COTS
• See next chart
• Multiple COTS

24
Primary CS577b Risk Items (cont.)

• Requirements UI
• Not matching client user needs
• Performance
• Memory, Disk Space usage (Bits)
• Bus, Network, CPU utilization bandwidth
  (Bits/sec)
• Overhead sources
• Reliability of deliver
• Safe
• Secure
• External tasks
• Client/operator preparation
• Commitment for transition

25
COTS External Component Risks

• COTS risks
• Immaturity
• Inexperience
• Incompatibility with
• Application
• Platform
• Other COTS
• Controllability

26
COTS External Component Risks (cont.)

• Non-commercial off-the shelf components
• Sources
• Reuse libraries
• Government (GOTS)
• Universities (ROTS)
• Issues
• Qualification testing
• Benchmarking
• Inspections
• Reference checking
• Compatibility analysis
• Both
• Safety
• Dependability
• Security

27
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

28
CS 577b PlanningCommon LCP Problems _at_ LCA

• Transition preparation
• Transition-leaders success plan (teammates,
  clients)
• Lack of core-capability specifics
• End-to-end demonstrable capability
• Lack of specific team member responsibilities
• By artifact increment but flexible
• Possible RLCA prototype, business-case iterations
• What have you done since last semester?
• Too many internal-increment deliverables

29
Test Preparation

• Test-leaders success plan
• Test data, drivers, tools, increments
• Problem tracking closeout
• GNATS tool
• Testing as requirements evaluation
• e.g. testing full portability, 24x7, ease of use
• OK to iterate requirements
• Verification cross-reference index
• Which requirements verified by test, analysis,
  inspection

30
Critical Success Factors for Adoption - I
31
Critical Success Factors for Adoption - II
32
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

33
CS577 Academic Integrity Guidelines

• Individual Assignments
• OK to discuss
• Not OK to copy each others solution elements
• Not OK to copy external sources without
  attribution
• Within Fair Use Guidelines
• Team Assignments
• OK to use other teams patterns
• e.g. MS Project tasks
• Not OK to copy other teams complete solutions
• e.g. MS course project schedules

34
Outline

• Course Challenges
• Staff Grading
• Course Project Schedule
• Project Team Risk Management
• Project Planning
• Other Course Preparation
• Academic Integrity Reminder
• Forms Logistics
• Comment Learning

35
Learning

• We each have a role
• Lou Holtz said
• Your talent determines what you can do.
• Your motivation determines how much you are
  willing to do.
• Your attitude determines how well you do it.
• Plutarch said
• A mind is not a vessel to fill but a fire to
  light.