Entries for July 2007

4025 Views
0 Likes
0 Comments
In the last few years, the agile software development movement has created a paradigm shift in how we work to understand system requirements. Agile teams shape software systems using a collaborative process, with executable software at its heart and documents marginalised to a peripheral role. This creates a fundamental shift away from tools for ma...
6509 Views
4 Likes
0 Comments
A use case represents a case of use of a system, ideally one that captures a functional requirement in terms of an identifiable and testable goal. So, what is the best way to document a use case? Approaches to content range from diagrammatic to textual, formal to free form, expansive and detailed to brief and abstract. The approaches to tool usage ...
3713 Views
0 Likes
0 Comments
A few years ago I took a photograph an old wooden tombstone. The tombstone read, “Walter Crumbly, Hanged by Mistake – Sorry Walter.” It seems like the software industry wants to collectively hang the waterfall software development method and structured methods. In the not too distant future the software development industry will wake up and realize...
6625 Views
0 Likes
0 Comments

Some of you may be working on systems with many complex relationships between the parts. These complex systems may be described as a system of systems, or may be described as a product line, or perhaps both at once.

In these cases, you will often find that the requirements of a large, overall system are shared among a number of related projects, each of which implements some well-defined part of the overall system.

Author: Geri Schneider Winters

11294 Views
3 Likes
0 Comments

This paper provides an in-depth introduction to the new BPMN standard, illustrating how it is used to model business processes and web services. The paper also provides greater detail on how BPMN fits within BPM, BPEL’s, BPMS’s, UML and other new industry standards and initiatives described above.

7408 Views
2 Likes
2 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 means.

Author: Geri Schneider Winters

17439 Views
11 Likes
0 Comments
In this article, Geri Schneider Winters discusses the question of whether use cases can be used to document requirements for reports.

Author: Geri Schneider Winters

5283 Views
0 Likes
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...
10472 Views
5 Likes
1 Comments

"Business Analysis is about thinking what your solution should do, while Design is about how to make it happen using the technology available. Don't ever combine the two - you save nothing."

This paper by Brian Cooney, principal instructor at IRM, describes the need for clear separation between the two phases and the benefits this provides for a successful project outcome.

Author: Brian Cooney

3512 Views
0 Likes
0 Comments
In this issue of the IIBA Newsletter: BABOK v2 Outlined by Kevin Brennan Requirements Simulation - Analyst's Perspective by Joel Benayon Update on Annual General Meeting 2007 by Indy Mitra Baltimore IIBA Chapter Note by Rick Straub New Brunswick Chapter Note by Mary Ann Johnson

 



 

Copyright 2006-2021 by Modern Analyst Media LLC