Interface-based software requirements analysis

Abstract

Software requirements analysis is a critical phase in the software development life cycle. It is usually carried out using one of the following: use cases, user stories or business scenarios. Use cases, user stories and business scenarios thus become inputs for the object-oriented analysis (OOA) of application software development. Most translating and mapping of software requirements from text to objects and classes creates problems with software acceptance. There is also a practical issue with object-oriented analysis, namely, that OOA and object-oriented design (OOD) both operate with the same objects and classes, and, in practice, it has not yet been possible to separate them from one another. The goal of this article is to provide a solution that will simplify software requirements analysis and separate such analysis from design, in order to give architects, developers and testers the ability to work independently through a contract (interface) that integrates their work.