HCOMP Praha, s.r.o. /   / Pojmosloví / UML / B
B

B

Bag

Within the OCL, a Bag is a Collection of elements, each of which may appear more than once.

A Bag results from navigation through more than one association whose multiplicities are greater than 1.
 

baseline

A baseline is a release of artifacts, which have been reviewed and approved by the appropriate stakeholders, that together form an agreed-on basis for further evolution or development of the system.

A baseline can be changed only via a formal procedure, such as a change request.
 

behavior

A behavior is a description of the sequence of state changes that an instance of a behaviored classifier, via a behavioral feature, may undergo in the course of its lifetime.

An activity is a form of behavior.
 

behavioral feature

A behavioral feature is the specification that a classifier will respond to a designated request for a particular behavior by invoking a method that implements that behavior.
 

behavioral thing

A behavioral thing represents a dynamic behavior through space and over time.

The UML defines two primary kinds of behavioral things: interactions and state machines.
 

behavioral view

The term behavioral view refers to a view of a given model that focuses on the behavior of the instances within the system being modeled.


behavior diagram

A behavior diagram is a diagram that shows aspects of the behavior of the system being modeled.

The UML defines four types of behavior diagrams:

activity diagram
interaction diagram
state machine diagram
use case diagram


behaviored classifier

A behaviored classifier is a classifier that owns behaviors. One of these may specify the behavior of the classifier itself.
 

behavior port

A behavior port is a port that passes invocation requests for one or more behavioral features to the instance of the owning classifier itself, rather than to any instances that this classifier may contain.
 

Beta Test Product

Within the RUP, Beta Test Product is an activity within the Deployment discipline.

This activity involves the end user installing the delivered software and providing feedback on its performance and usability.


binary association

A binary association is an association with exactly two association ends.
 

bind

The term bind is a stereotype attached to a dependency to signify a binding.

When bind is present, there must also be a list of actual parameters that match up with the given template's formal parameters.
 

binding

A binding is a dependency within which the source instantiates the target template to produce a new model element that uses the specified actual parameters.
 

body expression

A body expression is an OCL expression that specifies the name, parameters, and return type of a query.

A body expression is specified with the use of the word body.
 

Boolean

The term Boolean refers to an enumeration that contains two values: True and False.
 

Boolean constant expression

A Boolean constant expression is a constant expression that refers to an enumeration literal.
 

Boolean expression

The term Boolean expression refers to an expression that resolves to a Boolean value.
 

boundary class

The term boundary class refers to a stereotype applied to a class to signify that the class, represented in the analysis model, defines one or more boundary objects with which an actor associated with one or more use cases interacts.
 

boundary object

The term boundary object refers to an instance of a boundary class.
 

bound element

A bound element is a model element that results from a binding.
 

branch

A branch is a place within an activity diagram where a trigger leads to more than one possible outcome, each of which has an associated guard or the keyword else.

broadcast signal action

A broadcast signal action is an invocation action that transmits an instance of a given signal to all of the potential target objects in the system.
 

build

In the context of the Unified Process, a build is an executable version of part of a system or an entire system.

Within the RUP, builds are part of the Implementation artifact set.

buildComponent

The term buildComponent refers to a stereotype on a set of components that signifies that the components have been grouped for organizational or system-level development purposes.
 

business actor

Within the RUP, the term business actor refers to a coherent set of roles that an entity (human or non-human) outside of the business being modeled plays when interacting with one or more business use cases.
 

business analysis model

Within the Unified Process, the term business analysis model is a stereotype attached to a model to signify that the model shows how the use cases within the business use case model are "performed" in terms of interacting roles, business entities, and work units.

The following comprise the business analysis model:

business entities
business events
business rules
business systems
business use case realizations
business workers

A business analysis model is generally represented by interaction diagrams and activity diagrams.

Within the RUP, the business analysis model is part of the Business Modeling artifact set.
 

business architecture document

Within the RUP, a business architecture document is an artifact that provides a comprehensive overview of the architecturally significant aspects of the business being modeled.

The business architecture document is part of the Business Modeling artifact set.
 

business case

Within the Unified Process, the term business case refers to an artifact that presents the case for going forward with a given project.

Within the RUP, the business case is part of the Project Management artifact set.
 

business designer

Within the RUP, a business designer is a person playing the role of specifying the business workers and business entities needed to realize one or more business use cases and distributing the behavior of those use cases to those workers and entities.
 

business entity

Within the Unified Process, a business entity is something that one or more people use in some fashion in the context of a use case within a business use case model.

A business entity is also an artifact. Within the RUP, business rules are part of the business analysis model.


business glossary

Within the RUP, a business glossary is an artifact that provides definitions of important terms used in the business being modeled.

The business glossary is part of the Business Modeling artifact set.
 

Business Modeling artifact set

Within the RUP, the Business Modeling artifact set is the set of artifacts related to the business model associated with a system..

The Business Modeling artifact set contains the following artifacts:

business analysis model
business architecture document
business glossary
business rules
business use case model
business vision document
supplementary business specification
target-organization assessment


Business Modeling discipline

Within the RUP, the purpose of the Business Modeling discipline is to build a business use case model and a business analysis model in order to achieve the following goals:
 
Understand the structure and dynamics of the organization in which the system is to be deployed.
Understand current problems in the target organization and identify potential improvements.
Ensure that the stakeholders have a common understanding of the target organization.
Discover the requirements that the new system must satisfy for the target organization.

The following activities comprise the Business Modeling discipline:
 

Assess Business Status
Describe Current Business
Design Business Process Realizations
Develop a Domain Model
Explore Process Automation
Identify Business Processes
Refine Business Process Definitions
Refine Roles and Responsibilities


business reviewer

Within the RUP, a business reviewer is a person who plays the role of participating in formal reviews of the business use case model and the business analysis model.
 

business process analyst

Within the RUP, a business process analyst is a person who plays the role of leading and coordinating the effort to build the business use case model and the business analysis model.
 

business rules

Within the RUP, business rules are declarations of policies or conditions that must be satisfied.

Business rules are part of the Business Modeling artifact set.
 

business system

Within the RUP, a business system is a grouping of business roles and business entities.

Business systems are part of the business analysis model.


business use case model

Within the Unified Process, the term business use case model is a stereotype attached to a model of the intended functions of a given business, stated in terms of actors (in this case, roles external to the business) and use cases (which represent processes here).

The following comprise the business use case model:

business actors
business goals
business use cases

A business use case model is generally represented by use case diagrams.

Within the RUP, the business use case model is part of the Business Modeling artifact set.
 

business use case realization

Within the RUP, a business use case realization is a description of how a particular business use case is realized within the business analysis model, in terms of collaborating business workers and business entities.

Business use case realizations are part of the business analysis model.


business vision

Within the RUP, a business vision is an artifact that defines the objectives and business goals of the business modeling effort.

The business vision document is part of the Business Modeling artifact set.
 

business worker

Within the RUP, the term business worker refers to an abstraction of a human who manipulates business entities while participating in business use case realizations.

Business workers are part of the business analysis model.



partnerská oblast
jméno
heslo
« back
nahoru