Using Software Project Courses to Integrate Education and ResearchOutline2009-10 Software Engineering ProjectsSlide 4MBASE Model Integration: LCO StageSlide 6The ResultsSlide 8Empirical Software Engineering ResearchSlide 10WikiWinWin – ToolWikiWinWin – Current ProgressSlide 13Axiom 1. Process Happens Where the Effort HappensCBA Spiral FrameworkCOTS Assessment ExampleExample: USCCS Evaluation ResultsInteroperability Evaluation Framework InterfacesiStudio ToolExperiment 1 ResultsSlide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Pair Development vs. Fagan Inspection TDC = Total Development CostsLean MBASE Effort ComparisonICM Electronic Process GuideIntegrating Software Research, EducationUniversity of Southern CaliforniaCenter for Systems and Software EngineeringUsing Software Project Courses to Integrate Education and ResearchBarry BoehmNovember 18, 2009University of Southern CaliforniaCenter for Systems and Software EngineeringOutline•Nature of real-client project course–Primarily USC campus, neighborhood e-services –MS-level; 2 semester; 6-8 person teams–Well-instrumented for continuous improvement•Research/education integration via project experiments–Validate new methods and tools via project usage–Partial basis of 12 PhD dissertations–Rqts. negotiation, formalization (3), COTS integration (2), Value-based methods (3), Agile methods (1), Quality tradeoffs (1), Risk analysis (1), Cost estimation (1)•Conclusions 11/18/2009University of Southern CaliforniaCenter for Systems and Software Engineering2009-10 Software Engineering Projects11/18/2009Project Client OrganizationOnline DB support for CSCI 511 Jim Alstad CSCI 511SHIELDS for Family Reginald Van Appelen SHIELDS for FamiliesTheater Stage Manager Program Julie Sanchez Jules T BearGrowing Great Online Matt McMahon GrowingGreatSPC Website Automation Enhancement Dean L. Jones Southland Partnership CorporationVALE Information Management System Pamela Clay Livingadvantage Inc.LANI D-Base Ashley WestmanLos Angeles Neighborhood Initiative (LANI)Freehelplist.org Stephen Wolfson FreehelplistEarly Medieval East Asian Timeline Ken Klien USC East Asian LibraryBHCC Website Development Cesar ArmendarizBoyle Heights Chamber Of CommerceClient Case Management Database OR Marcy Pullard Avenue Of IndependenceWebsite Development : Avenue Of Independence Marcy Pullard Avenue Of IndependenceHealthcare The Rightway Roderick Foreman Right Way DirectionAROHE Web Development Janette Brown AROHEUniversity of Southern CaliforniaCenter for Systems and Software Engineering11/18/2009University of Southern CaliforniaCenter for Systems and Software EngineeringMBASE Model Integration: LCO Stage11/18/2009Domain ModelWinWin TaxonomyBasic Conceptof OperationFrequentRisksStakeholders,Primary win conditionsWinWin NegotiationModelIKIWISI Model,Prototypes,Properties ModelsEnvironmentModelsWinWin Agreements, Shared VisionViableArchitectureOptionsUpdated ConOps, Business CaseLife Cycle PlanelementsOutstanding LCO risksRequirementsDescriptionLCO RationaleLife Cycle Objectives (LCO) PackageAnchor PointModeldeterminesidentifiesidentifiesdeterminessituates exercise exercisefocususe of focus use of determinesguidesdetermination ofvalidateinputs for providesinitialize adopt identify identifyupdate updateachieveiterate tofeasibility,consistency determines exitcriteria for validates readiness ofinitializesUniversity of Southern CaliforniaCenter for Systems and Software Engineering11/18/2009S&C Subdomain (General)1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 20, 31, 32, 35, 36, 37, 39Type ofApplicationSimple Block DiagramExamples(project nos.)DeveloperSimplifiersDeveloperComplicatorsMultimediaArchive- Use standardquery languages- Use standard orCOTS searchengine- Uniform mediaformats- Natural languageprocessing- Automatedcataloging orindexing- Digitizing largearchives- Digitizingcomplex or fragileartifacts- Automatedannotation/description/ or meaningsto digital assets- Integration oflegacy systemsMM assetinfoCatalogMMArchivequeryMM assetupdatequeryupdatenotification- Rapid access tolarge Archives- Access toheterogeneousmedia collectionsUniversity of Southern CaliforniaCenter for Systems and Software EngineeringThe Results•Projects That Failed LCO Criteria•Post-1997 failures due to non-S&C causes–Team cohesion, client outages, poor performance11/18/2009University of Southern CaliforniaCenter for Systems and Software EngineeringOutline•Nature of real-client project course–Primarily USC campus, neighborhood e-services –MS-level; 2 semester; 6-8 person teams–Well-instrumented for continuous improvement•Research/education integration via project experiments–Validate new methods and tools via project usage–Partial basis of 12 PhD dissertations–Rqts. negotiation, formalization (3), COTS integration (2), Value-based methods (3), Agile methods (1), Quality tradeoffs (1), Risk analysis (1), Cost estimation (1)•Conclusions and references11/18/2009University of Southern CaliforniaCenter for Systems and Software EngineeringEmpirical Software Engineering Research•Empirical software engineering research generally slow–Projects take 2-5 years to complete–Improvements confounded with other factors–Data generally sparse, hard to compare across projects•Team projects the ESE equivalent of the fruit fly–20 per year, real clients, using industrial-grade processes–Teams include 2 off-campus working professionals–1-2 of 6 on-campus students have 1-2 years work experience–Extensive data, consistently collected–Opportunities to run (partially) controlled experiments•Projects, teams not identical11/18/2009University of Southern CaliforniaCenter for Systems and Software Engineering11/18/2009Project Course Experience Factory Projects Organization Experience Factory1. Characterize2. Set Goals3. Tailor ProcessExecution plans4. Execute ProcessProjectSupport5. Analyzeproducts,lessons learned,models6. TechnologyInitializeApply, RefineFormalizeDisseminateExperienceBaseenvironmentcharacteristicstailorabletechnology,mentoringprojectanalysis,processmodificationdata,lessonslearnedUniversity of Southern CaliforniaCenter for Systems and Software Engineering11/18/2009WikiWinWin – ToolShaper facilitate negotiation in WikiWinWinInitial ideas surfaced at the meetingShaper organize them into a prospective win condition after the meetingStakeholders engage in a further discussionUniversity of Southern CaliforniaCenter
View Full Document
Unlocking...