Developing and Deploying Siebel Business Applications > Overview of Developing a Siebel Application > About The Business Case This Book Uses >

NREC Design Strategy

This topic describes the NREC design strategy.

Design Strategy for the Data Layer

Figure 7 includes an entity relationship diagram that NREC uses to describe entities and relationships between entities.

Figure 7. NREC Entity Relationship Diagram

This diagram includes the following information:

1. Entity. A category of data.
2. Data source. Provides the source of data for each entity. Siebel CRM stores most data in tables. For example, house information resides in the S_PROD_INT table. Siebel CRM can derive data from an external source. For example, the House Renovations virtual business component derives data from an external source.
3. Relationship. Indicates the nature of the relationship between entities, such as one-to-one, one-to-many, or many-to-many.

Design Strategy for the Business Object Layer

NREC plans to use the following business objects:

• Accounts
• Activities
• Contacts
• Internal Products
• Opportunities

NREC plans to use the following business components:

• Activity
• Appraisals (new business component)
• Contacts
• Internal Product
• Opportunity
• Partner Company
• Renovations VBC (new virtual business component)

Design Strategy for the User Interface Layer

NREC plans to use several screens for the Partner Portal. Each view contains one or more applets. The Opportunities, Contacts, and Activities screens are predefined in the Partner Portal application. NREC must create a new screen for houses. The views that make up each screen are master-detail views or list-form views. The applets are list applets or form applets.

Figure 8 illustrates part of the user interface layer. NREC will also use other screens, such as Partner Management and Application Administration.

Figure 8. NREC Screens, Views, and Applets