IBM: Software Engineering: C1: M1
Software Engineering -
"The application of engineering principles to software development in the
systematic, disciplined, and quantifiable approach to the development, operation, and
maintenance of software."
Software Development Life Cycle (SDLC) -
"A process for planning, creating, testing, and deploying an information system,
which includes phases such as planning, analysis, design, implementation, and maintenance."
Agile Methodology -
"A group of software development methodologies based on iterative development,
where requirements and solutions evolve through collaboration between self-organizing
cross-functional teams."
Waterfall Model -
"A linear and sequential approach to software development that has distinct phases
such as requirements, design, implementation, testing, deployment, and maintenance."
Scrum -
"An agile framework for managing knowledge work, with an emphasis on software
development, characterized by cycles or sprints, stand-up meetings, and a final review to
discuss what was done and what could be improved."
Extreme Programming (XP) -
"A software development methodology that is intended to improve software quality
and responsiveness to changing customer requirements with practices such as pair
programming, extensive code review, and unit testing."
Function Point Analysis -
"A standardized method to measure the size of a development project which aids in
the estimation of the project's scope, complexity, and resource requirements."
Software Metric -
"A measure that is used to quantify some aspect of a software system or process,
which can help in planning, managing, and improving software development."
Continuous Integration (CI) -
"A software development practice where developers regularly merge their code
changes into a central repository, after which automated builds and tests are run."
Continuous Deployment (CD) -
"A software development practice where code changes are automatically built,
tested, and deployed to production without explicit approval from a developer, ensuring that
the software can be reliably released at any time."
Unit Testing -
1|Page
, "The process of testing individual units or components of a software to validate that
each unit performs as designed."
Integration Testing -
"A phase in software testing in which individual software modules are combined
and tested as a group to identify interface defects between modules."
System Testing -
"A level of software testing where a complete, integrated system is tested to
evaluate the system's compliance with its specified requirements."
Acceptance Testing -
"A test conducted to determine if the requirements of a specification or contract are
met before the system is accepted."
DevOps -
"A set of practices that combines software development (Dev) and IT operations
(Ops) to shorten the systems development life cycle and provide continuous delivery with
high software quality."
Structured Programming -
"A programming paradigm aimed at improving the clarity, quality, and
development time of a computer program by making extensive use of subroutines, block
structures, and loops."
Object-Oriented Programming (OOP) -
"A programming paradigm based on the concept of 'objects', which can contain
data and code: data in the form of fields (often known as attributes), and code, in the form of
procedures (often known as methods)."
Functional Programming -
"A programming paradigm where programs are constructed by applying and
composing functions. It emphasizes the application of functions, in contrast to the imperative
programming paradigm, which emphasizes changes in state."
Software Prototype -
"An initial version of a software application, developed to showcase the concept,
design, features, and functionalities to users before the final product is developed."
Version Control Systems -
"Tools that help a software team manage changes to source code over time, keeping
track of every modification. If a mistake is made, developers can turn back the clock and
compare earlier versions of the code to help fix the mistake while minimizing disruption to
all team members."
Debugging -
"The process of finding and resolving defects or problems within a computer
program that prevent correct operation of computer software or a system."
Code Refactoring -
2|Page
, "The process of restructuring existing computer code—changing the factoring—
without changing its external behavior, aimed at improving nonfunctional attributes of the
software."
Software Framework -
"A platform for developing software applications. It provides a foundation on
which software developers can build programs for a specific platform."
API (Application Programming Interface) -
"A set of routines, protocols, and tools for building software applications. An API
specifies how software components should interact and APIs are used when programming
graphical user interface (GUI) components."
Model-View-Controller (MVC) -
"A software architectural pattern for implementing user interfaces. It divides a
given application into three interconnected parts in order to separate internal representations
of information from the ways that information is presented to and accepted from the user."
Software Testing -
"The process of evaluating and verifying that a software product or application
does what it is supposed to do. The purpose of testing is to identify any bugs or errors in the
software before it is launched to the public."
Load Testing -
"The process of putting demand on a system or device and measuring its response,
used to determine a system's behavior under both normal and anticipated peak load
conditions."
User Interface (UI) Design -
"The process of making interfaces in software or computerized devices with a focus
on looks or style. Designers aim to create interfaces which users find easy to use and
pleasurable."
User Experience (UX) Design -
"The process of creating products that provide meaningful and relevant experiences
to users. This involves the design of the entire process of acquiring and integrating the
product, including aspects of branding, design, usability, and function."
Software Crisis -
"A period marked by projects running over budget, behind schedule, and producing
unmanageable, buggy code, leading to the need for more formalized software development
processes."
CASE Tools -
"Software tools that provide support for the early stages of software development,
helping to alleviate the software crisis by automating the process of software design and
testing."
Software Development Process -
3|Page
Software Engineering -
"The application of engineering principles to software development in the
systematic, disciplined, and quantifiable approach to the development, operation, and
maintenance of software."
Software Development Life Cycle (SDLC) -
"A process for planning, creating, testing, and deploying an information system,
which includes phases such as planning, analysis, design, implementation, and maintenance."
Agile Methodology -
"A group of software development methodologies based on iterative development,
where requirements and solutions evolve through collaboration between self-organizing
cross-functional teams."
Waterfall Model -
"A linear and sequential approach to software development that has distinct phases
such as requirements, design, implementation, testing, deployment, and maintenance."
Scrum -
"An agile framework for managing knowledge work, with an emphasis on software
development, characterized by cycles or sprints, stand-up meetings, and a final review to
discuss what was done and what could be improved."
Extreme Programming (XP) -
"A software development methodology that is intended to improve software quality
and responsiveness to changing customer requirements with practices such as pair
programming, extensive code review, and unit testing."
Function Point Analysis -
"A standardized method to measure the size of a development project which aids in
the estimation of the project's scope, complexity, and resource requirements."
Software Metric -
"A measure that is used to quantify some aspect of a software system or process,
which can help in planning, managing, and improving software development."
Continuous Integration (CI) -
"A software development practice where developers regularly merge their code
changes into a central repository, after which automated builds and tests are run."
Continuous Deployment (CD) -
"A software development practice where code changes are automatically built,
tested, and deployed to production without explicit approval from a developer, ensuring that
the software can be reliably released at any time."
Unit Testing -
1|Page
, "The process of testing individual units or components of a software to validate that
each unit performs as designed."
Integration Testing -
"A phase in software testing in which individual software modules are combined
and tested as a group to identify interface defects between modules."
System Testing -
"A level of software testing where a complete, integrated system is tested to
evaluate the system's compliance with its specified requirements."
Acceptance Testing -
"A test conducted to determine if the requirements of a specification or contract are
met before the system is accepted."
DevOps -
"A set of practices that combines software development (Dev) and IT operations
(Ops) to shorten the systems development life cycle and provide continuous delivery with
high software quality."
Structured Programming -
"A programming paradigm aimed at improving the clarity, quality, and
development time of a computer program by making extensive use of subroutines, block
structures, and loops."
Object-Oriented Programming (OOP) -
"A programming paradigm based on the concept of 'objects', which can contain
data and code: data in the form of fields (often known as attributes), and code, in the form of
procedures (often known as methods)."
Functional Programming -
"A programming paradigm where programs are constructed by applying and
composing functions. It emphasizes the application of functions, in contrast to the imperative
programming paradigm, which emphasizes changes in state."
Software Prototype -
"An initial version of a software application, developed to showcase the concept,
design, features, and functionalities to users before the final product is developed."
Version Control Systems -
"Tools that help a software team manage changes to source code over time, keeping
track of every modification. If a mistake is made, developers can turn back the clock and
compare earlier versions of the code to help fix the mistake while minimizing disruption to
all team members."
Debugging -
"The process of finding and resolving defects or problems within a computer
program that prevent correct operation of computer software or a system."
Code Refactoring -
2|Page
, "The process of restructuring existing computer code—changing the factoring—
without changing its external behavior, aimed at improving nonfunctional attributes of the
software."
Software Framework -
"A platform for developing software applications. It provides a foundation on
which software developers can build programs for a specific platform."
API (Application Programming Interface) -
"A set of routines, protocols, and tools for building software applications. An API
specifies how software components should interact and APIs are used when programming
graphical user interface (GUI) components."
Model-View-Controller (MVC) -
"A software architectural pattern for implementing user interfaces. It divides a
given application into three interconnected parts in order to separate internal representations
of information from the ways that information is presented to and accepted from the user."
Software Testing -
"The process of evaluating and verifying that a software product or application
does what it is supposed to do. The purpose of testing is to identify any bugs or errors in the
software before it is launched to the public."
Load Testing -
"The process of putting demand on a system or device and measuring its response,
used to determine a system's behavior under both normal and anticipated peak load
conditions."
User Interface (UI) Design -
"The process of making interfaces in software or computerized devices with a focus
on looks or style. Designers aim to create interfaces which users find easy to use and
pleasurable."
User Experience (UX) Design -
"The process of creating products that provide meaningful and relevant experiences
to users. This involves the design of the entire process of acquiring and integrating the
product, including aspects of branding, design, usability, and function."
Software Crisis -
"A period marked by projects running over budget, behind schedule, and producing
unmanageable, buggy code, leading to the need for more formalized software development
processes."
CASE Tools -
"Software tools that provide support for the early stages of software development,
helping to alleviate the software crisis by automating the process of software design and
testing."
Software Development Process -
3|Page
