Resource
Certification Resource
Forum
![[Level:28]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/28.gif "Point:24150point (36%), Level:28/30"){kind=icon}
bughunterA
- accept
- To add any change set to a repository workspace, such as a change set attached to a work item.
- actual
- The project data such as costs, dates, and work that have occurred, as opposed to those that are scheduled, or planned.
- actual result
- The behavior or response that is produced or observed when a component or system is tested.
- artifact
- An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.
- artifact type
- A class of objects that is specific to a requirement definition technique. Artifact types include document, business process sketch, user interface sketch, user interface sketch part, screen flow, storyboard, use case diagram, requirement, glossary, and term.
- assign
- To appoint or designate a profile or resource to an activity that is to be completed within a specified period.
- attribute
- A defined quality and values that can be assigned to an artifact. For example, a work item artifact might have a 'priority' or 'severity' attribute.
- attribute group
- Convenience grouping of one or more attributes. For example, the attribute group "Address" might include the attributes Street, City, State, and Zip.
B
- baseline
- A permanent copy of a component in a particular repository workspace or stream. A component baseline represents a configuration of a component at a particular point in time.
- blocked
- The status of a test case that cannot be run because the preconditions for running the test case have not been met.
- business process sketch
- A diagram that illustrates a directed flow of activities that are specified by using a subset of Business Process Modeling Notation (BPMN). Two types of processes are supported: simple and business-to-business.
- business rule
- A policy, constraint, or required operation that applies to a specific set of business conditions or dependencies. An example of a business rule for a bank is that a credit check is not required when opening an account for an existing customer.
C
- change request
- A request to change some aspect of the project, project plan, activity definition, or document.
- change set
- A group of related changes to files for folders in a workspace or stream.
- CLM
- See Collaborative Lifecycle Management.
- code churn
- A report that shows the volume of changes in a project over time.
- Collaborative Lifecycle Management
- The integration of products on Jazz™ technology to connect the work of analysts with development and test teams. These integrations provide a common approach to artifact linking, dashboards, security, and user interface frameworks.
- comment
- An annotation attached to an artifact, element, or a collection of elements.
- completed change set
- A change set that can no longer be changed.
- component
- A grouping of related artifacts in a stream or repository workspace. A component can contain any number of folders and files.
- conflict
- A discrepancy among change sets in a repository workspace.
- consequence cost
- The impact on cost if a risk is not addressed.
- content store
- The database that contains the data needed to operate, such as report specifications, published models, and security rights.
- critical path
- A series of activities that determines the earliest completion of a project; the critical path changes as activities or tasks are completed ahead or behind the original schedule estimates.
D
- dashboard
- A web user interface component that provides information about the project status at a glance. Users can view project summary information or more detailed information.
- data mart
- A subset of a data warehouse that contains data that is tailored and optimized for the specific reporting needs of a department or team. A data mart can be a subset of a warehouse for an entire organization, such as data that is contained in online analytical processing (OLAP) tools.
- data model
- A common model that faciliates reporting of all types of data from multiple data sources.
- data set definition
- A Jazz model object that describes a partitioned data set (PDS) and is stored in the Rational Team Concert™ Jazz repository. If the PDS already exists, the data set definition must specify just the PDS name. If the PDS is new, the data set definition must specify both the name of the PDS, and the location where it should be stored. Every data set that a build process references must correspond to a data set definition.
- data set prefix
- An identifier that, together with the data set name (indicated in the data set definition), specifies a data set that is allocated to Rational Team Concert. A data set prefix can contain multiple segments, including a high-level qualifier (HLQ); for example, HLQ.PROD. With a prefix defined by a user, artifacts can be modified in isolation from other users.
- defect
- A project element that allows a project manager to track bugs and bug fixes.
- defect aging
- A report that helps track patterns in defects, which can be used to take corrective action for reducing both defect resolution time and number of defects.
- defect report
- A document that contains reports of flaws in a component or system that might prevent a component or system from performing as required.
- deliver
- To conduct an outgoing flow of change sets and baselines from a repository workspace to a stream or to another repository workspace.
- dependency
- A link between interrelated projects activities. Activities with these links depend on the start and finish dates of at least one other element and therefore cannot be completed without taking the other into consideration.
- document
- An item that can be stored, retrieved, and exchanged among Content Manager systems and users as a separate unit. It can be any multimedia digital object. A single document can include varied types of content, including for example, text, images, and embedded artifacts.
- duration
- A period of time during which a project element continues. It is calculated as the finish time minus the start time.
E
- effort
- The estimated hours of work required for an activity. Effort is
calculated based on the specified duration (in days) of the activity,
and the number of working hours per day specified in the project calendar.
- entry criteria
- The set of general and specific conditions that must be met before beginning a specific task, a test phase for example. Applying entry criteria can help prevent teams from starting a task, which would entail more unnecessary effort than the effort needed to meet all the entry criteria.
- execution result
- The behavior or response that is produced or observed when a component
or system is tested. This behavior and information regarding the test
run such as the weight distribution and result details are also recorded.
- exit criteria
- The general and specific conditions upon which stakeholders agree to officially complete a process. Applying exit criteria can help prevent team members from considering a task as completed when parts of the task are not finished. Exit criteria are used in reports and in planning when to stop testing.
- expected result
- The behavior of the component or system under specified conditions
that a specification or document predicts.
F
- failed
- The status of a test when the actual results do not match expected results.
- finish-to-start
- A dependency type between two project elements where the predecessor element must finish before the successor element can start.
- flow
- An arrangement between two workspaces or between a workspace and a stream that enables users to deliver and accept change sets.
- flow target
- A source or destination of incoming and outgoing change sets. In a team setting, most workspaces have flow targets. Streams have flow targets only if they are part of a stream hierarchy.
- formal review
- An evaluation of a product or project status with the objective of finding discrepancies between actual and planned results and recommending improvements. This evaluation entails following documented procedures and requirements.
I
- impact analysis
- The evaluation of a change to development documentation, test documentation, and components in order to accommodate an alteration to specified requirements.
- incoming change set
- A change set in a stream or repository workspace that flows to a user repository workspace. An incoming change set is present in a workspace flow target, but not in the workspace itself.
- iteration plan
- An artifact that shows the work items and additional unstructured information for a team or project area within a development phase.
O
- outgoing change set
- A change set in a repository workspace that flows to a stream or to another repository workspace. An outgoing change set is present in a workspace, but not in a workspace flow target.
- outgoing synchronization
- A process by which changes that users make to work items are propagated to the ClearQuest® user database.
P
- package
1. A product or component that is specifically designed for installation by IBM Installation Manager.
2. A subset of a project that is created to make metadata available to users. Different packages can be created so different user groups can create the reports they need.
- page
- In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.
- pass
- The status of a test when the actual results match the expected result.
- postcondition
- A set of environmental and state conditions that must be met after a test or test procedure is run.
- precondition
- A set of environmental and state conditions that must be met before a component or system can undergo a specific test or test procedure.
- predecessor
- An activity in a dependency relationship that logically precedes another.
- project
- A temporary endeavor or initiative created and managed to achieve an organization's objectives.
- project calendar
- A calendar selected from the base calendars and associated to a project during project creation. The project calendar is the reference for all time-based aspects of the project, including the schedule, timesheets, and resource allocation. The project calendar includes all the information of the base calendar, and it can be further customized to meet project-specific requirements, such as adding additional non-working days.
- project release plan
- An artifact that shows plan items and additional unstructured information for a team or project area and all related child team areas and iterations.
- project snapshot
- A subset of a baseline that identifies artifacts that have been approved or assigned to a milestone or other meaningful event.
R
- report
- A set of data deliberately laid out to communicate business information.
- report server
- An application server that hosts reports and report editors.
- report template
- A template that is used to create reports. Parameters in the report template are specified when the report is created or run.
- repository workspace
- A workspace that holds a developer's private copy of the source file base.
- requirement
- A condition or capability that a system must provide. This condition is either derived direction from user needs or stated in a contract, standard, specification, or other document.
- resolve
- To reconcile discrepancies among change sets in a repository workspace.
- resource
1. A person who can be assigned to work breakdown structure (WBS) elements.
2. A specific XML entity in an XML data source. A resource can be associated with an XML schema and can be used to map a data source to a relational database table to create reports.
- resource group
- A collection of XML sources from a product that share a common base Web address. The Web address determines the connection between the product data and the relational database that is used to create reports.
- resource leveling
- During plan scheduling, the process of resolving over-allocated resources by delaying tasks until the assigned resources are available to work on them.
- resume
- To reinstate a previously suspended change set to a repository workspace.
- risk
- An ongoing or upcoming concern that has a significant probability of adversely affecting the success of major milestones.
S
- sandbox
- An area on a file system where a developer can modify and test source code in isolation, before returning it to the source control component and sharing it with other developers.
- schedule constraint
- A limit to set controls on the start and finish dates on project tasks. Available constraints are as soon as possible and finish-no-later-than.
- screen flow
- A representation of a sequence of user-driven software processes that are presented as a series of graphical user interfaces.
- security testing
- An evaluation of the ability of a software product to prevent unauthorized access to programs and data.
- server friend
- A server that allows other servers to communicate with it. After cross-server communication is configured, project areas and artifacts can be linked across servers.
- snapshot
- A record of the data in the data warehouse that is used for reporting.
- source control
- A tool that is used to manage source code, documents, and other artifacts to place under version control and share with a team.
- stakeholder
- An individual or organization that is involved in or may be affected by project activities.
- start date
- A point in time associated with the start of work and usually qualified as actual, planned, estimated, and scheduled. Start date combined with duration and dependencies permits the calculation of finish date.
- storyboard
- A sequential illustration of a user scenario that consists of numbered frames on a timeline.
- stream
- An artifact that holds the master copy of a source file base.
- summary task
- A container element that comprises a series of tasks.
- suspend
- To temporarily remove a change set from a repository workspace.
- synchronization engine
- The process that synchronizes data between Rational® ClearCase® and Rational Team Concert source control.
- synchronize
- To add, subtract, or change one feature or artifact to match another.
T
- tag
- An identifer that groups related artifacts.
- task
- A scheduled project activity to which a resource can be assigned to perform work.
- team area
- A place within a project area for managing team membership, roles, assignments, and team artifacts.
- team release plan
- An artifact showing plan items and additional unstructured information for a team or project area and a development iteration and the associated child iteration plans.
- test case
- The inputs, execution conditions, and expected results that are used to evaluate an aspect of a system under test.
- test case design
- A specification of the test conditions, or coverage items, for a test item and the detailed test approach. It also identifies associated high-level test cases.
- test data
- Data that has been collected before a test run and that affects or is affected by the component or system under test.
- test environment
- A specific instance of a configuration of hardware and software established for the purpose of conducting tests under known and controlled conditions.
- test estimation
- The calculated approximation of running a test, which is informative even if input data is incomplete, uncertain, or difficult to define.
- time code
- A code that is used by resources in the timesheet module to classify reported time.
- translator
- A Jazz model object that describes a single build step in which a translator executable program is invoked with the required inputs and outputs. Inputs and outputs are the same as z/OS® data sets, so a translator must reference multiple data set definitions.
W
- WBS
- See work breakdown structure.
- work
- An assignment to tasks with estimated or planned hours.
- work breakdown structure
- A grouping of project elements, organized in a hierarchical tree structure. It defines the total scope of the project at the highest level in the tree and each descending level provides an increasingly granular definition of each element.
- work item
- An artifact representing a generalized notion of a development task, such as a task, defect report, or enhancement request.
- workspace
- In Eclipse, the collection of projects and other resources that the user is currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might reside in the same directory.
- workspace flow target
- A source or destination of incoming and outgoing change sets.
- workspace snapshot
- A record that captures the contents of a repository workspace at a particular time. A workspace snapshot consists of a collection of baselines, one for each component in the repository workspace.
Z
- zComponent
- A logical group of artifacts that share a common context; for example, all of the artifacts in a zComponent might comprise part of some application.
- zComponent project
1. An Eclipse integrated development environment (IDE) project with specific Rational Team Concert components.
2. A container into which buildable artifacts, such as COBOL programs, can be grouped.
- zFile
- An artifact that represents a PDS member on MVS. A zFile can be associated with a language definition for Ant builds or for Rational Developer for System z® integration syntax checking.
- zFolder
- A container for a group of artifacts within a zComponent Project, used to represent a partitioned data set (PDS). Each zFolder is associated with a data set definition to create the source PDS on z/OS
Service
New
Popular Documents
Popular Download
Weekly
Monthly
Yearly
Twitter
tag
Visitor