Introduction to Software Engineering Concepts

A discipline that uses computers and software technologies to solve problems. Focuses on building robust, reliable, and maintainable software solutions.

The relationship involves using the principles and concepts of computer science as a foundation for software engineering. Computer science provides the theoretical underpinnings while software engineering focuses on practical application and system design.

A mistake that is made by a human in the process of designing, coding, or testing software.

A deviation from the expected or desired behavior of a software system. It is a consequence of an error.

A problem or flaw in a software system that causes it to behave incorrectly. It can range from minor inconveniences to serious security vulnerabilities.

A view of software quality that emphasizes its ability to meet the needs and expectations of its users.

A view of software quality that focuses on the degree to which the software conforms to its specifications.

A view of software quality that considers the value that customers place on the software, often reflected in its pricing and marketability.

The quality of the product refers to the user's perception of how well the software meets their needs. This includes factors like functionality, reliability, performance, and usability.

The quality of the process evaluates how well the software development process is structured and executed. This includes aspects like efficiency, effectiveness, and adherence to standards.

The quality of the product in the context of the business environment considers how well the software aligns with the company's goals and objectives. It relates to factors like return on investment (ROI) and its impact on profitability.

McCall's quality model is a framework for evaluating software quality based on a set of attributes. These attributes include reliability, maintainability, portability, usability, and efficiency.

The Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) is a framework for assessing and improving the maturity of a software development organization based on its processes.

ISO 9000 is a set of standards for quality management systems applicable to various industries, including software development. It focuses on establishing a structured and documented quality management framework.

SPICE (Software Process Improvement and Capability dEtermination) is a framework for evaluating and improving the effectiveness of software development processes. It emphasizes the use of measurements and data to drive improvement.

Return on Investment (ROI) is a common metric for evaluating the business value of a software project. It measures the financial return generated by the software compared to its cost.

Software development practices evolved from single-processor mainframes to multiple systems that perform multi-functions.

A critical factor that has driven changes in software development is the increasing need to rapidly deliver software products to market.

The cost of computing has decreased significantly, making software development accessible to a wider range of users and organizations.

Powerful desktop computers have enabled more complex software development and have made it easier for individuals to create software.

Networking has revolutionized software collaboration, allowing developers to work together seamlessly on distributed projects.

Object-oriented technology has provided a structured approach to software development, allowing for code reuse and easier maintenance.

Graphical user interfaces have made software easier to use and more accessible to a wider audience.

The traditional waterfall model of software development has been shown to be inflexible, leading to alternative methodologies like agile development.

Describes a system by breaking it down into smaller units and defining their relationships. Techniques include modular, data-oriented, event-driven, outside-in-design, and object-oriented decomposition.

The different ways software is developed, depending on its size and complexity. For example, enterprise-wide applications require more control, while departmental apps benefit from rapid development.

Reusing already existing software components to speed up new development and reduce costs. Potential challenges include balancing generality and specificity, maintenance responsibility, and whether it's faster to build new components than search for existing ones.

Using numerical measures to describe the quality of software, such as the number of bugs found or the time it takes to complete a task.

Using existing software components from previous projects to improve productivity and reduce costs.

The company, organization, or individual who pays for the software system.

The company, organization, or individual responsible for building the software system.

The person or people who will directly use the software system.

A detailed description of the activities, objects, and relationships within a system. Also includes the origin of inputs and the destination of outputs.

Events triggered by something else. Examples include turning on a light switch or submitting a form.

Elements involved in activities. Examples include people, documents, or computers.

The boundaries between different systems, indicating where inputs come from and where outputs go.

A method for developing software that involves a series of steps, starting with requirements analysis and ending with maintenance.

Individuals responsible for working with customers to understand and document their needs.

Professionals responsible for designing the software system's architecture and overall structure.

The ability of different software tools to work together seamlessly, despite being developed on different platforms.

Ensuring that all software tools present a consistent and familiar user interface, regardless of the underlying technology.

Integrating software tools with the development process to streamline workflows and improve efficiency.

Sharing data across different software tools so they can access and use it without conflicting information.

Allowing one software tool to initiate actions in another tool, creating a connected system.

A real-time software system that monitors and controls processes, often used in critical applications.

The failure of the Ariane-5 rocket due to a software error which resulted in the conversion of a 64-bit floating-point number to a 16-bit signed integer, causing a program crash.

A diagram that shows the interactions between a system and its environment, illustrating the flow of data and control.