Untitled

• Error correction costs are highest for errors uncovered during usage and maintenance, costing 100-1000x more.
• Errors found during the definition stage have a cost of 1x.
• Errors found during construction cost 10-100x to correct.
• According to "Chaos Reports," about 31% of IT projects are fully successful.
• About 50% of IT projects are challenged, and 19% fail.
• Requirements analysis typically does not involve selecting stakeholders' representatives.
• A reliability requirement expresses that a system must be failure-free for a specified duration.
• An assumption of the waterfall model is that going back to previous stages is prohibited.
• The moment of system acceptance by the customer is called delivery.
• The V software lifecycle model is not based on the idea of iterative development.
• Integration testing is a phase of the V lifecycle model.
• Unit tests should first be performed in development according to the V-model.
• Requirements implementation is not a main area of Requirements Engineering.
• The "L" in SOLID principles stands for Liskov substitution principle.
• The "I" from SOLID principles means it is better to use many small interfaces than one complex interface
• The "D" from SOLID principles stands for Dependency inversion; high-level modules should not depend on low-level modules. Both should depend on abstractions.
• A defect represents a wrong instruction or data definition in the software source code.
• An error is a state or behavior of the program deviating from expectations/
• An incorrect instruction in the program code is called a defect.
• The valid causal relationship is Defect → Error → Failure.
• Refactoring is NOT an activity belonging to the deployment area.

Requirements Engineering

• Requirements validation confirms requirements by the stakeholders.
• A portability requirement specifies the hardware and/or software platforms a system must operate on.
• Non-functional requirements specifying the devices, platforms, and browsers the system must operate on are portability.
• A flexibility requirement identifies the most probable directions of a system's further extensions/modifications.
• The SMART approach is dedicated to defining system goals.
• A design pattern is NOT a method of synchronizing access to shared global resources.
• The Business Logic layer depends on none other layer.
• Changes made due to environment changes are called adaptive maintenance.
• Adoption of SOLID principles belongs to the architecture design (system design, high-level design).
• Functional is NOT a category of design patterns.
• Changes made due to user requests are called perfective maintenance.
• "The system shall be developed using Spring Framework" is a non-functional (quality) requirement.
• The downtime (unavailability) of the system shall not exceed 0.5% is a non-functional requirement.
• Interviews can be used to elicit virtually all kinds of requirements.
• The business Logic layer provides its services to the Presentation layer.
• Cryptography belongs to both Software Engineering (SE) and Computer Science (CS).
• Attributes are on the lowest level of hierarchical models of software quality.
• Changes made due to defects are called corrective maintenance.
• A traceability matrix is used for analyzing dependencies between requirements.
• Ease of introducing changes is not a characteristics of the software.
• Optimizing class structure is not a scope for system project.
• The ATAM method is used for evaluating possible system architectures.
• Analytical patterns is NOT a category of requirements.
• Observations is one of the techniques used in the area of requirements validation.
• A system stakeholder CANNOT be inanimate.
• Presentation, Business Logic, Services, Data is the correct order of system layers.
• Selecting stakeholders' representatives is NOT within Requirements analysis.
• Requirements implementation is NOT a main area of Requirements Engineering.
• A design pattern is NOT a method of synchronizing access to shared global resources.
• The business Logic layer depends on none other layer.
• Changes due to environmental changes are adaptive maintenance.
• Refactoring is NOT an activity belonging to the deployment area.
• A reliability requirement expresses that the system must be failure-free for a specified period.
• Adoption of SOLID principles belongs to architecture design.
• It's better to use many small interfaces than one complex interface.
• The proportion of fully successful IT projects in recent years is About 1/3
• Requirements validation is dedicated to confirming requirements by stakeholders.
• A functional category is NOT a category of design patterns.
• Changes resulting from user requests are perfective maintenance.
• "The system shall be developed using Spring Framework" is a non-functional requirement.
• Integration testing is a phase of the V lifecycle model.
• Design pattern is NOT a method of synchronizing access to shared global resources.
• The Hawthorne effect is deliberately altered behavior of people who know they are being observed.
• Deployment diagrams helps create the design of a company's network.
• Interviews elicits practically all categories of requirements.
• Highest cost of correction should be expected for errors detected during usage and maintenance.
• Detachment of the development process is one of the weaknesses addressed by the V-model .
• Portability requirement indicates the most probable directions for further system expansions/modifications.
• Prototyping is a model of an iterative development cycle.
• Feasibility study is NOT a requirement elicitation technique.
• The Incremental model utilizes dedicated functionalities.
• Large projects is NOT a characteristic that has to be true for every plan-driven methodology?
• Introducing changes to the IT system after its deployment is dedicated to software maintenance.
• Freedom over centralized management is NOT among the four expressed in the Agile Manifesto.
• Analytical patterns is NOT a category of requirements.
• Analysis and design are the main causes of project failures?
• Cowboy coding is NOT agile.
• Deployment is not considered acceptance by the client.
• Requirements implementation is NOT a main area of requirements engineering.
• MOSCOW is one of the techniques in the area of validation.
• No other layer provides business logic to?
• Optimizing class structure belongs to design is high-level design.
• Cost increases over time.
• Boundaries belong to class design.
• Integration testing is the following phases in a phase of the V-model lifecycle?
• Data and the expected users is A requirement is performance requirement.
• Focused on design, not production is NOT technologies/
• Both CS and SE is the field that machine learning belongs to?
• Harm environment is a quality requirement and is safety.
• Yes is a non-functional requirement.
• Workshops require moderator.
• Not an area of high level is optimization of class structure.
• Area of development its team management.
• Found defect are around ten percent.
• Reusable issues are designed pattern.
• Activities performed as system topology.
• Data layer depend on a business logic layer?
• Corporate resource management is an area.
• Functional is NOT a category.
• High-level analysis is performance by design patterns.
• Making changes its NOT specific to requirements!
• Which subarea of requirements engineering is used to confirm requirements. Validation is requirements.
• Downtime is Non-functional.
• Which action to expect? The answer is error.
• Harder too influence is that it can NOT be that non living is correct.
• More system.
• Hardware the system it performance.
• Principles in low coupling means it is iterative of the v model
• Clicktraccking is one of the techniques for requirement eliciation.
• Adpative is the answer as to why DBMS isn't?
• Presentation services?
• Stakeholders:
• Categories requirements? Configuarilibity.
• Refriactoring and design?
• Desing interface is not part of high level.
• All requirements relate to design.
• Its COMPOSITE!!!
• Flexibility is the most non-flexible requirement of non functional!
• Retro is common for all agile!
• A class responsibility.
• Extreme.
• Its not from human nature.
• 60 to 80 maintainence??
• print the invoices.
• Resource manament.
• The paterns should NOT be used in a SRS.
• 3 teir system can be put into 1 to 3 physical.
• 4 pattern of description of a design patterns structure are.