Requirements Management - SRM

Monitoring aktuálních informací a webových zdrojů týkajících se "Software Requirements Managementu - SRM". Weblog je součástí informačního portálu AKA-MONITOR, www.akamonitor.cz, spravovaného doc. A. Katolickým. Stránka podporuje službu RSS! Vzhledem k malému počtu českých zdrojů, jsou odkazy směrovány rovněž na stránky v angličtině nebo němčině.

Moje fotka
Jméno:
Místo: Plzeň, Czechia

Internetový publicista provozující AKA-MONITOR ISSN 1804-042X www.akamonitor.cz,.

4.1.07

5 základních chyb v analýze požadavků a jak na ně

Analýza sw požadavků ( Requirements Analysis ) je považována za kritickou fázi celého procesu správy požadavků ( Requirements Management ). Na portálu TechRepublic.com byl vystaven zajímavý článek, nazvaný:
"Five common errors in requirements analysis (and how to avoid them)".
Z článku vybírám úvod a seznam problémů. Plný text si můžete přečíet nebo stáhnout na níže uvedené adrese.
Overview:
In the traditional waterfall model of software development, the first phase of requirements analysis is also the most important one. This is the phase which involves gathering information about the customer's needs and defining, in the clearest possible terms, the problem that the product is expected to solve. Well, at least that's the way it's supposed to work theoretically. In reality, there are a number of problems with this theoretical model, and these can cause delays and knock-on errors in the rest of the process. This download discusses some of the more common problems that
project managers experience during this phase, and suggests possible solutions.
Takeaway
In the traditional waterfall model of software development, the first phase of requirements analysis is also the most important one. There are a number of problems with this theoretical model, and these can cause delays and errors in the rest of the process. This article discusses some of the more common problems that project managers experience during this phase, and suggests possible solutions.
Requirements analysis
In the traditional waterfall model of software development, the first phase of requirements analysis is also the most important one. This is the phase which involves gathering information about the customer's needs and defining, in the clearest possible terms, the problem that the product is expected to solve.
This analysis includes understanding the customer's business context and constraints, the functions the product must perform, the performance levels it must adhere to, and the external systems it must be compatible with. Techniques used to obtain this understanding include customer interviews, use cases, and "shopping lists" of software features. The results of the analysis are typically captured in a formal requirements specification, which serves as input to the next step.
Well, at least that's the way it's supposed to work theoretically. In reality, there are a number of problems with this theoretical model, and these can cause delays and knock-on errors in the rest of the process. This article discusses some of the more common problems that project managers experience during this phase, and suggests possible solutions.
5 problémů:
Problem 1: Customers don't (really) know what they want Problem
2: Requirements change during the course of the project Problem
3: Customers have unreasonable timelines Problem
4: Communication gaps exist between customers, engineers and project managers Problem
5: The development team doesn't understand the politics of the customer's organization
Celý text najdete na adrese:
http://articles.techrepublic.com.com/5100-3513-6146544.html