0% found this document useful (0 votes)
10 views

Intro To SE

The document defines software engineering terms in an alphabetized glossary. It includes over 50 terms commonly used in software engineering and provides a brief definition and video reference for each term. The glossary covers topics like programming languages, software design patterns, testing methods, and more.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views

Intro To SE

The document defines software engineering terms in an alphabetized glossary. It includes over 50 terms commonly used in software engineering and provides a brief definition and video reference for each term. The glossary covers topics like programming languages, software design patterns, testing methods, and more.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

8/23/23, 12:06 PM about:blank

Software Engineering Glossary


Welcome! This alphabetized glossary contains many of the terms you’ll find within this course. This
comprehensive glossary also includes additional industry-recognized terms not used in course videos. These
terms are important for you to recognize when working in the industry, participating in user groups,
and participating in other certificate programs.

Video where the


Term Definition term is
introduced
Week 4:
2-tier is a computing model in which the server hosts, delivers,
Architectural
2-tier and manages most of the resources and services delivered to the
Patterns in
client.
Software
The 3-tier pattern organizes applications into three logical and
Week 4:
physical computing tiers: the presentation tier, or user interface,
Architectural
3-tier the middle tier which is usually the application tier where
Patterns in
business logic is processed, and the data tier, where the data is
Software
stored and managed.
Agile is an iterative method of software development. Teams
work in cycles, or sprints and unit testing happens in each sprint. Week 1: Software
Agile At the end of each sprint, a chunk of working code is released at Development
a meeting where stakeholders can see the new functionality and Methodologies
provide feedback.
The alpha release is the first functioning version of the system Week 1: Building
Alpha release
released to a select group of stakeholders. Quality Software
Week 4:
The API Gateway routes the API from the client to a service. Architectural
API gateway
Orchestration handles communication between services. Patterns in
Software
Week 4:
Application
An application environment is the combination of the hardware Application
deployment
and software resources required to run an application. Deployment
environment
Environments
Week 2: The
Application
importance of
Programming An API is code that allows two programs to communicate.
backend
Interface (API)
development
Week 3:
In an array, a fixed number of elements of the same type are Introduction to
Array
stored in sequential order, starting from index zero. Programming
Concepts Part 1
Week 3: Query
Assembly language is a low-level programming language that and Assembly
Assembly language
uses a set of symbols to represent machine code. Programming
Languages
Week 4: Object-
Attributes An object’s properties and data are its attributes. oriented Analysis
and Design
about:blank 1/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
Week 2:
Backend developers deal with everything that happens on the Overview of Web
Backend developers
server before the code and data are sent to the client. and Cloud
Development
Behavioral models describe what a system does, without Week 4: Software
Behavioral models explaining how it does it. The overall behavior of a system can Design and
be communicated through behavioral models. Modeling
The beta release, also called a limited release, is given to the Week 1: Building
Beta release
stakeholders outside of the developing organization. Quality Software
Black box testing is a method of testing where the tester does Week 1: Software
Black-box testing
not look at source code or internal structure. Testing
Week 3:
Branching and
A Boolean expression is a type of programming statement with
Boolean expression Looping
only two values, either “true” or “false.”
Programming
Logic
Week 3:
Branching logic is where a computer program makes a decision Branching and
Branching following a different set of instructions, depending on whether Looping
certain conditions are met during the program’s execution. Programming
Logic
Week 2: More
Build automation Build automation servers execute build automation utilities on a Application
servers scheduled or triggered basis. Development
Tools
Week 2: More
Build automation Build automation utilities generate build artifacts like Application
utilities executables, by compiling and linking source code. Development
Tools
Week 4:
An application’s business logic dictates things like transaction Production
Business logic
results and what data is written to and retrieved from a database. Deployment
Components
Developers use CSS to create stylish websites. CSS provides
front-end developers with a standard method to define, apply, Week 2: Learning
Cascading Stylesheets
and manage different sets of style characteristics for a website Front-end
(CSS)
and each of its components. CSS ensures uniformity in look and development
feel, style, colors, fonts, designs and layouts.
The CTO oversees all of the research and development in a
Week 5: Career
Chief Technology company. They monitor the company’s systems and
Paths in Software
Officer (CTO) infrastructure to ensure that they meet company needs and
Engineering
budget.
Week 4: Object-
A class is the generic version of an object. The class contains the
Class oriented Analysis
object’s generic attributes – its properties and methods.
and Design
Class diagrams are commonly used to communicate a software Week 4: Object-
Class diagram system’s structure in OOAD. The class diagram shows how the oriented Analysis
classes in an object-oriented design relate to one another. and Design
Client-Server Another term for 2-tier. Week 4:
Architectural

