USC e-Services Software Engineering Projects Barry Boehm, Winsor Brown, Sue Koolmanojwong, Di Wu, Pongtip Aroonvatanaporn, Nupul Kukreja USC Center for Systems and Software Engineering 2009-2010 Project Client Prospectus August 21, 2009 (boehm, awbrown, koolmano, diwu, aroonvat, kukreja)@ usc.edu 08/21/09 ©USC-CSSE

Outline e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo 08/21/09 ©USC-CSSE

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 08/21/09 ©USC-CSSE

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 08/21/09 ©USC-CSSE

“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 08/21/09 ©USC-CSSE

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 08/21/09 ©USC-CSSE

Incremental Commitment Model in Software Engineering Class 08/21/09 ©USC-CSSE

WikiWinWin: Identify and Resolve Issues 08/21/09 ©USC-CSSE

Outline e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo 08/21/09 ©USC-CSSE

Timelines: Summer 2009 July – August 21: Project Recruiting Project Scoping, Goals and Objectives defining Friday August 21: Potential Clients’ meeting II 08/21/09 ©USC-CSSE

Timelines: Fall 2009 Sept. 9: Teams formed; projects selected; Sept 10: Site visit Sept 11: 11:00 - 12:30 hands on WWW training (ITS lab) 12:30 - 1:30 lunch and Q&A session with staff (SAL322) 2:00 - 3:20 pm CS 577a class Session with clients (OHE122) During the semester: Sept. 10 – Dec. 10 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 Oct 1 : VCR preparation and teleconference meeting Oct. 19-23: FCR ARB meetings Nov 30- Dec 4: DCR ARB meetings Dec. 11: Submit Client evaluation form DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review; WWW: WikiWinWin 08/21/09 ©USC-CSSE

Timelines: Spring 2010 Jan. 11- Feb. 12: Work with teams: Rebaseline prototype, prioritize requirements Plan for CS 577b specifics, including transition strategy, key risk items Participate in ARB review Feb 15 – May 7: Scheduled Weekly Meetings with Teams to: Discuss status and plans Provide access to key transition people for strategy and readiness discussions Mar 8 – 26: 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 7: Client Evaluations 08/21/09 ©USC-CSSE

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 08/21/09 ©USC-CSSE

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 08/21/09 ©USC-CSSE

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/ 08/21/09 ©USC-CSSE

CSCI577 Project Demonstration (2) Theatre Script Online Database User Management Script Management 08/21/09 ©USC-CSSE

CSCI577 Project Demonstration (3) AAA Petal Pushers Plant Service Tracking System 08/21/09 ©USC-CSSE

For more information http://greenbay.usc.edu/csci577/fall2009/site/clients/index.html Or email boehm@usc.edu awbrown@usc.edu koolmano@usc.edu aroonvat@usc.edu 08/21/09 ©USC-CSSE

Proyecto Pastoral Website 08/21/09 ©USC-CSSE