Sample wbs dictionary (cath,lhey,jhoy)

Concept

A concept (abstract term: conception) is a cognitive unit of meaning—an abstract idea or a

mental symbol sometimes defined as a "unit of knowledge," built from other units which act as a
concept's characteristics. A concept is typically associated with a corresponding representation in
a language or zymology such as a single meaning of a term.

There are prevailing theories in contemporary philosophy which attempt to explain the nature of
concepts. The representational theory of mind proposes that concepts are mental representations,
while the semantic theory of concepts (originating with Frege's distinction between concept and
object) holds that they are abstract objects.[1] Ideas are taken to be concepts, although abstract
concepts do not necessarily appear to the mind as images as some ideas do.[2] Many philosophers
consider concepts to be a fundamental ontological category of being.

The meaning of "concept" is explored in mainstream information science,[3] cognitive science,

metaphysics, and philosophy of mind. The term "concept" is traced back to 1554–60 (Latin
conceptum - "something conceived"), but what is today termed "the classical theory of concepts"
is the theory of Aristotle on the definition of terms.[citation needed]

A project management plan, as defined in the PMBOK Guide Third Edition,

is a formal, approved document that defines how the project is executed,
monitored and controlled. It may be summary or detailed and may be
composed of one or more subsidiary management plans and other planning
documents. The objective of a project management plan is to define the
approach to be used by the Project team to deliver the intended project
management scope of the project.

Software engineering (SE) is a profession dedicated to designing, implementing, and modifying

software so that it is of higher quality, more affordable, maintainable, and faster to build. It is a
"systematic approach to the analysis, design, assessment, implementation, test, maintenance and
reengineering of software, that is, the application of engineering to software." [1] The term
software engineering first appeared in the 1968 NATO Software Engineering Conference, and
was meant to provoke thought regarding the perceived "software crisis" at the time.[2][3] The IEEE
Computer Society's Software Engineering Body of Knowledge defines "software engineering" as
the application of a systematic, disciplined, quantifiable approach to the development, operation,
and maintenance of software, and the study of these approaches; that is, the application of
engineering to software.[4] It is the application of Engineering to software because it integrates
significant mathematics, computer science and practices whose origins are in Engineering.[5]

Computer software, or just software, is a collection of computer programs and related data that
provide the instructions telling a computer what to do and how to do it. We can also say software
refers to one or more computer programs and data held in the storage of the computer for some
purposes. In other words software is a set of programs, procedures, algorithms and its
documentation. Program software performs the function of the program it implements, either by
directly providing instructions to the computer hardware or by serving as input to another piece
Sample wbs dictionary (cath,lhey,jhoy)

of software. The term was coined to contrast to the old term hardware (meaning physical
devices). In contrast to hardware, software is intangible, meaning it "cannot be touched".[1]
Software is also sometimes used in a more narrow sense, meaning application software only.
Sometimes the term includes data that has not traditionally been associated with computers, such
as film, tapes, and records.[2]

Hardware is a general term for the physical artifacts of a technology. It may also mean the
physical components of a computer system, in the form of computer hardware.

Hardware is a comprehensive term for all of the physical parts of a

computer, as distinguished from the data it contains or operates on, and the
software that provides instructions for the hardware to acoomplish tasks. The
boundary between hardware and software is slightly blurry - firmware is
software that is "built-in" to the hardware, but such firmware is usually the
province of computer programmers and computer engineers in any case and
not an issue that computer users need to concern themselves with.

Deliverable management

System testing of software or hardware is testing conducted on a complete, integrated system to

evaluate the system's compliance with its specified requirements. System testing falls within the
scope of black box testing, and as such, should require no knowledge of the inner design of the
code or logic. [1]

System Test™ software lets you develop and execute tests that exercise
MATLAB® algorithms and Simulink® models. It includes predefined test
elements that let you build and maintain standard test routines. You can
map test variables into a result set for analysis.

Support Services

Referring to technical or user support services often available from a manufacturer or vendor.
Methods to access support may include telephone hot-lines and/or automated voice-response
systems, Web sites, e-mail, fax, and others.

Installation