about:blank 2/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
Patterns in
Software
Compiled languages use a compiler program creates a program Week 3:
file, which runs the software. The compiler takes the source code Interpreted and
Compiled language and converts it from the programming language to machine Compiled
code. Then it is compiled into one executable file. Finally, the Programming
program runs when you select the icon or file on your device. Languages
Week 4:
A component is an individual unit of encapsulated functionality
Approaches to
Component that serves as a part of an application in conjunction with other
Application
components.
Architecture
Component-based architecture focuses on the decomposition of
the design into logical components. Component-based Week 4:
Component-based architecture provides a higher level of abstraction than object- Approaches to
architecture oriented designs. A component-based architecture should define, Application
compose, and implement loosely coupled independent Architecture
components so they work together to create an application.
Week 3:
Branching and
An “if-then” statement that allows computers to use branching
Conditional statement Looping
logic.
Programming
Logic
Week 3:
A constant is a data item whose value does not change within a Introduction to
Constant
program. Programming
Concepts Part 1
CI/CD refers to the practices of continuous integration and either
Continuous
continuous delivery or continuous deployment. CI/CD is a best
Integration /
practice for DevOps teams enabling developers to deliver Week 2: More
Continuous Delivery
frequent changes reliably. Continuous Integration (CI) ensures Application
or Continuous
that all the code components work together smoothly. Development
Integration /
Continuous delivery (CD) begins where CI ends. The CI process Tools
Continuous
automatically builds and tests your code, then CD deploys all
Deployment (CI/CD)
code changes in a build to a testing or staging environment.
Week 3: Query
Create, Insert,
CRUD is shorthand referring to the most common types of and Assembly
Update, Delete
queries: create, insert, update, and delete. Programming
(CRUD)
Languages
Week 4:
Database
The DBMS controls a database by connecting the database to Production
Management System
users or other programs. Deployment
(DBMS)
Components
A distributed system is a system with multiple services located Week 4:
on different machines that coordinate interactions by passing Approaches to
Distributed system
messages to each other via a communication protocol such as Application
hypertext transfer protocol, also known as HTTP. Architecture
Driver/navigator is a pair programming style where one
developer is the driver, typing in the code, and the other is the Week 2: Pair
Driver/navigator
navigator, reviewing the code as it’s written and giving Programming
directions on where to go next.
Dynamic content Dynamic content is generated each time it is requested by the Week 2:
client. Overview of Web
about:blank 3/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
and Cloud
Development
Week 4:
Encapsulation consists of bundling a component’s data and
Approaches to
Encapsulation methods to hide its internal state, so it doesn’t expose its specific
Application
implementation.
Architecture
The event-driven pattern focuses on producers and consumers of
events. Producers listen for and react to triggers while
Week 4:
consumers process an event. The producer publishes the event to
Architectural
Event-driven an event router. The router determines which consumer to push
Patterns in
the event to. The triggering event generates a message, called an
Software
event notification, to the consumer which is listening for the
event.
Week 4:
Extensibility entails the ability to add behavior to a component Approaches to
Extensibility
without changing other components. Application
Architecture
Week 4:
Firewalls prevent unauthorized access to or from a private Application
Firewall
network. Deployment
Environments
Week 2:
Frameworks provide a standard way to build and deploy
Introducing
applications. You can think of a framework as being a skeleton
Framework Application
that you can extend by adding your own code, providing a
Development
scaffold on which to build your apps.
Tools
Week 2:
Frontend developers deal with everything that happens on the Overview of Web
Frontend developers
client side. It is everything the user can see and interact with. and Cloud
Development
Week 2:
Fullstack developers have skills, knowledge, and experience in Overview of Web
Fullstack developers
both frontend and backend environments. and Cloud
Development
A function is a piece of structured, stand-alone, and reusable Week 3:
code that will perform a single specific action. Functions take in Introduction to
Function
data as an input, then process the data, and then return the result Programming
as an output. Concepts Part 2
Functional testing is a type of black box testing which is Week 1: Software
Functional testing
concerned with testing inputs and outputs. Testing
Week 1: Building
General availability A stable version of the software intended for all users.
Quality Software
Week 2:
Git is a code repository where you can track changes, split code Introducing
Git into different branches for more focused development, and then Application
merge them back into the main body of code. Development
Tools
Week 4:
A mix of both public and private clouds, working together Application
Hybrid Cloud
seamlessly, is called a hybrid cloud model. Deployment
Environments

