18
Improving LSPCM Applying LSPCM to High Level Design for outsourcing projects. By Nishanth S. Shetty Swaraj S.Bhat

Improving LSPCM Applying LSPCM to High Level Design for outsourcing projects. By Nishanth S. Shetty Swaraj S.Bhat

  • View
    214

  • Download
    0

Embed Size (px)

Citation preview

Improving LSPCM Applying LSPCM to High Level Design for

outsourcing projects.

By

Nishanth S. Shetty

Swaraj S.Bhat

Contents

• Introduction• Certification• Offshore projects• LSPCM• Research Objectives• Specific criteria for HLD• Deliverables & Timeline

Research objectives11/18/2009 PAGE 2/ SET Seminar

Introduction

• Software project failure:

• Customer requirements not met.• Delivery deadline not met.• Actual cost higher than estimated cost.• Too many errors.

• Statistical facts: The Standish group reported in 2003 • 34% computer projects succeeded • 27% experienced cost overrun of over 20%, • 15% failed altogether.

11/18/2009 PAGE 3/ SET Seminar

Introduction

• Software Certification can be used to prevent these failures and to improve the quality of the software product.

• “Certification is a process of confirming

that a system or a component complies

with its specified requirements and

is acceptable for operational use.”− IEEE Computer Society. IEEE Std 829-1998. IEEE Standard for Software Test

Documentation 1998

11/18/2009 PAGE 4/ SET Seminar

Certification

• Benefits of certification:

• Helps to obtain certainty and confidence in software artifacts.

• Offers an advantage over the competition.

• Gives more confidence to the prospective buyers.

• In outsourcing projects, an independent party can determine that deliverables are acceptable.

11/18/2009 PAGE 5/ SET Seminar

Certification for an Offshore project

• Outsourcing process is threatened by the missing context information at handover moments:

• Requirements• High level design• Source code• End system

• Certification at handover moments helps to achieve that documents are

− consistent − made in the right way.

11/18/2009 PAGE 6/ SET Seminar

LSPCM

• LaQuSo Software Product Certification Model.

• A rule based software product certification model.

• Model consists of 6 product areas:• Context description• User requirements• High Level design (HLD)• Detailed design• Implementation• The tests

11/18/2009 PAGE 7/ SET Seminar

LSPCM

• In order to analyze the artifacts LSPCM defines three Certification Criteria (CC) for all Product Areas:

• [CC1] Completeness – All required elements in the Product Area should be present.

• [CC2] Uniformity – The style of the elements in the Product Area should be standardized.

• [CC3] Conformance – All elements should conform to the property that is subject of the certification.

11/18/2009 PAGE 8/ SET Seminar

Certification criteria achievement levels

CC1 Completeness

0 Some required elements are missing

1 All required elements are present

2 Semi-formal elements have been added

3 Formal elements have been added

CC2 Uniformity

0 No standardization

1 Within the product

2 Style complies to a company standard

3 Style complies to an industry standard

CC3 Conformance

0 Faults are detected

1 Manual review/testing has not detected any faults

2 Automated approach has not detected any faults

3 Formal verification has not detected any faults11/18/2009 PAGE 9/ SET Seminar

LSPCM – Certification Levels

• Initial

• Manually verified

• Automated verified • Model verified • Formally verified

11/18/2009 PAGE 10/ SET Seminar

Objectives

• Improve LSPCM - Applying LSPCM 1.1 to the HLD of an offshore project.

• Scaling of certification and specific criteria for high level design.

• Incremental

11/18/2009 PAGE 11/ SET Seminar

Process flow

11/18/2009 PAGE 12/ SET Seminar

Specific criteria for High level design.

• [SC1] Complete:1. Required elements.

2. Semi-formal elements.

3. Formal elements.

• [SC2] Uniform:1. Uniformity within product area.

2. Compliance with company standard.

3. Compliance with industry standard.

11/18/2009 PAGE 13/ SET Seminar

Specific criteria for High level design.

• [SC3] Conformance:1. Manual check.

2. Automated check.

3. Formal check.

11/18/2009 PAGE 14/ SET Seminar

Issues

• Some issues common to all models in G with respect to HLD:

• Missing High-level documents such as− component model. − flowcharts.

According to an experimental comparison by D.A.Scanlon, it is considered very helpful to introduce flowcharts to describe process flow, as it increases comprehension of the program.

• Missing translation document.

• Ambiguous use cases.

11/18/2009 PAGE 15/ SET Seminar

Deliverables

• Analysis report on model 2

• Analysis report on model 3

• Reports on interviews with project experts.

• List of suggestions what LSPCM criteria are of less importance and why.

• List of suggestions how LSPCM can be improved for outsourcing projects.

11/18/2009 PAGE 16/ SET Seminar

Timeline

11/18/2009 PAGE 17/ SET Seminar

Questions

11/18/2009 PAGE 18/ SET Seminar