By Topic

Qualifying use case diagram associations

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Dedeke, A. ; Suffolk Univ., Boston, MA ; Lieberman, B.

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

Published in:

Computer  (Volume:39 ,  Issue: 6 )