Software Engineering Concepts

<p>Difficulty in understanding the overall system design. (B)</p> Signup and view all the answers

<p>A tiny input change in a digital system can drastically alter the output. (D)</p> Signup and view all the answers

<p>It can make it difficult to track changes and maintain code consistency. (C)</p> Signup and view all the answers

<p>The focus is on learning and experimentation, not on producing marketable products. (A)</p> Signup and view all the answers

<p>Software is typically developed for real-world customer needs. (C)</p> Signup and view all the answers

<p>Adaptive maintenance (A)</p> Signup and view all the answers

<p>To make the code more understandable and easier to modify in the future. (A)</p> Signup and view all the answers

<p>Preventive maintenance (D)</p> Signup and view all the answers

<p>Changing the software's architecture and high-level interfaces. (D)</p> Signup and view all the answers

<p>Degradation of code structure and understandability (B)</p> Signup and view all the answers

<p>To detect bugs, errors, and failures. (B)</p> Signup and view all the answers

<p>Deployment planning. (D)</p> Signup and view all the answers

<p>The concept that repeatedly running the same tests will eventually stop finding new bugs. (A)</p> Signup and view all the answers

<p>A failure is noticeable to users, while an error might not be. (C)</p> Signup and view all the answers

<p>The point at which the system starts being used by the customer. (A)</p> Signup and view all the answers

<p>Tailoring the software to the customer's specific needs. (D)</p> Signup and view all the answers

<p>To ensure that new changes or fixes don't introduce other defects. (B)</p> Signup and view all the answers

<p>The stakeholders requirements. (A)</p> Signup and view all the answers

<p>Type of operating system used (B)</p> Signup and view all the answers

<p>To provide an understanding of the business problem and identify IT system requirements (B)</p> Signup and view all the answers

<p>The expected number of concurrent users (C)</p> Signup and view all the answers

<p>Marketing strategies (B)</p> Signup and view all the answers

<p>The budget for the project (B)</p> Signup and view all the answers

<p>Future users (D)</p> Signup and view all the answers

<p>Failure-free operation for a specified period (D)</p> Signup and view all the answers

<p>Comprehending and identifying business problems and goals (B)</p> Signup and view all the answers

<p>Quantitative data such as number of employees and main business processes (C)</p> Signup and view all the answers

<p>Protecting the system from unauthorized access (A)</p> Signup and view all the answers

<p>The existing skills of the users (B)</p> Signup and view all the answers

<p>Direct fund transfers via Internet banking (D)</p> Signup and view all the answers

<p>The core process of capturing and managing system requirements (D)</p> Signup and view all the answers

<p>The ability to function on multiple devices and platforms (D)</p> Signup and view all the answers

<p>Expressing requirements in a verifiable and measurable way (D)</p> Signup and view all the answers

<p>Laws and regulations (D)</p> Signup and view all the answers

<p>The system should allow easy expansion of functionality. (A)</p> Signup and view all the answers

<p>The decomposition of the system into layers and subsystems (A)</p> Signup and view all the answers

<p>Potential market trends (D)</p> Signup and view all the answers

<p>User interface testing (B)</p> Signup and view all the answers

<p>Division of responsibilities within the organization (B)</p> Signup and view all the answers

<p>Single Responsibility Principle (C)</p> Signup and view all the answers

<p>To capture and manage system requirements (B)</p> Signup and view all the answers

<p>Adherence to the customer's technology policy for the data layer (B)</p> Signup and view all the answers

<p>To understand potential sources of requirements for the system. (B)</p> Signup and view all the answers

<p>To outline a preliminary understanding of the business problem and the system's scope. (B)</p> Signup and view all the answers

<p>Domain knowledge and regulations (A)</p> Signup and view all the answers

<p>The user's prior experience with similar IT systems (C)</p> Signup and view all the answers

<p>Current market trends in the organization's industry. (C)</p> Signup and view all the answers

<p>The degree of interaction and shared functions between systems (A)</p> Signup and view all the answers

<p>A party interested in the system with a justifiable right to influence it. (C)</p> Signup and view all the answers

<p>Performance requirement (A)</p> Signup and view all the answers

<p>Because the system should reduce time spent at the counters and allow standard operations via internet. (A)</p> Signup and view all the answers

<p>The system should operate without failure for 99.99% of the time (D)</p> Signup and view all the answers