a work of art requiring construction or elaborate setting up at its exhibition site: an installation
typically makes use of a variety of media and often includes nontraditional media, as projected
images or taped sounds
Sample wbs dictionary (cath,lhey,jhoy)

II
System evaluation
A periodic evaluation of the system to assess its status in terms of original or current
expectations and to chart its future direction.

Planning in organizations and public policy is both the organizational

process of creating and maintaining a plan; and the psychological process of
thinking about the activities required to create a desired goal on some scale.
As such, it is a fundamental property of intelligent behavior. This thought
process is essential to the creation and refinement of a plan, or integration of
it with other plans, that is, it combines forecasting of developments with the
preparation of scenarios of how to react to them. An important, albeit often
ignored aspect of planning, is the relationship it holds with forecasting.
Forecasting can be described as predicting what the future will look like,
whereas planning predicts what the future should look like.

The Project Technical Plan

The project technical plan shows a detailed breakdown of the relationships
between the major activities required by the project. Subsequent sub-
project technical plans are based on it and any later amendments should be
highlighted. Prepared at the same time as the project resource plan; these
two plans together show a high level view of the projects products, activities
and resources. Once approved by the project owner the project technical
plan becomes the top level production schedule for the major products
required throughout the project.

Software design is a process of problem-solving and planning for a

software solution. After the purpose and specifications of software are
determined, software developers will design or employ designers to develop
a plan for a solution. It includes low-level component and algorithm
implementation issues as well as the architectural view.

Software build refers either to the process of converting source code files
into standalone software artifact(s) that can be run on a computer, or the
result of doing so. One of the most important steps of a software build is the
compilation process where source code files are converted into executable
code.

Unit testing is a method by which individual units of source code are tested
to determine if they are fit for use. A unit is the smallest testable part of an
Sample wbs dictionary (cath,lhey,jhoy)

application. In procedural programming a unit may be an individual function

or procedure. Unit tests are created by programmers or occasionally by
white box testers.

Hardware requirement planning

Deliverables tracking

Subsystem Tests

Subsystem tests aid in fault isolation by testing specific functions

within a subsystem to determine if they are generated correctly. In
many cases, these tests check the transmission of data between the
subsystem under test and associated subsystems. Computer pro- grams
are available that provide specific test capa- bilities suited to
subsystem testing.

Configuration management (CM) is a field of management that focuses

on establishing and maintaining consistency of a system or product's
performance and its functional and physical attributes with its requirements,
design, and operational information throughout its life.

III

Cost and scheduling management

Technical supervision is a permanent process; it begins when construction of

bridges and civil engineering structures starts and goes on throughout their
...

System requirement specification

Software Unit coding

One of the most important aspects of testing computer software is that the earliest you can find
an error or bug, then the easier and cheaper it is to fix. There is no earlier opportunity to resolve
such a problem, then directly after a developer has written the code. This sort of testing is called
Unit Testing, and although a development team may be responsible for conducting it, unit
testing is an important part of any quality assurance test plan.

Unit Test Plan

This document describes the Test Plan in other words how the tests will be carried out.
This will typically include the list of things to be Tested, Roles and Responsibilities,
 Sample wbs dictionary (cath,lhey,jhoy)

prerequisites to begin Testing, Test Environment, Assumptions, what to do after a test is

successfully carried out, what to do if test fails, Glossary and so on

Hardware system

Deliverable: Production Implementation Strategy

The implementation strategy identifies how software updates will be introduced into production
and establishes the criteria for an “emergency” fix.

System integration testing

System integration testing is process of verifying the synchronization

between two or more software systems and which can be perform after
software system collaboration completed.

Quality assurance

Quality assurance, or QA for short, is the systematic monitoring and

evaluation of the various aspects of a project, service or facility to maximize
the probability that minimum standards of quality are being attained by the
production process. QA cannot absolutely guarantee the production of
quality products.

The project scope management knowledge area is defined by the

processes that limit and control the work included in a project. These
processes ensure that all the work of the project is included. Processes in
this knowledge area include the initiation process as well as all the processes
related to the scoping of the project. Each process has a set of input and a
set of output. Each process also has a set of tools and techniques used to
convert input into output.

Business Requirements Definition