about:blank 4/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
HTML is used to create the physical structure of a website. The Week 2: Learning
Hypertext Markup
physical structure contains elements such as text, links, Front-end
Language (HTML)
images/videos, page dividers and buttons. development
Week 1: Roles in
Information Software
Information developer is another term for technical writer.
developer Engineering
Projects
A subclass inherits the same properties and methods as its parent Week 4: Object-
Inheritance class but also may add its own additional properties and oriented Analysis
methods. and Design
IDEs make it easier to build and manage code. Good IDEs
Week 2:
Integrated support multiple languages and integrate with management and
Overview of Web
Development storage tools like Git and GitHub. Other useful IDE features
and Cloud
Environment (IDE) include custom extensions and themes for supporting your
Development
working style and environment.
Integration testing is a testing stage that occurs after unit testing, Week 1: Building
Integration testing
when the components are integrated into a larger product. Quality Software
Interpreted languages are commonly referred to as scripted or
scripting languages. Programs written in interpreted or scripted Week 3:
language, like Python and HTML, run through the programming Interpreted and
Interpreted language interpreter on your computer’s operating system or in your web Compiled
browser. The interpreter takes the human-readable scripted code Programming
and then translates it into machine code, enabling the computer Languages
to complete the requested task.
JavaScript is an object-oriented programming language that is Week 2: Learning
JavaScript used in conjunction with HTML and CSS to add interactivity to Front-end
a website. development
Week 2: Learning
Learner Stylesheets
LESS enhances CSS, adding more styles and functions. Front-end
(LESS)
development
Week 2:
Introducing
Libraries are collections of code, like standard programs and
Library Application
subroutines, that you can use within your code.
Development
Tools
Week 4:
Load refers to the number of concurrent users, the number of
Application
Load transactions, and the amount of data transferred back and forth
Deployment
between the clients and servers.
Environments
Load balancers distribute network traffic efficiently amongst
multiple servers on a network. Load balancers are used to Week 4:
prevent server traffic overload and are located between clients Production
Load balancer
and the servers. A load balancer determines which servers are Deployment
capable of fulfilling those requirements in a manner that Components
maximizes availability and responsiveness.
Week 3:
Branching and
A loop is a sequence of instructions that continually repeats until
Loop Looping
reaching a specific condition.
Programming
Logic
Method Another term for function. Week 3:
Introduction to
about:blank 5/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
Programming
Concepts Part 2
Week 4:
Microservices are an approach to building an application that Architectural
Microservices
breaks its functionality into modular components called services. Patterns in
Software
The MVP is a basic feature set software release given to
Week 1: Software
Minimal Viable stakeholders so they can provide feedback on the basic feature
Development
Product (MVP) set. The MVP contains a feature set to validate assumptions
Methodologies
about the software.
Week 4:
A node is any device on a network that can recognize, process, Approaches to
Node
and transmit data to other nodes on the network. Application
Architecture
Non-functional testing tests an application for attributes like
performance, security, scalability, and availability. Non- Week 1: Software
Non-functional testing
functional testing checks to see if the SUTs non-functional Testing
behavior is performing properly.
Object-oriented OOAD is is an approach for analyzing and  Week 4: Object-
Analysis and Design designing a software system when the system will use object- oriented Analysis
(OOAD) and Design
oriented programming languages to develop it.
A programming methodology that is focused on objects rather
than functions, which is what procedure-oriented programming
is focused on. The objects themselves will contain data in the
Week 3:
form of properties (or attributes) and code in the form of
Object-Oriented Introduction to
procedures (or methods). The key distinction between the two
Programming (OOP) Programming
methodologies is that where procedural programming uses
Concepts Part
methods to operate on separate data structures, OOP packages
them both together, so an object operates on its own data
structure.
Week 2: The
Object-Relational importance of
Tools used to connect the database and retrieve the correct data.
Mapping (ORM) backend
development
Week 4:
For on-premises software deployments, an organization is
On-premises Application
responsible for the system, hardware, related infrastructure, and
deployment Deployment
maintenance required to run the application.
Environments
Week 1: Roles in
Software
Ops engineer Ops engineer is another term for site reliability engineer.
Engineering
Projects
Week 2: More
Package managers take care of the tasks of finding, installing,
Application
Package manager maintaining, or uninstalling software packages at the user’s
Development
request.
Tools
Packages are archive files that contain the app files, instructions
Week 2: More
for installation, and any metadata that you choose. They have
Application
Packages their own metadata, including the package description, package
Development
version, and any dependencies, like other packages that need to
Tools
be installed beforehand.
about:blank 6/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
Pair programming is an extension of teamwork where two Week 2: Pair
Pair programming
developers work side-by-side at one computer. Programming
Week 3:
Introduction to
Parameter The data that is passed into a function.
Programming
Concepts Part 2
Week 4:
The peer-to-peer architecture consists of a decentralized network
Architectural
Peer-to-peer (P2P) of nodes that are both clients and servers. The workload is
Patterns in
partitioned among these nodes.
Software
Ping-pong is a pair programming style that incorporates test-
driven development. For each task, one developer writes a
Week 2: Pair
Ping-pong failing test and then the second developer writes code to pass
Programming
that test. The two developers work together at the end of each
task refactoring the successful code to refine and improve it.
A principal engineer is responsible for the architecture and
Week 5: Career
design of a software solution, as well as the development of it.
Principal Engineer Paths in Software
They are expected to create processes and procedures for your
Engineering
team and provide technical direction.
With a private cloud, the cloud infrastructure is provisioned for Week 4:
exclusive use by a single organization. The software system can Application
Private Cloud
be run on-premises, or the infrastructure could be owned, Deployment
managed, and operated by a service provider. Environments
Week 3:
Introduction to
Procedure Another term for function.
Programming
Concepts Part 2
Week 1: Roles in
Product manager is similar to a product owner. The term product
Software
Product manager manager is typically used in a waterfall or waterfall-like
Engineering
software development project.
Projects
The product owner has the vision of what the product should
look like. They have an intimate understanding of the client’s Week 1: Roles in
requirements, and the end-user’s needs. They are responsible for Software
Product owner
leading development efforts to create the software and for Engineering
ensuring the product provides the value stakeholders are looking Projects
for.
Week 4:
The production environment is comprised of the infrastructure
Production Introduction to
that runs and delivers the application to the end-user such as the
environment Software
servers, load balancers, and databases.
Architecture
The production environment includes the entire solution stack Week 4:
Production consisting of both hardware and software on which the Application
environment application runs as additional infrastructure components. The Deployment
production environment is intended for all users. Environments
A project manager makes sure a project runs smoothly and
Week 1: Roles in
facilitates communication about the project. The project
Software
Project manager manager often deals with big picture issues such as planning,
Engineering
scheduling, and budgeting, allocating personnel and resources,
Projects
executing the software plan, and team communication.
A prototype is a small-scale replica of the end product used to Week 1: Phases
Prototype
get stakeholder feedback and establish requirements. of the SDLC
about:blank 7/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
A proxy server is an intermediate server that sits in between two
Week 4:
tiers and handles requests between those tiers. A proxy server
Production
Proxy server can serve multiple purposes such as load balancing, system
Deployment
optimization, caching, acting as a firewall, obscuring the source
Components
of the request, encryption, scanning for malware, and more.
Week 3:
Understanding
Pseudocode provides a beneficial bridge to the project code
Pseudocode Code
because it closely follows the logic that the code will.
Organization
Methods
Week 4:
The public cloud is when you leverage the software’s supporting
Application
Public Cloud infrastructure over the open internet on hardware owned by the
Deployment
cloud provider.
Environments
QA engineers are in-charge of ensuring the quality of the
Week 1: Roles in
product and that the software solution meets customer
Software
QA engineer requirements. They are responsible for writing and executing test
Engineering
cases to identify bugs or deficiencies and provide this feedback
Projects
to the development teams.
Week 3: Query
A query uses predefined and understandable instructions to and Assembly
Query
make a request to a database. Programming
Languages
Week 1: Software
Prototype A prototype is used to test basic design ideas.
Testing
Regression testing, also called maintenance testing, confirms
Week 1: Software
Regression testing that a recent change to the application, such as a bug fix, does
Testing
not adversely affect already existing functionality.
Week 2: Learning
Responsive design of a website means that it will automatically
Responsive design Front-end
resize to the device it is being accessed from.
development
Week 4:
Scalability is the application’s ability to dynamically handle the
Application
Scalability load as it or shrinks without it affecting the application’s
Deployment
performance.
Environments
Week 3: Query
and Assembly
Scripting language Another term for an interpreted language.
Programming
Languages
Week 1: Roles in
The scrum master is focused on ensuring team and individual Software
Scrum master
success. Engineering
Projects
Week 4:
A service is like a component, also a unit of functionality, but it
Approaches to
Service is designed to be deployed independently and reused by multiple
Application
systems. A service focuses on a solution to a business need.
Architecture
Service-oriented In a service-oriented architecture, or SOA, services are loosely Week 4:
architecture (SOA) coupled and interface with each other via a communication Approaches to
protocol over a network. SOA supports building distributed Application
Architecture

