Slide 1Slide 2Slide 3Slide 4Slide 5Software Engineering Project Course (CS 577)Incremental Commitment Model in Software Engineering ClassWikiWinWin: Identify and Resolve IssuesSlide 9Slide 10Slide 11Slide 12Slide 13Slide 14CSCI577 Project Demonstration (1) Proyecto Pastoral WebsiteCSCI577 Project Demonstration (2) Theatre Script Online DatabaseCSCI577 Project Demonstration (3) AAA Petal Pushers Plant Service Tracking SystemFor more informationSlide 19University of Southern CaliforniaCenter for Systems and Software Engineering08/21/09©USC-CSSE 1USC e-Services Software Engineering ProjectsBarry Boehm, Winsor Brown, Sue Koolmanojwong, Di Wu, Pongtip Aroonvatanaporn, Nupul KukrejaUSC Center for Systems and Software Engineering2009-2010 Project Client ProspectusAugust 21, 2009(boehm, awbrown, koolmano, diwu, aroonvat, kukreja)@ usc.eduUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 2Outline•e-Services projects overview•Stakeholder win-win approach•Client participation timelines•Client critical success factors and benefits•Example project demoUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 3e-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 factorUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09©USC-CSSE 4Stakeholder Win-Win ApproachStakeholders•Students, Employers•Project clients•Faculty, ProfessionWin 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 projectsUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 5“Software Engineering”: The disciplines which distinguish the coding of a computer program from the development of a software productRequirements, Design, Implement, Architecture Code MaintainStagesIssuesComputer ScienceUser ApplicationsEconomicsPeopleCS Focus•Accommodate new tools and techniques•Web services, GUI prototypers, WinWin, Spiral processes•Integrate all these considerations- Via Incremental Commitment ModelUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSoftware 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 feedback08/21/09 ©USC-CSSE 6University of Southern CaliforniaCenter for Systems and Software EngineeringIncremental Commitment Model in Software Engineering Class08/21/09 ©USC-CSSE 7University of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 8WikiWinWin: Identify and Resolve IssuesUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 9Outline•e-Services projects overview•Stakeholder win-win approach•Client participation timelines•Client critical success factors and benefits•Example project demoUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 10Timelines: Summer 2009• July – August 21: •Project Recruiting•Project Scoping, Goals and Objectives defining•Friday August 21: •Potential Clients’ meeting IIUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 11Timelines: 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 formDCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review; WWW: WikiWinWinUniversity of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 12Jan. 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 DrivethroughApr 15 - Apr 16: Project Transition Readiness ARB ReviewsApr 20: Installation and Transition–Install Product–Execute Transition Plan May 4-5: Operational Commitment Review for Initial Operational CapabilityMay 7: Client EvaluationsTimelines: Spring 2010University of Southern CaliforniaCenter for Systems and Software Engineering08/21/09 ©USC-CSSE 13Architecture Review Boards•Commercial best practice- AT&T, Lucent, Citibank•Held at critical commitment points- FCR, DCR milestones•Involve stakeholders, relevant experts- 1
View Full Document
Unlocking...