Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Overview : About Projects, Packages and Processes

About Projects, Packages and Processes
In TIBCO Business Studio there is a hierarchy consisting of project, package, and process:
Projects
TIBCO Business Studio supports the full project life cycle, bringing together all artifacts in a single place. The project is the container for these artifacts. As such, projects help to facilitate sharing and organization of resources. For example, team members may have different responsibilities but need to use the same resources that are made available through the TIBCO Business Studio project.
You must create a project to use TIBCO Business Studio. Each project has a corresponding directory in the file system (specified when you create the project). Projects can also refer to other projects (see Creating Project References).
Packages
A package is a mandatory container for processes and their infrastructure (such as participants and data fields). The package and any processes stored in it are saved in XPDL format. For example, in the insurance environment, separate packages could contain the processes used by the Claims Department, the Policy Origination/Maintenance Team and the IT Department. Processes can be shared between packages and projects so libraries of process components can be created and reused. For more information on reuse, see Using Sub-Processes and Process Interfaces.
If the Data Fields folder is empty, it will be hidden by default. This is because the preferred usage is to define Data Fields at the Process level.
Processes
There are two types of process in TIBCO Business Studio:
A business process models actual and future processes in your organization that usually involve more than one person. Business processes are short or long-lived.
A pageflow process is a short-lived process (always executed in a single sitting) designed to implement a user interface dialog. It is always executed by one person (the person that initiates the process instance).
The Process Editor provides tools on a palette that use Business Process Modeling Notation (BPMN). By creating your process this way, you can fully prepare it for implementation by a specialist in your organization.
Some objects such as business assets can be shared at the project level. Others such as data fields and participants can be created at either the package level (where they can be shared amongst processes in that package), or at the individual process level (where they can only be used by that process).
Process Interface
A process interface provides a way of allowing the dynamic selection of sub-processes at runtime. A process interface specifies the events and their parameters that must be present in processes created using that interface. At runtime, any of the processes that implement the interface may be chosen based on data available at that time. For more information, see Process Interfaces.
Asset Types
Besides business process assets, there are other types of assets that you can include in your project. When you create the project, you can decide which types of assets to include, and also designate a special folder for each asset type. For example, the default analysis project has special folders for business objects, forms, organization models, process packages, and business assets:
For more information about special folders, see Working With Special Folders.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved