Joins

Joins: A join object creates a relationship between a business component and table other than its base table.
This relationship allows the business component to use columns from other table.
A join is always 1:1 relationship and it is always between a business component and a table.
Joins are two types.
1. Implicit joins
2. Explicit joins
Implicit joins:
Implicit joins exist as part of the Siebel object architecture. They are not explicitly defined using Siebel tools.
Unlike joins that you define in Siebel tools user can update the columns from implicit joins.
Implicit joins exist for the following
1. All 1:1 (_X) extension tables and all relevant intersection tables.
2. Extension tables of S_PARTY, such as S_ORG_EXT, S_CONTACT, S_POSTN and S_USER.
Explicit joins:
We are explicitly defined using Siebel tools.
When creating a joined field in a BC, you can change the type property from the default DTYPE_TEXT to a more appropriate type. DTYPE_TEXT refers to the data as a string of length 2000 or less
The Type property of a Field object type definition corresponds to the physical type of the column in the underlying table.
For example, if you are joining a table column that contains phone numbers, you can change the type field to DTYPE_PHONE.
Set the “outer join flag” to “TRUE”, if you want to retrieve all the records in the business component even when the joined fields are empty.
 “Join specification” object definition identifies the foreign key field in the business component & the primary key column in the joined table.
 The “Source field property” identifies the foreign key column in the joined table.
 In rare circumstances, there can be multiple join specifications in a single join.
For example, the sub campaign BC has a join to the S_LANG table with two join specifications.
 A “Join constraint” is a constant-valued search specification applied to a column during a join. It is for use with outer join.
 “Foreign key column” represents in the base table, pointing to rows in a particular table used in joins.
 “Join table” provides the columns to the BC through the join. It is a master table.
 The “Primary key column” identifies the joined table. Every standard table in standard Siebel application has a ROW_ID column that uniquely identifies rows in the table.
Mapped Column: Columns in the joined table are available for use in the fields in the BC.
 When bring in party data into a nonparty BC, create a new join with the join specification based on PAR_ROW_ID.
 When bringing in party data into a party BC, use appropriate explicit join.
 When mapping fields in party BC, use the implicit join for the extension table.
 You cannot use a pre-default value in the regular way as a default field value if nothing is specified when a record is inserted.

Types of Siebel Applications

Siebel CRM Applications are built on a common architecture & allow you to implement business processes based on the standard functionality.
Types of Siebel enterprise application:
a) Employee Applications:
b) Customer Applications:
c) Partner Applications:
1. Siebel Sales: It is used by a company’s sales reps and manager to manage accounts, sales, opportunities and contacts.
2. Siebel Call Center: It is use by a company’s telesales & service representatives.
3. Siebel eSales: It is used by customer to purchase products over the web. Includes search & product comparison mechanisms and online ordering capabilities.
4. Siebel Partner Portal: It is used by a company’s partner to communicate, collaborate & conduct business with a web based interface

Diff b/w Retesting and Regression Testing

What is difference between Retesting and Regression Testing?

Retesting: It is conformation testing after a defect is fixed, developers will send that to testers as status changed to RPSIT. Then once again we will go for “retest” that test case for confirming the original defect has been successfully removed.

Regression Testing: Testing which ensures that existing build functionality remains same even a new build is released.

In Real Time: Suppose a version 2.1 is existing and a new requirement comes say 2.2 and this 2.2 works properly with existing 2.1 functionality.

What is CRM?

CRM Stands for “Customer Relationship Management“. CRM is a Process or Methodology used to learn more about customers needs and behaviors in order to develop stronger relationships with them.

It will help together lots of Pieces of information about Customer, Sales, Marketing effectiveness, and responsiveness and Market trends.CRM is the Business Strategy that aims to Understand, Anticipate, and Manage and personalize the needs of an Organizations Current and Potential Customer.

About Siebel CRM

Siebel is a brand name of Oracle Corporation. Siebel System Inc., founded by Thomas Siebel in 1993, was principally engaged in the design, Development, Marketing and support of CRM applications. On September 12, 2005 Oracle Corporation had agreed to buy Siebel System for $5.8 billion.

Major Releases:
Oracle Siebel 8.0
Oracle Siebel 7.8
Siebel 7.7
Siebel 7.5
Siebel 7.0
Siebel 6 (also known as Siebel 2000)
Siebel 99
Siebel 98

Siebel system is the worlds leading provider of “Customer Relation Management " software solutions and a leading provider of software applications for business intelligence and standard-based integration. Siebel provide CRM software solutions for any kind of organization, any type of business and any type of budget.

Priority & Severity

Priority: How important to fix the bug & it will be change according to situation.
P1- High-- No work around is possible. (Menu- New if not possible , need to fix immediately)
P2- Medium-- Before release we need to fix, work around is possible.
P3- Low-- If we have time, it will fix, otherwise it should move to deferred status.

Severity: How bad the bug is and impacts all the application. (OR) How serious the defect.
S1- Critical-- System crash (Data loss)
S2- Major-- Wrong result, loss of functionality (Like in calculator missing +, _, *, %,..)
S3- Medium-- Miss Spelled
S4- Minor

V- Model

Explain the process of V-Model?

Main theme of V-Model is Verification and Validation.
Verification represents “Are we building the product RIGHT?" i.e. Verification is a process to verify the software product or application is developed the right way.

Validation is a process of finding out if the product being built is right? i.e. whatever the software product is being developed, it should do what the user expects it to do.
All types of testing methods are basically carried out during the Validation process. Test plan, test suits and test cases are developed, which are used during the various phases of Validation process.

Requirement & Gap Analysis:

- Business analyst (BA)gathers the requirements from Client and prepares Business Requirement Document (BRD)
- User Acceptance Testers (UAT) go through the same BRD and Prepares UAT test case design/Checklist & UAT test plan document

System Design & Planning:

- SA review and go through the BRD and prepares SRS document
- System testers review and go through the SRS and prepare System test case
design & test plan documents

Architect & Module Design:

- Senior developers review and go through the SRS and prepares the HLD & LLDs
- Development team review and go through the HLD and LLDs then prepare the integration & Unit Test case design and test plan documents

Coding:
Once the Coding is done same programming team would validate the developed system code by performing the Unit, Integration testing based Unit & Integration test case design and plan.

System Testing: Testers validate the developed system by executing the design test cases against the application as per test plan
UAT testing: After System testing, UAT testers validate the developed application based UAT test case design & test plan.

V-Model Advantages:

1. An important aspect of this model is that testing activities like planning, test designing
happens well before coding
2. Its more flexible compare to Waterfall model

V-Model disadvantages:

1. It needs lot of resources and money.
2. it needs an established process to implement
3. It can be implemented by only some big companies