University of Southern California Center for Systems and Software Engineering 577a Critique Summary Barry Boehm CSCI 577b January 22, 2010

University of Southern California Center for Systems and Software Engineering Outline Overview of CS577a Critiques IICM-Sw Tools and Methods Lectures, Tutorials, Readings, Homework Course Management IV&V and Project Management 1/22/102(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Overview of CS577a Critiques Very good overall –Average 144; Range Will address some suggestions in 577b –Homework, grading, websites, communication, IV&V interaction Most apply to 577a; will rework for Fall 2010 –DC Package content, tools, readings, 577a homework, tutorials, sizing Project Management lessons learned valuable for 577b (C) USC-CSSE31/22/10

University of Southern California Center for Systems and Software Engineering IICM-Sw Critique Summary Overall coverage General issues EPG Artifacts (C) USC-CSSE41/22/10

University of Southern California Center for Systems and Software Engineering ICM-Sw General Issues Risk emphasis helpful Win-win approach creates good teamwork Need more case studies to clarify good/bad usage More coverage in lectures 1/22/105(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering ICM-Sw EPG Stronger modeling of IV&V activities Include exit criteria more explicitly Clarify artifacts that are needed e.g. test planning Supplement with more examples Add needed role/skills to EPG Better search capability Better navigation aids Would be nice to have tailored subsets of EPG for project roles 1/22/106(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering ICM-Sw Artifacts Some artifacts should have multiple agents More special packaging of templates for NDI/NCS Consolidate OCD and SSRD More consistent template formatting 1/22/107(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of CS577a Critiques IICM-Sw Tools and Methods Lectures, Tutorials, Readings, Homework Course Management IV&V and Project Management 1/22/108(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Tools and Methods Critique Summary Overall RSM, UML, SSAD WikiWinWin Project Management Other tools (C) USC-CSSE91/22/10

University of Southern California Center for Systems and Software Engineering Overall Have team passwords for tool use, especially WikiWinWin Have single login to various tools –Common portal for tools 1/22/1010(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering RSM, UML, SSAD RSM –RSM licensing problem with Windows Vista and 7 –Consider using different tools other than RSM (i.e. Argo UML) –Not suited for modeling non-technical business workflow 1/22/1011(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering WikiWinWin Simplify WikiWinWin and improve navigation among pages Only project participants should have WikiWinWin write rights Have Requirements Engineer serve as WikiWinWin shaper Use a mock negotiation session in WikiWinWin training Have wider gap between WikiWinWin sessions 1/22/1012(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering QA Tools Bugzilla –Make easier to search by fix agent, bug type, etc. –Higher criticality threshold for Bugzilla entries –Improve procedures too lock-stop; too slow –Consider alternatives to Bugzilla iStudio –Need to update NDI/NCS definitions 1/22/1013(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Project Management COCOMO II –Reengineer COCOMO II or use COINCOMO DART –Extend DART to track risk resolutions –Have clients use DART –Fix DART bugs, e.g. RE = P(UO) & L(UO) ER –Use work breakdown structure to link planning and effort reporting MS Project –Consider using Google Calendars as alternative to MS Project 1/22/1014(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Other Tools Prototyping –Consider using iRise for initial prototypes Business workflow –Visio Business Workflow better than RSM for non-technical flows More change/fix auto-notification of affected parties Use of Google Wave for communications Use of Google Docs 1/22/1015(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of CS577a Critiques IICM-Sw Tools and Methods Lectures, Tutorials, Readings, Homework Course Management IV&V and Project Management 1/22/1016(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Lectures (1) More coverage of psychology and people factors More explanation of COCOMO drivers More industry guest lecturers Cover function point sizing –More on sizing in general Explain team roles early for better team formation More on the use of effort reports –Often enter overlaps in most relevant category 1/22/1017(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Lectures (2) Less just-in-time lecture coverage of deliverables Less redundancy in lecture materials Post lecture materials earlier Update obsolete lecture charts –MBASE, … Better content sequencing for 1-semester projects Have general-class prototype demo sessions 1/22/1018(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Tutorials Need more tutorials for RSM, even recorded ones More training for shapers Use homework to reinforce tutorials Record tutorials for later review Make sign-ups electronic vs. physical Ensure tutorials are done before assignments due 1/22/1019(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Readings Reduce readings to essentials More ICM-oriented readings Textbook overkill –Abstract not user manual 1/22/1020(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Assignments In-class –Continue having in-class quizzes later in semester –More content in later in-class exercises Homework –More feedback on skills-learning homework –Do a mid-semester critique –Encourage students to keep a critique log –Consider an early practical homework assignment –Spread assignments more widely; less upfront –Faster grading turnaround 1/22/1021(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of CS577a Critiques IICM-Sw Tools and Methods Lectures, Tutorials, Readings, Homework Course Management IV&V and Project Management 1/22/1022(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Course Architects’ special meeting good; need more Schedule should include all deadlines, e.g. surveys More emphasis on architecture; mini-ARBs More rapid response on questions, grading Longer ARB sessions Rework commitment form; demotivating Even out Foundations phase workload 1/22/1023(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Website Integrate class and DEN websites Too many s; use website or discussion board more More use of Google Calendar for assignment reminders Consider using Google Group vs. DEN discussion board Consider standardizing team websites 1/22/1024(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Project & Team (1) Assign students to teams randomly Stronger identification of weak performers Emphasize constructiveness of peer evaluations More emphasis on doing peer reviews Encourage more team building activities Require multi-country tteams 1/22/1025(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Project & Team (2) More role-based group meetings Do team mixer earlier Provide more info on projects to be selected For teams earlier; earlier mixer, experience postings Consider pre-mixer/ or ice breaker events Encourage use of Skype for DEN interactions 1/22/1026(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Staff TAs very effective Role-based mentors great; need more Organize TA interactions to minimize waiting 1/22/1027(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of CS577a Critiques IICM-Sw Tools and Methods Lectures, Tutorials, Readings, Homework Course Management IV&V and Project Management 1/22/1028(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Project Management (1) Need to be pro-active with clients Complete documents early and peer review Don’t over focus WikiWinWin on just capabilities Better naming and numbering of builds Prototyping –Do build-on (JSP) vs. throwaway (iRise) prototypes –Prototype much earlier 1/22/1029(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Project Management (2) Decide on NDI/NCS earlier; avoid excess UML Have formal weekly team meetings Weak communication risky Do more team building activities 1/22/1030(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering IV&V: Reviewing IV&V very helpful Exit criteria could be improved –Only helpful early –Go value-based early Clarify, reinforce IV&V roles, activities Tendency of IV&Vers to destabilize design (sometimes good) More up-front participation 1/22/1031(C) USC-CSSE

University of Southern California Center for Systems and Software Engineering IV&V: System Engineer Need to interact with clients more Role needs better definition 1/22/1032(C) USC-CSSE