1 / 6

Requirements analysis

Requirements analysis. Requirements : informal description of what customer wants. Specification : precise description of what design team should deliver. Requirements phase links customers with designers.

wenger
Télécharger la présentation

Requirements analysis

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements analysis • Requirements: informal description of what customer wants. • Specification: precise description of what design team should deliver. • Requirements phase links customers with designers. • Sia i requisiti che le specifiche riguardano il comportamento esterno del sistema, non la sua struttura interna Overheads for Computers as Components

  2. Types of requirements • Functional: input/output relationships. • Non-functional: • timing; • power consumption; • manufacturing cost; • physical size; • time-to-market; • reliability. Overheads for Computers as Components

  3. Good requirements • Correct. • Non redundant. • Unambiguous. • Complete. • Verifiable: is each requirement satisfied in the final system? • Consistent: requirements do not contradict each other. Overheads for Computers as Components

  4. Good requirements, cont’d. • Modifiable: can update requirements easily. • Traceable: • know why each requirement exists; • go from source documents to requirements; • go from requirement to implementation; • back from implementation to requirement. Overheads for Computers as Components

  5. Setting requirements • Customer interviews. • Comparison with competitors. • Sales feedback. • Mock-ups, prototypes. • Next-bench syndrome (HP): design a product for someone like you. Overheads for Computers as Components

  6. Specifications • Capture functional and non-functional properties: • verify correctness of spec; • compare spec to implementation. • Many specification styles: • control-oriented vs. data-oriented; • textual vs. graphical. Overheads for Computers as Components

More Related