SE101 REVIEWER

Sur cette roue (26 options)

• is the process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed. ----------------------------------------- Requirements Engineering
• are statements, in a natural language plus diagrams, of what services the system is expected to provide to system users and the constraints under which it must operate.----------------------------------------- User Requirements
• Detailed description of what the system should do including the software system's functions, services, and operational constraints.----------------------------------------- System Requirements
• These are statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in particular situations. ----------------------------------------- Functional Requirements
• define system properties and constraints e.g. reliability, response time, and storage requirements. Constraints are I/O device capability, system representations, etc....... may be more critical than functional requirements. If these are not met, the system may be useless.----------------------------------------- Non-Functional Requirements
• These requirements specify or constrain the behavior of the software. Examples: include performance requirements on how fast the system must execute and how much memory it requires, reliability requirements that set out the acceptable failure rate, security requirements, and usability requirements.----------------------------------------- Product Requirements
• hese requirements are broad system requirements derived from policies and procedures in the customer’s and developer’s organization. Examples: include operational process requirements that define how the system will be used, development process requirements that specify the programming language, the development environment or process standards to be used, and environmental requirements that specify the operating environment of the system.----------------------------------------- Organizational Requirements
• his broad heading covers all requirements that are derived from factors external to the system and its development process. ----------------------------------------- External Requirements
• may be new functional or non-functional requirements, constraints on existing requirements, or define specific computations. ,,,----------------------------------------- Domain Requiremetns
• Two main problems with domain requirements: ----------------------------------------- Understandability and Implicitness
• Requirements are expressed in the language of the application domain, which is not always understood by software engineers developing the system.----------------------------------------- Understandability
• Domain specialists understand the area so well that they do not think of making the domain requirements explicit(clear). ----------------------------------------- Implicitness
• sometimes called the software requirements specification or SRS,,,, s an official statement of what the system developers should implement. ----------------------------------------- Software Requirements Document
• is the process of writing down the user and system requirements in a requirements document. ----------------------------------------- Requirements Specification
• Two main areas that are focus of requirement specification; ----------------------------------------- System Requirements and User REquirements
• sed for writing requirements because it is expressive, intuitive and universal. This means that the requirements can be understood by users and customers. ----------------------------------------- Natural Language Specification
• What are the three priblems with Natural Language ----------------------------------------- Lack of clarity, Requirements Confusion, Requirement amalgation
• Precision is difficult without making the document difficult to read ----------------------------------------- Lack of clarity
• Functional and non-functional requirements tend to be mixed up ----------------------------------------- Requirements Confusion
• Several different requirements may be expressed together.----------------------------------------- Requirements amalgation
• An approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way. ----------------------------------------- Structured Specifications
• An informal interview, also known as a conversational or informal chat interview, is a non-formal job interview, often held in a neutral setting such as a café, usually over food or drink.----------------------------------------- Informal
• designed to evaluate multiple aspects of a job candidate. It generally focuses less on personal questions and more on professional ones.----------------------------------------- Formal interview
• Give the 2 types of Interview
• Type of interview : avoid pre-conceived ideas about the requirements, and be willing to listen to stakeholders. ----------------------------------------- Be open-minded
• where various issues are explored with stakeholders. ----------------------------------------- Open Interiews