Improving CASA and LSPCM
on high level design for
offshoring
Students: Nivedita Angadi
Tanya Kudchadker
Guides:
Prof. Mark van denBrand, Tu/e
Martijn Klabbers, LaQuso, Tu/e
Cornelly Spier , Capgemini
Rob Boomsma, Capgemini
Rob Ista, Capgemini
To begin with…
• What is offshoring?
• Why offshoring followed in the Industry?
- Cost Reduction
- Efficient use of skilled labors
- Focus is on core competence and innovation
Challenges in offshoring
• What are the risks in offshoring?
- Geographical risks
- Project risks
- Infrastructure and Operational risks
• Quality and Productivity consideration.
Productivity
Time
• Productivity
Cost
The production or delivery of more products or
services with less effort and less cost in a shorter
time period with the better quality[1].
• Productivity =
Output produced by the process
Input consumed by the process
Productivity Conceptual Model
Inputs
•People – Experience,
Knowledge,Skill
•Management
•Processes
•Systems ,Tools and Materials
Conversion Process
Outputs
•Improved Services
•Reduced Costs
•Increased Volume
Improving Quality of High Level Design
• Existing Approaches in Capgemini for Analysis,
Design and Architecture
- CASA – Capgemini Accelerator for Software
Architecture
• LSPCM analysis as a quality gate for High Level
Design
- LSPCM – LaQuso Software Product Certification Model
CASA - Capgemini Accelerator for Software
Architecture
• What is CASA?
- Capgemini Accelerator for Software Architecture
• Aim of CASA
- “Building the Product right”.
Predictability
Productivity
CASA
Product
Qualiity
Collaboration
Positioning of CASA
Positioning of CASA [2]
What CASA contains ?
Guidelines
Checklists
Templates
Examples
LaQuso Software Certification Model (LSPCM)
• What is LSPCM?
- Rule based software product certification model.
• What LSPCM contains?
- Product areas
- Properties of product areas
- Certification Criteria (CC) for all product areas
[CC1]Completeness
[CC2]Uniformity
[CC3]Conformance
- Specific Criterias (Rules)
- Certification levels
Quality improvement for High Level Design
• High Level Design
• Why quality improvements for High Level Design?
Research Goals
• Suggest improvements for High Level Design in the
context of offshoring
- LSPCM Certification Model
- CASA
- Case Studies
Side goals
• Improve productivity
- Analyzing influence of high level design quality.
- Analyzing the split in activities between onshore
and offshore teams.
Research Question
• What aspects of the software artifact High Level
Design determine the quality of offshored software
development?
• Side Questions:
- How can quality of high level design influence
project’s productivity?
- How can split in activities between onshore and
offshore team influence on the project’s
productivity?
Plan for tasks
1.
2.
3.
4.
5.
Literature study on productivity
Literature study on Software Architecture and high level design
Analysis of necessary artifacts of CASA for high level design
Analysis of defects faced with offshored projects.
Analysis of Case studies and Suggestions for improvement in high
level design.
6. Thesis and Presentation.
Deliverables
Name of the Task
Deliverable
1. Literature study on Productivity
Overview report on Productivity.
2.Literature Study on high level
design and architecture.
Overview Report on High Level
Design and architecture.
3. Analyze the necessary
artifacts of CASA for High Level
Design.
Report on CASA for High Level
Design
4. Interview with CASA expert.
a. Analysis report of quality
demand for high level design in
outsourcing.
b. Analysis report for productivity
improvement.
5. Analysis of HLD for case
studies for LSPCM and CASA(2).
a. Case Study 1
b. Case Study 2
a.
b.
c.
6. Final report and presentation
preparation.
a.
b.
Analysis report of Case
Study1.
Analysis report of Case
Study2.
Revised report based on
refinements.
Final Thesis Report
Presentation
References
[1] Rob Ista., “Productivity: Point of view”
[2] http://wiki.capgemini.com/index.php/Portal:CASA
[3]LaQuso Software Certification Model (LSPCM 1.1)
[4]Ian Gorton., “Essential Software Architecture”,
Springer Publications (2006).
[5] Kruchten .P,. Architectural Blueprints – The “4+1”
View Model of Software Architecture,IEEE
Publication (1995)