University of Southern California

Center for Systems and Software Engineering

577a Critique Summary

Supannika Koolmanojwong CSCI 577b

University of Southern California

Center for Systems and Software Engineering

Outline

• ICSM • Tools and Methods • Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management

(C) USC-CSSE 2

University of Southern California

Center for Systems and Software Engineering

ICSM General Issues

• • • • •

Risk emphasis helpful Win-win approach creates good teamwork Need more case studies to clarify good/bad usage More coverage vs. duplication in lectures Secondary role is confusing (C) USC-CSSE 3

University of Southern California

Center for Systems and Software Engineering

ICSM

•

With the lack of experience, students do not understand the "process", just finishing documentation

The Four ICSM Principles • Stakeholder value-based system definition and evolution. • Incremental commitment and accountability. • Concurrent hardware-peopleware-software system definition and development. • Evidence and risk-based decision-making.

(C) USC-CSSE 4

University of Southern California

Center for Systems and Software Engineering

ICSM

•

With the class limitation, the team has no control over the schedule or risk-driven phase (C) USC-CSSE 5

University of Southern California

Center for Systems and Software Engineering

ICSM EPG

• • •

Stronger modeling of IV&V activities Supplement with more examples Make Benefit Chain a team activity to converge contributions (C) USC-CSSE 6

University of Southern California

Center for Systems and Software Engineering

ICSM Artifacts

• Some artifacts should have multiple agents • Full example documents • Exit criteria for each artifacts would help IIV&V focus on high-priority content vs guideline is the exit criteria • Different due dates for artifact, so to ensure the consistency and dependencies • templates really help • document template: should add "reviewed by"

(C) USC-CSSE 7

University of Southern California

Center for Systems and Software Engineering

Outline

• Overview of CS577a Critiques • ICSM •

Tools and Methods

• Lectures, Tutorials, Readings, Homework • Course Management • IV&V and Project Management

(C) USC-CSSE 8

University of Southern California

Center for Systems and Software Engineering

Overall

• • • • •

Website unavailable often Tools tutorials could be done in class Should have VDO tutorials for every tool Have single login to various tools

–

Common portal for tools Need Mac OSx compatible tool (C) USC-CSSE 9

University of Southern California

Center for Systems and Software Engineering

COCOMO / COTIPMO

• • •

Need case study for COCOMO for COTIPMO for studying COCOMO / COTIPMO are overkill COTIPMO is good; use earlier vs. should be used only when the development has started because %developed and %tested in valuation phase are always zero (C) USC-CSSE 10

University of Southern California

Center for Systems and Software Engineering

COTIPMO

•

not really helpful for certain development architecture (components not in one file)

•

not help much for planning for 2 semester team ( not a lot of changes )

•

questions should be naive user (non COCOMO expert)'s friendlier (C) USC-CSSE 11

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, starUML, visio, dia, visual Paradigmto) (C) USC-CSSE 12

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 took very long time to enter the bug and to close the bug

–

Consider alternatives to Bugzilla

•

JIRA, redmine,Trac, Gforge, FusionForge Use ClearCase / ClearQuest (C) USC-CSSE 13

University of Southern California

Center for Systems and Software Engineering

Winbook / WinWin session

• • • •

TA moderation helpful VS. pushy, confusing Planning poker

– –

Good Not useful; see others’ result; bias Need entry/exit criteria for each session First session, when clients are asked to put anything they want,



false hope (C) USC-CSSE 14

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

(C) USC-CSSE 15

University of Southern California

Center for Systems and Software Engineering

Schedule

• • •

Wants more interaction with the clients before the first meeting Schedule Team Mixer earlier

–

don't rush of committing to a team until the final day Late feedback on Mid-sem peer review (C) USC-CSSE 16

University of Southern California

Center for Systems and Software Engineering

Readings

• • •

Reduce readings to essentials More ICSM-oriented readings Textbook overkill

–

Abstract not user manual (C) USC-CSSE 17

University of Southern California

Center for Systems and Software Engineering

Assignments

• • •

In-class

–

In-class should be more challenging Homework

–

HW 6 – bad timing Less percentage on Ind. Critique (C) USC-CSSE 18

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

(C) USC-CSSE 19

University of Southern California

Center for Systems and Software Engineering

Course

• • • •

Peer evaluation, to ensure that the team member read the feedback - need follow up assignment on respond to evaluation Peer evaluation, don’t let team members read the comments Peer evaluation, do not show individual score off-campus students feel being left alone for class activities (C) USC-CSSE 20

University of Southern California

Center for Systems and Software Engineering

Website

• •

Integrate class and DEN websites Consider using Google Group vs. DEN discussion board (C) USC-CSSE 21

University of Southern California

Center for Systems and Software Engineering

Project & Team (1)

•

Need something like team meeting minutes to enforce the communication and keep all stakeholders in the loop

•

TA should form the teams based on their qualification; reflect industry-like teams (C) USC-CSSE 22

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 Should be able to meet the clients before select the projects For teams earlier; earlier mixer, experience postings Consider pre-mixer/ or ice breaker events Encourage use of Skype for DEN interactions (C) USC-CSSE 23

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

University of Southern California

Center for Systems and Software Engineering

IV&V

• • • • •

should have some guideline in the EPG on what documents are historically more important or high priority in each phase Complete documents early and peer review Prefer VB Testing than exit criteria Add macro of VB spreadsheet to prioritize orders Consider peer review as part of artifact submission process (C) USC-CSSE 25

University of Southern California

Center for Systems and Software Engineering

Individual Research Presentation

University of Southern California

Center for Systems and Software Engineering

Topics, not limited to:

• • • • • • •

New Process Model Risk Management Project Management Quality Management and Assurance Testing Architecture Cost Estimation (C) USC-CSSE 27

University of Southern California

Center for Systems and Software Engineering

Examples of research presentation from previous years

• Business Case Analysis and Tool for Software Engineering Course – Kantipa Lumyai • Requirement Gathering Tool : CaseComplete – Himani Ganjoo • Using Collaboration tools to improve artifact consistency in CS577 projects Allen Kou

(C) USC-CSSE 28

University of Southern California

Center for Systems and Software Engineering

Example (2)

• WinWinForum – Ryan Hoover • Benefits and Rationales of using Breakthrough thinking for requirement gathering/ specification. – Pachara Supanakoon

(C) USC-CSSE 29