Using Siebel Tools > Working with Projects >

About Projects

Projects are sets of objects that reside in the Siebel repository. They are used group objects based on functional areas. Every object is associated with a project. The names of projects that are delivered with a standard Siebel application indicate the functional area with which they are associated. For example, Account contains objects that pertain to the Account functional area.

A project named without a suffix, such as Account, usually contains business object layer objects that span multiple Siebel applications. Project names that have a suffix (for example, Account (SSE)) contain user interface or business objects that are specific to the Siebel application indicated by the suffix. For example, the suffix SSE in Account (SSE) indicates an entry containing Account user interface data for Oracle's Siebel Sales application. Other examples of suffixes indicating user interface data only are SSV for Oracle's Siebel Service and CC for Oracle's Siebel Call Center.

The project structure supplied with the Siebel repository is usually well suited to having several developers work on the same repository without contention for the same objects. However, when developers need access to the same set of objects simultaneously, changing the standard project structure may be necessary.

• Create an application development plan that includes a PERT chart showing dependencies and parallel activities.
• Analyze the plan to see if the project structure interferes with developers who need access to objects in the same projects at the same time. If so, break out groups of objects into separate projects to enable concurrent development. Alternatively, for projects that are expected to be in contention, enable those projects for Object Check-in/Check-out.