Requirements change management based on object-oriented software engineering with unified modeling language

User requirements for software development are getting more complicated and are changing all the time. Not only should the requirements engineering process be well-organized but requirements change management should also be effective, especially for complex systems. However, the software engineering methodology employed can also make requirements change difficult to manage. Object-oriented software engineering using unified modeling language (UML) describes software systems by providing multiple views and diagrams. Therefore, software development with UML needs effective requirements change management. This study proposed a requirements change management model for object-oriented methodology with UML. In order to demonstrate the proposed model, business models from the selected case study, Mission Hospital Phuket, were chosen as the user requirements for the prototype system. Two aspects of the proposed system's performance were evaluated in the research laboratory: (1) users' expectation and (2) users' satisfaction.

I. Introduction

Computer and information technologies have been widely used for several purposes for more than a decade. Besides hardware, software plays a key role for computing systems. To build effective software, an appropriate and well-organized methodology is needed. User requirements for software development are getting more complicated and are changing all the time in order to meet and maintain the goals of business operation as well as an organization's vision and mission. Many factors and reasons may lead to requirements change [1]: user demands, increased understanding of customer needs, availability of new technologies, and, especially in today's changing world, organizational restructuring in response to business competition.