The requirements management practices: A study at UUM IT

Requirements engineering is a main process in software engineering that focusing on development and managing the user requirements. One of the requirements engineering activities is requirements management. It plays an important role when it comes to the support of product development teams. Despite this, there is a lack of practice in requirements management activity in the software project development. Malaysian software markets are still facing several problems in requirements management practices such as requirements quality, requirements inadequately, and identification of requirements; with limited studies that address it. In this study, UUM IT as computer services provider in a local universities in Malaysia is design as case study, to represent as one organization in Malaysia software markets. This study aims to investigate the current situation for the requirement management in UUM IT, and assess the relationship CMMI level 2 with the requirements management practices in UUM IT. This study adopted mixed method through used questionnaire with the UUM IT team, as well as, interviews with managers of UUM IT for more reliability. The outcome of study showed that the UUM IT are used requirements management activities but there is a need for more attention and improve. Moreover, the study proposes CMMI appraisal method to enhance the performance of software development tea

Using active database for management of requirements change

Software system development projects experience numerous changes during their life cycle. These changes are inevitable and driven by several factors including changes to a system\u27s environment and changes of customers\u27 needs. Requirements change has been reported as the major contributing factor for poor quality or even failures of software projects. This indicates that management of requirements change still remains a challenging problem in software development. A critical part of the requirements change management process is impact analysis. To carry out impact assessment, traceability information is needed. Over two decades, requirements traceability has been an important research topic in software research, but the actual practice of maintaining traceability information is not always entirely successful. In this thesis, a new traceability technique was presented for mapping dynamic behaviors of requirements into Active Databases. The technique keeps requirements and their related artifacts synchronized with respect to their states. It automatically maintains traceability links between requirements and related artifacts when a requirement is changed. This approach can not only efficiently handle basic and necessary traceability functions, but also centralize reactive behavior by using Active Database to ensure no one bypass traceability policies.Dept. of Computer Science. Paper copy at Leddy Library: Theses & Major Papers - Basement, West Bldg. / Call Number: Thesis2005 .G42. Source: Masters Abstracts International, Volume: 44-03, page: 1401. Thesis (M.Sc.)--University of Windsor (Canada), 2005