chap006 (1)

chap006 (1) - Introduction to Requirements Discovery...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Introduction to Requirements Discovery Requirements discovery – the process and techniques used by systems analysts to identify or extract system problems and solution requirements from the user community. System requirement – something that the information system must do or a property that it must have. Also called a business requirement . Why – Over budget, overdue, doesn’t meet expectations, high operating cost, unreliable, reputation.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Functional vs. Nonfunctional Requirements Functional requirement - something the information system must do Nonfunctional requirement - a property or quality the system must have Performance Security Costs
Background image of page 2
The Process of Requirements Discovery Problem discovery and analysis Requirements discovery Documenting and analyzing requirements Requirements management
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Ishikawa Diagram (Problem Discovery and Analysis) The Ishikawa diagram is a graphical tool used to identify, explore, and depict problems and the causes and effects of those problems. It is often referred to as a cause-and-effect diagram or a fishbone diagram.
Background image of page 4
Requirements Discovery Given an understanding of problems, the systems analyst can start to define requirements. Fact-finding – the formal process of methods and techniques to collect information about system problems, requirements, and preferences. It is also called information gathering or data collection . Seven Fact-Finding Methods: Sampling of existing documentation, forms, and databases. Research and site visits. Observation of the work environment. Questionnaires. Interviews. Prototyping. Joint requirements planning (JRP).
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Sampling Existing Sampling –process of collecting a representative sample of documents, forms, and records. Organization chart Memos and other documents that describe the problem Standard operating procedures for current system Completed forms Manual and computerized screens and reports Samples of databases Flowcharts and other system documentation And more
Background image of page 6
Things to be Gleaned from Documents Symptoms and causes of problems Persons in organization who have understanding of problem Business functions that support the present system Type of data to be collected and reported by the system Questions that need to be covered in interviews
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Sampling Notes Determine Sample Size how certain you want and need to be. Sample Size = 0.25 x (Certainty factor/Acceptable error)
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/22/2010 for the course ISOM 313 taught by Professor Mee during the Fall '10 term at Suffolk.

Page1 / 24

chap006 (1) - Introduction to Requirements Discovery...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online