<p>To identify the future users and collaborating systems. (A)</p> Signup and view all the answers

<p>The system's developers. (A)</p> Signup and view all the answers

<p>The system’s protection against malicious attacks (D)</p> Signup and view all the answers

<p>To identify and describe the requirements for the planned IT system. (D)</p> Signup and view all the answers

<p>Portability (B)</p> Signup and view all the answers

<p>Flexibility (B)</p> Signup and view all the answers

<p>Corrective maintenance (B)</p> Signup and view all the answers

<p>Refactoring modifies the internal code structure without changing behavior, while restructuring involves higher-level architectural changes. (B)</p> Signup and view all the answers

<p>Refactoring (C)</p> Signup and view all the answers

<p>Increased code complexity (A)</p> Signup and view all the answers

<p>To address potential problems before they actually appear. (D)</p> Signup and view all the answers

<p>Academic projects are usually individual focused on technologies, while industrial projects focus on business applications with real customers. (C)</p> Signup and view all the answers

<p>Software is considered an immaterial product and does not wear out over time rather its vulnerabilities come from design faults or environment issues, physical products erode. (B)</p> Signup and view all the answers

<p>A minor input change can sometimes lead to very unpredictable and large shifts in output, unlike analog systems. (C)</p> Signup and view all the answers

<p>Software projects face challenges due to a digital base and the many interdependencies not easy to see, unlike in construction where the physical materials are much more obvious. (A)</p> Signup and view all the answers

<p>It can lead to unwanted changes, errors, or a decrease in the software's final quality. (D)</p> Signup and view all the answers

<p>Because software has many possible execution paths making it difficult to test each one thoroughly, especially when handling complex interdependencies. (A)</p> Signup and view all the answers

<p>Because the main focus is on academic questions and once these are solved, there is no further requirements for the software. (B)</p> Signup and view all the answers

<p>The complex interdependencies could lead to defects and issues that emerge after the initial development. (D)</p> Signup and view all the answers

<p>A module where all elements are related to the same task. (C)</p> Signup and view all the answers

<p>The program's inability to perform a function as users expect. (B)</p> Signup and view all the answers

<p>Customization (A)</p> Signup and view all the answers

<p>Modules independent of each other and able to be reused. (B)</p> Signup and view all the answers

<p>To ensure that previously fixed bugs do not reappear after changes. (C)</p> Signup and view all the answers

<p>A program state or behavior that deviates from the expected, but may not be immediately visible. (D)</p> Signup and view all the answers

<p>Transferring existing data into the new system (C)</p> Signup and view all the answers

<p>To test particular classes, methods or functions. (C)</p> Signup and view all the answers

<p>To capture, represent, and manage system requirements. (D)</p> Signup and view all the answers

<p>System design describes the system's modules and their interactions, while class design details module operations. (D)</p> Signup and view all the answers

<p>The software must be compatible with a specific operating system. (A)</p> Signup and view all the answers

<p>To separate the system's functions from their implementation on hardware. (C)</p> Signup and view all the answers

<p>Discovering and understanding the needs and constraints from stakeholders. (B)</p> Signup and view all the answers

<p>The user must be able to export data to a csv file. (C)</p> Signup and view all the answers

<p>It is verifiable, measurable, and doesn't dictate a specific design. (D)</p> Signup and view all the answers

<p>BA focuses on high-level business needs, while SA centers on system requirements. (B)</p> Signup and view all the answers

The process of using knowledge and principles to design, build, and analyze objects.

Software is a product that exists only in the digital world. It's not physical, so you can't touch it. To see it, you need to have at least part of it implemented.

The creation of multiple copies of software is easy and doesn't take much effort. Every software product is unique and different.

Software, unlike physical objects, doesn't wear out physically. But it can have errors or bugs due to design flaws or incompatibility with the environment it runs in.

Software can be very complex, far more than a building. It's challenging to test every single path and ensure it's completely bug-free.

Software design isn't limited by physical laws. Designers have freedom to structure the system, but bad structure can make future changes difficult.

Different parts of software often depend on each other, even in hidden ways. This can lead to problems during development, errors, and maintenance difficulties.

Software responds to input in a digital way. A tiny change in input can lead to a very different output, unlike analog systems where changes are gradual.

A process that analyzes a business problem, including the customer organization, their processes, goals, and strategies to identify requirements for a new IT system.

