Showing papers in "Journal of Systems and Software in 2007"

TL;DR: In this article, the authors report experiences with applying one such approach, the practice of systematic literature review, to the published studies relevant to topics within the software engineering domain, and some lessons about the applicability of this practice to software engineering are extracted.

TL;DR: The five industrial software architecture design methods are compared and it is found that the five approaches have a lot in common and match more or less the ''ideal'' pattern that can be used for further method comparisons.

TL;DR: A scheme to improve authentication ability that prevents dishonest participants from cheating is presented and the arrangement of embedded bits is defined to improve the quality of stego-image.

TL;DR: In this paper, the authors present guidelines for performing systematic reviews on software engineering, and comment on systematic review generally with respect to their experience conducting one, and recommend researchers clearly and narrowly define research questions to reduce overall effort, and to improve selection and data extraction.

TL;DR: Analysis of two months of sales data collected by an Australian company selling CMMI appraisal and improvement services found small organizations not adopting CMMI tend to say that adopting it would be infeasible, but do not say it would not be unbeneficial.

TL;DR: This work introduces a rationale-based architecture model that incorporates design rationale, design objects and their relationships and applies traceability techniques for change impact analysis and root-cause analysis, thereby allowing software architects to better understand and reason about an architecture design.

TL;DR: It is shown that some bad smells were positively associated with the class error probability in the three error-severity levels in an industrial-strength open source system.

TL;DR: The MANOVA analysis revealed that no association between the probability of occurrence and composite impact among the six risk dimensions exists and hence, it is a crucial consideration for project managers when deciding the suitable risk management strategy.

TL;DR: This paper employs a novel exploratory modeling technique, multiple adaptive regression splines (MARS), to build software maintainability prediction models using the metric data collected from two different object-oriented systems, and suggests that for one system MARS can predict maintainability more accurately than the other four typical modeling techniques, and that for the other system MARs is as accurate as the best modeling technique.

TL;DR: The empirical results show that applying a suitable linear model to adjust the analogy-based estimations is a feasible approach to improving the accuracy of software effort estimates and that the proposed model is comparable with those obtained when using other effort estimation methods.

TL;DR: Vietnamese and Indian software development practitioners' perceptions of the role of trust in managing client-vendor relationships and the factors that are critical to trust in off-shore software outsourcing relationships are understood.

TL;DR: It is found that with increasing institutionalization of a consistent and empowered product management role, the success rate of projects in terms of schedule predictability, quality and project duration improves.

TL;DR: This paper develops a formal procedure for a “stepwise” approach to variable selection that involves sequentially maximizing the average change in the efficiencies as variables are added or dropped from the analysis.

TL;DR: This paper explains the neural networks from the mathematical viewpoints of software reliability modeling and shows how to apply neural network to predict software reliability by designing different elements of neural networks and uses the approach to build a dynamic weighted combinational model (DWCM).

TL;DR: The authors' experiments indicate that SaveCCT provides appropriate expressiveness, resource efficiency, analysis and verification support for component-based development of vehicular software.

TL;DR: What implications usability has for software development is analyzed, paying special attention to the impact of this quality attribute on design, and a possible quantification, calculated from a number of real applications, of the effect of incorporating certain usability features at design time.

TL;DR: It is concluded that the capability maturity model levels do associate with IS implementation strategies and higher CMM levels relate to higher software quality and project performance and that information systems (IS) implementation strategies have a significant impact on software qualityand project performance.

TL;DR: Using data collected from software projects developed in Korea, the impacts of specific risk management strategies and residual performance risk on objective performance measures such as cost and schedule overrun are investigated.

TL;DR: The conclusion from this study shows that software organizations can achieve some economic gains in terms of software development productivity and product quality if they implement OSS components reuse adoption in a systematic way.

TL;DR: COCOA allows the dynamic realization of user tasks according to the specifics of the pervasive computing environment in terms of available services and by enforcing valid service consumption.

TL;DR: In this paper, an architecture-based unified hierarchical model for software performance, reliability, security and cache behavior prediction is proposed, which employs discrete time Markov chains (DTMCs) to model software systems and provides expressions for predicting the overall behavior of the system based on its architecture as well as the characteristics of individual components.

TL;DR: The experimental results show that the HPSO is robust against different problem size, task interaction density, and network topology, and the proposed method is also more effective and efficient than a genetic algorithm for the test-cases studied.

TL;DR: A model-driven transformation framework, centered around a kernel language whose aim is to capture the relevant information for the analysis of non-functional attributes of component-based systems, with a focus on performance and reliability is defined.

TL;DR: This work proposes a reusable context ontology model that is based on two levels: a generic level and a domain specific level and introduces a comprehensive adaptation approach that involves content adaptation and presentation adaptation inline with the adaptation of the core services of applications.

TL;DR: This study provides an example of security architecture planning based on EA, which aligns the development of technological solutions with the business goals and provides arguments for cohesive identity and access management (IAM) in a business network.

TL;DR: This paper presents a technique for evaluating risk levels in software projects through analogies with economic concepts that allows a manager to estimate the probability distribution of earnings and losses incurred by an organization in relation to its software project portfolio.

TL;DR: It is shown how hidden data may be extracted to gain evidence in forensic environment where even a small piece of information may be relevant and a new stegosystem especially designed for Microsoft Office documents is introduced.

TL;DR: This approach provides a structured way to construct state-based models of a product line having significant, safety-related variations and to systematically explore the relationships between behavioral variations and potential hazardous states through scenario-guided executions of the state model over the variations.

TL;DR: This study collected a set of static metrics and change data at class level from two open-source projects, KOffice and Mozilla, and identified and characterized the change-prone classes in the two products by producing tree-based models and suggested a prioritization strategy.

TL;DR: This work proposes the use of Fuzzy Logic theory with the purpose of determining and reasoning about the current situation of the involved user and elaborate on the architectural model that enables the system to assume actions autonomously according to previous user reactions and current situation.