PT1420

Unit 6 Research Paper 1: “Advantages and Disadvantages of Using Case Structures”
Advantages:
Because of their many important advantages and extreme popularity, use cases have become a fundamental part of object technology and have been incorporated in one form or another into most major object-oriented development methods.
1.You can create logic flows; in which is a method used to make the reading easier for the reader.
2.Because they are written in natural language, use cases are easy to understand and provide an excellent way for communicating with customers and users. 3.Static depth, in which “if” can be set to however amount the user wants.
4.Low CPU overhead.
5.You can insert certain captions using “< >//”
6.As a user-centered technique, use cases help ensure that the correct system is developed by capturing the requirements from the user's point of view.
-------------------------------------------------

-------------------------------------------------

-------------------------------------------------

-------------------------------------------------

-------------------------------------------------

Disadvantages:
In the rush to jump onto the use case bandwagon, use cases have been perceived by some as either a panacea or as an end in-and-of themselves. Unfortunately, this has often led to the uncritical acceptance of use cases without any examination of their numerous limitations and ample opportunities they offer for misuse. The following provides an overview of the major risks associated with use cases:
1.If it is case specific, in which a case can’t be re-used.
2.If it is static, in which the user will not be able to create most implements. 3.The “Bloated syntax” takes space, in which case is more functional when used in an equation. 4.It takes a lot of maintenance, because for any change requires fixing throughout the entire structure. 5.Most programmers use it; which means that whatever you’re creating is basically of the norm. 6.Use cases are not object-oriented 7.This scattering of objects to use cases leads to the Humpty Dumpty effect, in which all the kings designers and all the king's coders are unlikely to put the objects and classes back together again without a massive expenditure of time and effort.
8.The simple structure of the use case model does not clearly map to the network structure of the object model with its collaborating objects and classes.

Refereneces: * [1] Ivar Jacobson, Object-Oriented Development in an Industrial Environment, Proceedings of OOPSLA´87, SIGPLAN Notices, Vol. 22, No. 12, pages 183-191, 1987. * [2] Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard, Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, Wokingham, England, 1992.