Identifying Other Requirements


Even with this fairly exhaustive list, there may well be additional requirements that need to be known and communicated in order to develop a successful system. They may come from a variety of sources; they may be similar to some of the categories above or they may not. In any case, we hope that by now you will recognize them when you see them and will record them accordingly . Examples include

  • Physical artifacts (CDs and so on) that are deliverables of the system

  • Target system configuration and preparation requirements

  • Support or training requirements

  • Internationalization and localization requirements

With a little forethought, you should be able to determine the other types of requirements that will impact the development of your particular system. With a little practice and a little experience, you will be able to determine when you have " discovered enough."


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257 © 2008-2017.
If you may any questions please contact us: