1/34
Vocabulary flashcards covering software engineering fundamentals, professional ethics, product attributes, case study architectures, and software process models from Chapters 1 and 2.
Software
Computer programs and associated documentation that may be developed for a particular customer or for a general market.
Software engineering
An engineering discipline that is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use.
Generic products
Stand-alone systems that are marketed and sold to any customer who wishes to buy them, where the developer owns the specification and decides on software changes.
Customized products
Software commissioned by a specific customer to meet their own needs, where the customer owns the specification and makes decisions on required software changes.
Software engineering cost distribution
The characteristic cost profile of software engineering where roughly 60% of software costs are development costs and 40% are testing costs, with evolution costs often exceeding development costs for custom software.
Maintainability
An essential software attribute requiring that software is written in such a way that it can evolve to meet the changing needs of customers within a changing business environment.
Dependability and security
An essential software attribute encompassing reliability, security, and safety, ensuring the software does not cause physical or economic damage during failure and protects against malicious access.
Efficiency
An essential software attribute requiring that software does not make wasteful use of system resources such as memory and processor cycles, including responsiveness, processing time, and memory utilisation.
Acceptability
An essential software attribute requiring that software must be understandable, usable, and compatible with other systems used by the target users.
Heterogeneity
The challenge of developing software systems required to operate as distributed systems across networks that include different types of computer and mobile devices.
Embedded control systems
Software control systems that control and manage hardware devices, representing numerically more systems than any other software application type.
Computer misuse
The unethical employment of technical software skills to compromise or misuse other people's computers, ranging from trivial actions like game playing on an employer's machine to serious dissemination of viruses.
ACM/IEEE Code of Ethics
A standard of ethical practice produced by US professional societies containing eight principles: Public, Client and Employer, Product, Judgment, Management, Profession, Colleagues, and Self.

Insulin pump hardware architecture
The hardware configuration of an embedded safety-critical medical system, consisting of a needle assembly, insulin reservoir, pump, sensor, controller, clock, alarm, displays, and power supply.

Insulin pump activity model
The processing sequence of an embedded medical pump that analyzes blood sensor readings, computes the required insulin dose based on rate of change, logs the dose, and transmits pump commands to control delivery.

MHC-PMS (Mental Health Care-Patient Management System)
A medical information system that maintains patient clinical histories, supports disconnected clinic PC operation, and generates management and safety warning reports.

Wilderness weather station system
A distributed data collection environment comprising weather station nodes that measure atmospheric conditions, a central data management and archiving system, and a satellite maintenance system.
Software process
A structured set of activities required to develop a software system, fundamentally consisting of specification, design and implementation, validation, and evolution.
Plan-driven processes
Software processes where all development activities are planned in advance and project progress is measured against this predetermined plan.
Agile processes
Software development processes where planning is iterative and incremental, designed to easily adapt the development path to changing customer requirements.

The waterfall model
A plan-driven process model with separate, sequential phases: requirements analysis and definition, system and software design, implementation and unit testing, integration and system testing, and operation and maintenance.

Incremental development
A software development approach where the activities of specification, development, and validation are interleaved and executed concurrently to deliver successive software versions.

Reuse-oriented software engineering
A process model based on integrating existing components or commercial off-the-shelf (COTS) systems through component analysis, requirements modification, system design with reuse, and development/integration.

Software specification
The requirements engineering process of establishing required services and constraints, comprising a feasibility study, requirements elicitation and analysis, requirements specification, and requirements validation.

Software design
The process of converting a software specification into an executable system structure, involving architectural design, interface design, component design, and database design.
Verification and validation (V & V)
The process intended to show that a system conforms to its specification and meets the requirements of the customer, primarily executed through software testing.

Testing stages
The three-stage validation sequence in software engineering comprising component testing (independent module tests), system testing (testing of emergent properties), and acceptance testing (testing with customer data).

Software evolution
The ongoing lifecycle process of modifying an existing software system to reflect changes in customer needs and the external business environment.
Change avoidance
A change management strategy where process activities anticipate possible changes before rework is required, such as creating early prototypes for customer review.
Change tolerance
A change management strategy where the process is structured to absorb changes at low cost, usually by delaying modifications to unbuilt increments or isolating changes to a single increment.
Throw-away prototype
A prototype system built to explore requirements or test user interfaces that is discarded after evaluation because it lacks documentation, has a degraded architecture, and omits quality standards.

Incremental delivery
A software delivery strategy where functionality is partitioned into prioritized increments that are deployed into operational use by end-users to gather realistic feedback.

Boehm's spiral model
A risk-driven process framework represented as a spiral where each loop is an iterative phase divided into four sectors: objective setting, risk assessment and reduction, development and validation, and planning.

Rational Unified Process (RUP) phases
The dynamic perspective of RUP structured across four chronological phases: Inception (business case), Elaboration (architecture and problem domain), Construction (development), and Transition (deployment).
RUP static workflows
The set of core process activities in RUP comprising business modelling, requirements, analysis and design, implementation, testing, deployment, configuration and change management, project management, and environment.