DOC PREVIEW
USC CSCI 577 - USC_e-Services_Software_Engineering_Projects-110721

This preview shows page 1-2-21-22 out of 22 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1Slide 2Slide 3Project ShowcaseLANILANI @ SalesForce.comLANI Home Showing Apps. and Custom TabsLANI @ SalesForce.com Showing Setup optionsSlide 9WikiWinWin: Identify and Resolve IssuesSlide 11Software Engineering Project Course (CS 577)Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18CSCI577 Project Demonstration (1) Proyecto Pastoral WebsiteCSCI577 Project Demonstration (2) Theatre Script Online DatabaseCSCI577 Project Demonstration (3) AAA Petal Pushers Plant Service Tracking SystemSlide 22University of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 11USC e-Services Software Engineering ProjectsBarry Boehm, Sue Koolmanojwong, Pongtip Aroonvatanaporn, Nupul Kukreja USC Center for Systems and Software Engineering2011-2012 Project Client ProspectusJuly 21, 2011(boehm, koolmano, aroonvat, nkukreja)@ usc.eduUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 22Outline•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 demoUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 33e-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 factorUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 4Project 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 HistoryUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 5LANI•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 snapshotsUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 6LANI @ SalesForce.comUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 7LANI Home Showing Apps. and Custom TabsUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 8LANI @ SalesForce.com Showing Setup optionsUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 99Stakeholder 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 Engineering7/21/2011 (c) 2007-2011 USC-CSSE 1008/21/09 10WikiWinWin: Identify and Resolve IssuesUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 1111“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, Risk Mgt. processes•Integrate all these considerations - Via Incremental Commitment ModelUniversity of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 12Software 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 Spiral Model method –Reworked annually based on student & client feedback12University of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 1313Outline•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 Engineering7/21/2011 (c) 2007-2011 USC-CSSE 1414Timelines: Summer 2011• July – August 31: •Project Recruiting•Project Scoping, Goals and Objectives defining•Thursday August 18: •Potential Clients’ meeting II•Project Scoping, Goals and Objectives defining•Classes start August 22University of Southern CaliforniaCenter for Systems and Software Engineering7/21/2011 (c) 2007-2011 USC-CSSE 1515Timelines: Fall 2011•Sept. 9: Teams formed; projects


View Full Document

USC CSCI 577 - USC_e-Services_Software_Engineering_Projects-110721

Documents in this Course
ec-04

ec-04

39 pages

CSep15

CSep15

37 pages

ec-24

ec-24

42 pages

ec-11

ec-11

42 pages

ep10

ep10

6 pages

ec-07

ec-07

51 pages

ec-02

ec-02

22 pages

Load more
Download USC_e-Services_Software_Engineering_Projects-110721
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view USC_e-Services_Software_Engineering_Projects-110721 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view USC_e-Services_Software_Engineering_Projects-110721 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?