1. USC e-Services Software Engineering Projects
Barry Boehm, Winsor Brown, Sue Koolmanojwong ,Di Wu, Pongtip Aroonvatanaporn, Itti Charoenthongtrakul, Raed Shomali
USC Center for Systems and Software Engineering
Project Client Prospectus
August 22, 2008
(boehm, awbrown, koolmano, diwu,
aroonvat, icharoen, usc.edu
06/24/08
©USC-CSSE

2. Outline e-Services projects overview Stakeholder win-win approach
Previous project highlights
Client participation timelines
Client critical success factors and benefits
Example project demo
06/24/08
©USC-CSSE

3. e-Services Projects Overview
Clients identify prospective projects
Operational capabilities or feasibility explorations
Fall: 12 weeks to prototype, analyze, design, plan, validate
Spring: 12 weeks to develop, test, transition
MS-level, 5-6 person, CS 577 project course
Clients, CSSE, negotiate workable projects
Useful results within time constraints
Operationally supportable as appropriate
Clients work with teams to define, steer, evaluate projects
Exercise prototypes, negotiate requirements, review progress
Mutual learning most critical success factor
06/24/08
©USC-CSSE

4. Stakeholder Win-Win Approach
Stakeholders
Win Conditions
Full range of SW Engr. skills
Real-client project experience
Non-outsourceable skills
Advanced SW tech. experience
Students, Employers
Useful applications
Advanced SW tech. understanding
Moderate time requirements
Project clients
Educate future SW Engr. leaders
Better SW Engr. technology
Applied on real-client projects
Faculty, Profession
06/24/08
©USC-CSSE

5. “Software Engineering”: The disciplines which distinguish the coding of a computer program from the development of a software product
Stages
Requirements, Design, Implement, Architecture Code Maintain
Issues
Computer Science
User Applications
Economics
People
CS Focus
Accommodate new tools and techniques
Web services, GUI prototypers, WinWin, Spiral processes
Integrate all these considerations
- Via Incremental Commitment Model
06/24/08
©USC-CSSE

6. Software Engineering Project Course (CS 577)
Fall: Develop Life Cycle Architecture Packages
Ops. Concept, Requirements, Prototype, Architecture, Plan
Feasibility Rationale, including business case
Results chain linking project results to desired outcomes
20 projects; 100 students; about 20 clients
Spring: Develop Initial Operational Capability
6-10 projects; students; 6-10 clients
Software, personnel, and facilities preparation
2-week transition period
then the student teams disappear
Tools and techniques: WikiWinWin; Benefit Chain; Rational Software Modeler; Subversion; USC COCOMO II; MS Project; USC Incremental Commitment model method
Reworked annually based on student & client feedback
06/24/08
©USC-CSSE

7. Incremental Commitment Model in Software Engineering Class
06/24/08
©USC-CSSE

8. WinWin Negotiation Win-Win Equilibrium
WinWin Definition: The win-win approach is a set of principles, practices, and tools, which enable a set of interdependent stakeholders to work out a mutually satisfactory (win-win) set of shared commitments.
Win Condition: objective which makes a stakeholder feel like a winner
Issue: conflict or constraint on a win condition
Option: A way of overcoming an issue
Agreement: mutual commitment to an option or win condition
Win-Win Equilibrium
All Win Conditions covered by Agreements
No outstanding Issues
06/24/08
©USC-CSSE

9. Initial ideas surfaced at the meeting Prospective win condition
WikiWinWin – Tool (1)
Initial ideas surfaced at the meeting
Prospective win condition
06/24/08
©USC-CSSE

10. Stakeholders engage in a further discussion
WikiWinWin – Tool (2)
Stakeholders engage in a further discussion
Reach Agreement
06/24/08
©USC-CSSE

11. Outline e-Services projects overview Stakeholder win-win approach
Previous project highlights
Client participation timelines
Client critical success factors and benefits
Example project demo
06/24/08
©USC-CSSE

12. Timelines: Fall 2008 Sept. 9: Teams formed; projects selected;
Sept 10 – 11: Prepare for Site visit
During the semester: Sept. 10 – Dec. 10
Intermediate consultation, prototype reviews, WikiWinWin negotiation follow-up
Scheduled weekly meetings with team
Sept. 12:
11: :30 hands on WWW training (KOH 208)
12:30 - 1:30 lunch and Q&A session with staff (RTH 306)
2:00 - 3:20 pm CS 577a class Session with clients (OHE122)
Sept Oct. 05: Interviews, prototype evaluations, on-campus win-win negotiation participation & off campus follow up, Identify other success-critical stakeholders
Oct 1 : VCR preparation and teleconference meeting
Oct : FCR ARB meetings
Dec.1-5: DCR ARB meetings
Dec. 10: Submit Client evaluation form
DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review; WWW: WikiWinWin
06/24/08
©USC-CSSE

13. Spring Schedule (2009) Jan. 12- Feb. 13: Work with teams:
Rebaseline prototype, prioritize requirements
Plan for CS 577b specifics, including transition strategy, key risk items
Participate in ARB review
Feb 13 – May 8: Scheduled Weekly Meetings with Teams to:
Discuss status and plans
Provide access to key transition people for strategy and readiness discussions
Mar 9 – 27: Core Capability Drivethrough
Apr 15 - Apr 16: Project Transition Readiness ARB Reviews
Apr 20: Installation and Transition
Install Product
Execute Transition Plan
May 4-5: Operational Commitment Review for Initial Operational Capability
May 8: Client Evaluations
06/24/08
©USC-CSSE

14. Elements of Critical Front End Milestones
(Risk-driven level of detail for each element)
Milestone Element
Foundations Commitment Review
Development Commitment Review
Top-level system objectives and scope
- System boundary
- Environment parameters and assumptions
- Evolution parameters
Operational concept
- Operations and maintenance scenarios and parameters
- Organizational life-cycle responsibilities (stakeholders)
Definition of
Operational
Concept
Elaboration of system objectives and scope of increment
Elaboration of operational concept by increment
System Prototype(s)
Exercise key usage scenarios
Resolve critical risks
Exercise range of usage scenarios
Resolve major outstanding risks
Top-level functions, interfaces, quality attribute levels, including:
- Growth vectors and priorities
- Prototypes
Stakeholders’ concurrence on essentials
Elaboration of functions, interfaces, quality attributes, and prototypes by increment
- Identification of TBD’s( (to-be-determined items)
Stakeholders’ concurrence on their priority concerns
Definition of System
Requirements
Top-level definition of at least one feasible architecture
- Physical and logical elements and relationships
- Choices of NDI and reusable software elements
Identification of infeasible architecture options
Choice of architecture and elaboration by increment
- Physical and logical components, connectors, configurations, constraints
- NDI, reuse choices
- Domain-architecture and architectural style choices
Architecture evolution parameters
Definition of System
and Software
Architecture
Identification of life-cycle stakeholders
- Users, customers, developers, maintainers, interoperators,
general public, others
Identification of life-cycle process model
- Top-level stages, increments
Top-level WWWWWHH* by stage
Elaboration of WWWWWHH* for Initial Operational
Capability (IOC)
- Partial elaboration, identification of key TBD’s for later
increments
Definition of Life-
Cycle Plan
Feasibility
Evidence
Assurance of consistency among elements above
- via analysis, measurement, prototyping, simulation, etc.
- Business case analysis for requirements, feasible
architectures
Assurance of consistency among elements above
All major risks resolved or covered by risk management
plan
*WWWWWHH: Why, What, When, Who, Where, How, How Much
06/24/08
©USC-CSSE

15. Architecture Review Boards
Commercial best practice
- AT&T, Lucent, Citibank
Held at critical commitment points
- FCR, DCR milestones
Involve stakeholders, relevant experts
- 1 week: artifacts available for client review
- 80 minutes: ARB meetings (spread over 1 week)
- Briefings, demo discussion
Identify strong points, needed improvements
All stakeholders to commit to go forward
06/24/08
©USC-CSSE

16. Client Critical Success Factors and Benefits
Mutual learning time with teams
Scenarios, prototypes, negotiations, reviews
Scheduled 1 -hour weekly meeting
WikiWinWin training and negotiation
ARB Preparation and Participation
Involve other success-critical stakeholders
End users, administrators, maintainers, ITS
CRACK characteristics
Committed, Representative, Authorized, Collaborative, Knowledgeable
Benefits
Useful applications or feasibility explorations
Understanding of new information technologies
Opportunity to rethink current approaches
06/24/08
©USC-CSSE

17. CSCI577 Project Demonstration (1) St. Francis Center Website
User view of the deployed system
Project artifacts
06/24/08
©USC-CSSE

18. CSCI577 Project Demonstration (2) LA County Parks and Recreation Homepage
User view of the deployed system
Project artifacts
06/24/08
©USC-CSSE

19. For more information Or
06/24/08
©USC-CSSE