C H A P T E R. 6. REQUIREMENTS DISCOVERY. Chapter Six Requirements Discovery. Define system requirements and differentiate between functional and nonfunctional requirements.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
C H A P T E R
The process and technique that a SA uses to identify, analyze, and understand system requirements are referred to as requirements discovery.
The Ishikawa diagram: graphical tool to identify, explore, and depict problems, causes and effects of those problems. (Also called a cause-and-effect diagram or a fishbone diagram.)
Context of Requirements for an Information System
A requirements definition document should consist of the following:
Requirements management - the process of managing change to the requirements.
** ..is used for across the entire development cycle, but extremely critical in the requirements analysis phase..**