Thursday, May 23, 2013

   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




BA ARTICLE ARCHIVE
» May 2013 (6)
» April 2013 (8)
» March 2013 (4)
» February 2013 (6)
» January 2013 (6)
» December 2012 (5)
» November 2012 (7)
» October 2012 (6)
» September 2012 (6)
» August 2012 (5)
» July 2012 (9)
» June 2012 (5)
» May 2012 (9)
» April 2012 (7)
» March 2012 (7)
» February 2012 (5)
» January 2012 (7)
» December 2011 (6)
» November 2011 (6)
» October 2011 (8)
» September 2011 (6)
» August 2011 (8)
» July 2011 (7)
» June 2011 (7)
» May 2011 (6)
» April 2011 (8)
» March 2011 (6)
» February 2011 (5)
» January 2011 (6)
» December 2010 (5)
» November 2010 (9)
» October 2010 (5)
» September 2010 (6)
» August 2010 (8)
» July 2010 (6)
» June 2010 (6)
» May 2010 (10)
» April 2010 (5)
» March 2010 (8)
» February 2010 (7)
» January 2010 (7)
» December 2009 (7)
» November 2009 (7)
» October 2009 (6)
» September 2009 (8)
» August 2009 (10)
» July 2009 (9)
» June 2009 (5)
» May 2009 (10)
» April 2009 (5)
» March 2009 (12)
» February 2009 (8)
» January 2009 (6)
» December 2008 (9)
» November 2008 (8)
» October 2008 (9)
» September 2008 (4)
» August 2008 (6)
» July 2008 (8)
» June 2008 (17)
» May 2008 (12)
» April 2008 (7)
» March 2008 (21)
» February 2008 (16)
» January 2008 (13)
» December 2007 (9)
» November 2007 (25)
» October 2007 (2)
» September 2007 (23)
» August 2007 (12)
» July 2007 (11)
» June 2007 (7)
» May 2007 (6)
» April 2007 (9)
» March 2007 (5)
» February 2007 (3)
» January 2007 (2)
Articles and White Papers
Minimize


Current Articles | Search | Subscribe (RSS)

Entries for the 'Requirements Analysis (BABOK KA)' Category


» FEATURED: How Detailed Should Requirements Be? Part 3 - When More Requirements Detail Is Advisable
Article Rating (8784 Views) (4 Comments)
How Detailed Should Requirements Be? Part 3 - When More Requirements Detail Is Advisable There are several situations in which recording only high-level requirements information increases the project’s risk. When you encounter situations such as the ones described in this article, expect to spend more time than average developing detailed requirements specifications.

» FEATURED: How Detailed Should Requirements Be? Part 2 - When Less Requirements Detail Is Appropriate
Article Rating (7080 Views) (2 Comments)
How Detailed Should Requirements Be? Part 2 - When Less Requirements Detail Is Appropriate Several conditions make it appropriate to leave the requirements descriptions at a higher level of abstraction. Recognize that these are broad guidelines. The BA should perform a risk-benefit analysis to balance the potential downside of omitting important information against the effort required to include it.

» Requirements Reuse: the State of the Practice
Article Rating (3069 Views) (0 Comments)
Requirements Reuse: the State of the Practice For several decades, software reuse has been a recognized solution to improving efficiency of software development. However, implementing reuse in practice remains challenging and the IT community has little visibility into the state of the practice specifically as it pertains to reusing software requirements. This paper presents the results of a s...

» FEATURED: How Detailed Should Requirements Be? - Part 1
Article Rating (12634 Views) (15 Comments)
How Detailed Should Requirements Be? - Part 1 Recently I was chatting at a wine tasting event with a couple of lawyers, who I had just met. One was surprisingly inquisitive about my work in the software requirements arena. Apparently she was working on case involving software at that very time. At one point she asked me, “How do you know how detailed to make the requirements?”

