..............................................................................................................iii 1 Integration Challenges for the Practitioner ................................................1 1.1 System Decomposition..........................................................................2 1.2 Business Requirements.................................................................

A method for reengineering software architectures is presented in this paper. The method explicitly addresses the quality attributes of the software architecture. Assessment of quality attributes is performed primarily through the use of scenarios. Design transformations are used to improve quality attributes that do not satisfy the requirements. Assessment and design transformation can be perf...

Non-functional requirements significantly affect and determine the quality of software systems. In this paper it is shown how non-functional requirements are modelled in MIKE, an approach to the development of knowledge-based systems. A semi-formal hypermedia-based model is used to describe the results of the elicitation and interpretation of non-functional requirements and their relationships....

Software requirements engineering produces several different artifacts. In order to cope with all requirements contained in these artifacts, they must be kept in a single place. Today, usually this place is a document or a simple list of requirement statements. A modelling infrastructure for the integration of requirements in models is a new way of keeping and managing requirements in a model-c...

Requirements elicitation is a critical phase in information systems development (ISD), having significant impacts on software quality and costs. Prior research suggests that it is a collaborative activity, where system requirements-related knowledge is extensively shared between users and analysts. This knowledge sharing can get extremely tenuous given the different knowledge perspectives of th...

Open innovation is becoming an important strategy in software development. Following this strategy, software companies are increasingly opening up their platforms to third-party products. However, opening up software platforms to third-party applications raises serious concerns about critical quality requirements, such as security, performance, privacy and proprietary ownership. Adopting approp...

The goal of Web service (WS) discovery is to select WSs that satisfy both the users’ functional and non functional requirements. Focusing on non functional requirements, a matchmaking algorithm usually takes place to verify if the quality offered by the WS provider overlaps the quality requested by the user. Since quality, in a provider perspective, is costly, a further step, a negotiation, sho...

Software requirements engineering is an essential activity for the successful development of information systems. The outcome of this activity is not always successful, which is visible in the lack of software quality, costs and schedules overruns. Although the efforts made and the initiatives proposed, there is not a widely accepted practice or standard in this area, comparable to what we have...

It is well known that requirements engineering plays a critical role in software quality. The use case approach is a requirements elicitation technique commonly used in industrial applications. Software requirements are stated as a collection of use cases, each of which is written in the user’s perspective and describes a specific flow of events in the system. The use case approach offers sever...

Over the years, research on software architecture has identified architectural styles. In this paper we consider five of such styles, and analyze whether these styles can also be found in business value models for networked enterprises. To this end, we analyze 17 evalue models, as discussed in 29 academic papers or book chapters. We also consider whether the quality attributes related to the so...