1. USC e-Services Software Engineering Projects
Barry Boehm, Sue Koolmanojwong, Pongtip Aroonvatanaporn, Nupul Kukreja
USC Center for Systems and Software Engineering
Project Client Prospectus
July 21, 2011
(boehm, koolmano, aroonvat, usc.edu
7/21/2011
(c) USC-CSSE 1

2. Outline e-Services projects overview
e-Services examples from previous years
Stakeholder win-win approach
Client participation timelines
Client critical success factors and benefits
Example project demo
7/21/2011
(c) USC-CSSE 2

3. e-Services Projects Overview
Clients identify prospective projects
Operational capabilities or feasibility explorations
Staff helps "right size" and "sell" projects to students
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
7/21/2011
(c) USC-CSSE 3

4. Project Showcase
Southland Partnership Corporation (SPC) Web Automation Enhancement
One Semester Analysis, Design, Development, and Transition (ADDT) with WordPress for content
Los Angeles Neighborhood Initiatives (LANI)
Eventually, one semester SaaS based on SalesForce.com
Contacts and small construction projects management
Growing Great On Line
Two semester ADDT on a Joomla platform
Timelines: Early Medieval East Asian History
7/21/2011
(c) USC-CSSE

5. LANI
Los Angeles Neighborhood Initiatives: manages small construction projects for City of Los Angeles
Generates RFPs and selects contractors
Monitors work and makes intermediate payments as appropriate
Reports back to the city government
Two semester ADDT, but implemented on Software as a Service (SaaS) based on SalesForce.com
Can not show live (we don't have a license)
Will show some snapshots
7/21/2011
(c) USC-CSSE

6. SalesForce.com
7/21/2011
(c) USC-CSSE

7. LANI Home Showing Apps. and Custom Tabs
7/21/2011
(c) USC-CSSE

8. LANI @ SalesForce.com Showing Setup options
7/21/2011
(c) USC-CSSE

9. Stakeholder Win-Win Approach
Stakeholders
Students, Employers
Project clients
Faculty, Profession
Win Conditions
Full range of SW Engr. skills
Real-client project experience
Non-outsourceable skills
Advanced SW tech. experience
Useful applications
Advanced SW tech. understanding
Moderate time requirements
Educate future SW Engr. leaders
Better SW Engr. technology
Applied on real-client projects
7/21/2011
(c) USC-CSSE 9

10. WikiWinWin: Identify and Resolve Issues
7/21/2011
08/21/09
(c) USC-CSSE 10

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

12. 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 client's desired outcomes
20 projects; 100 students; about 20 clients
Spring: Develop Initial Operational Capability
4-8 projects; students; 4-8 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 Spiral Model method
Reworked annually based on student & client feedback
7/21/2011
(c) USC-CSSE 12

13. Outline e-Services projects overview Stakeholder win-win approach
Client participation timelines
Client critical success factors and benefits
Example project demo
7/21/2011
(c) USC-CSSE 13

14. Timelines: Summer 2011 July – August 31: Project Recruiting
Project Scoping, Goals and Objectives defining
Thursday August 18:
Potential Clients’ meeting II
Classes start August 22
7/21/2011
(c) USC-CSSE 14

15. Timelines: Fall 2011 Sept. 9: Teams formed; projects selected;
2:00 - 3:20 pm CS 577a class Session with clients (OHE122)
3:30 – 4:30 pm hands on WWW training (in an ITS classroom)
Sept 10-13: Site visit
During the semester: Sept. 12 – Dec. 9
Intermediate consultation, prototype reviews, WikiWinWin negotiation, scheduled weekly meetings with team, prototype evaluations, on-campus win-win negotiation participation & off campus follow up, Identify other success-critical stakeholders
Sep 23 : VCR preparation and teleconference meeting
Oct : FCR ARB meetings
Nov 28-Dec 2: DCR ARB meetings
Dec. 9: Submit Client evaluation form
DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review; WWW: WikiWinWin
7/21/2011
(c) USC-CSSE 15

16. Timelines: Spring 2012
Dec. 12, Jan. 9 to Feb. 11: Work with [parts of] teams:
Rebaseline prototype, prioritize requirements
Plan for CS 577b specifics, including transition strategy, key risk items
Participate in ARB review
Feb 15 to April 30: Scheduled Weekly Meetings with Teams to:
Discuss status and plans
Provide access to key transition people for strategy and readiness discussions
Mar 19 to 23: Core Capability Drivethrough (Clients exercise systems)
Apr 15 - Apr 16: Project Transition Readiness Reviews
Apr 21: Installation and Transition
Install Product
Execute Transition Plan
May 3-4: Operational Commitment Review for Initial Operational Capability
May 7: Client Evaluations
7/21/2011
(c) USC-CSSE 16

17. 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
7/21/2011
(c) USC-CSSE 17

18. 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
7/21/2011
(c) USC-CSSE 18

19. CSCI577 Project Demonstration (1) Proyecto Pastoral Website
User view of the deployed system
Project artifacts
7/21/2011
(c) USC-CSSE 19

20. CSCI577 Project Demonstration (2) Theatre Script Online Database
User Management
Script Management
7/21/2011
©USC-CSSE
(c) USC-CSSE 20

21. CSCI577 Project Demonstration (3) AAA Petal Pushers Plant Service Tracking System
7/21/2011
(c) USC-CSSE 21

22. Proyecto Pastoral Website
7/21/2011
©USC-CSSE 22