Requirements Discovery Methods and Process Modeling

---

Requirements discovery is the process and techniques used by systems analysts to identify or extract system problems and solution requirements from the user community.

The Requirements Discovery Process

• Requirements Planning
• Requirements Elicitation
• Requirements Analysis & Documentation
• Requirements Verification & Review
• Requirements Validation & Acceptance
• Requirements Change Management

---

Fact-finding

Fact-finding is a technique that is used across the entire development cycle, but it is extremely critical in the requirements analysis phase.It is also called information gathering or data collection.Tools, such as data and process models,document facts, and conclusions are drawn from facts. Fact Finding. Once fact-finding has been completed, tools such as use cases, data models, process models, and object models will be used to document facts, and conclusions will be drawn from the facts.During fact-finding, systems analysts often come across or analyze information that is sensitive in nature.Effective fact-finding techniques are crucial to the development of systems projects.
Fact-finding is most crucial to the systems planning and systems analysis phases.It is during these phases that the analyst learns about the vocabulary,problems,opportunities,constraints,requirements,and priorities of a business and a system.During systems design,fact-finding becomes technical as the analyst attempts to learn more about the technology selected for the new system.

Four common fact-finding techniques

• Sampling of existing documentation,forms, and databases.
• Research and Internet site visits.
• Observation of the work environment.
• Questionnaires

---

Context Data Flow Diagram

Context Diagrams and Data-Flow Diagrams were created for systems analysis and design.It is a graphical visualization of the movement of data through an information system. The Context Diagram shows the system under consideration as a single high-level process and then shows the relationship that the system has with other external entities (systems, organizational groups, external data stores, etc.).

A sample Context Diagram


Some of the benefits of a Context Diagram are:

• Shows the scope and boundaries of a system at a glance including the other systems that interface with it
• No technical knowledge is assumed or required to understand the diagram
• Easy to draw and amend due to its limited notation
• Easy to expand by adding different levels of data flow diagrams
• Can benefit a wide audience including stakeholders, business analyst, data analysts, developers