Presentation Outlines 2 Context of Global Software Engineering - - PowerPoint PPT Presentation

presentation outlines
SMART_READER_LITE
LIVE PREVIEW

Presentation Outlines 2 Context of Global Software Engineering - - PowerPoint PPT Presentation

S OFTWARE A RCHITECTURE AND C ONSTRUCTION TITLE: A PROCESS FRAMEWORK FOR GLOBAL SOFTWARE


slide-1
SLIDE 1

SOFTWARE ARCHITECTURE AND CONSTRUCTION

………………………………………………………………………………………………………………………………… TITLE: A PROCESS FRAMEWORK FOR GLOBAL SOFTWARE ENGINEERING TEAMS AUTHORS: ITA RICHARDSON, VALENTINE CASEY, FERGAL MCCAFFERY, JOHN BURTON, SARAH BEECHAM (INFORM.SOFTW.TECHNOL.(2012), HTTP:// DX.DOI.ORG/10. 1016/J.INF SOF.2012.05. 002) …………………………………………………………………………………………………………………………………. BELACHEW REGANE ADDIS ABABA UNIVERSITY IT DOCTORIAL PROGRAM SOFTWARE ENGINEERING TRACK

APRIL, 2019

slide-2
SLIDE 2

Presentation Outlines

Context of Global Software Engineering

Process support in GSE

Research Questions

Research Approach

GSE Factors

Rationale for developing GT process

Development of Global Teaming Process Area

Global Teaming Model Structure

Results of the Study

Discussion and Open Issues

Contribution

Conclusion

Remarking Points

Lesson Learnt

2

slide-3
SLIDE 3

Context of Global Software Engineering (GSE)

 Increasing numbers of software engineers in world

wide, are expected to operate in a distributed environment

 Challenges within this environment

 physical separation  temporal distance  cultural distance  language, or linguistic distance

3

slide-4
SLIDE 4

Context of GSE (2)

 These distances experienced in Global Software

Engineering (GSE) environments

 Given the substantial growth and associated

complexities of GSE

 process models are developed to support GSE

 De facto models like CMMI is not sufficient for GSE  Therefore, a specific process area, Global Teaming

(GT) have proposed

 aims to support GSE implementation

4

slide-5
SLIDE 5

Context of GSE (3)

Reason for growth of GSE

 Advancement in technical communication

 Internet and Telecommunication

 Skilled manpower with reduced cost in different

countries

 Different skills and knowledge at different area

5

slide-6
SLIDE 6

Process support in GSE

Software Process

 Organizations improve their software processes to

improve the quality of their product Definitions

 Set of tools, methods and practices used to produce

a software product

 Set of activities, methods, practices and

transformations that people use to develop and maintain software and the associated products

6

slide-7
SLIDE 7

Process support in GSE (2)

Debating issues in process

 Argue against:

 implementing planned processes decrease the

efficiency of the software development process

 Argue for:

 implementing planned processes can increase

productivity and efficiency

7

slide-8
SLIDE 8

Research Questions

Two linked research questions: RQ1: What are the threats faced by global software project teams if they do not implement GSE processes correctly? RQ2: Can Global Teaming research be integrated in the Capability Maturity Model Integration (CMMI) model?

8

slide-9
SLIDE 9

Research Approach

Empirical studies

 Action research and a grounded theory approach

 for data gathering and data analysis

Literature review

 From 1999 to 2007 in three different phases

9

slide-10
SLIDE 10

GSE Factors

 Findings from empirical case study research and

literature reviews led to the identification of several GSE factors such as

 technical support  team selection  clear definition of roles and responsibilities  skills management  process management  risk management  reporting and information management  etc

10

slide-11
SLIDE 11

Rationale for developing GT process

 Potential threats were identified

 through analysis of the literature  empirical work

 GSE can lead to increased risks especially when

  • rganizational boundaries are crossed

 Socio-cultural factors can affect global teams and

increase risks

 De facto process models are not sufficient to GSE  etc

11

slide-12
SLIDE 12

Development of Global Teaming Process Area

Gap Analysis: CMMI GSE factors

 To understand how GSE is supported within the

CMMI for Development process model

 matching the GSE factors identified to the statements in

the CMMI model documentation

 Systematic gap analysis

 explicit process areas  implicit processes defined  GSE factors, not mentioned in the CMMI

12

slide-13
SLIDE 13

Global Teaming Model Structure

 Having completed the literature review, case

studies, threat analysis and gap analysis

 GT model developed

 to reflect the current CMMI structure to include

 Specific Goals, Specific Practices and Sub-practices

 Adapt and customize the structure as the CMMI is

internationally recognized and used extensively by

 industry in their Software Process Improvement activities

13

slide-14
SLIDE 14

Result of the study

Answer for RQ#1:

 Analysis of the literature and empirical studies, found

that ignorance of associated risks can lead to

 a loss of competitive advantage  practitioner de-motivation  poor quality software

 Failing to implement GSE processes correctly means

 organizations are putting themselves at risk of project

failure

 Organizations lack support in how to implement a

GSE strategy

14

slide-15
SLIDE 15

Result of the study (2)

Answer for RQ#2:

 the CMMI structure used as a basis for the

development of the GT process area

 by augmenting with new factors found to be

important in setting up global software development teams

 Thus, GT process area can be used

 as a CMMI supplement  used in conjunction with other processes

15

slide-16
SLIDE 16

DISCUSSION AND OPEN ISSUES

 CMMI is not sufficient as a process model for GSE

 therefore, it is necessary developing a process model

which supplements the CMMI to fit the global environment

 Base on gap analysis

 GT Model developed

 has two Specific Goals (SGs)

16

slide-17
SLIDE 17

DISCUSSION AND OPEN ISSUES (2)

 GT process area has two Specific Goals (SGs)

 Define Global Project Management

 represents practices required at project initiation

 Define Management Between Locations

 classifies practices required when the project is operational  ensures that as operating procedures are set up correctly  focuses on collaboration between locations  Each SG has Specific Practices (SPs) and sub-

practices

17

slide-18
SLIDE 18

DISCUSSION AND OPEN ISSUES (3)

GT Model Validation

 In order to answer second research question

 GT model practices presented, to groups of experts in

two organization and given copy of the model

 to gain some informal feedback on the mode  The experts found the guidelines immediately

accessible and easy to follow

18

slide-19
SLIDE 19

DISCUSSION AND OPEN ISSUES (4)

Open Issues

 In order to gain more formal feedback as to how

the model could be improved

 in depth validation of the GT processes based on a

Decision Support System (DSS) - on the study

 Validating Global Teaming model in industry

 need longitudinal study  open issue and on the study by researchers

19

slide-20
SLIDE 20

Contribution

 Global Teaming process area

 important for establishing and managing effective

software teams in the globally distributed setting

 provide specific goals, specific practices, sub-practices

and guidelines

 can be used by industry to implement a GSE strategy

 Explanation to potential threats to GSE if

these practices are not considered

20

slide-21
SLIDE 21

21

slide-22
SLIDE 22

Conclusion

 Many organizations have discovered to their cost

that implementing a GSE strategy is

 a complex and difficult task

 Studies show that a number of factors including

 the nature and impact of geographical  temporal distance  cultural distance  linguistic distance

22

slide-23
SLIDE 23

Conclusion (2)

 On the other hand, in geographically distributed

environment, team-based software development, the issue is not simply a technical activity

 has human, social and cultural implications  need to be specifically addressed

 Thus, Global Teaming process area developed to

  • vercome the issues

 focuses on the importance of establishing and

managing effective software teams in the globally distributed setting

23

slide-24
SLIDE 24

Remarking Points

Strength the study

 Ways of problem domain and solution domain

defined

 Way of factors identified and gap analyzed  Way of threats identified and analyzed looking

ahead to minimize risk

 Ways of literature review, case studies and gap

analysis done

 Way of designing and implementing validation

strategies

24

slide-25
SLIDE 25

Remarking Points (2)

Points to be considered

 There is no clear boundary set for Framework,

Model and Guidelines

 lack of consistency in used  create ambiguity

eg. GT process/area/mode/framework/Guidelines

 The reason why the approaches believe to yield

better result than others is not justified

25

slide-26
SLIDE 26

Lesson Learnt from the Study

 Ways literature review, case studies, threat analysis

and gap analysis should done

 Use of grounded theory approach for data

collection and analysis

 How to identify Global Software Engineering

Factors

 How to do Gap Analysis compering with CMMI  How to develop Global Teaming Process Area

26

slide-27
SLIDE 27

THANK YOU

27