» FEATURED: How to Effectively Engage Requirement Contributors to Achieve Project Success
Article Rating (6300 Views) (1 Comments)
How to Effectively Engage Requirement Contributors to Achieve Project Success Your new system just went live and the project, that replaced a critical legacy system, is coming to a close. Business analysts gathered requirements and worked closely with users and developers, but did you capture all of the requirements?  

» FEATURED: Starting Your Requirements Education
Article Rating (7396 Views) (1 Comments)
Starting Your Requirements Education So you want to be a better requirements analyst. Or maybe you’re completely new to business analysis and you just want to learn what requirements analysis involves, period.

» FEATURED: An Introduction to Requirements Traceability
Article Rating (16402 Views) (1 Comments)
An Introduction to Requirements Traceability Requirements traceability ensures that each business need is tied to an actual requirement, and that each requirement is tied to a deliverable. This is a valuable practice for the business analyst. According to A Guide to the Business Analyst’s Body of Knowledge, (BABOK 2.0), all requirements are “related to other requirements, to solution componen...

» FEATURED: Requirements Are Rules: True or False?
Article Rating (25630 Views) (2 Comments)
Requirements Are Rules: True or False? “Requirements are rules. They arise from business models, but they are different from those business models.”  Perhaps you’ve heard the argument. Maybe you’ve even made it yourself. Are they?  No!  Read this article to find out why.

» FEATURED: Taming the Beast of Complexity
Article Rating (4249 Views) (1 Comments)
Taming the Beast of Complexity In that article we presented our case that the typical approach to business requirements management was fundamentally flawed, with key issues being development of business requirements within a project context, and capture of those requirements using unstructured artifacts, particularly narrative.

» FEATURED: The structure of business analysis documents
Article Rating (31820 Views) (6 Comments)
The structure of business analysis documents The structure of business analysis documents isn't a commonly discussed topic. This article will show what documents are produced by a BA and the main sections they contain. These are the main documents produced by a BA over the course of a project...  

» FEATURED: iRise Requirements Visualization
Article Rating (7165 Views) (0 Comments)
iRise Requirements Visualization Thousands of business analysts have turned to software visualization from as a strategy to simplify their jobs and cut through the confusion. With iRise, business analysts are empowered to quickly assemble a high-fidelity working preview of an application before development ever begins. These visualizations look and act just like the final product,...

» Measurably Improving Your Requirements
Article Rating (5906 Views) (3 Comments)
Measurably Improving Your Requirements Requirements continue to be a major problem area for most organizations. According to industry reports, the leading causes of quality, cost, and schedule problems are lack of understanding of the customer’s needs, incomplete requirement specifications, and managing changing requirements. In fact, requirements are so important that one of the defini...

» FEATURED: Requirements and the Beast of Complexity
Article Rating (15140 Views) (1 Comments)
Requirements and the Beast of Complexity This article promotes a new approach to requirements management that reduces project complexity and improves communication between business and IT. This new approach can be used on its own, or as a supplement or precursor to existing approaches. Critical features of the approach are: detachment of business requirements from individual projects; and...

» FEATURED: Six Simple Steps for Accelerating and Perfecting Requirements: A Framework, a New Model, and Visualization
Article Rating (7702 Views) (2 Comments)
Six Simple Steps for Accelerating and Perfecting Requirements: A Framework, a New Model, and Visualization We present a requirements framework and methodology that may be different from what you are doing. Its three prominent characteristics are a framework, a new model, and visualization. The framework ensures completeness of all requirements. The new model is the Decision Model, transforming important business thinking into a tangible and manageable b...

» FEATURED: Using Extreme Inspections to Significantly Improve Requirements Practice
Article Rating (7577 Views) (6 Comments)
Using Extreme Inspections to Significantly Improve Requirements Practice Extreme Inspections are a low-cost, high-improvement way to assure specification quality, effectively teach good specification practice, and make informed decisions about the requirements specification process and its output, in any project. The method is not restricted to be used on requirements analysis related material; this article however is l...
Page 2 of 7First   Previous   1  [2]  3  4  5  6  7  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-2013 by Modern Analyst Media LLC