Developing strategic plans should be part of any enterprise and organization's process to achieve
any goal. Translating the strategic plans into a form suitable for implementation and
development is side stepped in many situations. helps you accomplish the definition of your
business requirements to help you refine your ideas and define them in detail to help your
developers or partners gain better understanding of your needs and problems. Helps you turn
your strategies into business requirements and into knowledge for your development team to
rapidly implement.
Sample wbs dictionary (cath,lhey,jhoy)

Software package - (computer science) written programs or procedures or rules and associated
documentation pertaining to the operation of a computer system and that are stored in read/write
memory; "the market for software is expected to expand"

Software unit debugging

Thorough debugging is a necessary step towards software quality. Bugs plague software project
big and small, and today's complicated software makes debugging more difficult than ever.

Advancements in unit testing are made, better tools are created and development teams work
proactively to scour their code. However, time pressures, poor planning and lack of knowledge
take their toll on this type of testing.

Unit test case preparation

Hardware component selection

Acceptance testing generally involves running a suite of tests on the completed system. Each
individual test, known as a case, exercises a particular operating condition of the user's
environment or feature of the system, and will result in a pass or fail, or boolean, outcome. There
is generally no degree of success or failure. The test environment is usually designed to be
identical, or as close as possible, to the anticipated user's environment, including extremes of
such. These test cases must each be accompanied by test case input data or a formal description
of the operational activities (or both) to be performed—intended to thoroughly exercise the
specific case—and a formal description of the expected results

Development tools and utilities

Task management is the process of managing a task (or task portfolio) through its life cycle,
including planning, testing, tracking and reporting. Task management can help either individuals
achieve goals, or groups of individuals collaborate and share knowledge for the accomplishment
of collective goals.[1] Tasks also differentiate by complexity, from low to high. Task management
may form part of project management and process management and can serve as the foundation
for efficient workflow in an organisation. Project managers adhering to task-oriented
management are known for having a detailed and up-to-date project schedule, and are usually
good at directing team members and moving the project forward.

System requirements are often suggested by software vendors for optimal performance of
software. Although not a necessity, this set of requirements is often sought after by power users
who expect to gain a better experience of software usability. Recommended System
Requirements do not promise best possible performance of software and are treated as more of a
guideline than a rule. Almost always a better system is available, or will be in future, to provide
better performance. Also, exceeding by far these requirements does not guarantee to the user that
everything will run with absolute smoothness and look its best. More often than not, games are a
bit disappointing in this respect, presenting issues that may or may not be corrected with future
modifications.
Sample wbs dictionary (cath,lhey,jhoy)

Software prototyping refers to the activity of creating prototypes of software applications, i.e.,
incomplete versions of the software program being developed. It is an activity that can occur in
software development and is comparable to prototyping as known from other fields, such as
mechanical engineering or manufacturing.

A prototype typically simulates only a few aspects of the final solution, and may be completely
different from the final product.

Prototyping has several benefits: The software designer and implementer can get valuable
feedback from the users early in the project. The client and the contractor can compare if the
software made matches the software specification, according to which the software program is
built. It also allows the software engineer some insight into the accuracy of initial project
estimates and whether the deadlines and milestones proposed can be successfully met.

Unit testing allows the programmer to refactor code at a later date, and make sure the module
still works correctly (e.g., in regression testing). The procedure is to write test cases for all
functions and methods so that whenever a change causes a fault, it can be quickly identified and
fixed.

Readily-available unit tests make it easy for the programmer to check whether a piece of code is
still working properly.

In continuous unit testing environments, through the inherent practice of sustained maintenance,
unit tests will continue to accurately reflect the intended use of the executable and code in the
face of any change. Depending upon established development practices and unit test coverage,
up-to-the-second accuracy can be maintained.

Hardware testing of software or hardware is testing conducted on a complete, integrated system

to evaluate the system's compliance with its specified requirements. System testing falls within
the scope of black box testing, and as such, should require no knowledge of the inner design of
the code or logic. [1]

As a rule, system testing takes, as its input, all of the "integrated" software components that have
successfully passed integration testing and also the software system itself integrated with any
applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies
between the software units that are integrated together (called assemblages) or between any of
the assemblages and the hardware. System testing is a more limited type of testing; it seeks to
detect defects both within the "inter-assemblages" and also within the system as a whole.

