Archive for the ‘ SAD ’ Category

Types of Requirements Elicitation

1.B.3-Types of Requirements Elicitation Greenfield Engineering Development starts from scratch, no prior system exists, and the requirements are extracted from the end users and the client Triggered by user needs Re-engineering Re-design and/or re-implementation of an existing system using newer technology Triggered by technology Enabler. -must understand business role and logic. Interface Engineering Provide the services [ READ MORE ]

Requirements Validation

1.B.2-Requirements Validation (check if required is needed or not) Usually performed: Requirements engineering Requirements analysis System delivery.   Validation criteria:     Completeness: All possible scenarios, in which the system can be used, are described, including exceptional behavior by the user or the system. Like: bank customer gets all cash money account Will close or not. I feel with completeness according customer talk about future of [ READ MORE ]

1.B.0-Types of Requirements

Functional requirements: Describe the interactions between the system and its environment independent from implementation Nonfunctional requirements: User visible aspects of the system not directly related to functional behavior. Constraints (”Pseudo requirements”): Imposed by the client or the environment in which the system operates       Functionality: Clear Function in Model. Usability: Malty of use and easy to use (user view). Performance: Mainly we mean time. Dependability: Reliability: [ READ MORE ]