1/36
Vocabulary practice flashcards covering fundamental software engineering definitions, layered architecture, generic and iterative process models, process activities, testing stages, and professional ethics.
Software
Instructions (computer programs) that provide desired features, function, and performance when executed; data structures that enable programs to manipulate information; and documentation describing operation and use.
Generic Software Products
Stand-alone software systems developed by an organization to be sold on the open market to a wide range of different customers (such as Word or Excel).
Bespoke (Custom) Software
Software systems commissioned by and developed specifically for a single, particular customer according to their unique specification.
Software Engineering (IEEE Definition)
The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.
Software Engineering Layers
A layered technology composed of four levels: A quality focus (the foundational bedrock), Process (the framework and glue holding activities together), Methods (the technical 'how-to's for modeling and design), and Tools (automated/semi-automated support).

Process Framework Activities
The five generic engineering activities applicable to all projects: Communication, Planning, Modeling (analysis and design), Construction (code generation and testing), and Deployment.
Umbrella Activities
Activities applied across an entire software project to manage quality, change, and risk, such as project tracking, software quality assurance, configuration management, and technical reviews.
Task Sets
The specific collection of work tasks, work products, quality assurance points, and project milestones defined within an individual software engineering action.
Polya's Problem-Solving Essence
A four-step framework for engineering practice: 1) Understand the problem, 2) Plan a solution, 3) Carry out the plan, and 4) Examine the result for accuracy.
Computer Science vs. Software Engineering
Computer science concentrates on underlying theory and fundamental principles, whereas software engineering is concerned with the practicalities of developing and delivering useful, reliable software.
System Engineering vs. Software Engineering
System engineering addresses all aspects of computer-based systems development (including hardware, software, and processes), while software engineering is the component focused specifically on software infrastructure, control, applications, and databases.
Software Engineering Cost Ratio
Roughly 60% of project costs are allocated to development, while 40% are allocated to testing; for long-lifetime custom software, evolution (maintenance) costs often exceed original development costs.
Upper-CASE
Computer-Aided Software Engineering tools designed to provide automated support for early process activities, including requirements specification, elicitation, and system design.
Lower-CASE
Computer-Aided Software Engineering tools designed to support later life-cycle activities, such as programming, debugging, and software testing.
Maintainability
An essential software quality attribute stating that software must be written in a manner that allows it to evolve to satisfy changing customer requirements and environments.
Dependability
An essential software quality attribute stating that software must be trustworthy, reliable, secure, and safe, avoiding physical or economic harm in the event of failure.
Acceptability
An essential software quality attribute requiring software to be understandable, usable, and compatible with other systems so that target users can effectively accept and adopt it.
Key Challenges in Software Engineering
Three overarching challenges: Heterogeneity (building software across diverse platforms and environments), Delivery (achieving faster delivery times), and Trust (demonstrating dependability to users).
Professional Competence
An ethical standard mandating that software engineers must not misrepresent their technical skills or knowingly accept assignments that fall outside their scope of competence.
Software Process
A structured sequence of activities required to produce and evolve a software system, fundamentally consisting of specification, design, validation, and evolution.
Software Process Model
An abstract, simplified representation of a software development process presented from a particular perspective (such as workflow, data-flow, or role/action).
Waterfall Model
A plan-driven process model with distinct, sequential phases (Requirements definition, System and software design, Implementation and unit testing, Integration and system testing, and Operation and maintenance) where one phase completes before the next begins.

Evolutionary Development
A software process model in which the core activities of specification, development, and validation are interleaved and executed concurrently to deliver successive versions of a system.
Exploratory Development
An evolutionary approach that begins with well-understood requirements and collaborates with customers to iteratively evolve the final system by adding features suggested by the customer.
Throw-away Prototyping
An evolutionary approach aimed at understanding unclear requirements by developing a quick prototype that is subsequently discarded once the true system requirements are established.
Component-Based Software Engineering
A software development approach where the system is constructed by integrating pre-existing, reusable software components rather than creating code from scratch.
Incremental Delivery
An iterative approach where system requirements are prioritized, core functionality is delivered early in separate increments, and requirements for an increment are frozen once development on it begins.
Spiral Model
A risk-driven process model represented as a spiral where each loop corresponds to a phase and risks are continuously assessed, evaluated, and resolved.

Spiral Model Sectors
The four quadrant activities in each loop of the spiral: 1) Objective setting, 2) Risk assessment and reduction, 3) Development and validation, and 4) Planning the next phase.
Requirements Engineering Process
A four-stage process for establishing system services and operational constraints, consisting of: Feasibility study, Requirements elicitation and analysis, Requirements specification, and Requirements validation.

Software Design Activities
The sequential activities that convert software requirements into a structure: Architectural design, Abstract specification, Interface design, Component design, Data structure design, and Algorithm design.

Structured Methods
Systematic approaches to software design that document architectures using standardized graphical notations (such as object, sequence, state transition, structural, and data-flow models).
Debugging Process
The multi-step process of discovering and removing faults from a program: Locate error, Design error repair, Repair error, and Re-test program.

Verification and Validation (V & V)
Quality checking and review processes designed to demonstrate that a software system conforms to its technical specification and fulfills customer requirements.
Testing Stages
The three primary testing phases: Component (unit) testing (independent modules/functions), System testing (testing the entire system and emergent properties), and Acceptance testing (validation using customer data).
Software Evolution
The ongoing activity of modifying and updating existing software to accommodate changing business circumstances, computing platforms, and operational demands.
Rational Unified Process (RUP)
A modern generic software process model that decouples process activities from life-cycle phases and provides structured, iterative stages of development.