Defect classification

Development environment is the set of processes and programming tools used to create the
program or software product. The term may sometimes also imply the physical environment. An
integrated development environment is one in which the processes and tools are coordinated to
provide developers an orderly interface to and convenient view of the development process (or at
least the processes of writing code, testing it, and packaging it for use).
Sample wbs dictionary (cath,lhey,jhoy)

Risk management is the identification, assessment, and prioritization of risks followed by

coordinated and economical application of resources to minimize, monitor, and control the
probability and/or impact of unfortunate events[1] or to maximize the realization of opportunities.
Risks can come from uncertainty in financial markets, project failures, legal liabilities, credit
risk, accidents, natural causes and disasters as well as deliberate attacks from an adversary.
Several risk management standards have been developed including the Project Management
Institute, the National Institute of Science and Technology, actuarial societies, and ISO
standards.[2][3] Methods, definitions and goals vary widely according to whether the risk
management method is in the context of project management, security, engineering, industrial
processes, financial portfolios, actuarial assessments, or public health and safety.

System architecture or systems architecture is the conceptual model that defines the structure,
behavior, and more views of a system.

An architecture description is a formal description and representation of a system, organized in a

way that supports reasoning about the structure of the system which comprises system
components, the externally visible properties of those components, the relationships (e.g. the
behavior) between them, and provides a plan from which products can be procured, and systems
developed, that will work together to implement the overall system. The language for
architecture description is called the architecture description language (ADL).

A computer case (also known as a computer chassis, cabinet, box, tower, enclosure, housing,
system unit or simply case) is the enclosure that contains most of the components of a computer
(usually excluding the display, keyboard and mouse). A computer case is sometimes incorrectly
referred to metonymously as a CPU or hard drive referring to components housed within the
case. CPU was a more common term in the earlier days of home computers, when peripherals
other than the motherboard were usually housed in their own separate cases.

Cases are usually constructed from steel (often SECC—Steel, Electrically Chromate Coated) or
aluminum. Plastic is sometimes used, and other materials such as wood and even Lego blocks
have appeared in home-built cases.

Unit test records

Internal product

Procurement management is the process companies use to purchase economic resources and
business input from suppliers or vendors. This process helps companies negotiate prices and get
the best quality resources for production processes. Smaller businesses do not usually have a
department dedicated to procurement since they have much smaller business operations. Usually,
small business owners or entrepreneurs are responsible for working with vendors and suppliers
to obtain the necessary goods for business operations. Larger companies are able to purchase
resources and inputs in large volume quantities; high volume purchases usually require a
procurement management process.
Sample wbs dictionary (cath,lhey,jhoy)

Technical Training Team (TTT) provides assessment, overall coordination, integration, and
career progression planning and clearinghouse services to ensure technical readiness of
employees working through the Regional Technical Centers and in Technical Services. Provides
recommendations for technical training that is applicable for consultants and local agencies.

The Technical Training Team will:

1. Provide overall coordination and integration of technical training and development

offerings to support the technical excellence of staff assigned to the Tech Centers and in
Technical Services.
o Serve as a link to their sections to ensure branch-wide coordination and
collaboration on training and development.
o Work with (discipline specific) Leadership Teams to identify and prioritize the
technical training needs of employees working through the Tech Centers.
2. Identify technical training that is applicable for consultants and/or local agencies.
3. Identify and produce a technical training and development catalogue to publicize
offerings developed or sponsored by Technical Services (TS).
4. Work with their respective sections and HR to develop career progression planning tools
and to communicate their availability throughout TS and the Regions.
5. Serve as a link to Subject Matter Expert instructors so that they get the support and other
assistance they need to be successful when teaching classes.
6. As requested, provide recommendations/advice to TS Management Team and others on
training budget, priorities, and other topics related to training and development.
7. Introduce and serve as a clearinghouse for the Branch on best practices for training and
development.

Quality management can be considered to have four main components: quality planning,
quality control, quality assurance and quality improvement.[1] Quality management is focused
not only on product/service quality, but also the means to achieve it. Quality management
therefore uses quality assurance and control of processes as well as products to achieve more
consistent quality.
Sample wbs dictionary (cath,lhey,jhoy)