Impact of Software Process on Quality Workshop

1
Impact of Software Process on Quality Workshop
Day 2Ege University 22 May 2004
2
Reklamlar ?

• http//groups.yahoo.com/group/harezmi/
• HAREZMI Newsgroup Türk Yazilim Mühendisligi
  Haber/Tartisma Grubu
• Dil 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 Katilin
3
(No Transcript)
4
(No Transcript)
5
Program Discussion Sessions

• 900 - 1030 Panel Session I
• 1030-1100 Break
• 1100-1200 Introduction to Discussion Session
  and start of Discussions
• 1200-1330 Lunch
• 1330-1500 Discussion Session II Define
  Mindmap and related questions
• 1500-1530 Break
• 1530-1630 Discussion Session III Describe
  Approach
• 1630-1700 Plenary Session Presentation of
  Results

6
Panel

• Topic
• Relation between process and quality
• Panel Members
• Naci Akkök, University of Oslo
• Yenal Gögebakan, Cybersoft
• Orhan Kalayci, Nitelik Danismanlik
• Alpay Karagöz, Bilgi Grubu
• Halil Sengonca, 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?
• Whats 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
Product Requirements
Evaluation of Process Improvement Models
Process Selection
Process Improvement Models
refinement
Constraints
Process
13
Questions
14
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
• a mindmap and
• a set of problem descriptions

17
Mindmap

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

18
Alternative Representation
Invited Talk
Costs
Workshops
Demonstrations
Conference Organization
Social Program
Tutorials
Planning
19
Define for each main idea the most important
problems
Main Topic5
Main Topic1
Core Idea
Main Topic2
Main Topic4
Main Topic3
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 problem
• Related Work List the related knowledge
  domains/related work for this problem

22
Deliverables lead to assignments/projects

• Example
• 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