Requirements Management Process Model for Software Development Based on Legacy System Functionalities

Poor or incomplete requirement specification as well as inadequate requirement management is one of the major reasons for project failure and an ongoing source of issues in business application development. These problems cause schedule and budget overruns as well as low level of quality in applications. This paper describes a process model for requirements elicitation, specification, analysis and management in a domain of back-office data entry Web applications meant to replace poorly documented legacy applications. The proposed process model is connected with the subsequent software change management process. The relationship between requirements and business process modelling is presented in business process artefacts which are acquired through requirement activities. The proposed process models are intended for a newly formed development department without an adopted process methodology, aiming at software development based on legacy system functionalities.