Transcript No Slide Title

University of Southern California
Center for Systems and Software Engineering
USC e-Services Software
Engineering Projects
Barry Boehm, Sue Koolmanojwong,
Nupul Kukreja, Daniel Link
USC Center for Systems and Software Engineering
2013-2014 Project Client Prospectus
July 19, 2013
(boehm, koolmano, nkukreja, dlink)@ usc.edu
7/19/2013
(c) 2007-2013 USC-CSSE
1
University of Southern California
Center for Systems and Software Engineering
Outline
•e-Services projects overview
•Stakeholder win-win approach
•Client participation timelines
•Client critical success factors and benefits
•Example project demo
7/19/2013
(c) 2007-2013 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
– 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/19/2013
(c) 2007-2013 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
7/19/2013
(c) 2007-2013 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, Risk Mgt. processes
•Integrate all these considerations - Via Incremental
Commitment Spiral Model
7/19/2013
(c) 2007-2013 USC-CSSE
5
University of Southern California
Center for Systems and Software Engineering
7/19/2013
WinWin negotiation
(c) 2007-2013 USC-CSSE
6
University of Southern California
Center for Systems and Software Engineering
7/19/2013
WinWin negotiation
(c) 2007-2013 USC-CSSE
7
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 client's desired outcomes
20 projects; 100 students; about 20 clients
• Spring: Develop Initial Operational Capability
–
–
–
–
4-8 projects; 30-50 students; 4-8 clients
Software, personnel, and facilities preparation
2-week transition period
then the student teams disappear
• Tools and techniques: Winbook; Benefit Chain; Visual
Paradigm for UML; Subversion; USC COCOMO II; MS
Project; USC Incremental Commitment Spiral Model
method
– Reworked annually based on student & client feedback
7/19/2013
(c) 2007-2013 USC-CSSE
8
University of Southern California
Center for Systems and Software Engineering
Outline
•e-Services projects overview
•Stakeholder win-win approach
•Client participation timelines
•Client critical success factors and benefits
•Example project demo
7/19/2013
(c) 2007-2013 USC-CSSE
9
University of Southern California
Center for Systems and Software Engineering
Timelines: Summer 2013
• July – August 31:
•Project Recruiting
•Project Scoping, Goals and Objectives defining
•Classes start August 26
7/19/2013
(c) 2007-2013 USC-CSSE
10
University of Southern California
Center for Systems and Software Engineering
Timelines: Fall 2013
• Wed. Sept. 11: Teams formed; projects selected;
•Fri. Sept 13:
•1:00 - 2:00 pm Win-Win negotiation Training for Clients (SAL322)
•2:00 - 3:20 pm CS 577a class Session with clients (OHE122)
•Sept 16-18: Site visit
•During the semester: Sept. 17 – Dec. 14
•Intermediate consultation, prototype reviews, WinWin negotiation, scheduled
weekly meetings with team, prototype evaluations, on-campus win-win
negotiation participation & off campus follow up, Identify other success-critical
stakeholders
•Oct. 14 – 18: FCR ARB meetings
•Dec 2 - 6: DCR ARB meetings
•Dec. 11: Submit Client evaluation form
DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review
7/19/2013
(c) 2007-2013 USC-CSSE
11
University of Southern California
Center for Systems and Software Engineering
Timelines: Spring 2014
Dec. 12, 2012…Jan. 13 to Feb.10: 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 10 to April 25: Scheduled Weekly Meetings with Teams to:
–Discuss status and plans
–Provide access to key transition people for strategy and readiness
discussions
Mar 17 to 21: Core Capability Drivethrough (Clients exercise systems)
Apr 14 - Apr 18: Project Transition Readiness Reviews
Apr 21: Installation and Transition
–Install Product
–Execute Transition Plan
May 1-2: Operational Commitment Review for Initial Operational Capability
May 5: Client Evaluations
7/19/2013
(c) 2007-2013 USC-CSSE
12
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
7/19/2013
(c) 2007-2013 USC-CSSE
13
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
– Win-Win 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/19/2013
(c) 2007-2013 USC-CSSE
14
University of Southern California
Center for Systems and Software Engineering
Project Showcase
• Southland Partnership Corporation (SPC)
Web Automation Enhancement
– One Semester Analysis, Design, Development,
and Transition (ADDT) with WordPress for
content
– http://www.istartonmonday.com
7/19/2013
(c) 2007-2013 USC-CSSE
15
University of Southern California
Center for Systems and Software Engineering
Project Showcase
• Los Angeles Neighborhood Initiatives
(LANI)
– Eventually, one semester SaaS based on
SalesForce.com
– Contacts and small construction projects
management
7/19/2013
(c) 2007-2013 USC-CSSE
16
University of Southern California
Center for Systems and Software Engineering
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, 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/19/2013
(c) 2007-2013 USC-CSSE
17
University of Southern California
Center for Systems and Software Engineering
7/19/2013
LANI @ SalesForce.com
(c) 2007-2013 USC-CSSE
18
University of Southern California
Center for Systems and Software Engineering
LANI Home Showing Apps.
and Custom Tabs
7/19/2013
(c) 2007-2013 USC-CSSE
19
University of Southern California
Center for Systems and Software Engineering
Project Showcase
• Growing Great On Line
– Two semester ADDT on a Joomla platform
– http://growinggreat.org/
7/19/2013
(c) 2007-2013 USC-CSSE
20
University of Southern California
Center for Systems and Software Engineering
Project Showcase
Proyecto Pastoral Website
• A 2 semester project
• User view of the deployed system
– http://www.proyectopastoral.org/index.php
7/19/2013
(c) 2007-2013 USC-CSSE
21
University of Southern California
Center for Systems and Software Engineering
Proyecto Pastoral Website
7/19/2013
(c) 2007-2013 USC-CSSE
22
University of Southern California
Center for Systems and Software Engineering
Project Showcase
Theatre Script Online Database
•User Management
•Script Management
7/19/2013
(c) 2007-2013 USC-CSSE
23
University of Southern California
Center for Systems and Software Engineering
Project Showcase
AAA Petal Pushers Plant Service Tracking System
7/19/2013
(c) 2007-2013 USC-CSSE
24