In this paper a short (16 hours) newly designed course on practical software engineering is described. This course has been designed according to specific objectives (i.e. orientation to the practice, generality and adequacy to the current software engineering community trends) and focused on the requirements elicitation, documentation, and analysis topics. In the course an innovative tool for ...

Multiple viewpoints are often used in Requirements Engineering to facilitate traceability to stakeholders, to structure the requirements process, and to provide richer modelling by incorporating multiple conflicting descriptions. In the latter case, the need to reason with inconsistent models introduces considerable extra complexity. This paper describes an empirical study of the utility of mul...

The goal of requirements engineering is to create a complete, consistent requirements specification of a desired system in order to establish the requirements at an abstract level. Business process modeling in the early phases of requirement engineering is rather useful. This paper examines business process modeling for the development of information systems. It presents the role of Business Pr...

The success of any software development cycle for producing the software product is based on the software requirements. The elicitation of requirements is the first and most important activity in the Requirement Engineering (RE). The problems in requirement elicitation process will result in poor requirements which can lead to the development of unsatisfactory software system. Moreover, the dev...

The proliferation of the Internet Things (IoT) devices and advances in their computing capabilities give an impetus to Edge Computing (EC) paradigm that can facilitate localize data storage. As a result, limitations like network connectivity issues, mobility constraints, real-time processing delays, Cloud be addressed more efficiently. EC create lot opportunities across breadth IT domains cyber...

In Requirements Engineering, requirements elicitation aims the acquisition of information from the stakeholders of a system-to-be. An important task during elicitation is to identify and render explicit the stakeholders’ implicit assumptions about the system-to-be and its environment. Purpose of doing so is to identify omissions in, and conflicts between requirements. This paper offers a concep...

This chapter identifies seven problems associated with requirements elicitation where the intended users are external to the firm, proposes characteristics for requirements elicitation methods to resolve the problems, and tells the story of a new method that supports resolution of six of the seven problems. Diverse, external users, with little relationship to the organization present special pr...