Requirements Engineering: Setting the Context

A Meta-Level Design Science Process for Integrating Stakeholder Needs - Demonstrated for Smart City Services

“…Requirements engineering is one of the crucial stages in software design and development, as it addresses the critical problem of designing the right software for the right user (Aurum and Wohlin, 2005). It is concerned with identification of goals for a proposed system, the operation and conversion of these goals into services and constraints, and the assignments of responsibilities for development.…”

“…Stakeholders play an essential part in requirements engineering, as they represent all the involved parties and will in one way or another define the requirements (Aurum and Wohlin, 2005). Typical stakeholders are product managers, various types of users and the products' software developers.…”

Reflection on Knowledge Sharing in F/OSS Projects

“…Software development is a human-based and knowledgeintensive activity [8,9]. In addition to sound technological infrastructure and effective tools to coordinate the collaborative software development process [1], the success of any project immensely depends on the knowledge and experience brought to it by software developers and users.…”

Business process-based requirements specification and object-oriented conceptual modelling of information systems

“…Requirements represent external characteristics of a software system (Davis, 1993) and can be specified at different abstraction levels (Aurum, Wohlin, 2005b). For example, requirements can be specified at the business level (business requirements) and at the software system level (system requirements).…”

“…As with the stakeholders taxonomy, there exist other requirements taxonomies and classifications (e.g., (Aurum, Wohlin, 2005b;Glinz, 2007;Lauesen, 2002)). Nonetheless, it is again important to present and define the requirements terminology that is used in this thesis.…”