1. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1 08/21/09 ©USC-CSSE1 USC e-Services Software Engineering Projects Winsor Brown, Sue Koolmanojwong, Di Wu, Pongtip Aroonvatanaporn, Nupul Kukreja, Qi Li, Ramin Moazeni USC Center for Systems and Software Engineering 2010-2011 Project Client Prospectus July 23, 2010 (awbrown, koolmano, diwu, aroonvat, nkukreja, qli1, moazeni)@ usc.edu

2. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE208/21/09©USC-CSSE2 Outline e-Services examples from 2009-2010 e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo

3. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE3 2009-2010 Project Showcase SPC Web Automation Enhancement –One Semester Analysis, Design, Development, and Transition (ADDT) with WordPress for content –http://www.istartonmonday.com 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

4. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE4 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

5. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE5 LANI @ SalesForce.com

6. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE6 LANI Home Showing Apps. and Custom Tabs

7. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE7 LANI @ SalesForce.com Showing Setup options

8. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE808/21/09©USC-CSSE8 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

9. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE9 08/21/09 ©USC-CSSE9 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

10. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1008/21/09©USC-CSSE10 “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

11. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE11 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: 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-CSSE11

12. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE12 Incremental Commitment Model in Software Engineering Class 08/21/09©USC-CSSE12

13. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE1308/21/09©USC-CSSE13 WikiWinWin: Identify and Resolve Issues

14. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1408/21/09©USC-CSSE14 Outline e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo

15. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1508/21/09©USC-CSSE15 Timelines: Summer 2010 July – September 10: Project Recruiting Project Scoping, Goals and Objectives defining Monday August 16: Potential Clients’ meeting II Project Scoping, Goals and Objectives defining Classes start August 23

16. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1608/21/09©USC-CSSE16 Timelines: Fall 2010 Sept. 8: Teams formed; projects selected; Sept 10: 9:30 - 11:00 hands on WWW training (in an ITS classroom) 12:30 - 1:30 lunch and Q&A session with staff (SAL322) 2:00 - 3:20 pm CS 577a class Session with clients (OHE122) Sept 10-13: Site visit 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 Sep 21 : VCR preparation and teleconference meeting Oct. 18-22: FCR ARB meetings Nov 29-Dec 3: DCR ARB meetings Dec. 11: Submit Client evaluation form DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review; WWW: WikiWinWin

17. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1708/21/09©USC-CSSE17 Dec. 12, 2010..Jan. 10 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 21 to 25: Core Capability Drivethrough (Clients exercise systems) Apr 15 - Apr 16: Project Transition Readiness 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 Timelines: "Spring" 2011

18. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1808/21/09©USC-CSSE18 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

19. University of Southern California Center for Systems and Software Engineering 7/23/2010(c) 2007-2010 USC-CSSE1908/21/09©USC-CSSE19 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

20. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE20 CSCI577 Project Demonstration (1) Proyecto Pastoral Website User view of the deployed system –http://www.proyectopastoral.org/index.phphttp://www.proyectopastoral.org/index.php Project artifacts –http://greenbay.usc.edu/csci577/fall2008/project s/team3/ 08/21/09©USC-CSSE20

21. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE21 CSCI577 Project Demonstration (2) Theatre Script Online Database 08/21/09©USC-CSSE21 User Management Script Management

22. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE22 CSCI577 Project Demonstration (3) AAA Petal Pushers Plant Service Tracking System 08/21/09©USC-CSSE22

23. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE23 For more information http://greenbay.usc.edu/csci577/fall2010/site/ clients/index.htmlhttp://greenbay.usc.edu/csci577/fall2010/site/ clients/index.html Or email –A Winsor Brown: awbrown@usc.eduawbrown@usc.edu –Nupul Kukreja: nkukreja@usc.edu@usc.edu –Ramin Moazeni: moazeni@usc.edu@usc.edu 08/21/09©USC-CSSE23

24. University of Southern California Center for Systems and Software Engineering 7/23/201008/21/09(c) 2007-2010 USC-CSSE ©USC-CSSE2408/21/09©USC-CSSE24 Proyecto Pastoral Website