Hi all, As I got the invitation to join this group I have Joined . Now can any one tell me what is the Objective of this group and why this group has been...
Rajesh Kumar
srikumar.rajesh@...
Sep 11, 2006 2:56 pm
29
Why are the requirements important? IMHO - Project management finds importance in the tasks needed for accomplishing a project while requirements engineering...
Hello, forum members! Would you agree to share experience on the use of RM tools? As you know, there exist a wide range of products, both in terms of price and...
Hi All; This is the most-known question for requirements engineering. Everyone has some opinions about this question. Yes, requirements are very important,...
Brad Edmonds wrote: By assigning a unique identifier to each requirement only the req ID is needed for tracing throughout the various documents. Hope that ...
Regarding traceability - at a minimum we trace requirements to the reference in the developer's design doc and to the test case. Though we don't trace to the...
That sounds good to me. I'd also point out that any initial requirement (pre-construction) doesn't need to be in any amount of written detail. For us, it's ...
Hello world! I'm an embedded software developer/designer/analyst/etc. The products I deal with are usually safety-critical. Lately we've been trying to trim...
as this goup is trying to reinvent the wheel i have left read a good book about QFD [Non-text portions of this message have been removed]...
Albert
caruabertu@...
Sep 10, 2006 9:41 am
20
This is something our software development group has been struggling with....how do you trace your source code to your requirements (or the documented design...
Hi All -- ... Here's a thought.... Good Requirements should be (a) In English that nonprogrammers can read and understand and (b) directly executable, so...
... Here are the criteria we came up with: Document Review • Template adequately followed? • Are all requirements written at a consistent and appropriate...
... There has been an interesting article in the Journal of Object Technology some time ago: @ARTICLE{Firesmith2003, author = {Donald G. Firesmith}, title =...
Stefan Winkler
stefan.winkler-et@...
Sep 8, 2006 12:38 pm
16
Keith, you hit it on the head! If a requirement is not testable pas or fail then it’s either not a requirement or needs work. There is a host of criteria...
But this should be an ongoing parallel activity. I'd consider this analysis important to getting missed stories into your pool of requirements as well as...
The questions to ask the user are first "how will you know when this requirement has been met?" and if they can't answer that try "what evidence would convince...
... are you ... test against? Hi, Gathering the requirements from customers and user is very difficult, however, also, writing the requirements is another...
... As you might guess, the IIBA Body of Knowledge committee has spent a lot of time on this issue. Since we were developing a body of knowledge for business...
the email below implies an initial requirements phase, agile or quick and dirty depending on your point of view - the collection of the customer priorities is...
Albert
caruabertu@...
Sep 7, 2006 8:58 am
9
can agile approach be used for general products (serveral customers) too? "Kent J. McDonald" <groups@...> wrote:...
Business Analysis can be done too by: 1- reading all policies and standards of a company and regulations 2- scanning what other softwares in this particular...
Agreed that requirements are very important. However, I do not believe that it follows that they have to be elicited in a phase. One of the advantages of...
... Before elicitation (or maybe the first part of it) must come understanding the business area. This is at least partly done through formal business...
Dear Kent, Thanks for your notice. But, I had thought, when I wrote "main theme", that It was the main phase in SDLC. If you say "main goal" or "target point",...
Actually, I would suggest that the main theme in software development is... running tested software. After all, isn't running tested software what software...
Hi, Business Analysis is the part of RE. Requirement engineering has 5 main parts. These are req. elicitation, requirement negotiation, validation, analysis...
Hi, How are the two fields, Business Analysis and Requirement Engineering, linked? Are they same or closely related? Are you are aware of any specific course...
Hi All, I believe that Requirements are the main theme in software development process. Because, If there are not a requirement, there is no software. However,...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
