1 / 15

User Requirements Elicitation and Analysis Process for System Architecture Development

This presentation details the structured approach to user requirements elicitation and the formal analysis process essential for developing system architecture. Each phase of the analysis helps the project team identify all facets of the system that constitute requirements. The requirements documentation aids architects in crafting high and low-level designs, and any modifications trigger a formal review of the Software Requirements Specification (SRS). Stakeholder analysis emphasizes key qualities such as availability, usability, modifiability, and testability, guiding implementation views and project planning.

eden
Télécharger la présentation

User Requirements Elicitation and Analysis Process for System Architecture Development

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. SmartPosition Title of Presentation

  2. Overview

  3. Elicitation

  4. User Requirements

  5. Specifications

  6. Formal Analysis

  7. Analysis Process

  8. Each stage of the analysis process allowed the project team to identify all aspects of the system that formed a requirement • The formal listing of requirement statements are being used by the system architects to produce both high and low level designs • Any changes to the requirements will result in a formal review of the SRS Analysis Process

  9. User Acceptance Testing

  10. Description of the system architecture. (use as many slides as you think necessary) Architecture

  11. Player - User • Coach - User • Project Owner - SportQuick CEO • Project Liaison - SportQuickProject Sponsor • Development Team - Red Team • Regulatory Department - Health and Safety Stakeholder Analysis

  12. After analysing the stakeholders and non-functional requirements the following have appeared identified as the most important system qualities • Availability • Usability • Modifiability • Testability System Qualities

  13. Conceptual View

  14. Implementation View

  15. Build Plan

More Related