Content tagged with: UML
The Unified Modeling Language (UML) is a modeling language standardized by the Object Management Group (OMG) used to manage requirements in software development projects. IDEF, the acronym for Integration DEFinition, refers to a family of modeling languages in the field of systems and software engineering.
Aspect-orientation provides a new way of modularization by clearly separating crosscutting concerns from non-crosscutting ones. While aspect-orientation originally has emerged at the programming level, it has now stretched also to the modeling activity.
As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts? Nancy Nee, VP Global Product Strategy at ESI International, shares her opinion on the role of business analysts in Agile software development projects and how this approach impacts the requirement gathering activity. She also provides some input on how to handle conflict between stakeholders.
What is the difference between user stories and use cases. This video shows the difference between them with examples, and also shows how they can be related.
This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. The author recommends that you shouldn’t start writing use cases until the team specifically asks for them.
This discussion on the topic of Database Modeling with Dr. Michael Blaha try to answer the question “How good are UML use cases for Database Design“? His opinion is that use cases are rote work. The developer listens to business experts and slavishly write what they hear with little interpretation and no abstraction. There is little reconciliation of conflicting use cases. In a database project, the conceptual data model is a much more important software engineering contribution than UML use cases.
This tutorial describes how to use domain driven modeling in Visual Studio 2010 with conceptual class diagrams. Microsoft Visual Studio Ultimate helps you understand, discuss, and communicate your users’ needs by drawing diagrams about their activities and the part your system plays in helping them achieve their goals.
This video provides an introduction to use case modeling using Visual Studio 2010.
Explore how to combine requirement gathering with documentation that development managers, developers, testers, and technical writers can re-purpose throughout the development cycle. The flexible extension mechanism in Darwin Information Typing Architecture (DITA) is becoming an industry standard for this kind of undertaking. In this article, you create a specialized schema for use case documentation.
This paper investigates the suitability of UML as a semiformal requirements specification language. It identifies and demonstrates various problems and deficiencies of UML, particularly concerning use case models and system decomposition.