Empirical software engineering conference 2011

Download Free PDF. Naveed Ikram. A short summary of this paper. As the SA as a discipline is Section III explains the outline of research methodology and maturing, large number of empirically supported studies are Section IV concludes the paper along with future work. There is a need to systematically aggregate, analyze and synthesize evidence based studies in SA. This paper aims at providing a brief identify all empirical research related to software description of systematic literature review SLR protocol to architecture, aggregate the empirical studies and summaries describe a process for synthesizing the empirically supported the evidence for future use.

Protocol for this review has already aggregate empirically supported literature i. Expected upon some evidence case study, experiment, experience outcome of this review will be state-of-the-art of empirical report and lesson learned etc such studies are also called work in the field of software architecture, strength and evidence-based studies. Similar work exists in several studies where researchers summarized the available literature and pointed Keywords-systematic literature review; software architecture out future directions but the focus of those studies was not state-of-the-art.

The studies, those reported state-of-the- art in software architecture, did not performed qualitative I. Software Architecture acts as a skeleton for the software The concept of software architecture as a separate development.

SA needs to be created early during the discipline started to emerge in [5] [6] and developed software development and then the whole development later on [7]. Since then, the key research areas of software process revolves around this skeleton, keeping into account architecture and its future directions have been identified the constraints and facilities implied by the software time to time by conducting informal literature reviews and architecture.

Few decades back there was nothing like surveys [5] [8] [9]. The research paradigms used in software architecture. The concept of software architecture was first architecture research have been focused by identifying the introduced in when layering was used in program types of research questions which were structured to use and development [1], then this concept was enhanced and the research design devised to answer those questions; state- structure of software was emphasized [2] [3].

Increasing of-the-art in software architecture with a perspective of complexity and software quality needs urged the growth in technology maturation model has also been practitioners to opt modularity and ultimately it turned into described [10] [11].

The chronological history of the the form which is now called software architecture. Software software architecture field, its innovative methods, tools, architecture is responsible for incorporating quality in techniques, software architecture community, papers, books software by accommodating quality attributes and functional and conferences has already been aggregated [5].

Moreover, software architecture must have to The above mentioned studies aggregated the existing accommodate the continuous changing needs so it should be literature of software architecture and each of these studies flexible enough to evolve. Academia and industry both are has different concerns and varying scope.

These studies were well aware of the importance of software architecture that is carried out as normal literature surveys without following a why there exists lots of empirical literature on various sub systematic process. None of these studies attempted to areas of software architecture.

But there is a need to aggregate the evidence-based software architecture literature. This is the reason to undertake this and summarizing empirical evidence will help researchers in systematic literature review.

This document provides an future and practitioners will also get quantified measures to outline of the protocol for this systematic literature review make informed decisions [12]. There is much work that and it is developed based on the guidelines of Kitchenham points towards the need to systematically gather empirical [4]. Mapping study [15] and many systematic be assessing the future research scope by evaluating and literature reviews exist in the field of software architecture aggregating the available literature.

They differ from our review in a way that their scope is limited to one sub-area of software architecture A. Search Strategy as opposed to our review. We focus on whole SA discipline. Identify Major Search Terms Moreover our review is focused on only empirically Search criteria used to construct major search terms is as supported evidence based SA studies.

Systematic review protocol is the concatenate search terms if these operators are allowed to outcome of this phase. Systematic review protocol is the be used in the search database strings.

Search Constraints RQ1: what is the state-of-the-art in empirical studies of Search is limited to published studies related to software architecture? Search will be applied on The main motive behind this research question is to find conferences papers, journal articles, and workshop out the current state of the software architecture field in papers.

This review will consider the work in terms of existing empirical studies and to extract some future English and since After Parnas work on guidelines from the existing empirical literature. The data software structure and decomposition [2] [3]. Publication Selection depict the mature and underdeveloped areas of software Inclusion Criteria architecture along with other relevant information in terms of Research articles based on empirical evidence related to quantity of the studies.

Only one instance will be included if multiple studies Objective behind this question is to find out the report same empirical results. Strength of empirical Editorials, prefaces, discussions, comments, summaries evidence is important for future research.

The studies of tutorials, workshop brief, panels and duplicate studies obtained for both of these questions will be same but the will be excluded. Studies with insufficient focus on main difference is in the perspective, for this question data software architecture or with absence of empirical data will be evaluated for quality of work to know what is the will be excluded source of data and what study design have been used to obtain this evidence etc.

Selecting Primary Studies The overall Evidence based investigation is focused on Search Strings will be applied on the databases and the type of question given by guidelines of Kitchenham [4]. Duplicates will be removed. The papers that are not clearly relevant or adequately measured i.

Case Study Is case study context defined? The understanding of the case? These sections are survey, case study, experiment consent, review board approval? This checklist generation was a mutual group Is the focus of study reported?

The detailed checklist is in Table I. Scores will also be assigned according the Are the aims clearly stated? Each paper selected for data extraction will be author? Then the Are negative findings presented?

The data will be extracted with the help of a classification scheme. The extracted data for research questions implications?

Survey is as: For RQ1 data extraction form will extract following Was the denominator i. Software Architecture area Software Architecture Did the author justified sample size? At present data extraction and quality experience report etc ranking procedure is under progress. Publication Channel studies studies E. The classification scheme used in data extraction will help here to 3 ScienceDirect 4.

After depicting data in quantitative 5 EI Compendex List of best practices [2] D. Analysis of evidence type versus participant type [3] D.

We are fortunate to be able to benefit from such an inspirational location in the heart of the Rocky Mountains. The individual events are:. Our overall objective has been to provide a forum where researchers and practitioners can report and discuss recent research results in the areas of empirical software engineering and software measurement.

We also seek to explore strengths and weaknesses of research methods from an empirical viewpoint and to provide learning and training opportunities so that attendees may benefit from the experiences of others. In addition, through rigorous review we can showcase the very best of our research for the rest of the world.

The main conferences have the following acceptance rates:. We are very conscious this is a community-wide event and that it would not have been possible without the help of so many people.