Content in the Articles Category
Use Cases are a classical format used in UML to describe user scenarios and document requirements. They have been mostly replaced by user stories when software development teams adopt Agile approaches like Scrum. This article by Paul Raymond discusses how classical use cases can be use to expand user stories during requirements elicitation in Scrum sprints.
The use cases model is used to capture requirements. The use case model is a part of UML (Unified Modeling Language), a standardized design notation for the design and development of object-oriented software. Its simplicity in terms of notations and expressiveness makes it easier to use both by customers and developers.
Data warehousing commonly implies complex data flows, either because of the large number of steps data transformations may consist of, or of the different types of data they carry. These issues rise interesting challenges concerning design-oriented modeling of data warehousing flows with UML.
The UML activity diagram is graphical presentation that describes the operational process and related causes used in each stage of the system. To detect the misconception and incorrect notation, this paper presents an automation approach to reviewing UML activity diagrams based on a domain specific language, called Action Description Language (ADL).
Some databases have more complex requirements than do the more traditional applications. This led to the development of additional semantic data modeling concepts that were incorporated into conceptual data models such as the Entity-Relationship (ER) model.
This paper presents an approach that utilizes object technology and the UML notation for the development of communication protocols. Object technology has been widely adopted in many application domains and the Unified Modeling Language (UML) has become the new industry standard for modeling software-intensive systems. UML is currently used for modeling of just about any type of applications, running on any type and combination of hardware, operating system, programming language and network. However,protocol design is still based on traditional methodologies.
The control-flows for five kinds of UML use cases are analyzed: for common use cases, variant use cases, component use cases, specialized use cases and for ordered use cases. The control-flow semantics of use cases – and of the uses-relation, the extends-relation and the precedes relation between use cases – is described in terms of flowgraphs. Sequence diagrams of use cases are refined to capture the control-flow adequately. Guidelines are given for use case descriptions to attain a well-defined flow of control.
In this article, Simon Brown discusses the impact of the Agile approaches on the conception and representation of software architectures. The main point of the article is that software developers seems to have abandoned the Unified Modeling Language (UML) or just haven’t learned it. The question is then: how would you represent the software architecture?
Starting from the relationship between the requirements and the test cases, Raul Rugiero proposes in this article to improve the notation of UML uses cases to achieve a better management of the relationship between UML uses cases their related test cases.
Object-oriented system modeling enables the sharing of responsibilities between system objects at a high level of system abstraction. The UML class diagram is the central part of the object-oriented system model and serves as a “bridge” between the information about the problem domain at the customer’s side and the software components at the developer’s side.