about:blank 8/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
systems that deliver services to other applications through the
communication protocol.
A site reliability engineer, sometimes called an SRE or ops
engineer, bridges development and operation by combining Week 1: Roles in
Site reliability software engineering expertise with IT systems management. Software
engineer They track incidents and facilitate meetings to discuss them; Engineering
They also automate systems, procedures, and processes; assist Projects
with trouble shooting; and ensure reliability for the customer.
Week 5: Skills
Soft skills are personal characteristics and interpersonal skills.
Required for
Soft skills They’re the non-technical skills are harder to define, quantify, or
Software
certify than hard skills.
Engineering
Software architecture serves as a blueprint for the software
system that the programmers use to develop the interacting
Week 4:
components of the software. The architecture comprises the
Introduction to
Software architecture fundamental structures of a software system and explains the
Software
behavior of that system. The architecture defines how
Architecture
components should interact with each other, the operating
environment, and the principles used to design the software.
The SDD is a collection of technical specifications that indicate
Week 4:
how the design should be implemented. It provides a functional
Software design Introduction to
description of the software and design considerations such as
document (SDD) Software
assumptions, dependencies, constraints, requirements,
Architecture
objectives, and methodologies.
The SDLC is a systematic process to develop high-quality
Software Week 1:
software in a predictable timeframe and budget. The goal of the
Development Introduction to
SDLC is to produce software that meets a client’s business
Lifecycle (SDLC) the SDLC
requirements.
Software
A document that combines and lists stakeholders’ requirements Week 1: Phases
Requirement
for an application. of the SDLC
Specification (SRS)
A software stack is a combination of technologies that includes
software and programming languages. The set of individual
technologies is stacked in a hierarchy and works together to
support the execution of an application. The higher levels in the
stack provide tasks or services for the user and the lower levels Week 2:
Software stack interact with the computer hardware. Software stacks typically Introduction to
include Frontend technologies such as programming languages, Software Stacks
frameworks, and user interface tools. And backend technologies
such as programming languages, frameworks, web servers, app
servers, operating systems, messaging applications, and
databases.
A squad is a small team of up to 10 developers. It is likely to
consist of: A squad leader who acts as the anchor developer and Week 2:
Squad coach for the squad. And a few software engineers who develop Teamwork and
and implement the product features and test cases. It may also Squads
include one or two user experience developers or designers.
Week 4:
The staging environment is the environment that is as close to
Application
Staging environment replicating the production environment as possible but is not
Deployment
meant for general users.
Environments

