|
 |
| Articles and White Papers
|
|
|
|
|
|
|
|
» Eight Things Your Business Analysts Need to Know
 (656 Views)
( 0 Comments)
| Each year, organizations across the globe face astronomical project failure rates, often wasting millions of dollars per failed project. This paper examines the roots of project failure and centers in on the elusive, often undefined role of the business analyst. In response to research showing that many organizations have not set concrete requireme... |
» Memoir of the CBAP Exam
(878 Views)
( 0 Comments)
| In this article from ESI Horizons newsletter, Chip Schwartz discusses his experiences with sitting for the first Certified Business Analyst Professional (CBAP) exam in November 2006.
Author: Chip Schwartz |
» Tips for Business Analysts: What are RUP, EUP, UP, OpenUP, EssUp?
 (1155 Views)
( 1 Comments)
| RUP describes a process for developing software systems. It seems there are so many variations of RUP, how do you know which is best for you and your organization, if any? What do all those acronyms mean? Where are these things coming from?
Author: Geri Schneider Winters |
» "Analysis and Design" Considered Harmful
 (498 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... |
» Implicit Data Dictionaries are Dangerous!
(562 Views)
( 0 Comments)
| Describes the difference between a data dictionary and an implicit data dictionary and why an implicit data dictionary (or no data dictionary at all) may spell trouble for your project. Can data dictionaries be used with UML Use Cases or an XP methodology?
Author: Conrad Weisert |
» Agile Requirements
(364 Views)
( 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... |
» How to Document Use Cases
(520 Views)
( 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 ... |
» The Agile Method and Other Fairly Tales
(305 Views)
( 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... |
» A Requirements Analysis Primer
(324 Views)
( 0 Comments)
| Depending on the maturity of the software development processes within an organization, activities such as requirements analysis and design are treated as wasted time. The logic seems to follow that programmers should be writing code, not talking about writing code. For anything but the most insignificant of solutions, this focus is short sighted a... |
» Tips for Business Analysts: Requirements in Complex Systems
(429 Views)
( 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, e... |
|
 |
|
|