1 / 32

577a Critique Summary

This summary provides an overview and feedback on the critique of CS577a regarding various tools, methods, lectures, tutorials, readings, homework, course management, IV&V, and project management. It covers general issues, EPG, artifacts, RSM, UML, SSAD, WikiWinWin, QA tools, project management tools, and other tools. Recommendations for improvements and enhancements for the upcoming sessions are included.

muriel
Download Presentation

577a Critique Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 577a Critique Summary Barry Boehm CSCI 577b January 22, 2010

  2. Outline • Overview of CS577a Critiques • IICM-Sw • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management (C) USC-CSSE

  3. Overview of CS577a Critiques • Very good overall • Average 144; Range 90-160 • 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-CSSE

  4. IICM-Sw Critique Summary • Overall coverage • General issues • EPG • Artifacts (C) USC-CSSE

  5. 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 (C) USC-CSSE

  6. 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 (C) USC-CSSE

  7. 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 (C) USC-CSSE

  8. Outline • Overview of CS577a Critiques • IICM-Sw • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management (C) USC-CSSE

  9. Tools and Methods Critique Summary • Overall • RSM, UML, SSAD • WikiWinWin • Project Management • Other tools (C) USC-CSSE

  10. Overall • Have team passwords for tool use, especially WikiWinWin • Have single login to various tools • Common portal for tools (C) USC-CSSE

  11. 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 (C) USC-CSSE

  12. 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 (C) USC-CSSE

  13. 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 (C) USC-CSSE

  14. 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 (C) USC-CSSE

  15. 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 (C) USC-CSSE

  16. Outline • Overview of CS577a Critiques • IICM-Sw • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management (C) USC-CSSE

  17. 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 (C) USC-CSSE

  18. 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 (C) USC-CSSE

  19. 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 (C) USC-CSSE

  20. Readings • Reduce readings to essentials • More ICM-oriented readings • Textbook overkill • Abstract not user manual (C) USC-CSSE

  21. 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 (C) USC-CSSE

  22. Outline • Overview of CS577a Critiques • IICM-Sw • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management (C) USC-CSSE

  23. 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 (C) USC-CSSE

  24. Website • Integrate class and DEN websites • Too many emails; 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 (C) USC-CSSE

  25. 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 (C) USC-CSSE

  26. 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 (C) USC-CSSE

  27. Staff • TAs very effective • Role-based mentors great; need more • Organize TA interactions to minimize waiting (C) USC-CSSE

  28. Outline • Overview of CS577a Critiques • IICM-Sw • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management (C) USC-CSSE

  29. 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 (C) USC-CSSE

  30. Project Management (2) • Decide on NDI/NCS earlier; avoid excess UML • Have formal weekly team meetings • Weak communication risky • Do more team building activities (C) USC-CSSE

  31. 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 (C) USC-CSSE

  32. IV&V: System Engineer • Need to interact with clients more • Role needs better definition (C) USC-CSSE

More Related