Several obstacles to industry acceptance of use cases

(a) Discuss several obstacles to industry acceptance of use cases.

Introduction.

Acceptance of use cases in systems development industry is currently very well go round. However, not all industries can accept the implementation of use cases. For example in the medical field and space. Sometimes the decision is a subjective and not suitable to be included systematically into the use cases that built. Accompa.com defined “A use case is a series of related interactions between a user (or more generally, an “actor”) and a system that enables the user to achieve a goal”.

Based on the above statement, we may conclude that the use cases do not fit and have some obstacles to be used when the user or "actor" failed to make a transaction with the system. Will be discussed further use cases receiving a number of barriers in the industry today.

1.0 Weakness

1.1 Weak consumer needs

In system development, use cases are widely used to collect system functions needs. But the use cases do not tell in detail the requirements between users and developers. In this case, users will not be described in detail in the model use cases. This resulted in conflicts between standards and technical users and system developers. Indirectly developed system experienced many changes and can not be completed within the planned time. Changes to the system very frequently and continuously will not benefit consumers. Therefore, some large industrial companies do not require use cases in the construction of their application systems. They are more concerned with the model user requirements against use cases model.

1.2 Use cases can not be tested

The main weakness of use cases is that it can not be tested. Each model is constructed use cases look almost perfect with the "actor", "use cases" and "association". In general, all use cases that could be constructed in terms of satisfying consumer needs. However, it can not be tested until the developers create applications testing. For example, each use case describes the relationship between users and systems in detail. But everything is explained in graphic form and are not tested with real data. Use cases also did not list the data sample as a simulation test. Therefore there is no accuracy in the test data until completion of the system developed and tested.

1.3 Complex diagrams

Large and complex diagrams will have a negative impact on the beholder. In this situation, the construction of large application systems in the industry will involve significant use case diagram. So, the greater the use case diagram built more difficult it is to be understood. In addition, developers use case will be very difficult to explain the use case flow that they build.

2.0 Use cases strengths

2.1 Easy to understand

In a telling weakness of use cases, we must also see the positive aspects of use need to be built. Among the main advantages of use case is that it uses a simple concept to understand almost all the managers. Most importantly, it is easily understood by non-technical people. Generated graphics and the system tells the journey of each consumer engaged.

2.2 Users focus on their needs

From each use case is built, users focus on their needs. Thus, the evidence given system must support the environmental conditions affecting the workforce and the ability of existing hardware. In the construction of use case, all this is reflected in a time of consumer involvement with the system using a clear workflow. Indirectly, the user can understand the functioning of the system more easily just by looking at a given use case diagram.

In conclusion, acceptance use case for the development of application systems in the industry has its own advantages and disadvantages. When looked at in more detail, use case more appropriate to describe the course in general. It explains the link between user and system in detail.

REFERENCES

http://www.accompa.com/product-management-blog/2009/09/19/use-cases-definition-requirements-management-basics

http://faculty.bracu.ac.bd

http://www.odbms.org/blog/2012/01/use-cases-and-database-modeling-an-interview-with-michael-blaha

http://www.jot.fm/issues/issue_2005_08/article1