Articles on Unified Modeling Language (UML), Software Architecture and Data Modeling
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 software development approaches like Scrum. This article by Paul Raymond discusses how classical use cases can be used to expand Agile user stories during requirements […]
Replacing User Stories with Use Cases Read More »
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.
Use Cases-Based Requirements Engineering Tool Read More »
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.
Model Data Warehousing Flows with UML Profiles Read More »
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).
UML Activity Diagram Review Read More »
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.
Enhanced Entity-Relationship and UML Modeling Read More »