Requirements analysis is a real skill. It requires a degree of domain knowledge and understanding of the technical issues involved, but more importantly, the "people" skills necessary to be able to effectively facilitate the ongoing discussion between the parties involved, and to appreciate the what is said and what remains unsaid. There are, of course, technical skills like facility with CASE tools, but more importantly, I see the requirements analyst as a kind of mentor that helps the users and developers to better understand what it is that they really want (and need). Sadly, developers are often not included in this conversation to the degree that they should be. My experience is that a balanced dialog between the involved parties from the beginning is the best way to develop good requirements.
--- "A. Forrey" <[EMAIL PROTECTED]> wrote: > This was exactly my point in the earlier exchanges about the role of > the > MDC and maintenance of the technical platform and infrastructure upon > > which VistA sits. The users are the health professional disciplines > and > they need to know how the technical infrastructure is maintained > conformant to Common conventions. They then can convey the Conceptual > > Content in the form of "Requirements" that are part of the Life Cycel > > Principles in ways that acknowledge the roles of the engineering > disciplines in the other processes of the Life Cycle. The MDC/MTA > forums > provided that mode of communication earlier; reactivation of a more > current environment will help each enterprise how this all works. > That > will benefit the future VistA Community. > > On Wed, 24 Aug 2005, Aylesworth Marc A Ctr AFRL/IFSE wrote: > > > Yes, that is my point it needs input from people on both ends of > the > > process!!! Both the people it is being made for and the people that > are > > making it must have the same vision or expectations or what is > being created > > will not work. The users make a wish list and the engineer keeps it > > realistic. > > > > Thanks > > > > Marc Aylesworth > > > > C3I Associates > > > > AFRL/IFSE > > > > Joint Battlespace Infosphere Team > > > > 525 Brooks Rd > > > > Rome, NY 13441-4505 > > > > Tel:315.330.2422 > > > > Fax:315.330.7009 > > > > Email: [EMAIL PROTECTED] === Gregory Woodhouse <[EMAIL PROTECTED]> "Design quality doesn't ensure success, but design failure can ensure failure." --Kent Beck ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
