Service oriented application development and support

• US 20080282219A1
• Filed: 06/18/2007
• Published: 11/13/2008
• Est. Priority Date: 06/16/2006
• Status: Active Grant

• Current Assignee: Sony Corporation (Sony Group Corp.), Sony Pictures Entertainment Incorporated (Sony Group Corp.)
• Original Assignee: Sony Corporation (Sony Group Corp.), Sony Pictures Entertainment Incorporated (Sony Group Corp.)
• Inventors: Lamperillo, Gary, Seetharaman, Arun, Saucier, Douglas
• Granted Patent: US 8,887,130 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

The system and method provide for software design and development that result in applications that are service-oriented. The systems provide for architecture development, integration, and maintenance using an SOA approach, and in particular an approach that provides for service-oriented development of applications (SODA). Such systems include numerous beneficial and advantageous features, including ways to define requirements and ways to design and develop applications.

Claims

1. A method of producing a service-oriented application, comprising:

a. Performing requirements-gathering, including;

i. developing an initial set of requirements for a service-oriented application;

ii. developing a list of use cases for the service-oriented application;

iii. developing a process model for the service-oriented application;

iv. reconciling the initial set of requirements with the process model;

v. developing a detailed set of requirements for a service-oriented application;

vi. developing a set of use cases for the service-oriented application, the set associated with the list;

vii. developing a set of business rules for the service-oriented application;

viii. reconciling the detailed set of requirements with the set of use cases and the business rules; and

ix. developing a logical domain model for the service-oriented application;

b. Performing application design, including;

i. developing at least one system use case associated with each one of the set of use cases;

ii. for each of the set of use cases, developing a use case realization;

iii. designing a user interface;

iv. defining an architecture for the service-oriented application, defining and designing application services for the service-oriented application, and defining a technical architecture for the service-oriented application;

v. using the logical domain model, designing a logical data model;

vi. defining test cases; and

vii. reconciling the designed application services, the user interface, and the technical architecture with the second set of requirements and the defined test cases;

c. Performing application development, including;

i. developing a page flow for the service-oriented application;

ii. developing at least one form.and at least one display for entering and displaying data, respectively;

iii. creating transfer objects;

iv. developing business rules and business objects;

v. creating a physical data model from the logical data model;

vi. creating a set of database objects and domain objects;

vii. developing a set of data accessor and mappers; and

viii. integrating a layer containing the page flow, form, display, and transfer objects with a layer containing the business objects and rules with a layer containing the physical data model, the database and domain objects, and the data accessor and mappers.

2. The method of claim 1, further comprising developing a data dictionary and/or a glossary.

3. The method of claim 1, further comprising developing a service facade.

4. The method of claim 1, wherein the step of developing at least one form.and at least one display for entering and displaying data includes developing at least one FormBean and one ViewBean, respectively.

5. A computer-readable medium containing instructions for causing a computer to implement the method of claim 1.

6. A product obtained by the method of claim 1.

7. A method of performing a requirements-gathering phase in a service-oriented development of applications, comprising:

i. developing an initial set of requirements for a service-oriented application;

ii. developing a list of use cases for the service-oriented application;

iii. developing a process model for the service-oriented application;

iv. reconciling the initial set of requirements with the process model;

v. developing a detailed set of requirements for a service-oriented application;

vi. developing a set of use cases for the service-oriented application, the set associated with the list;

vii. developing a set of business rules for the service-oriented application;

viii. reconciling the detailed set of requirements with the set of use cases and the business rules; and

ix. developing a logical domain model for the service-oriented application.

8. A computer-readable medium containing instructions for causing a computer to implement the method of claim 7.

9. A product obtained by the method of claim 7.

10. A method of performing a requirements-gathering phase in a service-oriented development of applications, comprising:

a. developing a set of requirements for a service-oriented application;

b. developing a list of use cases and a set of use cases for the service-oriented application;

c. developing a process model for the service-oriented application;

d. reconciling the set of requirements with the process model;

e. developing a set of business rules for the service-oriented application;

f. reconciling the set of requirements with the set of use cases and the business rules; and

g. developing a logical domain model for the service-oriented application.

11. A method of performing an application design phase in a service-oriented development of applications wherein a set of requirements has been defined, comprising:

a. developing at least one system use case associated with each one of a set of use cases for a service-oriented application;

b. for each of the set of use cases, developing a use case realization;

c. designing a user interface;

d. defining an architecture for the service-oriented application, defining and designing application services for the service-oriented application, and defining a technical architecture for the service-oriented application;

e. designing a logical data model for the service-oriented application;

f. defining test cases; and

g. reconciling the designed application services, the user interface, and the technical architecture with the set of requirements and the defined test cases.

12. A computer-readable medium containing instructions for causing a computer to implement the method of claim 11.

13. A product obtained by the method of claim 11.

14. A method of performing a application development phase in a service-oriented development of applications in which as logical data model has been developed, comprising:

a. developing a page flow for a service-oriented application;

b. developing at least one form and at least one display for entering and displaying data, respectively;

c. creating transfer objects;

d. developing business rules and business objects;

e. creating a physical data model from the logical data model;

f. creating a set of database objects and domain objects;

g. developing a set of data accessor and mappers; and

h. integrating a layer containing the page flow, form, display, and transfer objects with a layer containing the business objects and rules with a layer containing the physical data model, the database and domain objects, and the data accessor and mappers.

15. A computer-readable medium containing instructions for causing a computer to implement the method of claim 14.

16. A product obtained by the method of claim 14.

17. A system for producing a service-oriented application, comprising:

a. A requirements-gathering module, including;

i. a module for developing a set of requirements for a service-oriented application;

ii. a module for developing a list of use cases and a set of use cases for the service-oriented application;

iii. a module for developing a process model for the service-oriented application;

iv. a module for reconciling the set of requirements with the process model;

v. a module for developing a set of business rules for the service-oriented application;

vi. a module for reconciling the set of requirements with the set of use cases and the business rules; and

vii. a module for developing a logical domain model for the service-oriented application;

b. An application design module, including;

i. a module for developing at least one system use case associated with each one of the set of use cases;

ii. a module for developing a use case realization;

iii. a module for designing a user interface;

iv. a module for defining an architecture for the service-oriented application, for defining and designing application services for the service-oriented application, and for defining a technical architecture for the service-oriented application;

v. a module for designing a logical data model;

vi. a module for defining test cases; and

vii. a module for reconciling the designed application services, the user interface, and the technical architecture with the second set of requirements and the defined test cases;

c. An application development module, including;

i. a module for developing a page flow for the service-oriented application;

ii. a module for developing at least one form.and at least one display for entering and displaying data, respectively;

iii. a module for creating transfer objects;

iv. a module for developing business rules and business objects;

v. a module for creating a physical data model from the logical data model;

vi. a module for creating a set of database objects and domain objects;

vii. a module for developing a set of data accessor and mappers; and

viii. a module for integrating a layer containing the page flow, form, display, and transfer objects with a layer containing the business objects and rules with a layer containing the physical data model, the database and domain objects, and the data accessor and mappers.

18. A system for performing a requirements-gathering phase in a service-oriented development of applications, comprising:

a. a module for developing a set of requirements for a service-oriented application;

b. a module for developing a list of use cases and a set of use cases for the service-oriented application;

c. a module for developing a process model for the service-oriented application;

d. a module for reconciling the set of requirements with the process model;

e. a module for developing a set of business rules for the service-oriented application;

f. a module for reconciling the set of requirements with the set of use cases and the business rules; and

g. a module for developing a logical domain model for the service-oriented application.

19. A system for performing an application design phase in a service-oriented development of applications in which a set of use cases and a set of requirements have been defined, comprising:

a. a module for developing at least one system use case associated with each one of the set of use cases;

b. a module for developing a use case realization;

c. a module for designing a user interface;

d. a module for defining an architecture for the service-oriented application, a module for defining and designing application services for the service-oriented application, and a module for defining a technical architecture for the service-oriented application;

e. a module for designing a logical data model;

f. a module for defining test cases; and

g. a module for reconciling the designed application services, the user interface, and the technical architecture with the set of requirements and the defined test cases.

20. A system for performing an application development phase in a service-oriented development of applications in which a logical data model has been defined, comprising:

a. a module for developing a page flow for a service-oriented application;

b. a module for developing at least one form.and at least one display for entering and displaying data, respectively;

c. a module for creating transfer objects;

d. a module for developing business rules and business objects;

e. a module for creating a physical data model from the logical data model;

f. a module for creating a set of database objects and domain objects;

g. a module for developing a set of data accessor and mappers; and

h. a module for integrating a layer containing the page flow, form, display, and transfer objects with a layer containing the business objects and rules with a layer containing the physical data model, the database and domain objects, and the data accessor and mappers.