Intel Flashcards

You may prefer our related Brainscape-certified flashcards:
1
Q

PME

A

Product marketing engineer — the person responsible for formulating requirements for specific
product features and customer parameters (licenses, prices, distribution channels, etc.)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

TCE

A

Technical Consulting Engineer — a member of product team, who provides technical consulting on
the product and the technologies supporting the product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Product 

A

The basic unit that Intel designs, builds, licenses and sells (e.g. Intel® Parallel Studio XE
Professional Edition).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Product group 

A

A set of products that are grouped together based on some property, for example, if they
have the same approved product name (like ‘Parallel Studio XE’) but different editions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Product owner

A

In Agile system, Product owner is a scrum development role for a person who represents
the business or user community and is responsible for working with the user group to determine what
features will be in the product release. Typically, a project’s key stakeholder. Part of the product owner
responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum
team. … The Scrum product owner’s job is to motivate the team with a clear, elevating goal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Product variation 

A

A set of attributes that defines different physical characteristics of a product: OS, host,
programming language, etc. (e.g. Intel® Parallel Studio XE 2018 Professional Edition for Fortran and C++
Windows*)
Intel Corporation Org Chart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

IAGS

A

Intel Architecture, Graphics and Software (former CVCG – Core and Visual Computing Group). A
strategic business group within the Intel organization that includes CPDP since April 2018.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

CPDP

A

Compute Performance & Developer Products - (former DPD - Developer Products Division), part
of IAGS, delivers software products to establish an influence point that helps drive value to the Intel
hardware platform through scalable ecosystem enabling of platform features, performance, and
compatibility. On April 2, 2020 a new Business Unit (BU) is formed - One Intel Software & Architecture
(OIGA – [‘oiga; o’aiga]) that consists of engineering organizations to align with the software stack and a
shared software product organization that will be responsible for the software products that we take to
market. We will also create a software architecture team, and a software business strategy team.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

MLP

A

Machine Learning Performance – a new org unit under IAGS, developing software alongside
CPDP, with a focus on machine learning. Comprises Intel Data Analytics Acceleration Library (DAAL),
OpenVINO Toolkit, and other units.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

SPS

A

Software Products Services, a member of IAGS/ISC, that enables and ensures professional, timely
and high-quality IAGS software products. A Business Unit providing installation, automation,
documentation, validation, and productization services to CPDP products. As announced on Apr 2, 2020,
will be restructured and renamed to Product Infrastructure team headed by Ivan Kuzmin.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

InfoDev

A

Embedded Computing, Debuggers and Libraries. ECDL is a department in CPDP, part of
IAGS. ECDL ensures Intel is the platform of choice for embedded and compute intensive applications
through world-class embedded development tools, debuggers, runtimes, and libraries that maximize Intel
platform differentiation and customer development productivity. As announced on Apr 2, 2020, will be
restructured and renamed to Debuggers, Libraries, & Java Engineering (DLJE) team. Part of
Developer Software Engineering team.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

IPL

A

Intel Performance Libraries. A department within ECDL developing Intel Math Kernel Library
(MKL), Intel Performance Primitives Lib (IPP), Intel Data Analytics Acceleration Library (DAAL), Intel
Autonomous Driving Library (AD Lib, ADL), Intel Threading Building Blocks (TBB).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

ICL

A

Intel Compiler Labs or, more recent, Intel Compilers and Languages. The Intel Compiler Labs
develop the Intel Compilers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

TCAR

A

The Technical Computing, Analyzers, and Runtimes team is one of the departments within
CPDP, part of IAGS. Responsible for running CPDP’s Technical & Enterprise Computing (TEC) business,
both the Enabling part as well as the Revenue part. Provides software technology & products to all DPD’s
segment businesses: TEC, Mobile & Embedded. The tools and technologies increase the demand for
Intel multi-core platforms by allowing software developers to productively create scalable parallel
applications and extract maximal performance. Among other responsibilities, TCAR designs the
discovery, performance and confidence analysis tools in Intel Parallel Studio XE, Cluster Studio XE and
the TBB, Cilk and OpenMP runtimes. Includes Intel VTune Amplifier, Intel Inspector, Intel Advisor,
and Intel Graphics Performance Analyzer (GPA) recently renamed to GDP (Graphics Development
Products) headed by Gary Baldes (Oregon). As of April 2, 2020, restructured within a new DSE org unit – see the above org charts).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

PLC

A

Product Life Cycle - The Intel Product Life Cycle is a high-level framework, which is the process
used to take a product from market research through production and eventually to product
discontinuance. See Platform and Product Life Cycles page.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

POR

A

Stands for Plan of Record. This refers to a benchmark plan, often one with proven historical
results. This may be used as a baseline for comparison or evaluating improvements in methods,
processes, technologies, etc. The existence of a plan generally means that everyone is committed and
resources have been allocated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

IPA

A

 Implementation Plan Approval. This is a meeting where the decision is made that all requirements
for the product release and launch are completed.

18
Q

PRD

A

