2014 ieee dotnet software engineering project governing software process improvements in globally...

6
Governing Software Process Improvements in Globally Distributed Product Development Abstract Continuous software process improvement (SPI) practices have been extensively prescribed to improve performance of software projects. However, SPI implementation mechanisms have received little scholarly attention, especially in the context of distributed software product development. We took an action research approach to study the SPI journey of a large multinational enterprise that adopted a distributed product development strategy. We describe the interventions and action research cycles enacted over a period of five years in GLOBALSOFT TECHNOLOGIES IEEE PROJECTS & SOFTWARE DEVELOPMENTS IEEE FINAL YEAR PROJECTS|IEEE ENGINEERING PROJECTS|IEEE STUDENTS PROJECTS| IEEE BULK PROJECTS|BE/BTECH/ME/MTECH/MS/MCA PROJECTS|CSE/IT/ECE/EEE PROJECTS CELL: +91 98495 39085, +91 99662 35788, +91 98495 57908, +91 97014 40401 Visit: www.finalyearprojects.org Mail to:ieeefinalsem[email protected]

Upload: ieeebebtechstudentsprojects

Post on 24-Jun-2015

58 views

Category:

Engineering


3 download

DESCRIPTION

To Get any Project for CSE, IT ECE, EEE Contact Me @ 09666155510, 09849539085 or mail us - [email protected] Our Website: www.finalyearprojects.org

TRANSCRIPT

Page 1: 2014 IEEE DOTNET SOFTWARE ENGINEERING PROJECT Governing software process improvements in globally distributed product development

Governing Software Process Improvements in Globally

Distributed Product Development

Abstract

Continuous software process improvement (SPI) practices have been extensively

prescribed to improve performance of software projects. However, SPI implementation

mechanisms have received little scholarly attention, especially in the context of distributed

software product development. We took an action research approach to study the SPI

journey of a large multinational enterprise that adopted a distributed product development

strategy. We describe the interventions and action research cycles enacted over a period of

five years in collaboration with the firm, which resulted in a custom SPI framework that

catered to both the social and technical needs of the firm's distributed teams.

Institutionalizing the process maturity framework got stalled initially because the SPI

initiatives were perceived by product line managers as a mechanism for exercising wider

controls by the firm's top management. The implementation mechanism was subsequently

altered to co-opt product line managers, which contributed to a wider adoption of the SPI

framework. Insights that emerge from our analysis of the firm's SPI journey pertain to the

GLOBALSOFT TECHNOLOGIESIEEE PROJECTS & SOFTWARE DEVELOPMENTS

IEEE FINAL YEAR PROJECTS|IEEE ENGINEERING PROJECTS|IEEE STUDENTS PROJECTS|IEEE

BULK PROJECTS|BE/BTECH/ME/MTECH/MS/MCA PROJECTS|CSE/IT/ECE/EEE PROJECTS

CELL: +91 98495 39085, +91 99662 35788, +91 98495 57908, +91 97014 40401

Visit: www.finalyearprojects.org Mail to:[email protected]

Page 2: 2014 IEEE DOTNET SOFTWARE ENGINEERING PROJECT Governing software process improvements in globally distributed product development

integration of the technical and social views of software development, preserving process

diversity through the use of a multi-tiered, non-blueprint approach to SPI, the linkage

between key process areas and project control modes, and the role of SPI in aiding

organizational learning.

Existing system:

Continuous software process improvement (SPI) practices have been extensively

prescribed to improve performance of software projects. However, SPI implementation

mechanisms have received little scholarly attention, especially in the context of distributed

software product development. We took an action research approach to study the SPI

journey of a large multinational enterprise that adopted a distributed product development

strategy.

Proposed system:

We describe the interventions and action research cycles enacted over a period of

five years in collaboration with the firm, which resulted in a custom SPI framework that

catered to both the social and technical needs of the firm's distributed teams.

Institutionalizing the process maturity framework got stalled initially because the SPI

initiatives were perceived by product line managers as a mechanism for exercising wider

controls by the firm's top management. The implementation mechanism was subsequently

altered to co-opt product line managers, which contributed to a wider adoption of the SPI

framework. Insights that emerge from our analysis of the firm's SPI journey pertain to the

integration of the technical and social views of software development, preserving process

diversity through the use of a multi-tiered, non-blueprint approach to SPI, the linkage

between key process areas and project control modes, and the role of SPI in aiding

organizational learning.

Page 3: 2014 IEEE DOTNET SOFTWARE ENGINEERING PROJECT Governing software process improvements in globally distributed product development

SYSTEM CONFIGURATION:-

HARDWARE CONFIGURATION:-

Processor - Pentium –IV Speed - 1.1 Ghz

RAM - 256 MB(min)

Hard Disk - 20 GB

Key Board - Standard Windows Keyboard

Mouse - Two or Three Button Mouse

Monitor - SVGA

Page 4: 2014 IEEE DOTNET SOFTWARE ENGINEERING PROJECT Governing software process improvements in globally distributed product development

SOFTWARE CONFIGURATION:-

Operating System : Windows XP

Programming Language : JAVA

Java Version : JDK 1.6 & above.

Page 5: 2014 IEEE DOTNET SOFTWARE ENGINEERING PROJECT Governing software process improvements in globally distributed product development