A document defining the business problem and scope of an IT system, laying out the initial vision for the project.

A party interested in the IT system development, having a justifiable right to influence it. They act as a potential source of system requirements.

The description of a customer's organization in a vision document includes precise data, business profile, key processes, relationships with other organizations, organizational structure, and responsibilities.

A stakeholder viewpoint describes their expectations and the role they envision the IT system playing in fulfilling those expectations.

Requirements that specify how the IT system should operate, outlining the system's functions and capabilities.

Requirements that specify the non-functional aspects of the IT system, such as performance, usability, security, and reliability.

Limitations or constraints that affect the development of the IT system, such as budget, time, and legal regulations.

The range of tasks the system is designed to perform. This includes the services it provides to users.

The expected quality of the services the system offers. This includes aspects like performance, reliability, and security.

Limitations imposed on the system's development. These can include deadlines, budget constraints, required technologies, and documentation requirements.

The number of users the system can handle simultaneously, the amount of data it processes, and how quickly it responds to user requests. It also considers how these factors might change over time.

The assurance that the system will operate error-free for a specified period or number of uses. It defines the system's expected level of reliability.

The availability of the system to users. This includes the desired uptime (how long it's operational) and acceptable downtime (how long it can be inactive). It also considers specific hours or days when uptime is more critical.

The protection of the system from unauthorized access or data breaches. The level of security needed depends on the sensitivity of the system's data.

The degree to which the system is secure from causing harm to people or property. It evaluates potential risks associated with the system's operation.

Changes made to fix defects in an existing software system.

Modifications that add new features, improve functionality, or optimize performance.

Changes made to adapt software to new environments or technologies.

Changes made to prevent potential problems from occurring in software.

A process of restructuring or reorganizing existing code without changing its behavior, making it easier to understand and maintain.

Describes the system in terms of its building modules (layers, subsystems) and their terms of cooperation.

Describes the internal operations and dependencies within particular modules.

The separation of the system into layers and subsystems based on their function.

Assigns logical modules to specific physical computers or devices.

How different parts of the system communicate with each other.

Reusable solutions to common design problems.

Principles and practices that promote good design and code.

Metrics used to evaluate the quality and effectiveness of design.

A measure of how well different parts of a software system work together.

A measure of how independent different parts of a software system are.

A bug or flaw in a program that prevents it from working correctly.

The inability of a program to execute a function as expected, making it noticeable to users.

An error or deviation in program behavior that might not be immediately visible to users.

The process of delivering a completed IT system to the customer and making it available for use.

The ongoing process of making changes to a deployed IT system after it's delivered.

The process of customizing a generic software product to meet the specific needs of a customer.

Software is an intangible product that can only be understood through its implementation. Before complete implementation, it exists only in representations like specifications, designs, and algorithms, each offering limited insight.

Software production is about creating a unique and different product, not simply manufacturing copies. Creating another copy is easy and doesn't require much effort.

Unlike physical objects, software doesn't wear out due to physical factors like corrosion. However, it can fail due to design flaws or conflicts with the environment it runs in.

Software's complexity can be vast, often surpassing that of a physical building. Thoroughly testing all possible paths and eliminating all defects is a major challenge.

Software design is not restricted by physical laws. Designers have the freedom to structure the system, but poor design choices can hinder future modifications.

Software components often rely on each other, even in ways that aren't immediately obvious. These interdependencies can lead to development issues, defects, and maintenance problems.

Unlike analog systems where small input changes lead to gradual output changes, a small input variation in software can trigger a completely different output. This digital behavior needs to be carefully considered during development.

Software's ease of modification is a valuable feature. However, it can also lead to unintended changes, errors, or an overall decrease in product quality.

A specific expectation or viewpoint expressed by a stakeholder about how the IT system should benefit them.

Any party that interacts with the system, including users, other systems, and external regulations.

The process of capturing, analyzing, specifying, validating, and managing requirements for a system.

The design concept describing the system's building blocks (layers, subsystems) and how they interact.

Describes the internal workings and dependencies within specific modules of the system.

The specific individuals who will interact with the system and the characteristics of each individual user.

The details of how the system interacts with other existing IT systems, including the extent of the interaction, functions exchanged, data formats, and technical methods employed.

A mistake or error in a program that prevents it from working correctly. It's like a typo in a recipe that ruins a dish