Product Requirements Document. A collaboratively developed document that describes the
standard product feature set, business plan, and product requirements in sufficient detail to enable
product planning, design, and development.

19
Q

Launch process 

A

Preparing and performing marketing activities and delivering new products to the
customers. Launch process starts with the decision on IPA meeting and ends on FCS date.

20
Q

Release process 

A

Preparing the product package for delivery to the customers. It starts with the decision
on IPA and ends on RTM date. Pre-release activities, covered by SPS services: integration, installation
and documentation development, start earlier.

21
Q

Code Freeze 

A

All planned code modifications (including bug fixes) are implemented. Only critical bug
fixes are allowed.

22
Q

Feature Freeze/Complete 

A

All features as defined by IPA (or by last amended PRD) are integrated. No
feature-blocking bugs remain open. No new requirements, configuration or features will be allowed unless
via an emergency change request.

23
Q

IDP

A

Internal Development Package. Unlike test packages, an IDP is validated and the validation effort
for the package is tracked. This package is created to support product development efforts and will be
placed in the a or b or p directory. The goal of an IDP is to integrate the product early and find
bugs prior to the release cycle. The number of IDPs can be negotiated within the program (including PV).
The validation target is negotiated with PV. PV disposition of IDPs is Failed/Previewed IDPs are not
released to anyone outside of Intel. Often, no one outside of the product team.

24
Q

RC

A

Release Candidate - Complete software product that, per the component owners, is ready to be
shipped to customers. This package will be checked against all tests in the product validation plan. If it
passes the release criteria for this product, it is RTMd. Applied to all release types. PV performs a full
validation, or the negotiated level of validation.

25
Q

Documentation Input Freeze (DIF)

A

Final documentation inputs for the release documentation delivered
to Documentation team to process and integrate into the product documents to be released.

26
Q

Documentation Freeze (DF)

A

Or Documentation Complete - Documentation delivered to an appropriate
repository (e. g., SVN, SWF) is final documentation for release.

27
Q

SWF

A

Software Factory - SPS`s umbrella name for a tool that comprises database, website, and
notification system, which support, automate, track, and document the SPS Release Process. SWF is
being replaced with Phoenix system.

28
Q

RTM — release

A

Release to manufacture — the decision made for RC package that it should go to the customer.
Release is posted to IRC, another appropriate delivery mechanism, and/or released to manufacturing. (CDs, Post for External Web).

29
Q

FCS

A

First Customer Shipment - The milestone at which production product is first available to be
shipped. Equivalent term is launch.

30
Q

SKU 

A

Stock keeping unit. An offer to the customer with clearly defined service/product and price, — is
the unit of sales. A SKU is uniquely identified by SKU# (SKU abbreviation) which conforms to the
predefined SKU nomenclature that encodes product variation+ version+ customer parameters (SKU
nomenclature is determined by the corresponding nomenclature version). SKUnomenclature is defined
by SKU nomenclature version. SKU has a price and a full description. SKU price is calculated based
onMSRPaccording to pricing formulae. Full description is generated based on a full description template
and according to the rules of full description generation. SKU may also have corresponding IDs in other
financial systems.MM# — an ID assigned to SKU in SAP.UPC — an ID assigned to tangible (physical)
SKUs. The SKUs that depend on the version are called version-specific; those that don’t are called
version-agnostic.

31
Q

EOL 

A

Stop providing existing specific product/service in the market. Normally, it means to
withdraw SKUs from the market. Usually it triggers a specific process that is executed by the launch
operation team.

32
Q

Host OS 

A

The OS on the computer where our tools install and run: for example, our Compilers install and
run on theHost. Additional examples ofHost OSinclude Windows and Linux. Note: We always must
have aHost OSin the SKU definition.

33
Q

Target OS 

A

The OS running on the computer where the binary is executed: for example, the resulting
binary code generated by our Compilers executes on theTarget.Additional example: Android is
theTarget OS, but not theHost OS. Note: We don’t always have to have theTarget OSin the SKU
definition. Whenhostandtarget OSare the same, it is not necessary to specify the target. It is implied.

34
Q

FlexLM 

A

Software license manager from Flexera Software*.

35
Q

ISP Web Store 

A

International software partners.

36
Q

IRC 

A

A piece of bits that goes through release stages and is deployed to customers.

37
Q

PV

A

Product Validation, a centralized software validation team providing support to the SSG product
development teams.

38
Q

PXT

A

Platform eXecution Team – regular project team meeting involving all key stakeholders.

39
Q

PDL

A

Public Distribution List, alias mail-list, e.g., CVCG Info developers, PSXE_InfoDevs

40
Q

SLA

A

Service-Level Agreement – a commitment to provide a certain service to internal or external
customers.

41
Q

SDL

A

Security Development Lifecycle - Security Development Lifecycle is a set of activities and
milestones which can drive high-quality security outcomes in product and services development at Intel.
SDL is Intel’s approach to make security and privacy an integral part of our product definition, design,
development and validation. SDL integrates with the Intel corporate PLC process in order to ensure that
Intel products meet Intel Security and Privacy requirements. An overview ofSDL and DFS can be found here