Developing and Deploying Siebel Business Applications > Overview of Developing a Siebel Application > About Developing a Siebel Application >

Documents You Use During the Design Stage

This topic describes documents that describe business requirements and detailed design. These documents are outputs of the design stage of developing a Siebel application. They describe the scope of the solution and document the specifications that developers require during configuration.

You can use the following design documents:

• Entity relationship diagram. Illustrates relationships between entities. Entities include object definitions, such as business components or business objects. For more information, see Figure 7.
• Business component design template. Defines the properties of business components, including user properties, joins, single-value fields, multi-value fields, and multi-value links.
• Business object design template. Groups business components and identifies links between business components, which indicates the parent and associated child records in the Siebel client. You use the business component design template and then the business object design template.
• Applet design template. A reference document you create for each applet. It documents the properties of the applet, the fields that are available on the applet, and the properties that are associated with each field. It must include a mock-up or screen shot of the applet. You create an applet design after you decide what entities you must track in your Siebel application.
• View design template. Describes what applets are part of the view definition and identifies any special visibility associated with a view. For example, a My Team's View or an All View. It must also document how the user uses drilldowns to navigate through the views, tabs, and other user interface elements.
• Screen design template. Lists the views available from each screen and indicates the default view for each screen.
• Report design template. Describes information about reports. Includes the business component, whether the report is dynamic or static, and lists any subreports that must be available.
• Workflow policy template. Describes information required to create workflow rules.
• Assignment manager template. Describes information required to create assignment rules.
• Testing strategy document. Describes project objectives and provides a structure for tracking progress. Without proper planning you might perform too much or too little testing.
• Test cases document. Describes test cases according to approved technical designs. A written test case can also serve as a blueprint to develop an automated test script.

Getting Help from Oracle

Design documentation is an important part of a development effort. If you require help from Oracle you can create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. You can also contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.