Web services development method

• US 20030233631A1
• Filed: 06/13/2002
• Published: 12/18/2003
• Est. Priority Date: 06/13/2002
• Status: Abandoned Application

• Current Assignee: Epionet
• Original Assignee: Epionet
• Inventors: Jordan, Clive A., Curry, Ambrose, Carville, Anthony, Brogan, Stephen
• Application Number:
  US10/171,173
• Publication Number:
  US 20030233631A1
• Time in Patent Office: Days
• US Class Current: 717/100
• CPC Class Codes: G06F 8/20 Software design

Abstract

A method for rapid design, development, deployment and support of web applications based on web services with minimum customized programming, maximized reuse of software components and compliance with standard development frameworks. The method of the invention systematically addresses the problems that are consistently encountered by web application developers by providing a generic platform that solves these problems. The invention enables developers to deliver web functionality without requiring them to understand the many technicalities of developing functionality for a distributed internet based architecture, and uses best practices to produce encapsulated, tested, quality oriented, applications based on web services.

Claims

1. A method for systematically creating web service based applications comprising the steps of:

assembling certified specifications;

refining said certified specifications to form a set of web services;

prioritizing said set of web services to form a prioritized web service set;

selecting web services for development from said prioritized web service set;

in the event that a visual interface is required for said selected web services, determining whether interface templates applicable to said web services for development are available in a template library;

compiling a list of interface templates to be used with said web services for development;

categorizing said interface templates on said list according to whether said interface templates are available for reuse, may be constructed by modifying an existing interface template, or must be constructed anew;

prioritizing said list of interface templates for development to form a prioritized template list; and

creating said interface templates according to said prioritized template list.

2. The method according to claim 1 further comprising the steps of:

upgrading said interface templates that are not optimally compatible with an overall application architecture; and

testing said interface templates for usability.

3. The method according to claim 1 further comprising the steps of performing an overall application architectural analysis to determine an overall architecture;

identifying web service based applications that are available for reuse and web service based applications that must be created anew;

designing classes and components within logical layers of said overall application architecture;

identifying existing classes and components that can be reused within said class and component designs; and

creating new classes and components for class and component designs that have not been identified as reusable from existing entities.

4. The method according to claim 3 further comprising the steps of:

defining web service metadata; and

creating said web service based applications according to said overall application architecture.

5. The method according to claim 4 further comprising the steps of:

in said event that a visual interface is required for said web service, constructing a presentation framework for said web service based application;

creating workspace pages to implement said template for interaction; and

creating a layout structure for the presentation of said workspace pages.

6. The method according to claim 3 wherein said architectural analysis step comprises the steps of:

designing a logical architecture of said web service according to the overall application architecture; and

designing a security architecture of said web service based application according to the overall application architecture.

7. The method according to claim 3 wherein said architectural analysis step comprises the steps of:

analyzing system environments within which said web service based application will be required to operate;

analyzing design goals of said web service based application; and

analyzing said web service based application to maximize reuse potential.

8. The method according to claim 1 wherein said certified specifications include business logic specifications.

9. A method for systematically creating web services comprising the steps of:

assembling certified business logic specifications;

refining said certified business logic specifications to form a list of web services;

prioritizing said list of web services to form a prioritized web service list;

selecting web services for development from said prioritized web service list;

determining whether interface templates applicable to said web services for development are available in a template library;

compiling a list of interface templates to be used with said web services for development;

categorizing said interface templates on said list according to whether said interface templates are available for reuse, may be constructed by modifying an existing interface template, or must be constructed anew;

prioritizing said list of interface templates for development to form a prioritized template list;

creating said interface templates according to said prioritized template list;

reviewing said interface templates for compatibility with an overall application architecture;

reworking or substituting interface templates that are not optimally compatible with said overall application architecture;

testing said interface templates for usability;

performing an overall architectural analysis;

identifying application entities that are available for reuse and application entities that must be created anew;

designing and creating databases for said web services;

designing classes and components within logical layers of said overall application architecture;

identifying existing classes and components that can be reused within said class and component designs;

creating new classes and components for class and component designs that have not been identified as reusable from existing entities;

defining web service metadata;

creating said web service using said classes and components according to said overall application architecture;

constructing a presentation framework for said web service;

creating workspace pages; and

laying out workspaces.

10. The method according to claim 9 wherein said steps of:

designing classes and components;

creating new classes and components;

constructing a presentation framework;

creating workspace pages; and

laying out workspaces are automated.

11. The method according to claim 9 further comprising the step of automatically adding said web service to a web service library.

12. The method according to claim 11 further comprising the steps of:

adjudicating said web services for reusability into sets of rejected, reworkable and reusable web services;

testing said reusable web services for quality assurance and usability;

categorizing said reusable web services;

publishing said reusable web services;

reworking said reworkable services by enhancing reusability of said reworkable web services;

re-adjudicating said reworked web services;

testing, categorizing, and publishing said reworked web services that have been deemed reusable during said re-adjudication step.

13. The method according to claim 9 wherein said architectural analysis step comprises the steps of:

designing a logical system architecture of said web service according to an overall application architecture; and

designing a security architecture of said web service according to an overall application architecture.

14. The method according to claim 9 wherein said architectural analysis step comprises the steps of:

analyzing system environments within which said web service will be required to operate;

analyzing design goals of said web service; and

analyzing said web service based application to maximize reuse potential.

15. The method according to claim 9 further comprising the step of:

deploying said web service.

16. The method according to claim 10 wherein said automation performed using means for rapid application development and deployment.

17. The method according to claim 16 further comprising the step of:

deploying said web service.

18. The method according to claim 17 wherein said deploying step comprising the steps of:

creating a single distributable package from a set of individual resources that make up an application;

delivering said package to a target computer system;

unpacking and installing said set of individual resources on said target computer system.

19. The method according to claim 18 wherein said steps of packing and unpacking comprise using a Packager software toolset.