University of Southern California Center for Systems and Software Engineering 7/19/2013(c) 2007-2013 USC-CSSE11 USC e-Services Software Engineering Projects.

Slides:



Advertisements
Similar presentations
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Advertisements

USC Football Recruiting Database System. Team 6 Client: Jared Blank with USC Football. Revati Kadu Natasha Karnik Akshay ArasMike Nicosia (IV & V) Abhishek.
University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
University of Southern California Center for Systems and Software Engineering Social Networking Technology Usage on Web Service Projects Supannika Koolmanojwong.
Proposed Way Forward for SERC EM Task Barry Boehm, USC-CSSE 30 January 2009.
University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering (IS&SE) with the Incremental.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.
Linda Nickel EPSB Project Specialist 1.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
University of Southern California Center for Systems and Software Engineering CS 577b: Software Engineering II Class Introduction.
University of Southern California Center for Systems and Software Engineering 1 WikiWinWin: Rapid Collaborative Requirements Negotiation Using Wiki and.
University of Southern California Center for Software Engineering C S E USC August 2001©USC-CSE1 CeBASE Experience Base (eBASE) -Shared Vision Barry Boehm,
Financials – Phase II Kick-Off Meeting September 11, 2008 Brenda Bolander, State Comptroller Michael Grisser, Project Manager.
S/W Project Management
Maintaining a Microsoft SQL Server 2008 Database SQLServer-Training.com.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
TEAM’S STRONG/WEAK POINTS David Wiggins – Remote Student 1.
Operational Concept Description
University of Southern California Center for Systems and Software Engineering 10/30/2009 © 2009 USC CSSE1 July 2008©USC-CSSE1 The Incremental Commitment.
2/5/20101 R-DCR ARB Preparation A Winsor Brown CS 577B Spring 2010.
University of Southern California Center for Systems and Software Engineering Incremental Commitment Spiral Model (ICSM) for CS 577 Barry Boehm, Supannika.
University of Southern California Center for Systems and Software Engineering Project Artifacts in each process model Supannika Koolmanojwong October 09,
University of Southern California Center for Systems and Software Engineering 1 CS577a Software Engineering I DCR ARB and Package Workshop Supannika Koolmanojwong.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
1. Housekeeping Items June 8 th and 9 th put on calendar for 2 nd round of Iowa Core ***Shenandoah participants*** Module 6 training on March 24 th will.
University of Southern California Center for Systems and Software Engineering 1 Architecture Review Boards Barry Boehm 10/14/2009.
University of Southern California Center for Systems and Software Engineering Introduction to: System and Software Construction, Transition and Support.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
University of Southern California Center for Systems and Software Engineering 11/22/ CS577a Software Engineering I DCR ARB and Package Workshop Supannika.
University of Southern California Center for Systems and Software Engineering Course Overview CSCI 577a Software Engineering I Barry Boehm August 24, 2009.
University of Southern California Center for Systems and Software Engineering 7/13/2012(c) USC-CSSE11 USC e-Services Software Engineering Projects.
University of Southern California Center for Systems and Software Engineering (c) USC-CSSE Incremental Commitment Spiral Model for CSCI577 1.
University of Southern California Center for Systems and Software Engineering 10/25/2010(C) USC CSSE1 CS 577a Overall FCR Feedback [Updated/More]
University of Southern California Center for Systems and Software Engineering 577 process CSCI 577a Software Engineering I Supannika Koolmanojwong Mobasser.
University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE CSCI577B 2010 Light Weight Sw Engg for Off-the-Books.
University of Southern California Center for Systems and Software Engineering Milestone Reviews CS 577b Software Engineering II Supannika Koolmanojwong.
University of Southern California Center for Systems and Software Engineering MS Project Tutorial CSCI-577a Software Engineering I Fall 2008 Itti Charoenthongtrakul.
University of Southern California Center for Systems and Software Engineering Quality Management & Architecture Review Board October 5, 2015 ©USC-CSSE1.
University of Southern California Center for Systems and Software Engineering Incremental Commitment Spiral Model (ICSM) Supannika Koolmanojwong, USC CS.
University of Southern California Center for Systems and Software Engineering 7/23/2010(c) USC-CSSE1 08/21/09 ©USC-CSSE1 USC e-Services Software.
University of Southern California Center for Systems and Software Engineering Aug. 26, 2010 © USC-CSE Page 1 A Winsor Brown CS 577a Lecture Fall.
University of Southern California Center for Systems and Software Engineering Core Capability Drive-Through Preparation Pongtip Aroonvatanaporn CSCI 577b.
University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.
Unit 6 Application Design.
CS 577b: Software Engineering II
USC e-Services Software Engineering Projects
Client Introductions to CS577a
USC e-Services Software Engineering Projects
CS 577b: Software Engineering II
USC e-Services Software Engineering Projects
CS577a Software Engineering I DCR ARB and Package Workshop
CSCI 577a Software Engineering I Dr. Barry Boehm August 27, 2012
CSCI 577b Tasks and Activities
USC e-Services Software Engineering Projects
OCD Risk Management CS 577a, Fall 2012 ©USC-CSSE.
Software Engineering I Fall 2017
USC e-Services Software Engineering Projects
ARB Schedule Locations
CS 577b Software Engineering II -- Introduction
DEN Student Roles In Detail
Software Engineering I Fall 2017
CS577a Software Engineering ARB #2 Workshop
Core Capability Drive-Through Workshop
Executive Project Kickoff
Presentation transcript:

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects Barry Boehm, Sue Koolmanojwong, Nupul Kukreja, Daniel Link USC Center for Systems and Software Engineering Project Client Prospectus July 19, 2013 (boehm, koolmano, nkukreja, usc.edu

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE22 Outline e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE33 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

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE44 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

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE55 “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 Spiral Model

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE6 WinWin negotiation

University of Southern California Center for Systems and Software Engineering 7/19/2013 (c) USC-CSSE7 WinWin negotiation

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE8 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; students; 4-8 clients –Software, personnel, and facilities preparation –2-week transition period –then the student teams disappear Tools and techniques: Winbook; Benefit Chain; Visual Paradigm for UML; Subversion; USC COCOMO II; MS Project; USC Incremental Commitment Spiral Model method –Reworked annually based on student & client feedback 8

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE99 Outline e-Services projects overview Stakeholder win-win approach Client participation timelines Client critical success factors and benefits Example project demo

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE10 Timelines: Summer 2013 July – August 31: Project Recruiting Project Scoping, Goals and Objectives defining Classes start August 26

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 Timelines: Fall 2013 Wed. Sept. 11: Teams formed; projects selected; Fri. Sept 13: 1:00 - 2:00 pm Win-Win negotiation Training for Clients (SAL322) 2:00 - 3:20 pm CS 577a class Session with clients (OHE122) Sept 16-18: Site visit During the semester: Sept. 17 – Dec. 14 Intermediate consultation, prototype reviews, WinWin negotiation, scheduled weekly meetings with team, prototype evaluations, on-campus win-win negotiation participation & off campus follow up, Identify other success-critical stakeholders Oct. 14 – 18: FCR ARB meetings Dec 2 - 6: DCR ARB meetings Dec. 11: Submit Client evaluation form DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE12 Dec. 12, 2012…Jan. 13 to Feb.10: 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 10 to April 25: Scheduled Weekly Meetings with Teams to: –Discuss status and plans –Provide access to key transition people for strategy and readiness discussions Mar 17 to 21: Core Capability Drivethrough (Clients exercise systems) Apr 14 - Apr 18: Project Transition Readiness Reviews Apr 21: Installation and Transition –Install Product –Execute Transition Plan May 1-2: Operational Commitment Review for Initial Operational Capability May 5: Client Evaluations Timelines: Spring 2014

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE13 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

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE14 Client Critical Success Factors and Benefits Critical success factors –Mutual learning time with teams –Scenarios, prototypes, negotiations, reviews –Scheduled 1-hour weekly meeting –Win-Win 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

University of Southern California Center for Systems and Software Engineering Project Showcase Southland Partnership Corporation (SPC) Web Automation Enhancement –One Semester Analysis, Design, Development, and Transition (ADDT) with WordPress for content – 7/19/2013(c) USC-CSSE15

University of Southern California Center for Systems and Software Engineering Project Showcase Los Angeles Neighborhood Initiatives (LANI) –Eventually, one semester SaaS based on SalesForce.com –Contacts and small construction projects management 7/19/2013(c) USC-CSSE16

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE17 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, 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

University of Southern California Center for Systems and Software Engineering 7/19/2013 (c) USC-CSSE18 SalesForce.com

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE19 LANI Home Showing Apps. and Custom Tabs

University of Southern California Center for Systems and Software Engineering Project Showcase Growing Great On Line –Two semester ADDT on a Joomla platform – 7/19/2013(c) USC-CSSE20

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE21 Project Showcase Proyecto Pastoral Website A 2 semester project User view of the deployed system – 21

University of Southern California Center for Systems and Software Engineering 7/19/ Proyecto Pastoral Website (c) USC-CSSE

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE23 Project Showcase Theatre Script Online Database 23 User Management Script Management

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE24 Project Showcase AAA Petal Pushers Plant Service Tracking System