The absence of a disciplined approach for capturing and managing architectural knowledge causes the loss of substantial knowledge generated during the software architecture process. This paper describes the use of a Spatial ...

Software developers are often interested in particular changes in programs that are relevant to their current tasks: not all changes to evolving software are equally important. However, most existing differencing tools, ...

Stakeholders frequently use speculative language when they need to convey their requirements with some degree of uncertainty. Due to the intrinsic vagueness of speculative language, speculative requirements risk being ...

Stakeholders are the primary source of requirements both as a source of information and for making requirements decisions. However, with different stakeholders having various roles and perspectives, with distinct or ...

This paper provides a detailed assessment of the current status of the Information Systems (IS) field by tracing its historical evolution. It uses lessons drawn from the history of another social science, sociology, to ...

The scale and complexity of product lines means that it is practically infeasible to develop a single model of the entire system, regardless of the languages or notations used. The dynamic nature of real-world systems means ...

Behaviour Driven Development (BDD) has gained increasing attention as an agile development approach in recent years. However, characteristics that constitute the BDD approach are not clearly defined. In this paper, we ...

Gaining an understanding of unfamiliar software systems is hard. Existing support tools are based on studies of the information sought by software developers, but often the developers themselves do not know what to look ...

When engineering complex software systems, the key Architectural Design Decisions (ADD) and the reasoning underlying those decisions need to be fully understood by all stakeholders. Achieving such understanding usually ...