|
 |
| Articles and White Papers
|
|
|
|
|
|
|
|
» Enterprise Architect for Business Analysts
 (4156 Views)
( 7 Comments)
| As a software architect and developer I’ve used Enterprise Architect (EA) from Sparx Systems (www.sparxsystems.com) for a number of years. In that time I’ve spent considerable time and energy trying to get our business analysts to do the same. While I’ve had some success I must admit it’s been an uphill battle. I suspect this is partly because EA i... |
» UML 2 Class Diagram Guidelines
 (757 Views)
( 0 Comments)
| UML class diagrams show the classes of the system, their inter-relationships, and the operations and attributes of the classes. Class diagrams are typically used, although not all at once, to:
Explore domain concepts in the form of a domain model
Analyze requirements in the form of a conceptual/analysis model
Depict the detailed de... |
» UML 2 Class Diagrams
 (381 Views)
( 0 Comments)
| UML 2 class diagrams are the mainstay of object-oriented analysis and design. UML 2 class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and attributes of the classes. Class diagrams are used for a wide variety of purposes, including both conceptual/domain ... |
» UML basics: The class diagram
 (1007 Views)
( 0 Comments)
| Structure diagrams in general
Structure diagrams show the static structure of the system being modeled. focusing on the elements of a system, irrespective of time. Static structure is conveyed by showing the types and their instances in the system. Besides showing system types and their instances, structure diagrams also show at least some of the ... |
» The Pros and Cons of Use Case Diagrams
 (803 Views)
( 0 Comments)
| In the Unified Modeling Language (UML), use cases are visually represented as ellipses. However, in spite of its popularity and size, UML has little of practical use to offer modelers beyond this simple iconic representation. Trying to capture and present requirements using just use case diagrams can often render the otherwise useful technique of u... |
» "Analysis and Design" Considered Harmful
 (383 Views)
( 2 Comments)
| This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts.
Author: Co... |
» Alternatives of Alternatives
 (356 Views)
( 1 Comments)
| Geri Schneider Winters writes about whether or not you could write alternatives to alternatives in use cases.
There is no actual standard for the formatting of a use case specification, just guidelines and best practices. Therefore, if using alternatives to alternatives in use cases makes the use case more clear - use it, by any m... |
» Database Modelling in UML
 (464 Views)
( 0 Comments)
| When it comes to providing reliable, flexible and efficient object persistence for software systems, today's designers and architects are faced with many choices. From the technological perspective, the choice is usually between pure Object-Oriented, Object-Relational hybrids, pure Relational and custom solutions based on open or proprietary file f... |
» Using UML Activity Diagrams for the Process View
 (1155 Views)
( 0 Comments)
| In this article, the focus shifts to a particular view in the 4+1 Architecture Views, defined by the Rational Unified Process. We will examine how to use Activity Diagrams as "roadmaps" for the Process View, to capture processing flows as a series of steps. We will also discuss several techniques for creating these diagrams and ensuring their effec... |
» UML Activity Diagrams: Versatile Roadmaps for Understanding System Behavior
 (575 Views)
( 0 Comments)
| The core purpose of software development is to provide solutions to customers' real problems. Use cases are a vital aspect of a technique that has been used successfully to ensure that development projects actually focus on these problems. They are used to discover, capture, and present customer requirements in a form that is accessible to develope... |
|
|
|
|