Archive for the ‘ IT ’ Category

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 ]

1- Problem Statement

developed by Client and can be represented by analysis. Ingredients of a Problem Statement A good problem statement describes    A-Current situation:   The Problem to be solved // target of system.   Description of one or more scenarios [ READ MORE ]

1st Step: System Identification

Two questions need to be answered:     We must identify the: Purpose of a system? : That determined which tools and technology I have to use. System boundary: What is inside, what is outside the system and sub system? Like: saving account in ATM will be by ATM system or Bank system.  Requirements process consists of two activities:     Requirements Elicitation: -User Language- Definition of the [ READ MORE ]