Given the central role that software development plays in the delivery and application of information technology, managers are increasingly focusing on process improvement in the software development area. This demand has spurred the provision of a number of new and/or improved approaches to software development, with perhaps the most prominent being object-orientation (OO). In addition, the focus on process improvement has increased the demand for software measures, or metrics with which to manage the process. The need for such metrics is particularly acute when an organization is adopting a new technology for which established practices have yet to be developed. This research addresses these needs through the development and implementation of a new suite of metrics for OO design. Metrics developed in previous research, while contributing to the field's understanding of software development processes, have generally been subject to serious criticisms, including the lack of a theoretical base. Following Wand and Weber (1989), the theoretical base chosen for the metrics was the ontology of Bunge (1977). Six design metrics are developed, and then analytically evaluated against Weyuker's (1988) proposed set of measurement principles. An automated data collection tool was then developed and implemented to collect an empirical sample of these metrics at two field sites in order to demonstrate their feasibility and suggest ways in which managers may use these metrics for process improvement. >

/pdf/a-metrics-suite-for-object-oriented-design-539bycjzzb.pdf

A metrics suite for object oriented design

http://emamispnu.persiangig.com/Projects/Cloud%20Computing/science_2.pdf

Review: A survey on security issues in service delivery models of cloud computing

BACKGROUND: A software engineering systematic map is a defined method to build a classification scheme and structure a software engineering field of interest. The analysis of results focuses on frequencies of publications for categories within the scheme. Thereby, the coverage of the research field can be determined. Different facets of the scheme can also be combined to answer more specific research questions.

OBJECTIVE: We describe how to conduct a systematic mapping study in software engineering and provide guidelines. We also compare systematic maps and systematic reviews to clarify how to chose between them. This comparison leads to a set of guidelines for systematic maps.

METHOD: We have defined a systematic mapping process and applied it to complete a systematic mapping study. Furthermore, we compare systematic maps with systematic reviews by systematically analyzing existing systematic reviews.

RESULTS: We describe a process for software engineering systematic mapping studies and compare it to systematic reviews. Based on this, guidelines for conducting systematic maps are defined.

CONCLUSIONS: Systematic maps and reviews are different in terms of goals, breadth, validity issues and implications. Thus, they should be used complementarily and require different methods (e.g., for analysis).

/pdf/systematic-mapping-studies-in-software-engineering-4h4l7vgsw3.pdf

Systematic mapping studies in software engineering

Goals capture, at different levels of abstraction, the various objectives the system under consideration should achieve. Goal-oriented requirements engineering is concerned with the use of goals for eliciting, elaborating, structuring, specifying, analyzing, negotiating, documenting, and modifying requirements. This area has received increasing attention. The paper reviews various research efforts undertaken along this line of research. The arguments in favor of goal orientation are first briefly discussed. The paper then compares the main approaches to goal modeling, goal specification and goal-based reasoning in the many activities of the requirements engineering process. To make the discussion more concrete, a real case study is used to suggest what a goal-oriented requirements engineering method may look like. Experience, with such approaches and tool support are briefly discussed as well.

/pdf/goal-oriented-requirements-engineering-a-guided-tour-2uwx0ha66r.pdf

Goal-oriented requirements engineering: a guided tour

One of the fundamental principles of the database approach is that a database allows a nonredundant, unified representation of all data managed in an organization. This is achieved only when methodologies are available to support integration across organizational and application boundaries.Methodologies for database design usually perform the design activity by separately producing several schemas, representing parts of the application, which are subsequently merged. Database schema integration is the activity of integrating the schemas of existing or proposed databases into a global, unified schema.The aim of the paper is to provide first a unifying framework for the problem of schema integration, then a comparative review of the work done thus far in this area. Such a framework, with the associated analysis of the existing approaches, provides a basis for identifying strengths and weaknesses of individual methodologies, as well as general guidelines for future improvements and extensions.

/pdf/a-comparative-analysis-of-methodologies-for-database-schema-3t0rjhby4y.pdf

A comparative analysis of methodologies for database schema integration

This book constitutes the refereed proceedings of the 23rd International Conference on Advanced Information Systems Engineering, CAiSE 2011, held in London, UK, in June 2011. The 42 revised full papers and 5 revised short papers presented were carefully reviewed and selected from 320 submissions. In addition the book contains the abstracts of 2 keynote speeches. The contributions are organized in topical sections on requirements; adaptation and evolution; model transformation; conceptual design; domain specific languages; case studies and experiences; mining and matching; business process modelling; validation and quality; and, service and management.

Advanced information systems engineering : 23rd International Conference, CAiSE 2011, London, UK, June 20-24, 2011 : proceedings

Interfaces bases de données avancées: quelles recherches pour quelles interfaces?

Evaluation of CRIS 1 IS Devlopments Methods Using a Three Cycles Framework.

We are concerned by distributed data base (DDB) consistency. We claim that a better DDB consistency requires to integrate in Distributed Base Management Systems a system of automata to manage its dynamics processing according to the description of data dynamics. We present a specification language in order to allow the dynamics DDB description according to the data dynamics modeling presented at the 4th VLDB Conference. We develop the system of automata able to perform in a distributed way the DDB dynamics processing and discuss the solution from concurrency and consistency points of view.

Distributed processing of data dynamics

The pape~ aims to p~esent a CASE system which is an integ~ated compute~ aided tool so-called RUBIS, fo~ designing and p~ototyping Info~mation Systems. RUBIS is o~ganized a~ound the R-schema (RUBIS-schema), which is a decla~ative specification of the Info~mation System (IS) content, based on a conceptual model which emphasizes equally the IS st~uctu~e and behaviou~. Afte~ a b~ief ove~view of the RUBIS a~chitectu~e, we p~esent th~ough examples how to const~uct the R-schema using PROQUEL: the fo~mal specification language of RUBIS. Then, we concent~ate on two diffe~ent aspects of RUBIS: the expe~t design tool, which helps the designe~ to p~oduce the R-schema fo~ a given application domain, and the p~ototyping tool, which allows the execution of specifications on test case data.

/pdf/information-system-engineering-the-rubis-system-16kydbkvch.pdf

Colette Rolland

Papers

Advanced information systems engineering : 23rd International Conference, CAiSE 2011, London, UK, June 20-24, 2011 : proceedings

Interfaces bases de données avancées: quelles recherches pour quelles interfaces?

Evaluation of CRIS 1 IS Devlopments Methods Using a Three Cycles Framework.

Distributed processing of data dynamics

Information System Engineering: The RUBIS System.