Join the Premier Community for Business Analysts!
In association with the
Register
Login
Thursday, July 03, 2008
Home
Forums
The Profession
Community
Resources
Careers
e-Journal
About Us
Resources
»
Articles
Business Analysis Articles & Systems Analysis Articles
Resources
Articles
News
Books
Directory of Websites
Training Courses
Organizations
Article Archive
July 2008 (2)
June 2008 (17)
May 2008 (12)
April 2008 (7)
March 2008 (21)
February 2008 (16)
January 2008 (13)
December 2007 (9)
November 2007 (26)
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
Current Articles
|
Categories
|
Search
|
Subscribe (RSS)
Articles from
April 2007
»
Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them
(172 Views) (
0
Comments
)
In this column, I summarize the 12 worst of the most common requirements engineering problems I have observed over many years working on and with real projects as a requirements engineer, consultant, trainer, and evaluator. I also list the negative consequences of these problems, and most importantly suggest some industry best practices that can he...
»
Requirements Engineering Tasks
(172 Views) (
0
Comments
)
Many managers and others who are not professional requirements engineers tend to greatly over-simplify requirements engineering (RE). Based on their observations that requirements specifications primarily contain narrative English textual statements of individual requirements and that all members of the engineering team are reasonably literate, the...
»
The Use Case Model
(180 Views) (
0
Comments
)
The Use Case Model describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example login to system, register with system and create order are all Use Cases. Each Use Case has a description which ...
»
Painless Functional Specifications - Part 4: Tips
(263 Views) (
0
Comments
)
In this fourth and final part of the series I'll share some of my advice for writing good specs. The biggest complaint you'll hear from teams that do write specs is that "nobody reads them." When nobody reads specs, the people who write them tend to get a little bit cynical. It's like the old Dilbert cartoon in which engineers use stacks of 4-inc...
»
Painless Functional Specifications - Part 3: But... How?
(179 Views) (
0
Comments
)
Now that you've read all about why you need a spec and what a spec has in it, let's talk about who should write them. Who writes specs? Let me give you a little Microsoft history here. When Microsoft started growing seriously in the 1980s, everybody there had read The Mythical Man-Month, one of the classics of software management. (If you haven'...
»
Painless Functional Specifications - Part 2: What's a Spec?
(184 Views) (
0
Comments
)
This series of articles is about functional specifications, not technical specifications. People get these mixed up. I don't know if there's any standard terminology, but here's what I mean when I use these terms. A functional specification describes how a product will work entirely from the user's perspective. It doesn't care how the thing is i...
»
Painless Functional Specifications - Part 1: Why Bother?
(162 Views) (
0
Comments
)
It seems that specs are like flossing: everybody knows they should be writing them, but nobody does. Why won't people write specs? People claim that it's because they're saving time by skipping the spec-writing phase. They act as if spec-writing was a luxury reserved for NASA space shuttle engineers, or people who work for giant, established insu...
»
First Things First: Prioritizing Requirements
(474 Views) (
0
Comments
)
Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product (at least, not if they want the features to work). However, if the development team cannot deliver every requirement by the scheduled initial delivery date, the project stakeholders must agree on which subset to implemen...
»
10 Requirements Traps to Avoid
(149 Views) (
0
Comments
)
The path to quality software begins with excellent requirements. Slighting the processes of requirements development and management is a common cause of software project frustration and failure. This article describes ten common traps that software projects can encounter if team members and customers don’t take requirements seriously. I descr...
ARTICLE/PAPER CATEGORIES
»
Activity Diagram
»
Agile Methods
»
Analytical and Problem Solving Skills
»
Business Analysis Planning (BABOK KA)
»
Business Process Management (BPM)
»
Business Process Modeling Notation (BPMN)
»
Career as a Business Systems Analyst
»
CBAP
»
Class Diagram
»
Data Analysis & Modeling
»
Elicitation (BABOK KA)
»
Enterprise Analysis (BABOK KA)
»
Estimation
»
Functional Specifications
»
Getting Started as a Business Systems Analyst
»
IIBA & BABOK
»
Interviewing & Hiring Business Systems Analysts
»
Leadership & Management
»
Process Improvement (CMMI, Six Sigma, SPICE, etc.)
»
Project Management
»
Requirements Analysis (BABOK KA)
»
Requirements Management and Communication (BABOK KA)
»
SDLC, Process, and Methodologies
»
Security Analysis
»
Service Oriented Architecture (SOA)
»
Soft Skills
»
Solution Assessment and Validation (BABOK KA)
»
Structured Systems Analysis (DFDs, ERDs, etc.)
»
Technical Topics
»
Testing & Quality Assurance (QA)
»
Tools
»
Unified Modeling Language (UML)
»
Use Cases
»
User Interface & Usability
»
Vertical Domain or Industry
Advertising Opportunities
|
Contact Us
Privacy Statement
|
Terms Of Use
Copyright 2006-2008 by Modern Analyst Media LLC