An Introduction to MultiAgent Systems.

Find loads of the research methods in the social sciences book catalogues in this site as the choice of you visiting this page. You can also join to the website book library that will show you numerous books from any types. Literature, science, politics, and many more catalogues are presented to offer you the best book to find. The book that really makes you feels satisfied. Or that's the book that will save you from your job deadline.

Research methods in the social sciences

Software requirements selection and prioritization using SBSE approaches

The Search-Based Software Engineering (SBSE) community is increasingly recognizing the inherit “multiobjectiveness” in Software Engineering problems. The old ways of aggregating all objectives into one may very well be behind us. We perform a well-deserved literature survey of SBSE papers that used multiobjective search to find Pareto-optimal solutions, and we pay special attention to the chosen algorithms, tools, and quality indicators, if any. We conclude that the SBSE field has seen a trend of adopting the Multiobjective Evolutionary Optimization Algorithms (MEOAs) that are widely used in other fields (such as NSGA-II and SPEA2) without much scrutiny into the reason why one algorithm should be preferred over the others. We also find that the majority of published work only tackled two-objective problems (or formulations of problems), leaving much to be desired in terms of exploiting the power of MEOAs to discover solutions to intractable problems characterized by many trade-offs and complex constraints.

/pdf/pareto-optimal-search-based-software-engineering-posbse-a-25muqel0ko.pdf

Pareto-optimal search-based software engineering (POSBSE): A literature survey

A method, system, apparatus and article of manufacture for producing a customized application. In a preferred method of the invention, a selection of components can be identified which are to be deployed to form the customized application. Within the selection of components, points of variability can be specified which can be assigned values when deploying the selection of components. The identified selection of components and the specified points of variability can be persisted in a template. Subsequently, the template can be processed to deploy the identified selection of components, to prompt for values to be assigned to the points of variability, and to configure the identified selection of components with the values at the points of variability thereby producing the customized application.

Creating customized applications using templates having points of variability

MAS-ML 2.0: Supporting the modelling of multi-agent systems with different agent architectures

In software development, release planning is a complex activity which involves several aspects related to which requirements are going to be developed in each release of the system. The planning must meet the customers’ needs and comply with existing constraints. This paper presents an approach based on multiobjective optimization for release planning. The approach tackles formulations when the number of releases is not known a priori and also when the stakeholders have a desired number of releases (target). The optimization model is based on stakeholders’ satisfaction, business value and risk management. Requirements interdependencies are also considered. In order to validate the approach, experiments are carried out and the results indicates the validity of the proposed approach.

A Multiobjective Optimization Approach to the Software Release Planning with Undefined Number of Releases and Interdependent Requirements

Agile software development is known by focusing on interaction among team members to share knowledge. However, little guidance is provided to encourage interaction across agile teams. Based on a preliminary conceptual model, this paper examines influencing factors, such as organizational strategy, and communication flow and channels, regarding inter-team knowledge sharing (KS) effectiveness in agile environments. We analyze the characteristics and the influence of the mentioned factors through a survey research method. Data was gathered from seven Brazilian agile software organizations. We employed statistical analysis techniques, e.g., structural equation modeling and cross-table analysis, to analyze the results. Within the surveyed companies, organizational strategy reflects on moderate commitment towards knowledge. KS practices are carried out to an acceptable standard. Extensive communication flow and the use of several channels denote that agile companies are also fostering interaction across teams. We found strong relationship between these factors and the companies' experience on agile methods. As companies continue on an agile adoption program, they growingly focus on long-term goals and consider knowledge as strategic resource. However, they still need to improve strategy alignment to all organization levels. Thus, we recommend that agile companies consider these factors when striving on this endeavor.

/pdf/the-influence-of-organizational-factors-on-inter-team-469h91iy0l.pdf

The Influence of Organizational Factors on Inter-team Knowledge Sharing Effectiveness in Agile Environments

Context: Previous work have investigated the industry's state of practice on technical debt (TD) by surveying invited practitioners. However, these studies have included only practitioners with a sound understanding of TD, which might incur biases in their findings. One way to reduce this bias is to consider Q&A platforms, such as Stack Overflow (SO), because of containing practitioners with different roles and levels of TD knowledge. Therefore, the discussions on SO can broaden the perception of the state of practice on TD in the industry. Goal: To investigate how TD concepts have been discussed by SO's practitioners. Method: First, we employed data mining techniques to identify TD-related discussions on SO. Next, based on significance and popularity metrics, we considered 195 discussions to be further investigated. For each discussion, we analyzed its contents to identify types of TD followed by activities, strategies, and tools used in its management. Results: We found that code, infrastructure, and architecture debt are the most discussed types of TD on SO. Similarly, TD identification and payment are the most discussed activities. Regarding tools and strategies for TD management, SonarQube and refactoring have been mostly mentioned by practitioners. Conclusion: Our findings may indicate new research directions, as well as expanding the empirical knowledge on how the industry has handled TD.

Technical Debt's State of Practice on Stack Overflow: a Preliminary Study

Although object-oriented software development has experienced the benefits of using frameworks, a thorough understanding of how to change them to meet evolving requirement needs is still object of research. Therefore framework development is very expensive, not only because of the intrinsic difficulty related to capturing the domain theory, but also because of the lack of appropriate methods and techniques to support the evolution and redesign of the framework architecture. This paper proposes the use of refactoring and unification rules to assist framework evolution. The approach is illustrated through the JUnit testing framework.

/pdf/using-refactoring-and-unification-rules-to-assist-framework-2vsqqwjass.pdf

Mariela I. Cortés

Papers

MAS-ML 2.0: Supporting the modelling of multi-agent systems with different agent architectures

A Multiobjective Optimization Approach to the Software Release Planning with Undefined Number of Releases and Interdependent Requirements

The Influence of Organizational Factors on Inter-team Knowledge Sharing Effectiveness in Agile Environments

Technical Debt's State of Practice on Stack Overflow: a Preliminary Study

Using refactoring and unification rules to assist framework evolution