Graduation date: 1987

Thesis (M.S. in Information Technology Management)--Naval Postgraduate School, June 2008. / Thesis Advisor(s): Kamel, Magdi N. "June 2008." Description based on title screen as viewed on August 26, 2008. Includes bibliographical references (p. 251-253). Also available in print.

Diss.--Landwirtschaftliche hochschule, Berlin. / Lebenslauf. "Literatur": p. 72-74.

Thesis--PlanB (M.S.)--University of Wisconsin--Stout, 2000. / Field project. Includes bibliographical references.

Chemnitz, Techn. Univ., Diplomarb., 2003.

Techn. Universiẗat, Diss., 2006--München.

No description available.

Requirements Engineering (RE) is nowadays considered to be an activity, that aims at supporting the whole lifecycle of an information system by: eliciting, documenting, validating, and managing the requirements of the system. This thesis aims at providing an overview of the area of Requirements Management (RM) and to identify important and interesting issues or areas where further research is needed. RM includes two major areas; organising requirements and requirements change management. Organising requirements is concerned with structuring the requirements and storing additional relevant information about them e.g. attributes and traceability information. Requirements change management is concerned with dealing with changing requirement in a systematic way i.e. making informed decisions whether to implement a certain change or not, and support the implementation of approved changes. In order to provided a broader view of RM, the literature study were complemented by an interview study of how RM is conducted in practice. This interview study shows that the effort resources spent on RM differs substantially between different organisations. Various reasons for these discrepancies are elaborated in the work, but one of the main reasons are the type of software development that is conducted in the organisation. There is a tendency that organisations that develop software products and continuously releases new versions of there products are more likely to spend resources on RM, compared with organisations that develop customers specific solutions in one shoot projects. The need to reuse requirements and knowledge, as well as the maturity of the RE/RM process, are other factors that affects the resources spent on RM. The RM activities performed in practice are concordant with the activities found in literature. A number of areas where further research is needed were identified: requirements change management, dependencies between requirements, RM tools, and information management

No description available.

This thesis reacts to the still poorly mastered area of requirements analysis in the development of software, which shows that incorrectly defined requirements are one of the major causes of failure of software projects. The thesis deals with the techniques for gathering requirements, for example the use of requirements workshops as an approach, where a number of various stakeholders under the guidance of a facilitator create a defined output and collectively shape the requirements for SW. Organizing similar workshops is an intensive activity in which it is necessary to consider many aspects; these are discussed in the theoretical part of the thesis. The practical outcome of this work is a methodological framework purposed as a guideline for organizing a specific workshop focused on understanding the problem areas and solutions, identifying stakeholders and the scope of the project, where the problem is viewed from the perspective of the overall context and detachment, which is essential in the early stages of the software project. The workshop was designed and implemented during a university course Software Project and adapted the MMSP methodology, which is used in the course.