USC e-Services Software Engineering Projects

University of Southern California

Center for Systems and Software Engineering

7/13/2012 (c) 2007-2012 USC-CSSE 11

USC e-Services Software Engineering Projects

Barry Boehm, Sue Koolmanojwong,

Nupul Kukreja, Daniel Link, Thammanoon Kawinfruangfukul

USC Center for Systems and Software Engineering

2012-2013 Project Client Prospectus

July 13, 2012

(boehm, koolmano, nkukreja, dlink, kawinfru)@ usc.edu



7/13/2012 (c) 2007-2012 USC-CSSE 22

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/13/2012 (c) 2007-2012 USC-CSSE 33

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/13/2012 (c) 2007-2012 USC-CSSE 4

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

• 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– http://growinggreat.org/

• Timelines: Early Medieval East Asian History



7/13/2012 (c) 2007-2012 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/13/2012 (c) 2007-2012 USC-CSSE 6

LANI @ SalesForce.com



7/13/2012 (c) 2007-2012 USC-CSSE 7

LANI Home Showing Apps. and Custom Tabs



7/13/2012 (c) 2007-2012 USC-CSSE 8

LANI @ SalesForce.com

Showing Setup options



7/13/2012 (c) 2007-2012 USC-CSSE 99

Stakeholder Win-Win ApproachStakeholders

•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/13/2012 (c) 2007-2012 USC-CSSE 1010

“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 Spiral Model



7/13/2012 (c) 2007-2012 USC-CSSE 11

WinWin negotiation



7/13/2012 (c) 2007-2012 USC-CSSE 12

WinWin negotiation



7/13/2012 (c) 2007-2012 USC-CSSE 13

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

13



7/13/2012 (c) 2007-2012 USC-CSSE 1414

Outline

•e-Services projects overview

•Stakeholder win-win approach

•Client participation timelines

•Client critical success factors and benefits

•Example project demo



7/13/2012 (c) 2007-2012 USC-CSSE 1515

Timelines: Summer 2012• July – August 31:

•Project Recruiting

•Project Scoping, Goals and Objectives defining

•Classes start August 27



7/13/2012 (c) 2007-2012 USC-CSSE 1616

Timelines: Fall 2012• Wed. Sept. 12: Teams formed; projects selected;

•Fri. Sept 14:

•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 17-19: 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 3 : VCR preparation

•Oct. 29 - Nov 2: FCR ARB meetings

•Dec 3 - 7: DCR ARB meetings

•Dec. 12: Submit Client evaluation form

DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review



7/13/2012 (c) 2007-2012 USC-CSSE 1717

Dec. 12, 2012…Jan. 9 to Feb.8: 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 8 to April 26: Scheduled Weekly Meetings with Teams to:

–Discuss status and plans

–Provide access to key transition people for strategy and readiness discussions

Mar 18 to 22: Core Capability Drivethrough (Clients exercise systems)

Apr 15 - Apr 16: Project Transition Readiness Reviews

Apr 22: Installation and Transition

–Install Product

–Execute Transition Plan

May 2-3: Operational Commitment Review for Initial Operational Capability

May 8: Client Evaluations

Timelines: Spring 2013



7/13/2012 (c) 2007-2012 USC-CSSE 1818

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/13/2012 (c) 2007-2012 USC-CSSE 1919

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/13/2012 (c) 2007-2012 USC-CSSE 20

CSCI577 Project Demonstration (1)Proyecto Pastoral Website

• User view of the deployed system– http://www.proyectopastoral.org/index.php

• Project artifacts– http://greenbay.usc.edu/csci577/fall2008/

projects/team3/

20



7/13/2012 (c) 2007-2012 USC-CSSE 21

CSCI577 Project Demonstration (2)Theatre Script Online Database

21

•User Management•Script Management



7/13/2012 (c) 2007-2012 USC-CSSE 22

CSCI577 Project Demonstration (3)AAA Petal Pushers Plant Service Tracking System



7/13/2012 2323

Proyecto Pastoral Website

(c) 2007-2012 USC-CSSE

Documents

USC e-Services Software Engineering Projects