Abstract
Object-oriented software engineering methodology defines systems requirements in the form of flow-oriented use cases. This OOSE process involves developing a formal problem description - a problem statement $then developing use cases to capture the functional requirements of a proposed system. According to the OOSE approach, use cases should be used throughout the entire development process. Thus, they play a major role in a project's analysis, design, testing, and implementation stages. Use cases have five key stakeholders namely customers, systems and business analysts, systems architects and developers, software testing and quality assurance engineers, and project managers. Conceptual use case diagrams that draw on critical analysis can enhance a project manager's ability to allocate medium-sized or large-scale development projects in a way that limits task duplication and functional overlaps
