Impact of Software Process on Quality Workshop – Day 2

Ege University 22 May 2004

2

Reklamlar…

http://groups.yahoo.com/group/harezmi/

HAREZMI Newsgroup – Türk Yazılım Mühendisliği Haber/Tartışma GrubuDil: Türkçe

Yazilim muhendisligi konulari hakkinda sorular/cevaplar Yazilim muhendisligi ile alakali calistay/seminer duyurusu Yazilim muhendisligi hakkinda is imkanlari duyurusu (yurtici ve yurtdisi) Beraber proje calisma onerisi (yurtici/yurtdisi) Yazilim muhendisligi hakkinda ilginc linkler Beraber calistay/seminer organizesinin onerisi Son teknoloji duyurulari Ilginc makaleler/kitaplar/dergiler Yazilim muhendisligi egitimi hakkinda sorular/bilgiler Yazilim muhendisligi musabakalarin duyurusu - vs.

Üye Olun!Bizlere Katılın

3

4

5

Program – Discussion Sessions

9:00 - 10:30 Panel Session I

10:30-11:00Break

11:00-12:00Introduction to Discussion Session and start of Discussions

12:00-13:30Lunch

13:30-15:00Discussion Session II – Define Mindmap and related questions

15:00-15:30Break

15:30-16:30Discussion Session III – Describe Approach

16:30-17:00Plenary Session – Presentation of Results

6

Panel

Topic: Relation between process and quality

Panel Members: Naci Akkök, University of Oslo Yenal Göğebakan, Cybersoft Orhan Kalaycı, Nitelik Danışmanlık Alpay Karagöz, Bilgi Grubu Halil Şengonca, Ege Universitesi

7

Approach

5-10 minutes view of each panel member Open discussion with audience

8

Questions

Different processes; processes are not independent from each other How to derive the best possible processes and/or improvement

models? Goal driven process selection, customization and improvement (what

are the business goals) Metrics for process selection and customization and improvement

(tailoring) usability of process for company; usability is upper metric consisting of

sub-metrics (size of project, application characteristics…) Constraints for selecting processes

Organizational perspectives of selecting processes Social issues Psychological (resistance/acceptance) Technological Skills of persons

9

Questions

What is the quality of company? How to evaluate? Metric based on process level (CMM level) Other metrics independent from CMM level?

Company/Organisation improvement instead of process improvement?

How to categorize projects to select the appropriate process?

10

Questions

Impact of stakeholders (clients) for impact of selection on process/process improvement model?

What’s the impact of the domain on process? How to evaluate process improvement models? “Selecting a process selects quality” Context analysis

11

Questions

Tailoring of processes Select/refine processes based on project

criteria/characteristics How to compose processes?

Usability

12

Short/initial summary

Business Requirements

Process Selection

Process Improvement Models

Evaluation of Process Improvement Models

Constraints

ProductRequirements

Process

refinement

13

Questions

Discussion Session I

15

Splitting the group

Tools

1.

2.

3.

4.

5.

6.

7.

8.

Criteria for

Processes

1.

2.

3.

4.

5.

6.

7.

8.

Comp.SD and

DE(Process)

1.

2.

3.

4.

5.

6.

7.

8.

Metrics

1.

2.

3.

4.

5.

6.

7.

8.

Modeling?

1.

2.

3.

4.

5.

6.

7.

8.

16

Deliverables

The session should deliver

(1) a mindmap and

(2) a set of problem descriptions:

17

Mindmap

(1) Mindmap: Draw one mindmap that shows the context of the described problems/domain.

Tutorials Demonstrations

Workshops

Planning

Social Program

Invited Talk

Costs

Conference Organization

Topics

Rooms

Workshop chair

Tasks

Students

Resources

Sightseeing

Dinner

Accomodation

Proceedings

Sub-topics associated with each main idea here, into sub-branches

Main ideas associated with the core idea here

18

Alternative Representation

Conference Organization

TutorialsPlanning

Social Program

Workshops

Invited TalkCosts

Demonstrations

19

Define for each main idea the most important problems

Core Idea

Main Topic2

Main Topic3

Main Topic4

Main Topic5

Main Topic1

Problem 4

Problem 5

Problem 2

Problem 3

Problem 1

20

Problem Description

The problems should be described in the following form:

Problem: describe textually what the problem is.

Why is it a problem?: Motivate why is this a fundamental problem.

21

Deliverables

The session should deliver a set of solution descriptions.

A solution description should be in the following format:

Problem: Describe the problem.Potential Approach: Describe the approach to tackle the problemRelated Work: List the related knowledge domains/related work for this problem

22

Deliverables lead to assignments/projectsExample:

Problem: Software Architecture Design is a Heavy Process which takes a long time before it

is finished. In practice however, due to stringent time-to-market requirements faster delivery is required…

Potential Approach: Apply agile methods to software architecture design methods.

Related Work: Software Architecture Design Agile Methods Method Engineering