UOOR: an Object-Oriented Approach for Requirements engineering

In industrial practice, requirements are an indispensable element of any serious software project. In the academic study of software engineering, requirements are one of the heavily researched subjects. And yet requirements as practiced in industry makes shockingly sparse use of the concepts propounded in the requirements literature. The talk starts from an assumption about the causes for this situation, and proposes a remedy to redress it. The posited explanation is that change is the major factor affecting the practical application of even the best-intentioned requirements techniques. Requirement methods that assume that requirements can be set once and for all to guide the development are doomed. The proposed remedy is a requirements method, called UOOR, which unifies many known requirements concepts and a few new ones in a framework entirely devised to accommodate and support seamless change throughout the project lifecycle. The UOOR method (the acronym stands for Unified Object-Oriented Requirements) encompasses the commonly used requirements techniques, namely, scenarios, and integrates them into the seamless software development process. We introduce the notion of seamless requirements traceability, which relies on propagation of traceability links, themselves based on formal properties of relations between project artifacts. As a proof of concept we present a Traceability tool, to be integrated into a general-purpose IDE, that provides the ability to link requirements to other software project artifacts, to display notifications of change in requirements and to trace those changes to the related project elements.
Рабочая (необработанная) запись на RuTube-канале ИСИ СО РАН: https://rutube.ru/video/160e925ef3c922085fe76975a668d58a/