| Tutorial T1 : |
SPI models and architectures for beginners -
staged and continuous, SPICE and CMMI |
|
John Hamilton, DERA , SPICE working group, (UK) |
This is a tutorial with a strong process assessment/CMM/SPICE theme
addressing systems as well as software - to be given by John Hamilton - a
leading expert - leading the SPICE standards activity. |
| Tutorial T2 : |
"PIPSI" - Process for Improving Programming Skills in Industry |
|
IVF (Sweden) and Gerry Coleman from IPSSI Consortium |
PIPSI is a European Commission funded initiative which provides a process
improvement framework for use by individual software engineers working in
European SMEs.
PIPSI focuses on two areas of concern to the software engineer - Personal
Project Management and Personal Quality Management. Both of these are
supported by an estimating process and the use of appropriate metrics for
measuring past success in estimating and providing a basis for future
planning. Each program worked on is treated as a 'project' by the software
engineer, who starts with a planning and estimating phase before starting
work on the program. As the work progresses detailed metrics are kept,
which are used both to monitor progress and to build up a history. These
metrics are personal to the programmer at all times, and are not available
to management for productivity assessment or similar purposes.
|
| Tutorial T3 : |
Workshop on GQM/B |
|
Mr. Ralf Kempkens and Mr. Rini van Solingen, Fraunhofer
IESE, (Germany) |
'You can't control, what you can't measure', is a widely accepted
statement. For professional decision-making and the professional execution
of software projects, a lot of information is needed. By measuring
software
processes and products, company specific information and knowledge on
software practices becomes available. This information can be used for
decision making, planning, improvement and cost/duration estimations. One
prerequisite is that in order to be able to identify the right metrics,
the
goals and related questions for measurement are explicitly defined. The
Goal/Question/Metric approach (GQM) follows these rules and has proven its
usefulness in the past years.
The objective of this workshop is to provide the audience with knowledge
and vision in the benefits of software measurement application with the
GQM
approach. Exchange of measurement experiences among the participants will
be an integral part of the workshop.
|
| Tutorial T4 : |
Assessment and Accreditation of Skills with a Network Based System Approach |
|
CREDIT Project, University of Amsterdam (NL), Telematica (UK), ISCN (IRL) |
In Europe the education systems are very different For instance, a
software engineer from UK has different qualifications than one from
Germany, although in a global market place they are used for e.g. the same
position in an organisation.
Also people collect different experiences over the time, which upgrade
their personal knowledge, but make them different from others.
So an organisation consists of many different individual brains
(experiences) and the knowledge gathered in them. The processes are then
just a mean to focus that knowledge on a business success of the firm.
A way to focus and direct this knowledge is to establish a skill profiling
and learning system which helps engineers from the workplace to get their
internal advise on a personal learning route, and the system ensures that
(although offered on a personal level) a common focus is achieved.
Here we refer to the EU project CREDIT which developed a generic
(configurable) environment which can be adapted to different skill sets,
learning routes, and offers guidance through an Intranet system. |
| Tutorial T5 : |
COSMIC - new software sizing techniques and developments and applications in software estimation process |
|
Charles Symons from USKMA/FESMA Consortium |
Being able to measure the functional size of software from its
requirements or specification, independently of the technology used for
its construction, is vital for estimating and project performance
measurement.
COSMIC (the COmmon Software Measurement International Consortium) is a
global initiative to develop a new functional sizing method which will be
equally applicable for sizing Business/MIS and real-time (e.g. telecoms,
process control, operating system, embedded, etc.) software.
Charles Symons' Tutorial will give an overview of the evolution of
functional size measurement, an introduction to the COSMIC FFP method, and
some results from the field trials which have confirmed the validity of
the method.
|
| Tutorial T6 : |
Software Process Improvement for E-business
applications |
|
Onion Technologies (Italy) |
Title "Software Process Improvement for E-business applications"
This half-day tutorial deals with SPI/ Testing for Web-based
applications. The tutorial covers both theoretical and pragmatic
aspects; the training material is constantly kept up-to-date with
respect to the unprecedented growth rate and dynamism of Internet
technologies and e-business. |
| Tutorial T7 : |
SPICE Update - the current ISO development work and complementary activities |
|
Risto Nevalainen, STTF (Finland) |
This tutorial explains SPICE architecture, reference model and assessment
process in the current ISO TR15504 standard set and in the coming ISO15504
standard. The current model is compared with some other published models,
especially the new CMMI model and SWEBOK 0.7 draft document.
SPICE model is used quite intensively in some European countries and also
worldwide. The experiences from Finland are explained. FiSMA (Finnish
Software Metrics Association) has created an assessment data base. Some
results from the database are explained and compared with SPICE trials
data.
Tutorial has following short presentations and discussion topics:
1. SPICE architecture and reference model
2. SPICE compared with CMM and CMMI models
3. The current ISO work to publish new ISO15504 standard set
4. Relations between SPICE and other standardisation activities
5. FiSMA SPICE assessment method
6. Examples of SPICE applications and extensions in Finland
7. FiSMA SPICE assessment database and statistical findings
|
| Tutorial T8 : |
How and when to apply tools in Software Test |
|
Chris Bagge & Kai Ormstrup, DELTA (Denmark) |
Tools can, correctly applied, increase the quality and productivity of the
software test process. This tutorial discusses what type of tools to use
in the different phases of the software development process. It dos as
well indicate what other conditions that shall be fullfilled to achieve a
successfull introduction and use of test tools. |
| Tutorial T9 : |
Better Requirements Using Scenarios, Prototyping and Usability Test |
|
Otto Vinter & Mads Christiansen, DELTA ( Denmark) |
The tutorial will illustrate the use of scenarios, prototypes and
usability test in the requirement phase. Applying the techniques results
in better products, partly because they address the real needs, partly
because they improve transfer of knowledge from the customer and/or the
user to the development team and finally because they improve cooperation
internally in the development team during the development life cycle.
|
| Tutorial T10 : |
A Learning Organisation Model and Virtual Enterprise for Process Improvement |
|
ISCN, Cork Institute of Technology (IRL), General Fundacion (Spain), Sztaki (Hungary) |
Many process improvement experts are too convinced from only one
(their
own) approach, leading to statements such as : Only Capability maturity
Model (CMM) will work; or, only Bootstrap will work; or, only SPICE (ISO
15504) is a comprehensive enough assessment framework; or, just skip all
assessment methodologies and use goal based metrics, and so forth.
Also, most of the improvement experts neglect that human factors, skills,
and social and teamwork competencies have a big influence on success. This
is a contradiction to the believe of many process guys who feel to create
processes making the company independent of people.
We promote the experience from 30 experts from 11 different European
countries and proposed a combined use of methodologies. These experts
worked together for 3 years (1995 to 1998) in a European Leonardo da Vinci
Project PICO (Process Improvement Combined apprOach). We especially
focussed on the combination of business aspects with pragmatic improvement
approaches as an essential requirement in order to make the right
improvement decisions.
Furthermore, in the last 3 years we analysed and identified factors which
further impact your improvement efforts even if the goals, the business
context, the methodology and the plan for improvement are right. Human
factors largely influence the behaviour of people, the effectiveness of
teamwork, how the communication in the team works, and what can be
achieved even if the processes are right.
The tutorial will base on the previous PICO tutorial (5 key success
factors to achieve a business return) and add 5 human factors (based on
the results of a project Bestregit which followed PICO and focussed more
on the experience with people issies).
|
I.S.C.N.
International Software Consulting Network