Modelagem de requisitos baseado em casos de uso para umsistema legado

Abstract

New modules, products and features are frequently being specified to credit card systems implemented in mainframe. Own forms or templates for requirements specifications are filled using formal textual escriptions. Although the use of models of business requirements and funcitional requirements , the error rate has been elevated. Often the requirementsspecifications are not clear enough for the development on time and with the quality expected by the stakeholders. It is not the intention of this work to propose change in methodology actually used (development focusing in cascade) by companies. However the intention is to study and present a case study that use new techniques such as Use Cases to improve understanding between every one involved in the work in relation to behavioral requirements, resulting in better product quality end. Engineering object-oriented software became popular in the 90s and at this time Ivar Jacobson presented Use Cases, his creation designed 2 decades ago, to the community Object Oriented Programming as reported by CockBurn (1999). Software Engineering emphasizes the need for gathering requirements for system development, as evidenced by the finding projects with high rates of error in terms of time,resources and even features that not agree properly with customers necessity (SAMPAIO; PRIMO; MARTINHO, 2005). The techniques of object-orientation with the possibility of deriving Use Cases from requirements motivate the research of this monograph, which willfocus on techniques for modeling requirements base on scenarios, User Stories and Use Cases.