Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Artifacts of Software Reference Architectures

Artifacts of Software Reference Architectures: A Case Study. Technical Research Paper at 18th International Conference on Evaluation and Assessment in Software Engineering (EASE) 2014.

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Artifacts of Software Reference Architectures

RQ 1: Which artifacts constitute an SRA designed by everis for a client organization?



RQ2: What is reused by everis in order to create SRAs?



RQ3: Could SRA's artifacts of a specific client organization be reused in other organizations with a different business domain?



RQ4: What is the perception of application builders about the role that an SRA plays in the development of applications?
Discussion
The common the scenario is that SRA are Created from Existing Assets
Creation of Reference Model and even platform-oriented Reference Architecture in everis

Surprising: no architectural knowledge from clients
Results
Discussion
It depends on the Goal of the SRA:
Standardize: Regulative role
Facilitating: Instructive/regulative role
Results
An SRA can play three roles:
Regulative role (restrictive)
Instructive role (moderately restrictive)
Informative role (no restrictive)
Results
RQ2: What is
reused
by everis in order
to create SRAs
?
RQ4. What is the perception of application builders about the
role that an SRA plays in the development of applications
?
RQ3: Could SRA's
artifacts
of a specific client organization be
reused in other organizations
with a different business domain?
RESULTS & DISCUSSIONS
RQ1
RQ2
RQ3
RQ4
RQ1: Which
artifacts
constitute an SRA designed by everis for a client organization?
INTRODUCTION
Artifacts of Software Reference Architectures: A Case Study
RESEARCH
METHODOLOGY

Architects vs. city planners
CONSULTING
FIRM

CLIENT ORGANIZATION
Application
Application
Application
Application

Application
Case study at
Software
Reference
Architecture
(SRA)
Research Questions
THANK YOU!!
@silveriomf
Silverio Martínez-Fernández
<smartinez@essi.upc.edu>

paper available at:
http://www.essi.upc.edu/~smartinez/
Motivation
Data Analysis
To conclude...
?
Common elements
Template of structure
How to manage a family of software systems?
How to reduce costs?
Background of Software Architecture
The software architecture of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both
"Every software system has a
software architecture" [Bass 2003]
Application
Application
Application
Application
Application

Software Reference
Architecture (SRA)
Practitioners find SRA literature scarce and abstract, limiting industrial uptake
What constitutes an SRA still varies significantly

Limited evidence about current industrial SRA practices
Threats to Validity
Construct Validity
From a software architecture to many:
Software Reference Architecture (SRA)
Which are the artifacts that compose an SRA and how such artifacts are designed, (re)used?
OUTLINE
1. Introduction

2. Research Methodology:
A Case Study

3. Results and Discussions

4. Q&A

18th International Conference on Evaluation
and Assessment in Software Engineering (EASE)
13-14 May 2014, London, UK
#EASE14
Silverio Martínez-Fernández , Claudia Ayala , Xavier Franch , Helena Marques
@SilverioMF
@gessi_upc
@gessi_upc
9 SRAs
Software Architect
Application
Builder
Architecture Developer
everis'
reference model
Sampling and Data Collection
Case Study
Explorative
Qualitative

Target: everis'
SRA projects
Selection of 9 SRA projects based on feasibility to contact a least with one of each role.


28 stakeholders


Other sources: SRA project card,
Documentation
,
Metrics
about invested effort, Informal
meetings
Software Architect

Face-to-face interviews to
Architecture Developer
Application
Builder
Gathering data:




Analysis:
Categorization (name of category, detailed description, participant, representative quotes)

Discussions to avoid researcher bias
Discussion


Hardware
It is concern of other stakeholders in the consulting firms context

Mission, vision and strategy of the client organization
SRAs mostly perceived at a technological level

An SRA could also include other artifacts
SRA does not have to include all the artifacts uncovered by this study
Platform-oriented are Potentially Reused in Many Business Domains
Conformance Analysis in Seldom in Practice
Add costs
Software Architect

Face-to-face interviews to
Software Architect
Face-to-face interviews to
Online questionnaires to
Application
Builder
Online questionnaires to
Architecture Developer
Application
Builder
Software Architect
9
9
10
Interview
transcripts
Online questionnaires:
LimeSurvey

External Validity
Results valid for the everis context
Possible generalization in similar contexts, i.e., IT consulting firms
Enable replication (facilitate instruments...)
Vital need disseminating empirical evidence
in order to
help practitioners in the design and use of SRAs
Results
AK: Architectural Knowledge
Sw: Software
Confounding factor: invested effort
Discussion
Results most important
cross-cutting elements
Internal Validity
9 SRA projects to study the context of each one
Diversity in the selection of SRA projects to study
1
1
1
2
1
2
Full transcript