about:blank 9/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
The stakeholder is mainly responsible for defining project Week 1: Roles in
requirements and providing feedback if team members need Software
Stakeholder
clarification on requirements or if a proposed solution cannot be Engineering
solved as planned. Projects
The SOP is written documentation that explains step-by-step
Standard Operating Week 1: Software
how to accomplish a common, yet complex task that is
Procedure (SOP) Documentation
organization specific.
Week 2:
Overview of Web
Static content Static content is content stored on a server.
and Cloud
Development
Strong style is a pair programming style junior software
engineers to learn from more experienced ones. So, the more Week 2: Pair
Strong style
experienced of the pair is the navigator and the driver learns Programming
from witnessing their implementation and thought processes.
Structured design conceptualizes a software problem into well-
Week 4: Software
organized smaller solution elements called modules and sub-
Structured design Design and
modules. Structured design stresses organization in order to
Modeling
achieve a solution.
Week 3: Query
Structured Query and Assembly
The most popular language used to query databases.
Language (SQL) Programming
Languages
Syntactically SASS enables you to use things like variables, nested rules, and Week 2: Learning
Awesome Stylesheets inline imports to keep things organized. SASS allows you to Front-end
(SASS) create style sheets faster and more easily than CSS. development
The system architect, designs and describes the architecture of a
Week 1: Roles in
project as well as communicates that architecture to team
Software
System architect members. They are responsible for designing the essential
Engineering
characteristics of the inner structure and technical aspects of the
Projects
software.
The SysRS contains system capabilities, interfaces, and user
characteristics in addition to what the SRS contains. It may
include policy requirements, regulation requirements, personnel
System Requirement Week 1:
requirements, performance requirements, security requirements,
Specification (SysRS) Requirements
and system acceptance criteria. It also outlines expectations of
the hardware needed for the system in addition to software
requirements.
System testing is a testing stage that occurs when the application Week 1: Building
System testing
is deemed completed. Quality Software
System Under Test Week 1: Software
The SUT is the software application when it is being tested.
(SUT) Testing
Week 5: Career
Technical Architect Another term for a principal engineer. Paths in Software
Engineering
Technical leads manage a team of developers and engineers
Week 5: Career
developing the software in an organization. They are responsible
Technical lead Paths in Software
for the entire development lifecycle and report to the project
Engineering
stakeholders.
Technical writer The technical writer writes documentation for the end-user. Week 1: Roles in
Software

