A directory of resources inthe field of technical communication.

Seilevel

3 found.

About this Site | Advanced Search | Localization | Site Maps

 

1.
#37255

Business Requirements Documents vs. Functional Software Requirements

To determine what goes into the BRD and what goes into an SRS, the best place to start is by thinking in terms of who uses the BRD vs. the SRS and what decisions do they need to make from it. If you think of a typical process model, executives must be presented with information following each phase to determine if the project should continue. Based on the information gathered in each phase, the team presents a summary to the executive who decides whether to proceed.

Chen, Anthony. Seilevel (2010). Articles>Business Communication>Requirements>Functional Specifications

2.
#37257

Five “Joys” of using Excel as a Software Requirements Management Tool

Early in the project, the program manager decided to use Microsoft Excel as the tool of choice for gathering and managing the requirements, each module would have their own set of requirements. It sounded like a good choice to the program manager, since everyone has Excel on their machine and it would be easy to share files amongst all interested parties. I’m sure that sounded good at the time, but it has certainly been a pain for me.

Stockdale, Betsy. Seilevel (2010). Articles>Business Communication>Requirements>Microsoft Excel

3.
#37256

Using Questionnaires in One on One Requirements Gathering Process

Questionnaires are usually associated with getting information from large groups of distributed users. They work very well when other means of eliciting requirements are not very practical. However, of late, I have been using them a lot to gather requirements from individuals or small groups whom I am meeting in person or via telephone.

Seilevel (2010). Articles>Business Communication>Recruiting>Surveys

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon