Software Engineering Class 9 - Software Engineering(CSC 4350\/6350 Rao Casturi Re-Cap Requirement Elicitation GSU Software Engineering CSC4350\/6350 Rao

Software Engineering Class 9 - Software Engineering(CSC...

This preview shows page 1 - 5 out of 15 pages.

Software Engineering (CSC 4350/6350) Rao Casturi
Re-Cap Requirement Elicitation 2 GSU: Software Engineering - CSC4350/6350 - Rao Casturi
Recap Requirement Elicitation Understanding the “System” Requirement Elicitation has 2 phases Requirement Specifications (Functional and Non Functional Requirements) Natural Language Focused around the communication with the client & user community Analysis Model (Dynamic, Analysis Object Model) More of formal or semi formal object models Communication between Developers and technical teams Concepts: (5) Functional (Need to have) Non-Functional (Not directly related to the System) Realism, Tractability, Verifiability Complete, Unambiguous From scratch, reengineering, just interface 3 GSU: Software Engineering - CSC4350/6350 - Rao Casturi
GSU: Software Engineering - CSC4350/6350 - Rao Casturi 4 Nonfunctional requirements : This activity describe aspects of the system that are not directly related to the functional behavior of the system. Nonfunctional requirements include a broad variety of requirements that apply to many different aspects of the system, from usability to performance. Functional requirements :- This describe the interactions between the system and its environment independent of its implementation. The environment includes the user and any other external system with which the system interacts.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture