Customer relationship management system and method having code reuse

• US 7,941,798 B2
• Filed: 08/14/2006
• Issued: 05/10/2011
• Est. Priority Date: 08/12/2005
• Status: Active Grant

• Current Assignee: Sugarcrm Incorporated
• Original Assignee: Sugarcrm Incorporated
• Inventors: Itani, Majed, Parsons, Joseph, Roberts, John, Oram, Clinton, Taylor, Jacob
• Primary Examiner(s): WANG, RONGFA PHILIP
• Application Number:
  US11/504,315
• Publication Number:
  US 20070143747A1
• Time in Patent Office: 1,730 Days
• Field of Search: 717/170
• US Class Current: 717/170
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A software-based customer relationship management system and method.

Claims

1. A system for software distribution, comprising:

a source code base repository;

a computer-based system having a build process wherein the build process detects a tag in the source code base repository wherein the tag indicates whether a particular portion of the source code base is included in two or more product versions of a software application and builds a product version of the software application so that the built product version of the software application contains the particular portion of the source code base based on the detected tags so that the portions of the source code base included in each product version of the software application is controlled by the tags.

2. The system of claim 1, wherein the build process removes the particular portion of the source code base based on the detected tag.

3. The system of claim 2, wherein the particular portion of the source code base removed further comprises lines of the source code base removed and wherein the build process, when the particular portion of the source code base is removed from a product version of the software application, inserts a number of blank lines, corresponding to the lines of the particular portion of the source code based removed from the version of the software application, into the product version of the software application to maintain the line numbering of the version of the software application.

4. The system of claim 1, wherein the source code base further comprises a piece of source code and wherein the tag further comprises a code level tag that indicates whether a particular portion of a piece of source code is included in two or more product versions of a software application.

5. The system of claim 1, wherein the source code base further comprises a source code directory and wherein the tag further comprises a directory level tag that indicates whether a particular source code directory is included in two or more product versions of a software application.

6. The system of claim 1, wherein the source code base further comprises a source code file and wherein the tag further comprises a file level tag that indicates whether a particular source code file is included in two or more product versions of a software application.

7. The system of claim 1, wherein the product versions further comprises one of an open source product version, an enterprise product version and a professional product version.

8. The system of claim 1, wherein the computer-based system further comprises a customer relationship management system having a database containing a plurality of pieces of data, one or more functional modules that perform a particular function on the pieces of data in the database, and a class object that is coupled to the one or more functional modules wherein the class object interfaces between the database and the functional modules.

9. A system for software distribution, comprising:

a source code base repository;

a computer-based system having a build process wherein the build process detects a tag in the source code base repository wherein the tag indicates whether a particular portion of the source code base is included in two or more product versions of a software application and builds a product version of the software application so that the built product version of the software application does not contain the particular portion of the source code base based on the detected tag so that the portions of the source code base included in each product version of the software application is controlled by the tags.

10. A method for distributing software wherein the software has a source code base wherein the source code base includes one or more tags in the source code base, the method comprising:

detecting, by a computer system, a tag in the source code base, the tag indicating whether a particular portion of the source code base is included in two or more product versions of a software application; and

building, by the computer system, the product version of the software application so that the built product version of the software application contains the particular portion of the source code base based on the detected tags so that the portions of the source code base included in each product version of the software application is controlled by the tags.

11. The method of claim 10, wherein building the product version of the software application further comprises removing the particular portion of the source code base based on the detected tag.

12. The method of claim 10, wherein building the product version of the software application further comprises, when the particular portion of the source code base is removed from a product version of the software application, inserting a number of blank lines, corresponding to the lines of the particular portion of the source code based removed from the version of the software application, into the product version of the software application to maintain the line numbering of the product version of the software application.

13. The method of claim 10, wherein the source code base further comprises a piece of source code and wherein the tag further comprises a code level tag that indicates whether a particular portion of a piece of source code is included in two or more product versions of a software application.

14. The method of claim 10, wherein the source code base further comprises a source code directory and wherein the tag further comprises a directory level tag that indicates whether a particular source code directory is included in two or more product versions of a software application.

15. The method of claim 10, wherein the source code base further comprises a source code file and wherein the tag further comprises a file level tag that indicates whether a particular source code file is included in two or more product versions of a software application.

16. The method of claim 10, wherein the product versions further comprises one of an open source product version, an enterprise product version and a professional product version.

17. A method for distributing software wherein the software has a source code base wherein the source code base includes one or more tags in the source code base, the method comprising:

detecting, by a computer system, a tag in the source code base, the tag indicating whether a particular portion of the source code base is included in two or more product versions of a software application; and

building, by the computer system, the product version of the software application so that the built product version of the software application does not contain the particular portion of the source code base based on the detected tags so that the portions of the source code base included in each product version of the software application is controlled by the tags.