Thursday, September 02, 2010

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

Business Analyst Articles: Business Analysis & Systems Analysis

Resources



Articles and White Papers
Minimize


Current Articles | Search | Subscribe (RSS)

Entries for July 2007


» Agile Requirements
Article Rating (945 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
Article Rating (1853 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
Article Rating (924 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
Article Rating (857 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
Article Rating (929 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...

» BPMN and Business Process Management
Article Rating (2653 Views) (0 Comments)
BPMN stands for Business Process Modeling Notation. It is the new standard for modeling business processes and web service processes, as put forth by the Business Process Management Initiative (BPMI – www.BPMI.org). BPMN is a core enabler of a new initiative in the Enterprise Architecture world called Business Process Management (BPM). Business Pro...

» Alternatives of Alternatives
Article Rating (1242 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...

» Use Cases and Reports
Article Rating (2965 Views) (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

» Database Modelling in UML
Article Rating (1462 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...

» Separating Analysis from Design
Article Rating (1795 Views) (0 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...
Page 1 of 2First   Previous   [1]  2  Next   Last   

Do you twitter?: If you want short updates on what's going on in the BA world and at ModernAnalyst.com, simply follow us on Twitter: http://twitter.com/ModernAnalyst



Privacy Statement  |  Terms Of Use
Copyright 2006-2010 by Modern Analyst Media LLC