SI - Kvíz 3.

The statement is true because it states that we use the terminology of the client when specifying requirements. This means that when documenting the requirements for a project, we use the language and terminology that the client is familiar with and prefers. This helps to ensure clear communication and understanding between the development team and the client, as well as aligning the requirements with the client's expectations and needs.

The given requirement is considered to be too general and cannot be evaluated properly. It lacks specificity and clarity, making it difficult to determine its exact meaning and requirements.

not-available-via-ai

We should avoid expressing multiple requirements in one requirement because it can lead to confusion and ambiguity. Similarly, using synonyms can also create confusion as different words may have different meanings or interpretations. Additionally, using long sentences with irrelevant information can make the requirements difficult to understand and may lead to misinterpretation.

Mimofunkčné požiadavky sú často kritické pre vývoj softvéru, pretože sa zaoberajú aspektami mimo samotnej funkcionality programu. Tieto požiadavky môžu zahŕňať bezpečnosť, výkon, škálovateľnosť, použiteľnosť a ďalšie faktory, ktoré majú vplyv na celkovú kvalitu softvéru. Zabezpečenie týchto mimofunkčných požiadaviek je dôležité pre zabezpečenie správneho fungovania a spokojnosti používateľov.

not-available-via-ai

The most common form of requirement specification is using natural language. This means that requirements are written in a way that can be easily understood by humans, without the need for any specific technical knowledge or skills. This form of specification allows for clear communication between stakeholders and developers, as it is accessible to everyone involved in the project. It also allows for flexibility and adaptability, as requirements can be easily modified or updated as needed. Overall, using natural language for requirement specification is a widely accepted and effective approach in software development.

The correct answer is Biznis, Používateľské, Systémové. This order suggests that the most general type of requirements is Biznis (business) requirements, followed by Používateľské (user) requirements, and finally Systémové (system) requirements, which are the most detailed and specific. This order reflects the logical progression of understanding and defining requirements, starting with the overall business objectives, then considering the needs and expectations of the users, and finally specifying the technical details and constraints of the system.

Biznis požiadavky sú hlavné požiadavky, ktoré odpovedajú na otázku "Prečo potrebujeme nový systém". Tieto požiadavky sa zameriavajú na potreby a ciele podniku a určujú, aké problémy alebo príležitosti by mal nový systém riešiť. Používateľské požiadavky sa zameriavajú na potreby a očakávania používateľov systému. Systémové požiadavky sa zameriavajú na technické a výkonnostné požiadavky systému. Doménové požiadavky sa zameriavajú na špecifické požiadavky a pravidlá v určitej oblasti alebo odvetví.

The disadvantages of using natural language in requirement specification include the difficulty in automating processes and the challenge of describing complex concepts or algorithms.

The most precise and detailed form of requirement specification is the "Špecifikácia rozhraní" (Interface specification). This form specifically focuses on defining the interfaces between different components or systems, detailing the inputs, outputs, and behaviors expected from each interface. It provides a clear and specific description of how different parts of a system should interact and communicate with each other. Pseudocode, use cases, and forms may provide some level of detail, but they do not specifically address the interface aspect of requirements.

The requirements are divided into user and system level descriptions. User-level requirements focus on the needs and expectations of the end-users or stakeholders, while system-level requirements deal with the technical aspects and constraints of the system.

By limiting the requirements, it becomes clear to both developers and customers what belongs and what does not belong in the system. This clarity helps in avoiding conflicts during the delivery of the solution.

The purpose of the requirements specification is to determine the terminology for communication between developers and clients, as well as to define what the software system should do.

The statement is false because the goal of a specification is not to determine how the proposed system should work. Instead, a specification outlines the requirements and functionality of the system without delving into the specifics of its operation. It provides a clear description of what the system should achieve and the constraints it must adhere to, leaving the actual implementation details to be determined later.

The advantage of using forms for specifying requirements is that it provides a consistent structure for the requirements, making maintenance easier. Additionally, using forms helps to limit ambiguity as it requires all items to be entered.

System requirements can be specified using natural language, UML diagrams, and pseudocode. These three methods provide different ways to describe and communicate the requirements of a system. Natural language allows for a more descriptive and narrative approach, UML diagrams provide a visual representation of the system's structure and behavior, and pseudocode offers a more structured and algorithmic representation. By using a combination of these methods, system requirements can be effectively communicated to stakeholders and developers.

The correct answer is the order in which the requirements are divided based on their level of description is User requirements, Business requirements, and System requirements. User requirements are the needs and expectations of the end-users of the system. Business requirements are the objectives and goals of the organization that the system is being developed for. System requirements are the technical specifications and constraints that the system must adhere to.

The advantages of natural language requirements specification include the clarity of description and ease of understanding, as well as the simplicity of creating them. This means that using natural language allows for clear and easily comprehensible requirements, while also making the process of creating them simpler and more straightforward.

The correct answer is "Mal by byť jednoducho štrúkturovaný, Obmedzuje implementáciu, Popisuje externé správanie sa systému." This is because these characteristics are important in a requirements specification. A requirements specification should be easily understandable and organized, which is why it should be simple and well-structured. It should also limit the implementation options, providing clear guidelines for the development process. Additionally, it should describe the external behavior of the system, outlining how it should interact with its environment.