about:blank 10/11
8/23/23, 12:06 PM about:blank

Video where the


Term Definition term is
introduced
Engineering
Projects
Test cases are written to verify the functionality of a software
application and ensure requirements have been satisfied. A test Week 1: Software
Test case
case contains steps, inputs, data, and the expected corresponding Testing
outputs.
UML diagrams are diagrams that communicate structure and Week 4:
Unified Modeling
behavior using common programming language agnostic Introduction to
Language (UML)
notation. UML diagrams will also be discussed in more detail in Software
diagrams
another video. Architecture
Unit testing is often done by the developer and tests the smallest
Week 1: Building
Unit testing component of code that can be isolated from the rest of the
Quality Software
system.
A use case is a description of how a user may interact with the
software system. A use case tends to be more granular than a Week 1:
Use cases
user story and describes how the system acts rather than the goal Requirements
of the user’s action.
User Acceptance UAT is a testing stage where the software is tested by the Week 1: Building
Testing (UAT) intended user. Quality Software
Week 1: Roles in
The UX designer balances making software intuitive but also as
User experience (UX) Software
robust as it needs to be to address requirements. They define
designer Engineering
how the software behaves from the user’s perspective.
Projects
User Requirement The URS describes the business needs and expectations of the Week 1:
Specification (URS) end-users of the software system. Requirements
A user story is an explanation of a software requirement written
Week 1:
User stories from the perspective of the end-user or customer. A user story is
Requirements
stated in terms of the goal of the user’s actions.
Variables have assigned values that are passed into a function or Week 3:
subroutine within a more extensive program. A variable has a Introduction to
Variable
value that can change, depending on conditions or information Programming
passed to the program. Concepts Part 1
Week 3:
Similar to arrays but vectors have a dynamic size, and they will
Introduction to
Vector automatically resize themselves as you add elements to them or
Programming
remove elements from them.
Concepts Part 1
The V-shape model is a method of software development that
Week 1: Software
contains “validation” phases and “verification” phases. The V-
V-shape model Development
shape model is like waterfall in that it is also sequential. Each
Methodologies
phase in verification corresponds with a validation phase.
Waterfall is a sequential method of software development where Week 1: Software
Waterfall the output of one phase is the input for the next phase of the Development
cycle. Methodologies

about:blank 11/11

You might also like