Transcript No Slide Title

University of Southern California
Center for Systems and Software Engineering
USC e-Services Software
Engineering Projects
Barry Boehm, Winsor Brown, Sue Koolmanojwong,
Di Wu, Pongtip Aroonvatanaporn, Itti Charoenthongtrakul
USC Center for Systems and Software Engineering
2008-2009 Project Client Prospectus
June 24, 2008
(boehm, awbrown, koolmano, diwu,
aroonvat, icharoen)@ usc.edu
06/24/08
©USC-CSSE
1
University of Southern California
Center for Systems and Software Engineering
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
2
University of Southern California
Center for Systems and Software Engineering
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
3
University of Southern California
Center for Systems and Software Engineering
Stakeholder Win-Win Approach
Stakeholders
Win Conditions
•Full range of SW Engr. skills
•Students,
Employers
•Real-client project experience
•Non-outsourceable skills
•Advanced SW tech. experience
•Useful applications
•Project clients
•Advanced SW tech. understanding
•Moderate time requirements
•Faculty,
Profession
•Educate future SW Engr. leaders
•Better SW Engr. technology
•Applied on real-client projects
06/24/08
©USC-CSSE
4
University of Southern California
Center for Systems and Software Engineering
“Software Engineering”: The disciplines which
distinguish the coding of a computer program from
the development of a software product
Stages
Issues
Computer Science
Requirements,
Architecture
Design,
Code
Implement,
Maintain
CS Focus
User Applications
Economics
People
•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
5
University of Southern California
Center for Systems and Software Engineering
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; 30-50 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
6
University of Southern California
Center for Systems and Software Engineering
Incremental Commitment Model in Software Engineering Class
06/24/08
©USC-CSSE
7
University of Southern California
Center for Systems and Software Engineering
WinWin Negotiation
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
WinCondition
Condition
Issue
Issue
involves
covers
addresses
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
Agreement
adopts
Option
Option
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
8
University of Southern California
Center for Systems and Software Engineering
WikiWinWin – Tool (1)
Initial ideas
surfaced at the
meeting
Prospective
win condition
06/24/08
©USC-CSSE
9
University of Southern California
Center for Systems and Software Engineering
WikiWinWin – Tool (2)
Stakeholders
engage in a
further
discussion
Reach
Agreement
06/24/08
©USC-CSSE
10
University of Southern California
Center for Systems and Software Engineering
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
11
University of Southern California
Center for Systems and Software Engineering
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:00 - 12:30 hands on WWW training (ITS lab)
•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. 15 - 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. 20-24: 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
12
University of Southern California
Center for Systems and Software Engineering
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
13
University of Southern California
Center for Systems and Software Engineering
Elements of Critical Front End Milestones
(Risk-driven level of detail for each element)
Milestone Element
Foundations Commitment Review
Development Commitment Review
System Prototype(s)
• 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)
• Exercise key usage scenarios
• Resolve critical risks
Definition of System
Requirements
• 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
• 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
Operational
Concept
Definition of System
and Software
Architecture
Definition of LifeCycle Plan
Feasibility
Evidence
06/24/08
• 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
• Assurance of consistency among elements above
- via analysis, measurement, prototyping, simulation, etc.
- Business case analysis for requirements, feasible
architectures
• Elaboration of system objectives and scope of increment
• Elaboration of operational concept by increment
• Exercise range of usage scenarios
• Resolve major outstanding risks
• Elaboration of WWWWWHH* for Initial Operational
Capability (IOC)
- Partial elaboration, identification of key TBD’s for later
increments
• 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
©USC-CSSE
14
University of Southern California
Center for Systems and Software Engineering
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
15
University of Southern California
Center for Systems and Software Engineering
Client Critical Success Factors and Benefits
•Critical success factors
–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
16
University of Southern California
Center for Systems and Software Engineering
CSCI577 Project Demonstration (1)
St. Francis Center Website
• User view of the deployed system
– http://www.stfranciscenterla.org/
• Project artifacts
– http://greenbay.usc.edu/csci577/fall2007/project
s/team6/
06/24/08
©USC-CSSE
17
University of Southern California
Center for Systems and Software Engineering
CSCI577 Project Demonstration (2)
LA County Parks and Recreation Homepage
• User view of the deployed system
– http://csseprt2.usc.edu/LACounty/
• Project artifacts
– http://greenbay.usc.edu/csci577/spring2008/proj
ects/team19/
06/24/08
©USC-CSSE
18
University of Southern California
Center for Systems and Software Engineering
For more information
• http://greenbay.usc.edu/csci577/fall2008/sit
e/clients/index.html
• Or email
–
–
–
–
06/24/08
[email protected]
[email protected]
[email protected]
[email protected]
©USC-CSSE
19