Lecture Notes on Software Engineering (LNSE)
Replacing legacy systems with off-the-shelf enterprise resource planning (ERP) software involves complex requirements analysis. To minimize risk and enable smooth execution of subsequent software development phases during implementation, they propose an approach that uses bipartite graph(s) to formalize ERP requirements. An industrial case study suggests that this type of lightweight formalism can be useful for large-scale, volatile projects such as ERP implementations. Their model is applicable to activities like product line engineering, domain analysis and test-driven development and facilitates reusing knowledge throughout the development lifecycle. Results indicate that bipartite matching can be advantageous for new and existing ERP projects that involve upgrading, merging, or transitioning.