System, method and article of manufacture for a table-driven automated scripting architecture

[0002] The present invention relates to scripting and more particularly to automated scripting solutions.

[0003] Newly developed software programs must be thoroughly tested in order to eliminate as many “bugs” or errors as possible before the software is released for widespread public use. Accordingly, development of software is largely a trial and error process. Several different methods for testing software programs have been developed. One conventional approach, generally referred to as beta testing, involves distributing the program, typically under a non-disclosure agreement, to a group of users who use the program for a period of time and report any errors which are encountered to the software developer. Although this type of testing is commonly used in the software industry, it is often found to be very time consuming, adversely affecting the scheduled release of products incorporating the software program. In addition, beta testing can be extremely difficult to control, particularly when a large number of users are provided the beta version of the software. Furthermore, due to the non-systematic use of the program, there is no guarantee that every error, or even most errors, will be identified with this approach, even under circumstances where a large number of users are using the software.

[0004] As software is developed on and runs on computers, it is not surprising to find that many of the techniques for automating the testing of software have been implemented in digital computers. A common approach for testing software is the use of test suites. Test suites compare “known good” outputs of a program (for a given set of input) against the current output. Tests that check program file output are easy to implement and can be automated with shell scripts (e.g., Expect available on the Internet). For programs with user interfaces that communicate to standard input/output devices (stdin/stdout), a similar method may be employed. Capture/playback tools are available for recording keyboard input and program output as a person tests a program.

[0005] Much of the code written today is for software products with a graphical user interface (GUI), such as Microsoft.RTM. Windows.TM.. In fact, much of software development itself is done within a graphical user interface, with software tool vendors providing products which allow software developers to develop GUI software using visual programming techniques. The Quality Assurance (QA) engineer faces more complex problems when testing GUI software. In particular, GUI programs must behave correctly regardless of which video mode or operating environment is being employed.

[0006] Intuitively, testing user interfaces should not be as difficult as testing a complex internal engine, such as a compiler or a real-time, multi-user operating system. In practice, however, user interface (UI) testing is the most challenging part of the QA process. This problem stems largely from the difficulty in automating UI tests. Tests for complex engines, in contrast, are often command-line programs whose testing can easily be automated using simple batch execution. Thus despite the plethora of present day tools for automating program testing, the task of developing, maintaining and analyzing the results of UI tests remains an arduous task.

[0007] The basic steps traditionally employed to test user interfaces may be summarized as follows. First, the application being tested is controlled by placing it into a specific state using either pre-recorded keyboard or mouse device actions, or entering input through a test script. Next, the then-current state of the application is recorded by taking a screenshot (e.g., capturing a screen bitmap). Finally, the captured screenshot is compared with a baseline screenshot that is known to be valid.

[0008] The approach is far from ideal, however. Consider, for instance, the determination of whether the state of a check box is valid within a specific dialog box. Here, the QA engineer must take a screenshot of that check box and compare it with the expected image. Thus, testing of even the simplest component is laborious. Moreover, the approach itself is prone to error. A change of just a few pixels across all windows—a common occurrence in GUI software development—causes all tests to fail. Consequently, as software becomes more and more complex, it becomes less and less feasible to test user interface tasks with present-day screen comparison methodology.

[0009] The software testing phase is a critical phase in the software development process. During the software development process, the software testing phase occurs after the software has been designed, implemented in a programming language, and tested to a limited degree. During the testing phase, software testers test the software extensively to ensure that the software meets all of the requirements it is intended to meet. In order to accommodate simultaneous testing of several different software packages by several testers, multiple test machines are often implemented. Different types of software packages may need to be tested on different types of test machines, such as, for example, test machines with different hardware configurations and/or different operating systems. When a large number of software testers are required to share common resources for software testing, provisions must be made for scheduling the tests in order to efficiently manage these shared resources. The efficient management of these shared resources may also require that tests and the results of the tests be recorded so that the tests can be used repeatedly if needed and so that the results of the tests can be analyzed and subsequently used for comparison with the results of tests performed at a later time.

[0010] In an effort to maximize efficiency in the handling of test scheduling and test execution, attempts have been made to automate software testing by using a server to manage test machines and to allocate test packages among the test machines in accordance with a schedule. Generally, these types of systems pre-allocate tasks to test machines by calculating the current and scheduled loads on the test machines and scheduling the tasks so that they are performed in a tine-efficient manner. For example, Sun Microsystems, Inc. has proposed an automated task-based scheduler for use with UNIX platform systems which allows users operating “client” machines to schedule tests to be executed on “target” machines. A central server receives a request from a client machine to perform a task. The server maintains information relating to all currently scheduled tasks on all target machines in a “status” database. The server maintains information relating to the expected duration of each test package and other test package attributes in a “packages” database.

[0011] When the server receives a request to perform a task from a client machine, the server determines the loads on each of the target machines which are suitable for performing the task. The loads are determined based on the expected duration of each test package. The server then schedules the task on the target machine with the least current load. A task file created at the client machine and copied to the server includes priority information relating to the task requested by the client machine. Once the server has selected a target machine for the task, the task file is copied to the selected target machine. The target machine selects a task to be performed based on this priority information contained in the task file copied to the target machine. Once a task is completed, the results are copied back to the server which compares them to a set of “golden results” and creates a comparison report which is mailed back to the user that requested the test.

[0012] A system, method and article of manufacture are provided for affording a table-driven automated scripting architecture. First, test script information is divided into a plurality of components of one or more words having a commonly understood meaning. Then the components are stored into a database. Later, the components are parsed into one or more words (each having a commonly understood meaning). The database is queried for the words to retrieve a set of computer instructions that cause a computer to perform functions related to the commonly understood meaning of the words and then to perform those functions.

[0013] In one aspect of the present invention, the test script information relates to at least one of either steps and/or actions. The test scenarios are typically data-driven. In addition, the test scenarios may be developed using an English-based interface. As an option, the interface may be accessed utilizing a network. Also optionally, the architecture is a two-tier architecture.

[0014] The invention will be better understood when consideration is given to the following detailed description thereof. Such description makes reference to the annexed drawings wherein:

[0015] FIG. 1 is a flowchart illustrating a method for affording an automated scripting solution for enterprise testing in accordance with one embodiment of the present invention;

[0016] FIG. 2 is a schematic diagram illustrating one exemplary system architecture of the present invention, in accordance with one embodiment of the present invention;

[0017] FIG. 3 is a representative hardware environment illustrating a hardware configuration of a client computer in accordance with a preferred embodiment;

[0018] FIG. 4 is a flowchart illustrating a method for affording a table-driven automated scripting architecture in accordance with one embodiment of the present invention;

[0019] FIG. 5 is a flowchart illustrating a method for affording improved accuracy in an automated scripting framework in accordance with one embodiment of the present invention;

[0020] FIG. 6 is a flowchart illustrating a method for affording application independence in an automated scripting framework, in accordance with one aspect of the present invention;

[0021] FIG. 7 is a flowchart illustrating a method for affording test development in an automated scripting framework, in accordance with an embodiment of the present invention;

[0022] FIG. 8 is a flowchart illustrating a method for affording synchronization in an automated scripting framework, in accordance with an aspect of the present invention;

[0023] FIG. 9 is a flowchart illustrating a method for affording test maintenance in an automated scripting framework in accordance with an embodiment of the present invention; and

[0024] FIG. 10 is a flowchart illustrating a method for affording metrics in an automated scripting framework, in accordance with an embodiment of the present invention.

[0025] FIG. 11 illustrates the creating of Container “Roles” according to an embodiment of the present invention;

[0026] FIG. 12 is an illustration of a graphic display at a point where a user has right-clicked on the Schema folder and selected New—Attribute according to an embodiment of the present invention;

[0027] FIG. 13 illustrates the adding of different Roles according to an embodiment of the present invention;

[0028] FIG. 14 illustrates an example of the graphic display showing the attributes of member “Joe Bloggs” according to an embodiment of the present invention;

[0029] FIG. 15 is a flowchart that illustrates a method for handling events in a system;

[0030] FIG. 15.1 illustrates a ReTA Event Handler framework that manages the informational, warning and error events that an application raises according to an embodiment of the present invention;

[0031] FIG. 16 is a flowchart depicting a method for managing user information;

[0032] FIG. 16.1 illustrates a User framework which enables two approaches to maintaining user information according to an embodiment of the present invention;

[0033] FIG. 17 is a flowchart that illustrates a method for managing business objects in a system that includes a plurality of sub-activities which each include sub-activity logic adapted to generate an output based on an input received from a user upon execution, and a plurality of activities which each execute the sub-activities in a unique manner upon being selected for accomplishing a goal associated with the activity;

[0034] FIG. 17.1 shows a SubActivity component using the Persistence framework to retrieve a Customer Object from the Database according to an embodiment of the present invention;

[0035] FIG. 18 is a flow chart depicting a method for persisting information during a user session;

[0036] FIG. 18.1 illustrates a Session Flow Diagram—On Session Start according to an embodiment of the present invention;

[0037] FIG. 19 illustrates a Session Flow Diagram—On Start ASP Page according to an embodiment of the present invention;

[0038] FIG. 20 is a flow chart illustrating a method for generating a graphical user interface;

[0039] FIG. 20.1 is an illustration showing the steps for generating a HTML page consisting of a form with a TextBox, a DropDown list and a PushButton according to an embodiment of the present invention;

[0040] FIG. 21 is a flow chart depicting a method for software configuration management

[0041] FIG. 21.1 is an illustration of an IDEA framework on which the ReTA Development Architecture Design is based according to an embodiment of the present invention;

[0042] FIG. 22 illustrates the Configuration Management Life Cycle according to an embodiment of the present invention;

[0043] FIG. 23 illustrates the change control ‘pipeline’ and each phase within the pipeline according to an embodiment of the present invention;

[0044] FIG. 24 depicts the application of Roles within the Microsoft Transaction Server (MTS) management console according to an embodiment of the present invention;

[0045] FIG. 25 illustrates an environment migration process that guides development within ReTA engagement environments according to an embodiment of the present invention;

[0046] FIG. 26 is an illustration of a Development/Unit test for existing applications according to an embodiment of the present invention;

[0047] FIG. 27 illustrates an assembly test for existing applications according to an embodiment of the present invention;

[0048] FIG. 28 illustrates a system test for existing applications according to an embodiment of the present invention;

[0049] FIG. 29 is a flowchart for production of existing applications according to an embodiment of the present invention;

[0050] FIG. 30 illustrates a graphic display of Visual Source Safe according to an embodiment of the present invention;

[0051] FIG. 31 illustrates a frame of PVCS Version Manager I-Net Client according to an embodiment of the present invention;

[0052] FIG. 32 is an illustration of a Build Source Control Model according to an embodiment of the present invention;

[0053] FIG. 33 illustrates an Assembly Test phase control mode according to an embodiment of the present invention;

[0054] FIG. 34 illustrates a Microsoft Visual SourceSafe ‘Labels’ dialog box according to an embodiment of the present invention;

[0055] FIG. 35 illustrates a Database Diagram within Visual Studio according to an embodiment of the present invention;

[0056] FIG. 36 illustrates Object Modeling within Rational Rose according to an embodiment of the present invention;

[0057] FIG. 37 illustrates directly calling a wrapped CICS component according to an embodiment of the present invention;

[0058] FIG. 38 illustrates indirectly calling a wrapped CICS component according to an embodiment of the present invention;

[0059] FIG. 39 illustrates RSW eTest Automated Testing Tool according to an embodiment of the present invention;

[0060] FIG. 40 is an illustration which describes the physical configuration necessary for ReTA development according to an embodiment of the present invention;

[0061] FIG. 41 illustrates the application & architecture configuration for a typical ReTA Build environment according to an embodiment of the present invention;

[0062] FIG. 42 illustrates the application & architecture configuration for a typical ReTA Build environment according to an embodiment of the present invention;

[0063] FIG. 43 illustrates an IDEA Framework with components in scope ReTA Phase 1 according to an embodiment of the present invention;

[0064] FIG. 44 illustrates a NCAF Framework with the shaded components in scope for Phase 1 according to an embodiment of the present invention;

[0065] FIG. 45 illustrates a MODEnc Framework according to an embodiment of the present invention;

[0066] FIG. 46 illustrates a NCAF Framework according to an embodiment of the present invention;

[0067] FIG. 47 illustrates the components that comprise the ReTA execution architecture and their physical location according to an embodiment of the present invention;

[0068] FIG. 48 illustrates a MODEnc Framework for Operations Architecture according to an embodiment of the present invention;

[0069] FIG. 49 is an illustrative representation of a solicited event resulting from the direct (synchronous) polling of a network component by a network management station according to an embodiment of the present invention;

[0070] FIG. 50 is an illustrative representation of when an unsolicited event occurs when a network component sends (asynchronously) data to the network management station according to an embodiment of the present invention;

[0071] FIG. 51 illustrates event management in a net-centric environment according to an embodiment of the present invention;

[0072] FIG. 52 illustrates event management in an Intranet-based net-centric model according to an embodiment of the present invention;

[0073] FIG. 53 illustrates event management when using an Extranet-based net-centric model according to an embodiment of the present invention;

[0074] FIG. 54 illustrates the tables and relationships required for the ReTA Phase 1 Architecture Frameworks according to an embodiment of the present invention;

[0075] FIG. 55 illustrates tables and relationships required for the ReTA Phase 1 validation application according to an embodiment of the present invention;

[0076] FIG. 56 illustrates the physical configuration of a possible ReTA-engagement development environment according to an embodiment of the present invention;

[0077] FIG. 57 illustrates the physical configuration of possible ReTA-based Assembly, Product and Performance testing environments according to an embodiment of the present invention;

[0078] FIG. 58 illustrates Separate Web and Application Servers according to an embodiment of the present invention;

[0079] FIG. 59 illustrates a Single Web and Application Server according to an embodiment of the present invention;

[0080] FIG. 60 illustrates a Commerce Membership Server [Membership Authentication] properties view according to an embodiment of the present invention;

[0081] FIG. 61 illustrates a Membership Directory Manager Properties Dialog according to an embodiment of the present invention;

[0082] FIG. 62 is an illustration of a Membership Server Mapping Property according to an embodiment of the present invention;

[0083] FIG. 63 is an illustration of a Create New Site Foundation Wizard according to an embodiment of the present invention;

[0084] FIG. 64 illustrates the web application being placed under the “Member” directory of “cm” in Windows Explorer according to an embodiment of the present invention;

[0085] FIG. 65 depicts a typical ReTA engagement development environment according to an embodiment of the present invention;

[0086] FIG. 66 illustrates the development environment configuration for a ReTA Phase 1 engagement according to an embodiment of the present invention;

[0087] FIG. 67 illustrates an interface associated with the ability of inserting or removing statements within a block without worrying about adding or removing braces according to an embodiment of the present invention;

[0088] FIG. 68 shows a Visual J++ Build Environment according to an embodiment of the present invention;

[0089] FIG. 69 shows an interface for attaching to the MTS Process for debugging according to an embodiment of the present invention;

[0090] FIG. 70 shows an interface for debugging an Active Server Page (example global.asa file) according to an embodiment of the present invention;

[0091] FIG. 71 illustrates an example of Rose generated java file and javadoc comments according to an embodiment of the present invention;

[0092] FIG. 72 is a flowchart illustrating a method for testing a technical architecture; FIG. 72.1 illustrates the application & architecture configuration for a typical ReTA Build environment according to an embodiment of the present invention;

[0093] FIG. 73 illustrates that the code for technology architecture assembly test may be migrated from the technology architecture component test environment as defined in the migration procedures according to an embodiment of the present invention;

[0094] FIG. 74 illustrates the application & architecture configuration for a typical ReTA Build environment according to an embodiment of the present invention; and

[0095] FIG. 75 illustrates the physical characteristics of the testing environment to be utilized during the Performance Testing Phases according to an embodiment of the present invention.

[0096] FIG. 1 is a flowchart illustrating a method 100 for affording an automated scripting solution for enterprise testing in accordance with one embodiment of the present invention. First, in operation 102, a table-driven automated scripting architecture is provided. Then, in operation 104, a test script is developed using the table-driven automated scripting architecture. A synchronized execution of the test script is then performed as indicated in operation 106. In operation 108, metrics of the synchronized execution of the test script are outputted.

[0097] The present invention has been developed and implemented to automate regression testing of host applications. Among other roles, the present invention can be used in an Integration Test (IT) phase to develop a more robust and systematic process for executing test scripts during certification testing. The present invention is a two-tier application, consisting of a database (Microsoft Access 97 or SQL Server) and an automation tool (Mercury Interactive WinRunner). The present invention reduces testing time and allows the testing team to detect and log more application issues, ensuring quality software delivery.

[0098] The present invention provides data-driven test scripts with an English-based, form-driven user interface. The present invention data architecture divides and stores test script information (steps, actions, application widgets, etc.) into separate, reusable components. The table relationships between these components provide the capability to develop easily maintained, data-driven test scenarios.

[0099] Traditional testing tools are manual and require long hours of slow and tedious testing. The few automated tools that do exist have limited flexibility and hard coded scripts.

[0100] In contrast, the present invention's unique and innovative features yield exceptional benefits in both scope and time. Organizational benefits include: increased development productivity, higher issue counts and shorter development cycles.

[0101] FIG. 2 is a schematic diagram illustrating one exemplary system architecture 200 of the present invention, in accordance with one embodiment of the present invention. The system architecture 200 includes a client script system 202 and a server script system 204. The client script system 202 includes a client computer 206, ASA modules 208, test script automator 210, and test script documentation 212. The server script system 204 includes a database 214, on-line help documentation 216, and metrics statistical reports 218.

[0102] In use, the client computer 206 updates test script data located on the database 214 utilizing an ODBC connection. The test script data is further passed to the ASA modules 208 via an SQL query. The ASA modules 208 then process the test script data and pass the processed data to the test script automator 210. Automated execution of the processed test script data is then performed by the test script automator 210, which is connected to a host application executing on the client computer 206.

[0103] In addition, the client computer 206 may be utilized to obtain the on-line help documentation 216 located on the server system 204. The server system also stores the metrics statistical reports 218 after execution of each test cycle. Finally, test script data is dynamically converted into English-based, test script documentation 212.

[0104] A preferred embodiment of a client computer system 206 in accordance with the present invention is preferably practiced in the context of a personal computer such as an IBM compatible personal computer, Apple Macintosh computer or UNIX based workstation. A representative hardware environment is depicted in FIG. 3, which illustrates a typical hardware configuration of a client computer 206 in accordance with a preferred embodiment having a central processing unit 310, such as a microprocessor, and a number of other units interconnected via a system bus 312. The workstation shown in FIG. 3 includes a Random Access Memory (RAM) 314, Read Only Memory (ROM) 316, an I/O adapter 318 for connecting peripheral devices such as disk storage units 320 to the bus 312, a user interface adapter 322 for connecting a keyboard 324, a mouse 326, a speaker 328, a microphone 332, and/or other user interface devices such as a touch screen (not shown) to the bus 312, communication adapter 334 for connecting the workstation to a communication network (e.g., a data processing network) and a display adapter 336 for connecting the bus 312 to a display device 338. The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.

[0105] A preferred embodiment is written using JAVA, C, and the C++ language and utilizes object oriented programming methodology. Object oriented programming (OOP) has become increasingly us ed to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided.

[0106] OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.

[0107] In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed.

[0108] OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.

[0109] OOP also allows creation of an object that “depends from” another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine “depends from” the object representing the piston engine. The relationship between these objects is called inheritance.

[0110] When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.

[0111] With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, one's logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows:

[0112] Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system.

[0113] Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.

[0114] An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.

[0115] An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.

[0116] With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.

[0117] If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built objects.

[0118] This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development.

[0119] Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal.

[0120] The benefits of object classes can be summarized, as follows:

[0121] Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems.

[0122] Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other.

[0123] Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.

[0124] Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.

[0125] Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.

[0126] Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.

[0127] Libraries of reusable classes are useful in many situations, but they also have some limitations. For example:

[0128] Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.

[0129] Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects.

[0130] Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should.

[0131] Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.

[0132] Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.

[0133] The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still “sits on top of” the system.

[0134] Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application.

[0135] Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).

[0136] A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems.

[0137] Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times.

[0138] There are three main differences between frameworks and class libraries:

[0139] Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.

[0140] Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together.

[0141] Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems.

[0142] Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. A preferred embodiment of the invention utilizes HyperText Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and the Newco. HTTP or other protocols could be readily substituted for HTML without undue experimentation. Information on these products is available in T. Berners-Lee, D. Connoly, “RFC 1866: Hypertext Markup Language—2.0” (November 1995); and R. Fielding, H, Frystyk, T. Berners-Lee, J. Gettys and J. C. Mogul, “Hypertext Transfer Protocol—HTTP/1.1: HTTP Working Group Internet Draft” (May 2, 1996). HTML is a simple data format used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879; 1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML).

[0143] To date, Web development tools have been limited in their ability to create dynamic Web applications which span from client to server and interoperate with existing computing resources. Until recently, HTML has been the dominant technology used in development of Web-based solutions. However, HTML has proven to be inadequate in the following areas:

[0144] Poor performance;

[0145] Restricted user interface capabilities;

[0146] Can only produce static Web pages;

[0147] Lack of interoperability with existing applications and data; and

[0148] Inability to scale.

[0149] Sun Microsystem's Java language solves many of the client-side problems by:

[0150] Improving performance on the client side;

[0151] Enabling the creation of dynamic, real-time Web applications; and

[0152] Providing the ability to create a wide variety of user interface components.

[0153] With Java, developers can create robust User Interface (UI) components. Custom “widgets” (e.g., real-time stock tickers, animated icons, etc.) can be created, and client-side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time Web pages can be created. Using the above-mentioned custom UI components, dynamic Web pages can also be created.

[0154] Sun's Java language has emerged as an industry-recognized language for “programming the Internet.” Sun defines Java as: “a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets.” Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add “interactive content” to Web documents (e.g., simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g., Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically, “C++ with extensions from Objective C for more dynamic method resolution.”

[0155] Another technology that provides similar function to JAVA is provided by Microsoft and ActiveX Technologies, to give developers and Web designers wherewithal to build dynamic content for the Internet and personal computers. ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content. The tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies. The group's building blocks are called ActiveX Controls, small, fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages. ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named “Jakarta.” ActiveX Technologies also includes ActiveX Server Framework, allowing developers to create server applications. One of ordinary skill in the art readily recognizes that ActiveX could be substituted for JAVA without undue experimentation to practice the invention.

[0156] FIG. 4 is a flowchart illustrating a method 400 for affording a table-driven automated scripting architecture in accordance with one embodiment of the present invention. First, in operation 402, test script information is divided into a plurality of components. Then, in operation 404 the components are stored into a database. A relationship between the components is identified using a table, as indicated in operation 406. Test scenarios involving the components are then developed based on the relationship. See operation 408.

[0157] In one aspect of the present invention, the test script information relates to at least one of either steps and/or actions. The test scenarios are typically data-driven. In addition, the test scenarios may be developed using an English-based interface. As an option, the interface may be accessed utilizing a network. Also optionally, the architecture is a two-tier architecture.

[0158] The table-driven architecture inherent within the present invention is what makes it such a unique innovation. This feature provides benefits such as simplified test script development and maintenance, inherent GUI testing Best Practices, and reduced training time via English-based GUI interface. The table-driven architecture further allows the capability to quickly load data, flexible test cycle planning, real-time and statistical test status reporting, and essentially 100% test script execution accuracy.

[0159] FIG. 5 is a flowchart illustrating a method 500 for affording improved accuracy in an automated scripting framework in accordance with one embodiment of the present invention. First, in operation 502, a relationship is identified between test script components. Next, in operation 504, test scenarios involving the components are developed based on the identified relationship. A plurality of predefined actions are then provided as indicated in operation 506. The test scenarios are then uniformly executed utilizing the predefined actions. See operation 508. In one aspect of the present invention, the cause of errors raised while executing the test scenarios is analyzed. In another aspect, the test scenarios are data-driven. Optionally, the test scenarios may be developed using an English-based interface. Also optionally, the interface may be accessed utilizing a network. Execution of scripts by hand is plagued by error (skipped steps, misread script, etc.) Script automation has the inherent advantage of consistency. Uniform execution provides value to the testing effort. To that end, the present invention's predefined suite of standard actions ensures that every user-widget interaction is executed consistently. Other advantages of this consistency include issue identification/cause analysis and issue recreation.

[0160] FIG. 6 is a flowchart illustrating a method 600 for affording application independence in an automated scripting framework, in accordance with one aspect of the present invention. In an initial operation 602, a database including test criteria is provided. Then, in operation 604, a relationship between test script components is identified based on the test criteria. Test scenarios for an application involving the components are then developed independent of the application based on the identified relationship as indicated in operation 606.

[0161] In one embodiment of the present invention the test criteria is business rules. Optionally, the test criteria may be test conditions.

[0162] In another embodiment of the present invention, the test scenarios are stored for delayed execution. The test scenarios may be data-driven. In addition, the test scenarios may be developed using an English-based interface. Further, the framework may utilize a two-tier architecture.

[0163] Conventional automated testing software requires the host application to be running while the user is creating each test script. In the instance where the host application is malfunctioning or has not yet been developed, test scripts may still be developed in the present invention, without the application, in accordance with system requirements. The scripts may be executed at a later date when the host application has been completed and/or is functioning normally.

[0164] The present invention scripts can be executed with minimal knowledge of application functionality, testing experience and supervision. The tool itself is English-driven and the business rules and test conditions for the application are retained in the present invention, not the user.

[0165] FIG. 7 is a flowchart illustrating a method 700 for affording test development in an automated scripting framework, in accordance with an embodiment of the present invention. First, in operation 702, a database including business rules is accessed. Next, in operation 704, a relationship between test script components is identified based on the business rules. As shown in operation 706, test scenarios involving the test script components are then developed based on the identified relationship. The test scenarios are accessed utilizing an English-driven interface via a network. See operation 708.

[0166] In one aspect of the present invention, the test scenarios are data-driven. Optionally, the test scenarios may be developed using the English-driven interface. Also optionally, the interface is accessed utilizing a network. Further, the framework may utilize a two-tier architecture.

[0167] With the present invention, the creation of automated test scripts no longer requires recording or coding. Using the form-driven, english-based interface is intuitive, providing ease of use, simplified training, reduced learning curve and increased productivity.

[0168] FIG. 8 is a flowchart illustrating a method 800 for affording synchronization in an automated scripting framework, in accordance with an aspect of the present invention. First, in operation 802, script data is received utilizing a language-driven interface. Then, in operation 804, reports having user readable sentences are created based on the received script data. The received script data is then translated into automation code as indicated in operation 806. In operation 808, automated testing is provided utilizing the automation code.

[0169] In one embodiment of the present invention, the reports are created as hard copies. Optionally, the received script data is translated into automation code using relational table values. In another embodiment, the script data may be divided into a plurality of components stored in a database. Further, the database may reside on a remote server.

[0170] The present invention scripts have the distinct advantage of simultaneously being both paper-based and automation-ready at all times. Once script data is entered in the tool, pre-defined reports present the data as readable sentences while relational table values translate the data into automation code.

[0171] FIG. 9 is a flowchart illustrating a method 900 for affording test maintenance in an automated scripting framework in accordance with an embodiment of the present invention. In an initial operation 902, a plurality of test scripts are developed. Next, in operation 904, the plurality of test scripts are stored in a centrally located database. A user is then allowed to edit a specific test script located on the centrally located database as indicated in operation 906. The user edits the specific test script are then propagated to each of the plurality of test scripts, in operation 908.

[0172] In one aspect of the present invention, the user edits to the specific test script are propagated to each of the plurality of test scripts simultaneously. In another aspect, the plurality of test scripts are utilized to develop test scenarios.

[0173] In an embodiment of the present invention, the test scenarios are developed using an English-based interface. In another embodiment, the interface is accessed utilizing a network. In a further embodiment, the framework utilizes a two-tier architecture.

[0174] The present invention's relational database architecture significantly simplifies and reduces script maintenance. Edits are propagated instantly to all scripts. Also, all data is centrally located and easily created/edited.

[0175] FIG. 10 is a flowchart illustrating a method 1000 for affording metrics in an automated scripting framework, in accordance with an embodiment of the present invention. First, in operation 1002, a user is allowed to plan a test cycle for later execution. Next, in operation 1004, ownership of the test cycle is assigned. The test cycle is then executed to produce an execution performance of the test cycle, as shown in operation 1006. A statistical report of the execution performance of the test cycle is generated. See operation 1008.

[0176] In one aspect of the present invention, the statistical report is generated after the test cycle is executed. In another aspect, the statistical report is generated real-time during execution of the test cycle.

[0177] In one embodiment of the present invention, the statistical report is generated as a word processor document. Optionally, the statistical report may be generated as an HTML file. Also optionally, the statistical report is displayed on a computer display device.

[0178] The Resources eCommerce Technology Architecture (ReTA) is a solution that allows the use of packaged components to be integrated into a client based eCommerce solution. Before the present invention, the Resources architecture offerings provided services that supported the construction, execution and operation of very large custom built solutions. In the last few years, client needs have shifted towards requirements for solutions that continually integrate well with third party applications (i.e., data warehouse and portion of the present description management systems). Previous engagements have proven that it is difficult to integrate these applications into a new solution. As application vendors continue to produce new releases that incorporate technical advancements, it is even more difficult to ensure that these integrated applications continue to work with a given solution.

[0179] The ReTA approach to constructing, executing and operating a solution emphasizes the ability to change solution components with minimal impact on the solution as a whole. From this approach, ReTA views third party applications as another component in the overall solution. ReTA is component based, which means the engagement can choose to take only the pieces it needs to meet its specific business requirements. ReTA is especially suited to building small applications, implementing tools and packages, integrating applications and web enabling applications.

[0180] The present invention provides the ability to generate statistical reports of past execution performance, plan and assign ownership of future test cycles, and conduct real-time status reporting during test execution. These reports can also be output as various media, including MS Word and HTML.

[0181] Automated execution of application tests using the present invention is much faster than manual execution. Additionally, manual script execution is tedious, labor-intensive and prone to error. With the present invention, clicking, typing, etc. are executed at a rate of approximately one second per step.

[0182] The present invention further provides the ability to generate statistical reports of past execution performance, plan and assign ownership of future test cycles, and conduct real-time status reporting during test execution.

[0183] In one embodiment, the present invention is application software, written in a programming language such as VBA 6.0, which works cooperatively with Mercury Interactive's WinRunner to perform its automated testing function.

[0184] Site Server Framework Execution Architecture

[0185] To connect to a Site Server, a COM component (UserSS) is used to make calls to Site Server's API. The ReTA UserSS component allows the developer to access Site Server's Personalization and Membership Services without any knowledge of Site Server's API.

[0186] In a Site Server framework architecture, the UserSS COM component connects to the Site Server. The UserSS component uses Site Server's Personalization and Membership; UserSS also performs security as well on a Commerce Site. The ReTA framework uses the UserSS layer to provide access to Site Server. The UserSS layer provides the following benefits:

[0187] It insulates the application developer from Site Server's API.

[0188] It provides functionality for using Site Server's Personalization and Membership Services.

[0189] Site Server Framework Development Architecture

[0190] UserSS Interface Methods

[0191] The UserSS component interfaces with the SiteServer personalization and membership services. This component uses SiteServer to handle the user security, role and preferences.

[0192] Methods

[0193] The IAFUser, IAFUserPreferences, and IAFUserRole interfaces define the access to the AFUserSS component. These interfaces support the following methods:

[0194] Site Server Personalization and Membership/Directory Membership Manager

[0195] This portion of the description describes the required settings in Site Server Commerce Edition used by the ReTA frameworks. This portion of the description also describes the steps involved in creating the required settings.

[0196] ReTA Required Settings

[0197] The Membership Directory Manager is used to manage administration and access control for Membership Directory objects, including users and groups, and schema objects. The Membership Directory stores objects used by all Site Server features.

[0198] The ReTA UserSS framework requires schema objects to be created. The schema objects required by the ReTA Frameworks are: Roles container, RoleName attribute, username attribute, webUserId attribute, and a Role class.

[0199] Required Container, Class, and Attribute Setup Instructions

[0200] Users may have different roles within the system. In Site Server ReTA takes advantage of this by creating a Container “Roles” that contains different “Roles” or different objects of the class “Role”. These “Roles” have attributes such as a default start page. Therefore different “Roles” (different objects of the class “Role”) such as “Operator” or “Customer” may both have a default start page attribute that may point to different URL's.

[0201] The Site Server portion of the present description details how to setup a Container, Class, and Attributes. The following lists the steps involved to setup the required attributes for the ReTA Frameworks to integrate with Site Server.

[0202] Using the Site Server Console, Right Click on the Membership Directory Manager Folder

[0203] Select New—Container, then type in Roles for the Container name.

[0204] FIG. 11 illustrates the creating of Container “Roles”. Right click on Membership Directory Manager 1100 and select New 1102—Container 1104. After creating the Container “Roles”, create the attribute “DefaultStartPage”, “username”, “webUserId”, and “RoleName” in the Schema. To create these attributes expand the Admin Container under the Membership Directory Manager.

[0205] Right click on the Schema folder 1200 and select New 1202—Attribute 1204 (See FIG. 12)

[0206] Define the class “Role” the same way by right clicking on Schema and selecting New—Class.

[0207] Select the “common-name” as a required attribute, also select the “DefaultStartPage” as an attribute but do not make it required.

[0208] Create the Roles for our Application, “Operator” and “Customer”.

[0209] See FIG. 13, which illustrates the adding of different Roles. Right click the Roles Container 1300 under the Membership Directory Manager folder 1302. Select New 1304—Object 1306, select “Role” for the class of object to create, type the name of the object i.e. “Operator”, add the attribute “DefaultStartPage” by clicking Add Attribute button and enter the URL.

[0210] Once these have been created, a member of the system can be assigned to a “Role” and the ReTA Framework required attributes can be added to the user. FIG. 14 illustrates an example showing the attributes 1400 of member “Joe Bloggs” (Note RoleName).

[0211] FIG. 15 illustrates a method 1500 for handling events in a system. In operation 1502, an event which includes metadata is recognized. Next, in operation 1504, the metadata of the event is read and, in operation 1506 a table look-up is performed for information relating to the event based on the metadata. The information includes a severity of the event and further information such as a type of the event, and a location where the event occurred. In operation 1508, a message is displayed either in-line in a currently depicted display or in a separate display based on the severity of the event.

[0212] Optionally, the event may additionally be indicated to components of the system other than the component in which the event occurred. The type of the event may be a database error, an architecture error, a security error, and/or an application error. Further the location of the event may be at least one of a method and an object where the event occurred. Also, the information may further relate to a code associated with the event.

[0213] The message may include the information relating to the event. In additionally, the message may also include a time during which the event occurred. Further, the message may include a string altered based on a user profile. The following material provides a more detailed description of the above-described method.

[0214] This portion of the present description details the ReTA Event Handler framework design from the perspective of the application developer. The role of this framework is to provide services to manage the informational, warning and error events that an application may raise. These services include:

[0215] Presenting the user with an understandable event explanation.

[0216] Informing other Components when errors happen (for example to restore transactional data to a consistent state) using a Publish/Subscribe mechanism.

[0217] Logging informational, warning and error event messages.

[0218] The Event Handler uses an Event Reference meta-data database table to maintain information about the types of events in an application and the policy for dealing with them. This gives a flexible approach and the event messages, the severity and other policies for the events can be changed during operations.

[0219] Phase 2—Event Handler Enhancements

[0220] For phase 2, Event Handler consists of the following enhancements:

[0221] The Event Handler framework is componentized. It no longer maintains references to any of the other framework components. Internally, the Event Handler continues to use the persistence light framework to log events to the database.

[0222] As in phase 1, it can be used as a Session level component. As an enhancement for phase 2, the Event Handler framework can be used as a stateless page level component. This means that a new instance of the component is created at the beginning of each ASP page and is released at the end of each page.

[0223] The Event Handler framework no longer requires Event Collection components as parameters to implement event handling, which only allowed handling events at the page level. In phase 2, the new method “processSingleEvent” takes the parameters of a single event as its input, which enables handling events at the occurrence of the event.

[0224] As in phase 1, The Event Handler can format error descriptions in HTML. As an enhancement for phase 2, the Event Handler can return the error message as a string and enables the application to implement client specific formatting (HTML or other).

[0225] The process event method no longer calls the ASP redirect method. Instead, it returns the severity level code. On return, the application logic determines whether to redirect to the error page or display the error in-line in the current page.

[0226] The Translator is no longer a separate component. Instead, it is a Java class inside the Event Handler component.

[0227] Event Handler Framework

[0228] Description

[0229] With reference to FIG. 15.1, the ReTA Event Handler Framework 1530 manages the informational, warning and error events that an application raises. The following describes the ReTA event handling sequence:

[0230] 1) The Event(s) Occurs

[0231] When an event occurs the following event information is recorded:

[0232] event type (defined in database Event Reference table), for example:

[0233] database error

[0234] security error

[0235] architecture error

[0236] application error

[0237] event location:

[0238] method and object name where the event occurred

[0239] event code (sub-type):

[0240] SQL error code,

[0241] application error code—mapped to a unique description in the database

[0242] architecture error code—mapped to a unique description in the database

[0243] event context:

[0244] Any relevant information about when the event occurred stored in a tagged

[0245] name value pair format. Eg.

[0246] [OrderNumber=1][Description=“Repeat Order”]

[0247] If the event occurs within a Java class inside a COM object, use the Java exception mechanism by throwing an AFEventException. If the exception occurs elsewhere, call the add method on the Event Collection passing the event information.

[0248] Each method defining a COM component interface captures these event exceptions and either adds them to an Event Collection component or directly calls a method on the Event Handler component.

[0249] Events are processed from the ASP page by calling the process method of the Event Handler. Events can also processed from the point where the event occurred by calling the “processSingleEvent” method of the Event Handler.

[0250] 2) The Event Handler Processes the Event(s)

[0251] For each event, set the user id and current page

[0252] For each event, retrieve the event severity from the event handler's “translator” class. This class caches in memory all event descriptions and severity levels retrieved from the event reference database table.

[0253] Add the events to the Event Handler context.

[0254] Implement the persistence policy on the events—events are logged in a batch.

[0255] Return the severity of the most severe event to the caller. The caller is responsible for either redirecting to the error page or displaying the event in-line in the Current Page.

[0256] 3) Display the Event

[0257] Use the Event Handler component to generate the error message. This message can contain context information describing when the event was created.

[0258] Create the HTML formatting and display the event message.

[0259] The Error Message is either displayed in-line in the current page or in a separate error page.

[0260] 4) The Event Handler Generates Error Display Message

[0261] Get the event with the highest severity level from its event context.

[0262] If the most severe event is “fatal”, display the user description associated with the event. Broadcast a SESSION_ABORT message using the Publish/Subscribe mechanism. Any component that is interested in these events must implement the IAFEventListener interface and register with the Event Broadcaster component as interested. To do this they call the addListener method of the Event Handler component.

[0263] If the most severe event is “logical unit of work”, display the user description associated with the event. Broadcast an ACTIVITY_ABORT message using the Publish/Subscribe mechanism.

[0264] If the most severe event is “warning”, display the user description associated with the event.

[0265] Note: The user event descriptions are retrieved from the database either on session start or on demand and are cached by the Translator class. When generating the event description page, this description is requested from the Translator. Event descriptions can have embedded context parameters. When generating the event description page, the event handler replaces these parameters with their values specified when creating the event.

[0266] Database Tables

[0267] The Event Handler uses two database tables: The T_AF_EventReference 1534 is a static table that describes the Event meta-data, giving the policies for each event type. The policies include:

[0268] The message that is displayed to the user. These messages can contain data from the Context that is included when the event is generated.

[0269] The severity of the event. The severity can be Information, Warning, Error and Fatal.

[0270] Whether to persist the event in the database event log.

[0271] The T_AF_EventLog 1536 contains the log of the events that occurred. The following information is logged:

[0272] Event type and Code

[0273] The location where the event occurred. I.e. ASP, Object name and Method Name.

[0274] The user that raised the event.

[0275] The datestamp.

[0276] The context information giving other information about what caused the event.

[0277] Services

[0278] The Event Handler Framework provides the following services:

[0279] Components and Classes

[0280] The Event Handler Framework implements these services through the following COM and Class objects:

[0281] These components and classes are described in detailed in the following sub-portions of the description.

[0282] AFEventHandler

[0283] The AFEventHandler component 1538 handles the events generated by the system. Depending on the severity level, the event handler may redirect the user to another ASP page and may abort the activity or session. The event handler also determines whether and when to log an event.

[0284] Methods

[0285] The IAFEventHandler interface defines the access to the AFEventHandler component. This interface supports the following methods:

[0286] AFEventCollection

[0287] The AFEventCollection component contains a collection of events.

[0288] Methods

[0289] The IAFEventCollection interface defines the access to the AFEventCollection component. This interface supports the following methods:

[0290] AFResult

[0291] The AFResult component defines the result return by a method execution.

[0292] Methods

[0293] The IAFResult interface defines the access to the AFResult component. This interface supports the following methods:

[0294] AFTranslator

[0295] The AFTranslator class returns event reference information (based on the event type and event code.

[0296] Methods

[0297] The AFTranslator class has the following methods:

[0298] AFEventException

[0299] The AFEventException class contains the event exception information and is added to the AFEventCollection component for processing by the AFEventHandler component.

[0300] Methods

[0301] The following AFEventException class methods are important for the application developer to understand:

[0302] AFEventReference

[0303] The AFEventReference component 1540 contains the event reference information that is defined by the application through the database table T₁₃AF_EventReference. The architecture reads the event reference data into memory on session start.

[0304] AFPersistableEvent

[0305] The AFPersistableEvent 1542 contains the event information captured during the application execution that is persisted to the database table T_AF_EVENTLOG.

[0306] FIG. 16 depicts a method 1600 for managing user information. A site server is provided in operation 1602. The side server has information stored on it including preferences, roles, and details relating to users. A database separate from the site server is provided in operation 1604. The database has information stored thereon including preferences, roles, and details relating to the users. In operation 1606, an identity of one of the users is authenticated. A single interface is displayed in operation 1608, which provides the user access to both the site server and the database upon authentication of the identity of the user. In operation 1610, the user is allowed to view and change the information that is stored on the site server and the database and that is associated with the user. The single interface is tailored in operation 1612 based on the information associated with the user.

[0307] The identity of the user may be authenticated by verifying a user name and a password, a secure sockets layer (SSL) certificate, and/or a log-in form. Further, the preferences relating to the users may include a currency in which monetary values are displayed and a language in which text is displayed. Also, the roles relating to the users may include a customer, a manager, and an employee. Additionally, the details of the users may include a user name and a legal name. The following material provides a more detailed description of the above-described method.

[0308] This portion of the present description details the ReTA User framework design from the perspective of the application developer. The primary role of this framework is to provide services that allow the application developer to maintain user preferences, roles and security.

[0309] In regards to security, the User framework provides User Authentication services through any of the standard Internet Information Server security methods:

[0310] Username/Password sent in clear text.

[0311] SSL Certificates

[0312] Windows NT Challenge/Response (Intranet only)

[0313] HTML Forms login (Site Server version only)

[0314] Once the user has been authenticated, the User framework provides services for accessing:

[0315] User information—NT username, Real Name.

[0316] User Preference information—For example Language, Currency (These are configurable)

[0317] User Role information (e.g. Customer, Manager, Employee)

[0318] User Role Preference information

[0319] There are two implementations of the User Component: One is database driven and the other interfaces with Site Server Personalization and Membership directory.

[0320] User Framework

[0321] Description

[0322] With reference to FIG. 16.1, the User framework 1630 enables two approaches to maintaining user information. The framework supports two approaches by exposing a single set of interfaces that can be used by either of the two user framework components. With the AFUserSS component 1632, the framework interfaces with the Microsoft Site Server products Personalization and Membership Directory. For this user component, SiteServer holds and manages user information. With the AFUserDB component 1634, the framework interfaces with database tables. For this user component, database tables define the user information.

[0323] Services

[0324] The User Framework provides the following services:

[0325] Components

[0326] The User Framework implements these services through the following COM objects:

[0327] These components are described in detailed in the following sub-portions of the description.

[0328] AFUserDB

[0329] The AFUserDB component holds the user role, preferences and details retrieved from the database. When created the user component retrieves the user NT login name, user details and constructs the user preference and user role objects.

[0330] Methods

[0331] The IAFUser, IAFUserPreferences and IAFUserRole interfaces define the access to the AFUserDB component. These interfaces support the following methods:

[0332] AFUserSS

[0333] The UserSS component interfaces with the SiteServer personalization and membership services. This component uses SiteServer to handle the user security, role and preferences.

[0334] Methods

[0335] The IAFUser, IAFUserPreferences, and IAFUserRole interfaces define the access to the AFUserSS component. These interfaces support the following methods:

[0336] FIG. 17 illustrates a method 1700 for managing business objects in a system that includes a plurality of sub-activities which each include sub-activity logic adapted to generate an output based on an input received from a user upon execution, and a plurality of activities which each execute the sub-activities in a unique manner upon being selected for accomplishing a goal associated with the activity. First, in operation 1702, an identifier and a reference to a business object are received from one of the sub-activities upon the execution thereof. In operation 1704, a database is accessed and data from the database is retrieved based on the identifier. The business object is created and populated with the data retrieved from the database in operation 1706.

[0337] The data may be stored on the database in tables. Further, the created business object may replace an existing business object. Additionally, the identifier may identify a customer and the business object may be a customer object. Also, a business object referenced by one of the sub-activities may be removed upon the execution thereof.

[0338] The business object may be a Visual Basic business object. In another aspect of the present invention, the business object may be a Java business object. The following material provides a more detailed description of the above-described method.

[0339] This portion of the present description details the ReTA Persistence framework design from the perspective of the application developer. The role of this framework is to provide services that interact with application database(s) to create, retrieve, update and delete business objects.

[0340] Persistence Framework

[0341] Description

[0342] The ReTA Persistence framework provides a transparent and flexible mapping of the business object attributes to relational database tables. To implement this “business object to database table” mapping, the framework is tightly integrated with all business objects. The framework exposes abstract methods that the application developer implements in the business objects. In contrast with the other ReTA frameworks, the Persistence framework is not implemented as a separate component. The Persistence framework is a set of local language classes available in Java or Visual Basic. FIG. 17.1 shows a SubActivity component 1730 using the Persistence framework 1732 to retrieve a Customer Object 1734 from the Database.

[0343] Services

[0344] The Persistence Framework provides the following services:

[0345] Classes

[0346] The Persistence Framework implements these services through the following Java or Visual Basic Classes:

[0347] These classes are described in detailed in the following sub-portions of the description.

[0348] AFPLPersistableObj

[0349] The AFPLPersistableObj abstract class contains methods called by the application developer objects to manage attribute values common to all persistable business objects (user id and last update timestamp). In addition, the AFPLPersistableObj class represents the superclass of a persisted object. In order to persist a business class; the application developer extends AFPLPersistableObj and implements the AFPLPersistableObj abstract methods.

[0350] The AFPLPersistableObj defines the following methods:

[0351] AFPLExtent

[0352] The AFPLExtent class provides the mapping between the business object and its associated database table. In addition, the AFPLExtent class represents the domain defined by the visible part of the database table for the specified user. This class holds the passed in database URL, username and password used during the access to the database. Lastly, the AFPLExtent class manages the database connection.

[0353] Methods

[0354] The AFPLExtent class implements the following methods used by the application developer from business factory objects:

[0355] VBPersistObj

[0356] The VBPersistObj interface class contains methods that need to be implemented on every VB Business Object.

[0357] The application developer implements the following methods from their business object:

[0358] VBExtent

[0359] The VBExtent class provides the mapping between the business object and its associated database table. In addition, the VBExtent class represents the domain defined by the visible part of the database table for the specified user. This class holds the passed in database URL, username and password used during the access to the database. Lastly, the VBExtent class manages the database connection.

[0360] Methods

[0361] The VBExtent class implements the following methods used by the application developer from business factory objects:

[0362] Session Framework Design

[0363] FIG. 18 illustrates a method 1800 for persisting information during a user session. First, in operation 1802, a session is initiated upon a user accessing a predetermined starting page. A current page accessed by the user is then tracked in operation 1804 while browsing a plurality of pages during the session. In operation 1806, a record is maintained of a page previously accessed by the user during the session. Information is persisted in operation 1808. This information is selected from a group of items such as user identifier, a time of a most recent user action during the session, activity components accessed during the session, and business components accessed during the session. During the session, the current page, previous page record, and information are provided to at least one activity component in operation 1810. Also in operation 1810, the activity component generates output based on input provided by the user via the plurality of pages.

[0364] In one embodiment of the present invention, the activity components to which the current page, previous page record, and information are provided may be selectively determined. In addition, the activity component may be provided an indication as to whether the user is permitted to access each of the pages. In such a case, the activity component may also be provided the indication as to whether the user is permitted to access each of the pages based on the previous page record.

[0365] In another embodiment of the present invention, the information may also include the user identifier. In such an embodiment, user preferences may be looked up based on the user identifier with the information including the user preferences. Also, in order to identify the persisted information, references to activity components, business components, a user component, a tracking manager component, a system preference component, and an event handler component may be employed. The following material provides a more detailed description of the above-described method.

[0366] This portion of the present description details the ReTA Session framework design from the perspective of the application developer. The primary role of this framework is to provide services to handle the stateless nature of Internet. By default, the Internet does not provide services for maintaining information between pages. Without these services, it would not be possible to implement most eCommerce functionality. For example, session level state is necessary to implement eCommerce functionality where a customer can select products on multiple product description pages and then submit a complete product order request from a confirm order page. The ReTA Session framework leverages the Internet Information Server/Active Server Page (IIS/ASP) session object, which is automatically created when a user who has no open IIS sessions requests a Web page.

[0367] Session Framework

[0368] Description

[0369] FIG. 18.1 illustrates a Session Flow Diagram—On Session Start. As shown, a Session framework 1830 operates in the MTS Runtime Environment 1832. FIG. 19 illustrates a Session Flow Diagram—On Start ASP Page. Again, the Session framework 1900 operates in the MTS Runtime Environment 1902. The ReTA Session framework provides services required throughout a user session. The user creates the Session framework at log on and removes the Session framework at log off. During the lifetime of the user session, application and architecture components require certain data to persist. This framework provides services to store and retrieve all information needed for a particular user session. This information may persist throughout the user session. The Session framework also provides services to uniquely identify the user and enforce access rights.

[0370] The user information that the Session framework persists, in memory, between Active Server Page requests includes:

[0371] User id

[0372] Identifies session user

[0373] Last page

[0374] Last page accessed by the session user.

[0375] Current page

[0376] Current page accessed by the session user.

[0377] Last connection time:

[0378] Session user's last connection time.

[0379] Current activity:

[0380] Activity currently being executed by the session user (refer to activity framework design)

[0381] Activity Components

[0382] All activity components accessed during user session

[0383] Business Components

[0384] All business components accessed during user session required by multiple activity components.

[0385] Note

[0386] This framework uses the Active Server Page's Session Object. Thus, the framework only works with browsers that accept cookies. For other browsers (or if cookies are disabled), a new ASP Session Object may start for each web page.

[0387] Services

[0388] The Session Framework provides the following services:

[0389] Components

[0390] The Session Framework implements these services through the following COM objects:

[0391] These components are described in detailed in the following sub-portions of the description.

[0392] AFSession

[0393] The AFSession component maintains the user's session state information. To maintain the state information, this component holds references to activity components (logical units of work—application flow logic), business components (business logic required across activity components), user component (user information), tracking manager component (web page access security and web page flow control information), system preference component (system preference information) and event handler component (event handler) created during the user's session.

[0394] From the application developer's perspective, the state maintenance work performed by the AFSession component is transparent. The application developer leverages the session services through populating the database tables with the client specific information.

[0395] Methods

[0396] The IAFSession, IAFEventBroadcaster and IAFContext interfaces define the access to the AFSession component. These interfaces support the following methods:

[0397] AFSystemPreferences

[0398] The AFSystemPreferences component contains system preferences (held during the session). This component uses the ReTA persistence framework to read the system preferences from the database (“system preferences” table).

[0399] Methods

[0400] The IAFSystemPreferences interface defines the access to the AFSystemPreferences component. This interface supports the following methods:

[0401] AFTrackingManager

[0402] The AFTrackingManager component provides page sequence security, dialogue flow and activity flow functionality for the session framework.

[0403] Page Sequence Security

[0404] The page sequence security is defined in the following tables:

[0405] Table “Authorized Destination Page” 1834:

[0406] Define for each page, the pages that are allowed to be accessed. If no authorized destination pages are defined, the page is authorized to access any page.

[0407] Table “Authorized Source Page” 1836:

[0408] Define for each page, the pages that are allowed to access it. If no authorized source pages are defined, the page is authorized to be accessed by any page.

[0409] Dialogue Flow

[0410] The dialogue flow is defined in the following table:

[0411] Table “Destination For Action” 1838:

[0412] Define the action flow between the web pages (i.e., which ASP is open when a specified push button is clicked during a specified activity).

[0413] Activity Flow

[0414] The activity flow is defined in the following table:

[0415] Table “Page Of Activity” 1840:

[0416] Define the automated activity switching when the user jumps from one web page to another.

[0417] Methods

[0418] The IAFTrackingManager interface 1904 defines the access to the AFTrackingManager component. This interface supports the following methods:

[0419] AFBrowserInfo

[0420] The IAFBrowserInfo component contains the user's browser information.

[0421] Methods

[0422] The AFBrowserInfo and IAFEditable interfaces define the access to the AFBrowserInfo component. These interfaces support the following methods:

[0423] FIG. 20 illustrates a method 2000 for generating a graphical user interface. A form is initially created in operation 2002. The form includes a plurality of attribute rules dictating a manner in which user interface objects are situated thereon. In operation 2004, a plurality of user interface objects are selected. A page is generated in operation 2006 with the selected user interface objects situated on the page in accordance with the attribute rules of the form. JavaScript actions are attached to the selected user interface objects in operation 2008. The JavaScript actions are capable of being executed upon detection of a user action involving one of the user interface objects.

[0424] The user interface objects may include one or more of the following: a push button, a text box, a text area, a radio button, a check box, a drop down, a blank item, a user interface list, and a static table. The user action may include at least one of clicking on one of the user interface objects, changing text in one of the interface objects, exiting a text box of one of the interface objects. Further, the user action involving one of the user interface objects may cause a predetermined event. Optionally, the page may be an HTML page. The following material provides a more detailed description of the above-described method.

[0425] This portion of the present description details the ReTA User Interface (UI) framework design from the perspective of the application developer. The role of this framework is to provide services that generate the HTML code for UI widgets and attach Javascript actions to UI widgets. The UI framework exposes these services through a set of Component Object Model (COM) objects. The application developer uses these UI COM objects and their services through scripting logic added to the application's Active Server Pages (ASP).

[0426] User Interface Framework

[0427] The User Interface framework provides components for generating HTML. An HTML page is generated from a combination of the various UI Components. FIG. 20.1 shows the steps for generating a HTML page consisting of a form 2030 with a TextBox 2032, a DropDown list 2034 and a PushButton 2036.

[0428] The User Interface Framework provides the following services:

[0429] The User Interface Framework implements these services through the following COM objects:

[0430] These components are described in detail in the following sub-portions of the description.

[0431] AFForm

[0432] The AFForm component is used in conjunction with form element widgets to build complex user interfaces. Initially, the application creates an instance of the form component and sets its attributes. Following this activity, the application creates instances of the associated form element widgets and adds them to the form using the form's add method. As another service, the form component provides methods to help align all associated form element widgets properly on the page.

[0433] Methods

[0434] The IAFForm interface defines the access to the AFForm component. This interface supports the following methods, which the developer uses to create a form.

[0435] AFPushButton

[0436] The AFPushButton component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFPushButton component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0437] Methods

[0438] The IAFPushbutton and IAFUIActionItem interfaces define the access to the AFPushbutton component. These interfaces support the following methods, which the developer uses to create a push button form element.

[0439] AFTextBox

[0440] The AFTextBox component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFTextBox component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0441] Methods

[0442] The IAFTextBox and IAFUIActionItem interfaces define the access to the AFTextBox component. These interfaces support the following methods, which the developer uses to create a Text Box form element.

[0443] AFTextArea

[0444] The AFTextArea component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFTextArea component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0445] Methods

[0446] The IAFTextArea and IAFUIActionItem interfaces define the access to the AFTextArea component. These interfaces support the following methods, which the developer uses to create a Text Area form element.

[0447] AFRadioButton

[0448] The AFRadioButton component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFRadioButton component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0449] Radio buttons are used in groups. Because of the complexity of the client side script required in conjunction with the radio button component, the application developer must call the generateRadioButtonScript ( ) method on the AFScriptgenerator object on the page wherever radio buttons are used. This method takes as inputs:

[0450] The name of the form object to which the radio button has been added.

[0451] The name of the radio button group within the form

[0452] The default value the radio button group may pass to the page view if nothing is selected by the user.

[0453] The return value from this method is the generated HTML and Javascript which is written to the client browser within the <HEAD> </HEAD> tag of the page.

[0454] Methods

[0455] The IAFRadioButton and IAFUIActionItem interfaces define the access to the AFRadioButton component. These interfaces support the following methods, which the developer uses to create a Radio Button form element.

[0456] AFCheckBox

[0457] The AFCheckBox component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFCheckBox component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0458] Methods

[0459] The IAFCheckBox and IAFUIActionItem interfaces define the access to the AFCheckBox component. These interfaces support the following methods, which the developer uses to create a Check Box form element.

[0460] AFDropDown

[0461] The AFDropDown component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code). An action object can be attached to a AFDropDown component. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0462] Methods

[0463] The IAFDropDown and IAFUIActionItem interfaces define the access to the AFDropDown component. These interfaces support the following methods, which the developer uses to create a Combo Box form element.

[0464] AFBlankItem

[0465] The AFBlankItem component can only be used in conjunction with a AFForm component (the form's generate method iterates through the generate method for all form element widgets to build the necessary HTML code).

[0466] Methods

[0467] The IAFBlankItem interface defines the access to the AFBlankItem component. This interface supports the following methods, which the developer uses to create a blank item form element.

[0468] AFUIList

[0469] The AFUIList component creates a sophisticated DHTML based single-select list box form widget. The list box widget consists of a fixed headings row and a scrollable set of data rows. The list box widget supports data entry through data row level associated check boxes and text boxes. In addition, action objects can be attached to the list box and are generated in the same way as described for other form components. (Refer to AFHardCodedASPAction and AFJScriptAction for details).

[0470] The list box widget refreshes itself by passing (as parameters) the selected item and the state of all check boxes and all text boxes. The AFUIList view captures the values and updates the state of the list box to reflect the user choice.

[0471] Note

[0472] The sophisticated functionality provided by this widget requires DHTML support. As of this portion of the present descriptions release date (Phase 2), only Internet Explorer 4.0 provides the necessary DHTML services. Therefore, this component is not cross-browser compatible.

[0473] Methods

[0474] The IAFUIList interface defines the access to the AFUIList component. This interface supports the following methods, which the developer uses to create a single select list box.

[0475] AFThumbNailContainer

[0476] The AFThumbNailContainer component generates a set of thumbnail images. The thumbnails are used as iconic pushbuttons. The application developer defines the single click and double click action destinations in the ASP page by coding the JavaScript functions referenced by the AFThumbNailContainer “generate” method.

[0477] Methods

[0478] The IAFThumbNailContainer interface defines the access to the AFThumbNailContainer component. This interface supports the following methods, which the developer uses to create a Thumbnail container.

[0479] AFStaticTable

[0480] The static table component creates a standard HTML table with the parameters set by the developer through scripting logic added to application's ASP.

[0481] Methods

[0482] The IAFStaticTable interface defines the access to the AFStaticTable component. This interface supports the following methods, which the developer uses to create a static HTML table.

[0483] AFHardCodedASPAction

[0484] The AFHardCodedASPAction component adds a user defined automatic navigation action to a UI component. The UI components that support this service include AFPushButton, AFTextBox, AFTextArea, AFRadioButton, AFCheckBox, AFDropDown and AFSelectedList. Attaching the navigation action to a UI item may automatically direct the user to the next page. The next page is identified by the flow control service of the session framework. This means that the developer does not have to specify the page to open. This service also ensures that all changes made to the open pages are capture before opening a new one. The navigation action is triggered when the user causes a defined event on the object. Defined events include clicking on a link or button and changing the text or exiting a text box. The Javascript events are onClick and OnChange.

[0485] The page that represents the target of the action must be entered into the database. The action logic may look to see which activity it belongs to and then look in the database to determine what page to show to the user. An example database entry in the T_AF_FWDestinationforaction table is:

[0486] Methods

[0487] The IAFAction and IAFHardCodedASPAction interface defines the access to the AFHardCodedASPAction component. These interfaces support the following methods, which the developer uses to create a navigational action.

[0488] AFJScriptAction

[0489] The AFJscriptAction component adds a user defined action to a UI Component. The UI components that support this service include AFPushButton, A-FTextBox, AFTextArea, AFRadioButton, AFCheckBox, AFDropDown and AFSelectedList. Attaching a Javascript action to a UI item may call a Javascript function when the action is triggered. Note: The application developer creates the called Javascript function on the correct application's ASP. The Javascript action is triggered when the user causes a defined event on the object. Defined events include clicking on a link or button and changing the text or exiting a text box. The Javascript events are onClick and onChange.

[0490] Methods

[0491] The IAFAction interface defines the access to the AFJscriptAction component. This interface supports the following methods, which the developer uses to create an action.

[0492] AFScriptGenerator

[0493] The AFScriptGenerator component creates the Javascript functions needed by the actions.

[0494] Methods

[0495] The IAFScriptGenerator interface defines the access to the AFScriptGenerator component. This interface supports the following methods, which the developer uses to generate the appropriate Javascript functions.

[0496] AFStyleSheet

[0497] The AFStyleSheet Component creates the Cascading Style Sheet text for the application.

[0498] Methods

[0499] The I AFStyleSheet interface defines the access to the AFStyleSheet component. This interface supports the following method, which the developer uses to generate the appropriate Cascading Style Sheet text.

[0500] FIG. 21 illustrates a method 2100 for software configuration management. First, in operation 2102, software configuration management units are identified. In operation 2104, software configuration management repositories and practices are established for storing work product related to the software configuration management units. A change control process is determined in operation 2106 for implementing change requests relating to the work product. Access to the work product is monitored in operation 2108 by a plurality of users and audits are performed to indicate whether the access to the work product by the users is authorized. Further, training requirements are calculated in operation 2110 by identifying a skill set required for the implementation of the change requests and determining a current skill set.

[0501] As an option, the software configuration management units may be identified based non configuration types, project baselines, and/or naming standards. The software configuration management units may also have characteristics including a name, a modification log, and a release affiliation. Further, the software configuration management practices may include backing up the repositories.

[0502] The change control process may include identifying users authorized to implement the change requests, defining criteria for implementing the change requests, allowing evaluation of the change requests by the users based on the criteria, and monitoring the implementation of the change request. The present invention m ay also optionally include the creation of a training schedule to fulfill the training requirements. The following material provides a more detailed description of the above-described method.

[0503] The ReTA Development Architecture Design includes a set of sub-components that represent all design aspects of the development architecture. The Development Architecture Design Deliverable is used to validate design of the development architecture against the requirements. After it is validated, it may be used as a basis for build and test of the architecture.

[0504] Development Architecture Component Design

[0505] Purpose

[0506] The ReTA Development Architecture Component Design is based on the IDEA framework 2130. See FIG. 21.1. IDEA provides a development environment framework and associated guidelines that reduce the effort and costs involved with designing, implementing, and maintaining an integrated development environment. IDEA takes a holistic approach to the development environment by addressing all three Business Integration components: organization, processes, and tools. In order to accomplish this, several subcomponents 2132 are provided around a central system building 2134.

[0507] The purpose of the development environment is to support the tasks involved in the analysis, design, construction, and maintenance of business systems, as well as the associated management processes. It is important to note that the environment should adequately support all the development tasks, not just the code/compile/test/debug cycle.

[0508] Configuration Management

[0509] The purpose of Software Configuration Management (SCM) 2106 is to establish and maintain the integrity of the components of an application throughout the project's life cycle.

[0510] This includes:

[0511] Comprehensively assessing and evaluating changes to a system after requirements have been agreed upon and commitments established.

[0512] Ensuring that approved changes are communicated, updated, verified and implemented properly.

[0513] Coordinate the project's day-to-day activities and avoid conflicting actions by controlling access to code and repositories.

[0514] The project manager is responsible for the completion of the Project Configuration Management Plan during Design—with the help of the project team. This may:

[0515] Clarify roles/responsibilities for migrations so that they are understood early in the project lifecycle. See FIG. 22, which illustrates the Configuration Management Life Cycle. First, a project study 2200 is created. Development and testing stages 2202,2204 follow the study. Finally, the implementation stage is reached 2206.

[0516] Increase visibility of non-application components (e.g. database, architecture) in Configuration Management to improve quality of delivered products. Many times these are the components that are missed during implementations.

[0517] The ReTA SCM Policy portion of the description can assist engagement executives in creating a project configuration management plan.

[0518] The following table provides a list of the active participants within the change control process. A person may have more than one role or responsibility depending on the size of the technical effort. Also note that the responsibilities are described here at a high level and are not intended to be all-inclusive. Most of the roles are would already exist on an engagement. However, there is one new role that is critical to the CM process, the Source Code Librarian.

[0519] Change Control

[0520] Description

[0521] Change requests as a consequence of changing requirements and changes requested due to nonconformity (or defects), either in the application software, or in the system software must be analyzed, authorized, scheduled, staffed, and tracked in a defined way. What, why, when, and who made a change must be tracked from the point of analysis to the reintroduction of the defective or changed component at the appropriate stage. Change control therefore governs what software component is changed, version controlled, and when it is re-migrated to a given development stage.

[0522] Configuration Management becomes more complex in a component-based development environment as the system is broken down to a greater level of granularity. For this reason, change control processes need to be clearly defined and communicated across the entire engagement team.

[0523] Tool Recommendation

[0524] ReTA Change Tracking Database

[0525] The Change Tracking Database is a Microsoft Access tool. It provides basic functionality of entering, modifying and reporting of system change requests encountered throughout the entire project life cycle.

[0526] Issues Tracking Database

[0527] The Issues Tracking Database is a Microsoft Access tool that is ideal for small to medium sized projects. It provides basic functionality of entering, modifying and reporting of project issues encountered throughout the entire project life cycle.

[0528] Procedures/Standards

[0529] FIG. 23 illustrates the change control ‘pipeline’ 2300 and each phase within the pipeline. The Change Control process can be divided into many different phases.

[0530] They include:

[0531] Log Change Request

[0532] The first phase 2302 of the change control process is to log a change request. Regardless of who initiates a change request and how the change request enters into the engagement work-in-progress pipeline each change request should be logged Change Tracking tool. IT personnel who log change requests should record as much information as possible.

[0533] Change Control Committee Review

[0534] During the second phase 2304, the Change Control Committee (CCC) meets regularly to review the change requests that have been logged to the Change Tracking tool in the past week. The committee also discusses the status of the changes scheduled for migration during the weekly migration windows, reviews the changes already moved to production, and sets the Staging Date for change requests.

[0535] Before each weekly meeting, the Change Control Committee facilitator may generate the following reports:

[0536] Report of the change requests that have been logged to the Change Tracking tool in the past week

[0537] Implementation Report that list all changes scheduled to be implemented

[0538] During the meeting the CCC may:

[0539] Review the new change requests

[0540] Discuss the cross-functional impacts

[0541] Verify that the target implementation date is realistic

[0542] Set the Staging Date

[0543] Update the status of the change requests scheduled to be implemented that week during one of the change windows

[0544] Evaluate the quality metrics of the changes that have been migrated to production and discuss any lessons learned

[0545] Statement of Work/Scope Definition Portion of the Present Description

[0546] During the third phase 2306, depending on the Change Category (Project, Enhancement, or Emergency), a Statement of Work or simple Scope Definition portion of the present description may or may not be required. These portions of the present descriptions both serve to define what the change request entails, and record what is agreed to by the change requester and IT.

[0547] The Statement of Work, which is currently in use sometimes in FIP, is a detailed portion of the present description that describes the work that may be done for the change request. The Scope Definition portion of the present description is a simple portion of the present description of the scope of the change. It can be an email message, a faxed letter, or a brief Microsoft Word portion of the present description.

[0548] The following table shows what is required:

[0549] Once the developer starts working on the Statement of Work or Scope Definition portion of the present description, the developer should set the status of the change request in the Change Tracking tool to “Assigned”.

[0550] The Statement of Work/Scope Definition portion of the present description is sent to the change requester for sign-off. The sign-off needs to be checked-off on the Migration Checklist in the Change Tracking Tool in order to migrate the change to production. This sign-off serves as a quality checkpoint that the work on the change request may meet the business needs of the change requester.

[0551] Analysis & Design

[0552] This phase 2308 is required only for project change requests. For example, the developer may create technical analysis and design specifications portion of the present descriptions. Other impacted groups may create a technical impact statement.

[0553] Code & Unit Test

[0554] In this phase 2310, the developer codes the change request and unit tests the code changes to ensure that it works as designed and that it meets the business needs. The developer should set the status of the change request in the Change Tracking tool to “Development”.

[0555] After the change has been coded and unit tested, the developer should fill in the Resolution field for the change request within the Change Tracking Database. The developer should also fill in the approximate number of hours it took to complete the change request in the Actual Hours field.

[0556] System Test

[0557] This phase 2312 is required for all project change requests and some enhancements. In this phase, the developer tests the change to ensure that the system's functionality works as designed. Furthermore, this test also ensures that the code change did not adversely affect other areas of the current system. This may entail running some pre-defined System Test scripts. For certain change requests, it is important to test the code change against a large volume of data. This may check if the change may handle all the data in the production environment. For any change requests which may impact interfaces both in and out of the target application, it is necessary to test that all the interfaces still work correctly. This may prevent a change request from adversely impacting other systems.

[0558] The developer should set the status of the change request in the Change Tracking tool to “Testing”.

[0559] User Acceptance Test

[0560] In this phase 2314, the most appropriate person, whether it is the requester or a user who may be directly affected by the change, may assume the role of the test administrator. The administrator tests the change request to ensure that it meets the original business need. In some cases, the developer may actually run the test plans that the test administrator creates, and the test administrator may validate the test results. Once the test administrator agrees that the change satisfies all the test criteria, the developer needs to check the user acceptance test sign-off box in the Change Tracking Tool.

[0561] The sign-off is needed to migrate the change to production. This sign-off serves as a final quality checkpoint that the work on the change request meets the business needs of the change requester.

[0562] Fill out Migration Form

[0563] In this phase, the developer goes through a final process before submitting the change request to be moved to production. The developer should move all objects associated with the change request from the testing environment to the staging area.

[0564] In order to move the change to production, the developer needs to complete the Migration Checklist form on the Change Tracking Tool and inform Production Control 2316 by the Staging Date. This form contains all the information about the objects that need to be moved from the staging area into the production environment. This form is a streamlined checklist of all the things that the developers must do in order for Production Services personnel to move the objects to production. Whenever a sign-off checkbox is checked or unchecked, the current user's ID and the current date may be captured by the Change Tracking tool.

[0565] The following Migration Checklist items are required for the different change categories:

[0566] The Ready to Migrate checkbox is used to summarize that all the required sign-offs have been obtained and that the code is ready to be migrated to production. Finally, the developer should set the status of the change request in the Change Tracking tool to “Migrate”.

[0567] Move to Production

[0568] Once Production Services personnel examines a completed Migration Checklist form, they may verify that all objects to be moved into production are in order, and that the change can be moved on the migration night in phase 2318. They may also ensure that all relevant items on the Migration Checklist have been completed. This check serves as the final quality checkpoint before the change goes into production.

[0569] Production Services personnel may move all project and enhancement change requests to the Production environment during prescheduled outages or immediately in the case of an emergency fix. Production Services may then informing all system users what changes have been moved into production.

[0570] Production Services personnel should set the status of each migrated change request in the Change Tracking tool to “Production”. They should also set the Actual Implementation Date to the date the change was moved to production. Measure/Monitor Change in Production Business users and developers should continue to actively monitor the change requests after it is migrated to production during phase 2320. If no problems develop in production due to the change request, the Change Control Committee may confirm that the team leader of the change request should set the status of the change request in the Change Tracking tool to “Closed”. If problems do develop in production, the status should be set to “Re-Open”. The developer is then re-assigned to fix the change request.

[0571] If the change request in production caused other problems to jobs in production, and a new fix is needed, the change request is reopened once again. If the change request caused problems in other jobs that requires modification to the other jobs, then a new change request is created, and the source of the new request is tracked back to the old request.

[0572] The Change Tracking tool contains metrics to track the quality of the change request. The Change Control Committee may assign the Migration Metric and Production Metric values for each change request approximately 35 days after it was migrated into production. If problems occur during the migration of the change request, the Change Control Committee may assign a “Fail” for the Migration Metric. The

[0573] Problem Description should then be completed to explain why this problem occurred. The Lessons Learned should be filled with what lessons can be learned from the experience. If no problems occur, the Migration Metric may be assigned a “Pass”.

[0574] If problems occur in production due to the change request, the Change Control Committee may assign a “Fail” for the Production Metric. The Problem Description and Lessons Learned fields should also be filled with the relevant information.

[0575] Below are the criteria for the Change Control Committee to use in deciding if a change request passed or failed the migration metric or the production metric. A change request may pass if it meets the following criteria.

[0576] Migration Metric Criteria

[0577] Flawless movement of all resources (Active Server Pages, MTS Components, Java Classes, Graphics, Data Model, etc.), from the staging environment to the production environment) is required. (I.e., resource movement must have no negative effects.)

[0578] During implementation activities there must be no unplanned, adverse effect on regularly scheduled batch or online processing, online availability feeds to other systems and reports.

[0579] Production Metric Criteria

[0580] Production online processing and production batch processing must not experience any release-related abends.

[0581] The production implementation may not cause problems, interruptions in service or failures in other areas within 35 days of the initial implementation date. Any release with is backed out due to quality or problems may fail this criterion.

[0582] The change must be delivered when planned. A postponement due to external reasons may not cause the change to fail this criterion. Postponements due to quality or readiness of code must be communicated to the Change Control Committee, project team, and customers at least 3 days prior to the scheduled implementation date.

[0583] Migration Control

[0584] Description

[0585] Migration Control tools control multiple versions of source code, data, and other items as they are changed, tested, and moved from one development environment into another, for example, from development to test and from test to production. The list below provides a list of the various environments and their specific purpose within the project lifecycle.

[0586] With a ReTA/Microsoft-centric environment, a few key issues arise with respect to environment migration. These issues relate to the fact that the application is based on the use of Active Server Pages, Microsoft Transaction Server components and Java Classes.

[0587] Sequence of Events

[0588] To perform the code migration, certain steps should be followed to ensure that users that are currently in the application are not adversely affected. This can be accomplished by performing the migration in the following order:

[0589] Using the Internet Information Server administration utility, monitor the site's number of active users. A count of zero indicates that no clients are currently hitting the site. Shut down the web listener to prevent additional users from connecting to the site.

[0590] Within the MTS Administration tool, shut down all server processes. This cleans up an components that may still be awaiting garbage collection from the Java Virtual Machine.

[0591] If the component interfaces have not been modified, it is possible to copy the new version of the Java Classes directly to the new environment. If the interfaces have been changed, the MTS administrator may need to delete and recreate the individual components within MTS.

[0592] Copy any new web server files (ASP, HTML, graphics, etc.) to the target directories on the web server.

[0593] Restart the web listener to allow users access to the application.

[0594] Module Location

[0595] There are basically three types of modules that get migrated during a ReTA engagement. Web Server files, Application files and database objects.

[0596] Web Server modules include Active Server Pages (ASP), static HTML portion of the present descriptions, graphics or images and JavaScript files. The ASP and HTML portion of the present descriptions may have security restrictions placed on them from within Microsoft Internet Information Server (IIS) and from the Windows NT Server. Security can be set to include individual user accounts, groups/roles, or no security.

[0597] Application Server—Two file types are migrated within application servers, COM Dynamic Link Library's and Java Classes. Both files are created during the application and architecture build processes. The COM DLL's require registration within MTS by inserting them into a MTS Package. In the event that the Web and Application servers are two physically different machines, an export process is required between them to instruct the Web server where the business components physically reside. For more information on the registration and exporting processes refer to the MTS online help.

[0598] In the case of the Java Classes, they need to reside in a directory that is defined within the server's ‘CLASSPATH’ environment variable. For ReTA Phase 1 & 2 development and testing all runtime files were located with C:\ReTA. Therefore the following classpath environment variable was defined on each developer's workstation:

[0599] CLASSPATH=C:\WinNT\Java\Classes;C:\WinNT\Java\TrustLib;C:\ReTA\Architecture;C:\ReTA\Application

[0600] Database Server—These items include tables, views, sequences, triggers, stored procedures and functions, and user/schema information. These items are not necessarily particular to multi-tiered development. However, care should be taken to ensure that architecture tables and other objects are located separately from the application objects.

[0601] Security

[0602] Within the ReTA application model, security is enforced at the Web and Application Servers. In the case of Web server security, access to ASP and HTML files can be restricted using the Access Control List security provided by Windows NT. Security on these objects can be set at the group (role) or individual user levels.

[0603] A component within MTS utilizes role-based security to determine who may or may not have access to a specific COM component. A role is a symbolic name that defines a group of users for a package of components. Roles extend Windows NT security to allow a developer to build secured components in a distributed application.

[0604] For example, FIG. 24 depicts the application of Roles 2400 within the Microsoft Transaction Server Management console 2402. The package labeled ‘ReTA Applications’ 2404 has a single role defined as being able to access it, ‘ReTA User’ 2406. Users that are members of the local ‘ReTA Administrators’ and ‘ReTA User’ Windows NT groups 2408,2410 are allowed to function in the ReTA User capacity defined for this package.

[0605] Due to the security options available at both the Web and Application server levels, care should be taken during code migration to ensure that security settings are consistent and applied correctly to ensure accurate execution.

[0606] MTS Transactions

[0607] Within MTS, every component has a transaction attribute that can be set by the MTS administrator to indicate what level of participation a component has within a transaction. Care must be taken during MTS component migrations to ensure that the correct transactional attributes are set within MTS. The transaction attribute can have one of the following values:

[0608] Requires a transaction. This value indicates that the component's objects must execute within the scope of a transaction. When a new object is created, its object context inherits the transaction from the context of the client. If the client does not have a transaction, MTS automatically creates a new transaction for the object.

[0609] Requires a new transaction. This value indicates that the component's objects must execute within their own transactions. When a new object is created, MTS automatically creates a new transaction for the object, regardless of whether its client has a transaction.

[0610] Supports transactions. This value indicates that the component's objects can execute within the scope of their client's transactions. When a new object is created, its object context inherits the transaction from the context of the client. If the client does not have a transaction, the new context is also created without one.

[0611] Does not support transactions. This value indicates that the component's objects do not run within the scope of transactions. When a new object is created, its object context is created without a transaction, regardless of whether the client has a transaction.

[0612] Tool Recommendation

[0613] Many configuration management tools are available on the market today, some of which provide many features useful for code promotion and management.

[0614] During the ReTA Phase 1 engagement, Microsoft Visual SourceSafe was utilized for it's labeling and source code management capabilities. Additionally, the ReTA Change Tracker database could be utilized for source code migrations that required change management knowledge and approval. In the event that client requires the use of paper or email based migration control, the ReTA Migration Request template can be used.

[0615] Procedures/Standards

[0616] Processes

[0617] The processes that guide development within ReTA engagement environments are represented in FIG. 25, which illustrates an environment migration process 2500. These processes include creating a new application 2502, modifying an existing application, and applying emergency bug fixes 2504. The solid lines represent stages required for new/modified application process. Dashed lines show the path for emergency bug fixes. Note: The term application used here is broadly applied to any managed module or component.

[0618] Processes are defined by stages shown as individual boxes. Through these stages, applications are eventually (or quickly in the case of emergency bug fixes) promoted to production. Stages provide for initiating, managing, securing and coordinating changes to applications.

[0619] The stages for the projects were developed in conjunction with representatives from each development team. It is important to note that the development stages represent the lifecycle of an application, not data. Within each development stage, there can be multiple data sets. For example, within the system test stage, an application team might wish to run several test cycles in parallel. In order to do that and keep the data consistent, a database for each cycle is required.

[0620] The CM process may ensure application modules are promoted through the development stages in a consistent manner. It is up to each application team to decide how to use each stage. For example, the application testing team may want four databases within the system test stage for different types of tests, whereas the assembly testing team may only want two.

[0621] Stage is used to consolidate and verify vendor changes. Depending on the change, it may be migrated to Development or System Test 2506,2508 directly. The order may be dictated by project requirements.

[0622] A very important tenet of the CM process is that an application modification can only be in one stage at any point in time. Consider the example of modulel. Modulel starts out in development. When the development team indicates, the Source Code Librarian moves modulel into system test. As soon as that happens, no changes can be made to module1. Only after module1 is promoted to production 2510 can modifications be made to the module (further enhancements, bug fixes, etc.). The purpose for this rule is to prevent the situation where one developer is modifying a module when that module needs to have a bug fix to continue testing. There is one exception to this rule, emergency fixes.

[0623] When the situation dictates an emergency fix, the module affected needs to be modified immediately. When this happens, the module in question should be fixed within the development stage. When the fix is made, the module may immediately be put back into production. However, the same change also needs to be applied/promoted to the module in system test stage. This may allow modules in system test to always be current with what is in production.

[0624] The CM process depends on change control records (CCR) for tracking changes to the system. A change control record is created for every new module or modification. The CCR is used to coordinate migrations and communicate status for each module in the system. One may see the use of the CCR throughout every process description. The CCR processing system may be automated through Notes.

[0625] Major tasks and responsibilities define each stage of a process and are covered in the pages that follow. These tasks and responsibilities are not intended to be a development methodology. Any references to deliverables and/or portion of the present descriptions is informational only and provided to help anchor an already existing development methodology. However, specific deliverables and portion of the present descriptions required for the change management process are required and may be highlighted.

[0626] Development/Unit Test

[0627] Development team checks required application source code out of source code control. See FIG. 26, which illustrates a Development/Unit test 2600 for existing applications. Note: In the event that this is a new application, the developer may use the appropriate template from source code control.

[0628] As needed, DBA 2602 checks required database source code out of source code control. Also as needed, DBA works with development team to approve and prepare modifications to development database. All work occurs on developer's workstation using local web and application server processes. Note: A shared web/application may be used for vendor staging.

[0629] Unit testing is ongoing during development. The development team checks modified application source code into source code control. The development team also fills in a change control record indicating which modules have changed. As needed, the DBA checks modified database source code into source code control. A source Code Librarian 2604 verifies/prepares necessary objects for building new applications. Unit test and development is completed. In some cases, a string test may be required. The system test team is notified, such as by e-mail.

[0630] Deliverables from this stage might include:

[0631] Modified or new application

[0632] Modified or new database objects

[0633] Unit test data and output

[0634] CM Deliverables from this stage include:

[0635] A change control record with developer information filled in.

[0636] Assembly Test

[0637] With reference to FIG. 27, an assembly test team 2700 reviews user requirements and prepares validation or test plan. Database modifications are fetched from source code control and applied to an assembly test environment 2702. The Source Code Librarian fetches new application, builds it and copies it into assembly test environment 2704. Validation or test plan is executed pass/fail/deviation. The assembly test team signs change control portion of the present description.

[0638] Deliverables from this stage might include:

[0639] Completed validation or test plan with pass/fail/deviation information.

[0640] CM Deliverables from this stage include:

[0641] A change control record with assembly test information.

[0642] System Test

[0643] System test team reviews user requirements and prepares validation or test plan. See FIG. 28, which illustrates a system test 2800 for existing systems. Database modifications are fetched from source code control 2802 and applied to the system test environment 2804. The Source Code Librarian fetches the new application, builds it and copies it into the system test environment. A validation or test plan is executed pass/fail/deviation. The system test team 2806 signs the change control portion of the present description.

[0644] Deliverables from this stage might include:

[0645] Completed validation or test plan with pass/fail/deviation information.

[0646] CM Deliverables from this stage include:

[0647] A change control record with system test information.

[0648] Production

[0649] FIG. 29 is a flowchart for production of existing applications. The change control record is forwarded to the production operations team 2900 responsible for scheduling changes to production. A promotion to production is scheduled on the production plan 2902. Database modifications are fetched from source code control 2904 and applied to the production environment 2906.

[0650] The Source Code Librarian fetches the new application, builds it and copies it into the production environment. The controlled change-tracking portion of the present description is signed and filed. Electronic copies of all portion of the present descriptions and portion of the present description can optionally be stored in source code control or other portion of the present description storage system.

[0651] Deliverables from this stage might include:

[0652] Application promoted to production.

[0653] CM Deliverables from this stage include:

[0654] A complete change control record with production information.

[0655] Version Control

[0656] Description

[0657] Version Control tools control access to source code as it is developed and tested and allow multiple versions to be created, maintained, or retrieved. For maintenance management purposes, it is desirable to designate one individual team member to function as the source control administrator. Duties for the source control manager would include the administration of source control users and projects, scheduling and performing periodic backups and applying labels to specific versions of the code (for migration purposes).

[0658] Examples of architecture and application source code maintained within the version control process include:

[0659] Tool Recommendation

[0660] Many configuration management tools are available on the market today, some of which provide test data management functionality.

[0661] During the ReTA Phase 1 engagement, two different tools where utilized and evaluated: MicroSoft's Visual SourceSafe™ and Intersolve's PVCS Version Manager™. Both applications are relatively simple use and administer. Visual SourceSafe is preferred for small to medium sized engagements and PVCS Version Manager is preferred for large, enterprise-scale development efforts. For a complete description of the configuration and usage of the Microsoft Visual SourceSafe application as it was utilized on the ReTA Phase 1 engagement, refer to Source Control.

[0662] Visual SourceSafe

[0663] Visual SourceSafe from Microsoft ships with the Visual Studio suite and as such is tightly integrated with the Visual Integrated Development Environments. See FIG. 30, which illustrates a frame 3000 of Visual Source Safe. Check in and check out functions 3002,3004 can be performed from with Visual Basic or Visual J++. Additionally, Rational Rose is also tightly integrated with SourceSafe.

[0664] Additionally, this product provides:

[0665] Easy to use drag-and-drop for file check in and check out

[0666] Historical reporting and impact analysis

[0667] User and project level security

[0668] Archive and restore functionality

[0669] Version ‘Labeling’ for source code migration

[0670] Support for web based applications

[0671] PVCS Version Manager

[0672] PVCS Version Manager from INTERSOLV is the industry standard for organizing, managing and protecting your enterprise software assets. Version Manager enables teams of any size, in any location, to coordinate concurrent development, with secure access and a complete audit trail. See FIG. 31, which illustrates a frame 3100 of PVCS Version Manager I-Net Client.

[0673] PVCS VM Server extends the power of Version Manager to teams enterprise-wide via the Internet and Intranets. An intuitive Web client lets users connect to a secure archive and work interactively, anywhere in the world, while sharing protected, centrally managed software.

[0674] Additional features include:

[0675] I-NET client is simple and easy to use. It supports developers in many locations, working on many platforms

[0676] Organizes and references all project components graphically with a flexible, project-oriented approach

[0677] Use easy drag-and-drop to check files in and out of the system with the check in and check out buttons 3102,3104

[0678] Graphically view project history and see file differences in side-by-side comparisons

[0679] Branch and merge as needed, with automatic alerts of any conflicts

[0680] Automate development processes with event triggers

[0681] Set up projects quickly with online assistants for project configuration, security and customization

[0682] Procedures/Standards

[0683] Build & Integration

[0684] FIG. 32 is an illustration of a Build Source Control Model. During the Build phase of a ReTA engagement, the workstation 3200 of each individual developer should be configured to function independently of other workstations and servers 3202 (except for the development database 3204). This process may require developers to first get an updated version of the application source files in addition to those files be checked out for modifications.

[0685] The benefits of this configuration are:

[0686] Individual development changes do not effect other developers

[0687] Easier debugging and testing

[0688] Different project team members may check out different versions and/or components of the application concurrently. Changes can then be merged later.

[0689] Assembly Test

[0690] FIG. 33 illustrates an Assembly Test phase control model. During the Assembly Test phase of a ReTA engagement, the Source Control Administrator may be responsible for the mass checkout and build of the entire application or architecture. Test workstations 3300 may access a web the app server 3302, which is connected to the source code repository 3304 and the database server 3306.

[0691] To aid in this process, the use of ‘Labels’ within the source code repository is employed to identify specific versions of files and projects. (See FIG. 34, which illustrates Microsoft Visual SourceSafe ‘Labels’ 3400). Labels allow for marking a specific set of files within the repository with a logical name and version. At a later point, it is possible to display the different labels and retrieve the desired version.

[0692] Environment Management

[0693] This portion of the description identifies the miscellaneous application and system-level services that do not deal with the human-computer interface, communication with other programs, or access to information. Environment Management Services identify each component used to perform the operating system services, system level services, application services, and run-time services.

[0694] Systems Management

[0695] In order to maintain an effective and secure infrastructure, System Management procedures are essential in the success of obtaining a stable environment. These systems require tools, utilities and processes that allow administrators to monitor running components and change their configuration. Systems Management involves all functions required for the day to day operation of the ReTA environment (e.g. event monitoring, failure control, monitoring, tape loading, etc.). Regardless of the changes taking place within the Net-Centric environment, Systems Management activities must take place in an on-going manner.

[0696] System Startup & Shutdown

[0697] A comprehensive development environment rapidly becomes sufficiently complex that the startup and shutdown of the environment must be managed carefully, and preferably automated. This is key to ensuring the integrity of the environment. Startup may involve the carefully sequenced initialization of networking software, databases, web servers and more. Similarly, shutdown involves saving configuration changes as needed and gracefully taking down running software in the correct sequence.

[0698] An Uninterrupted Power Supply (UPS) provides a server with power when the AC power fails or is marginal. The UPS may also shut the server down, in an orderly fashion, in the event of a power failure. The UPS may not shut down the server if the power failure is brief.

[0699] The Smart UPS 1400 should be configured with an interface to the server. The recommended interface is the serial port B (COM2) on most servers. PowerChute Plus 5.0 software from American Power Conversion is the recommended choice. The basic purpose of PowerChute Plus is to safely shut down an operating system and server in the event of a power failure. To do this properly, PowerChute Plus needs the UPS to provide battery power to the system while PowerChute shuts down the system. This is where the correct sequencing of Events becomes important. Clear and accessible portion of the present description of startup/shutdown procedures Automated startup/shutdown process that rarely requires manual intervention A product that has remote power on reset capabilities

[0700] Backup and Restore

[0701] The incremental value of the daily work performed on the development project is high. This investment must be protected from problems arising from hardware and software failure, and from erroneous user actions and catastrophes such as fires or floods. The repositories and other development information must therefore be backed up regularly. Backup and restore procedures and tools must be tested to ensure that system components can be recovered as anticipated. The large volumes of complex data generally require automation of backups and restores.

[0702] The advent of Netcentric technologies has introduced an increase in media content that requires storage. The environment may support a high volume of media files, which must be considered in the backup/restore plans. Storage capacity planning should allow for the typically increased size of these file types.

[0703] As the amount of storage may grow significantly over time on a large project, the hardware requirements may increase. Sufficient room for growth should be planned when selecting the tools and hardware. Switching tools and hardware can be problematic due to lack of upward compatibility (DDS-DLT, various tools etc.).

[0704] The time required for backups must also be considered. Usually the number of hours without development per day decreases over time and if backups can only be performed when no user is logged in, this might become a problem. It is generally the case that the project may benefit from buying the fastest and largest backup hardware/software it can afford.

[0705] Storage Management

[0706] ReTA may implement an automated tape management system that provides location/retention special handling, file integrity and data protection.

[0707] Archiving

[0708] Archiving can be particularly useful to safeguard information from previous versions or releases. More generally, it is used to create a copy of information that is less time-critical than the current environment at a given time. Archiving may be performed to a medium, which is different from the backup medium, and may involve other tools, which, for example, provide a higher compression ratio.

[0709] Performance Monitoring

[0710] Performance Management ensures that the required resources are available at all times throughout the distributed system to meet the agreed upon SLAs. This includes monitoring and management of end-to-end performance based on utilization, capacity, and overall performance statistics. If necessary, Performance Management can adjust the production environment to either enhance performance or rectify degraded performance.

[0711] Operating System

[0712] Windows NT may function as the ReTA Phase 1 Development Environment operating system, handling Environment System Services such as multi-tasking, paging, memory allocation, etc.

[0713] System Level Services

[0714] The Windows NT Domain Controller allows users and applications to perform system-level environment services such as a login/logoff process for authentication to the operating system; enforced access control to system resources and executables; and access to the local or remote system's user or application profiles.

[0715] Application Services

[0716] The ReTA Phase 1 Frameworks may perform application Security Services, Error Handling/Logging Services, State Management Services and Help Services within the application.

[0717] State Management

[0718] State Management Services enable information to be passed or shared among windows and/or Web pages and/or across programs. In Netcentric environments, the HTTP protocol creates a potential need for implementing some form of Context Management Services (storing state information on the server). The HTTP protocol is a stateless protocol. Every connection is negotiated from scratch, not just at the page level but for every element on the page. The server does not maintain a session connection with the client nor save any information between client exchanges (i.e., web page submits or requests). Each HTTP exchange is a completely independent event. Therefore, information entered into one HTML form must be saved by the associated server application somewhere where it can be accessed by subsequent programs in a conversation

[0719] Security Services

[0720] ReTA implements Application Security through the ReTA Session and Activity frameworks. The Session framework provides “Session level Page access authorization”, “User identification” and “session timeout” services. The Activity framework provides “Activity level Page access authorization”.

[0721] Error Handling/Logging Services

[0722] Error Handling Services support the handling of fatal and non-fatal hardware and software errors for an application. An error handling architecture takes care of presenting the user with an understandable explanation of what has happened and coordinating with other services to ensure that transactions and data are restored to a consistent state.

[0723] Logging Services support the logging of informational, error, and warning messages. Logging Services record application and user activities in enough detail to satisfy any audit trail requirements or to assist the systems support team in recreating the sequence of events that led to an error.

[0724] Runtime Services

[0725] The ReTA Phase 1 Development Environment may use the Microsoft Transaction Server and the Microsoft Java Virtual Machine as a Run-Time Environment System Service. This affords a layer of abstraction between the applications and the underlying operating system.

[0726] Problem Management

[0727] Problem Management tools help track each system investigation request—from detection and portion of the present description to resolution (for example, Problem Tracking, Impact Analysis, Statistical Analysis). Several problem management software packages are available from a variety of vendors.

[0728] Tool Recommendation

[0729] SIR Workbench

[0730] The SIR Workbench is another Microsoft Access tool that was developed for small to medium sized projects. It provides basic functionality of entering, modifying and reporting of architecture and application problems encountered during the testing and release phases of the project life cycle.

[0731] Visual SourceSafe

[0732] Visual SourceSafe (VSS) from Microsoft ships with the Visual Studio suite and as such is tightly integrated with the Visual Integrated Development Environments. One of the features provided by VSS is the ability to search through the source code for given text strings. This is useful for performing impact analysis.

[0733] Security Management

[0734] Security Management tools provide the components that make up the security layer of the final system, and may provide required security controls to the development environment. While some of these tools may be considered as nothing more than security-specific Packaged Components, many are an integral part of the development environment toolset.

[0735] Database

[0736] Development Database security may be minimal. Database User IDs may be setup to grant user-level security. The engagement Database Administrator (DBA) may have a logon to allow for full permissions. Otherwise, a Developer ID may allow read/write access and a Core User ID may allow for read access only.

[0737] Network

[0738] A Windows NT Group created specifically for the engagement may protect the Development shared file folder and subsequent sub-folders (ex ‘ReTAArch’). Project members individual network accounts may be added to the Domain Group ensuring access. Local network administrators may be responsible for the creation and maintenance of individual and group account information.

[0739] Application Server

[0740] The application server has two forms of security: Static security and dynamic (context dependent) security.

[0741] A Windows NT group may be created for each Role in the completed application (e.g. Customer, Manager). Microsoft Transaction Server's integrated Windows NT security allows the developer to determine the security rights for each component. The dynamic, context dependent security is implemented by the developer using the Event Handler framework for the logging and display of errors to the user.

[0742] Web Server

[0743] The web server has static security for each page and security to maintain control of the flow between pages. The static security uses the Windows NT group for each user role to restrict access to each page. For the flow control, the developer uses the Session framework to restrict the ordering of page requests. The allowed ordering of pages are entered into the Session database tables.

[0744] Systems Building

[0745] System Building tools comprise the core of the development architecture and are used to design, build, and test the system.

[0746] Analysis & Design

[0747] The BI Methodology has several application development routes that apply to different development scenarios. Routes currently exist in the methodology for custom and packaged application development. Component development is among several routes to be developed. Until the component development route is completed, component-based projects should be planned using a combination of BI Methodology and ODM task packages. In general, BI Methodology should be used for all tasks that are independent of a specific technology. For example, tasks related to business modeling, user interface design, training development, package selection, and product testing should all be taken from BI Methodology rather than ODM. These technology-independent tasks typically occur early (business modeling, solution strategy, and requirements gathering) and late (product testing through deployment) in the project.

[0748] ODM content should be used for all tasks that are related to component and object development. In addition, ODM is the primary source for those tasks related to obtaining characteristics associated with component- and object-based development (such as flexibility and reuse). When using ODM task packages, take care to ensure that one consider how they link with the other elements of business integration (such as human performance).

[0749] Data Modeling

[0750] Description

[0751] Data Modeling tools provide a graphical depiction of the logical data requirements for the system. These tools usually support diagramming entities, relationships, and attributes of the business being modeled on an Entity-Relationship Diagram (ERD). Several techniques have evolved to support different methodologies (e.g., Chen, Gane & Sarson, and IDEF).

[0752] As systems are often built on top of legacy databases, some data modeling tools allow generation of an object model from the legacy database data model (DDL). By understanding the E-R diagram represented by the database, it is easier to create an efficient persistence framework, which isolates business components from a direct access to relational databases. Caution is required, however, as the resulting model is at best only partial, as an object model has dynamic aspects to it as well as static relationships, and may not correctly reflect the analysis performed in the problem domain.

[0753] When a component or object-based approach is used, data modeling is not performed. Rather, the object model represents both the data and the behavior associated with an object. In most systems, relational databases are used and the object model must be mapped to the data model. Standard mechanisms for mapping objects exist.

[0754] Tool recommendation

[0755] Visual Studio

[0756] Microsoft's Visual Studio 6.0 includes a database diagram tool that helps developers visualize structures of tables and relationships within a relational database. See FIG. 35, which illustrates a Database Diagram 3500 within Visual Studio 3502. Using this project within Visual Studio it is possible to, for example:

[0757] Connect to existing Oracle 7.33+ or SQL Server 6.5+ databases.

[0758] View, print and modify existing database objects including table attributes and properties, views 3504, columns, indexes, relationships, procedures 3506 and functions 3508.

[0759] Create new database objects.

[0760] Generate SQL scripts for schema creation and update.

[0761] Version control schema information using Visual SourceSafe.

[0762] Visual Studio

[0763] Additionally, Rational Software's Rational Rose 98 provides Oracle8 data modeling functionality including schema analysis, SQL/DDL generation, reporting and editing. For a complete description of the product and its features visit the Rational Rose Website at www.rational.com.

[0764] Performance Modeling/Management

[0765] Description

[0766] The performance of a system must be analyzed as early as possible in the development process. Performance modeling tools support the analysis of performance over the network. A simple spreadsheet may be suitable in some well-known and understood environments, but dedicated performance modeling tools should be considered on any project with high transaction volumes or complex distributed architectures involving several platforms.

[0767] In the case of Internet-based applications, as the Internet is not a controlled environment, performance modeling is limited to those components within the domain of the controlled environment (i.e. up to the Internet Service Provider). However, in the case of intranet-based systems, where the environment is controlled from end-to-end, performance modeling may be performed across the entire system.

[0768] Performance modeling for components involves the analysis of the projected level of interaction between components and the level of network traffic generated by this interaction. It is important for performance reasons that communication between components is minimized, especially if these components are distributed.

[0769] Tool recommendation

[0770] Visual Quantify

[0771] Tivoli

[0772] Sniffer Basic

[0773] Application Expert

[0774] Object Modeling

[0775] Description

[0776] An object model usually contains the following deliverables:

[0777] Class Diagram (1 per functional area or 1 per component)

[0778] Class Definition (1 per class)

[0779] Class Interaction or Sequence Diagram (1 or more per scenario/workflow)

[0780] Class State Transition Diagram (1 per Class with complex state)

[0781] Tools such as MS Word, MS PowerPoint, ABC Flowchart (MicroGrafix), may be used to produce these deliverables. See FIG. 36 illustrating Object Modeling 3600 within Rational Rose 3602. Specific modeling tools do exist, however, and provide advantages such as cross referencing (for example, are all the methods used in the Interaction diagrams described in the class definitions?), automatic propagation of changes to other diagrams, generation of reports, and generation of skeleton code.

[0782] However, some tools have problems with:

[0783] Usability and stability

[0784] Single users or small numbers of concurrent users

[0785] Proprietary repositories (usually file-based, rather than DB-based)

[0786] Support of extensions/customizations

[0787] As well as providing the usual editing and graphical functionality, a good modeling tool should:

[0788] Interface with a repository (to support versioning)

[0789] Support multiple users

[0790] Generate code from the design

[0791] The industry standard to represent the object model is UML notation (adopted by OMG).

[0792] Tool Recommendation

[0793] Rational Rose 98

[0794] Visio 5.0

[0795] Visual Modeler 2.0 (Only valid for VB and VC++)

[0796] Component Modeling

[0797] Description

[0798] Component modeling can mean either designing components from scratch, or customizing and integrating packaged software. No specific component modeling tools exist, and current object modeling tools only provide limited support for components (e.g. for packaging related classes together). Class packages can be used to separate the object models for different components, with a separate class package(s) for the component model. This approach, however, is not enforced by current modeling tools, and requires project naming and structuring standards.

[0799] When component modeling is being performed using existing packaged software, some form of reverse engineering or importing is required from the modeling tool to capture the existing design.

[0800] During component design, the partitioned component model is designed, which defines physical interfaces and locations for components. It is important for performance reasons that communication between components is minimized, especially if they are distributed.

[0801] Tool Recommendation

[0802] Rational Rose 98

[0803] Visio 5.0

[0804] Visual Modeler 2.0 (Only valid for VB and VC++)

[0805] Application Logic Design

[0806] Description

[0807] Application Logic Design tools graphically depicts an application. These tools include application structure, module descriptions, and distribution of functions across client/server nodes.

[0808] A variety of tools and techniques can be used for Application Logic Design. Examples are structure charts, procedure diagrams (module action diagrams), and graphics packages to illustrate distribution of functions across client and server.

[0809] Application Logic Design functionality is also provided by a number of Integrated Development Environments (IDE).

[0810] With component-based development, Application Logic Design is performed through object and component modeling. The functionality is captured in use cases, scenarios, work flows and/or operations diagrams along with interaction diagrams/sequence diagrams. These are usually produced using MS Word, MS PowerPoint, ABC Flowcharter (Micrografix), or an object modeling tool.

[0811] Tool Recommendation

[0812] Rational Rose 98

[0813] Visio 5.0

[0814] Database Design

[0815] Description

[0816] Database design tools provide a graphical depiction of the database design for the system. They enable the developer to illustrate the tables, file structures, etc. that may be physically implemented from the logical data requirements. The tools also represent data elements, indexing, and foreign keys.

[0817] Many data design tools integrate data modeling, database design, and database construction. An integrated tool may typically generate the first-cut database design from the data model, and may generate the database definition from the database design.

[0818] With an object-based or component-based solution, the data-modeling task changes. In most cases, relational databases are still used, even where there are no dependencies on legacy systems. As there is an ‘impedance mis-match’ between an object model and a data model, a mapping activity must be undertaken. There are standard mechanisms for doing this. There are also tools on the market which allow the mapping of classes to relational tables, and which generate any necessary code to perform the database operations.

[0819] There is a tendency (especially when dealing with legacy systems) to treat data models and object models the same. It is important to recognize that at best, the data model represents only the static part of the object model and does not contain any of the transient or dynamic aspects. The physical data model may also change significantly (for DB optimization), further confusing the issue.

[0820] There can be performance problems with objects mapped to a relational database. In a worst case scenario, an object can be spread across many tables, with a single select/insert for each table, and as each object is loaded one by one, the performance becomes very poor. Some tools provide lazy initialization (only loading the parts as they are needed) and caching (minimizing DB hits).

[0821] The current trend seems to be for object-relational databases, with vendors such as Oracle adding object features to their core products. Although the support provided at the moment is limited, it is likely that in future versions Java or C++ classes may be able to interface directly.

[0822] Tool Recommendation

[0823] Rational Rose 98 (Only valid for Oracle 8)

[0824] ERwin

[0825] Presentation Design

[0826] Description

[0827] Presentation design tools provide a graphical depiction of the presentation layer of the application. Tools in this category include window editors, report editors, and dialog flow (navigation) editors. Window editors enable the developer to design the windows for the application using standard GUI components. Report editors enable the developer to design the report layout interactively. Placing literals and application data on the layout without specifying implementation details such as page breaks. The majority of these tools generate the associated application code required to display these components in the target system.

[0828] Using the dialog flow (navigation) editors, the developer graphically depicts the flow of the windows or screens. The Control-Action-Response (CAR) diagram is a commonly used technique for specifying the design of GUI windows.

[0829] The majority of Netcentric systems use Web browsers to provide a common cross-platform user interface. Presentation design for this type of environment therefore entails the generation of HTML pages, often with additional components (JavaScript, 3rd party ActiveX controls, Plug-ins) providing enhanced functionality or media content. Many tools are currently available for designing and creating web content, although HTML remains the common denominator, at the very least as a placeholder for the content.

[0830] In the case of systems published on the Internet, defining the target audience is less straightforward than in traditional systems, but equally important. Having a good understanding of the intended audience may be a big advantage when thinking about user interaction with the system, and therefore, the presentation layer of the system.

[0831] Within a ReTA based application, three types of web pages that are available include:

[0832] Tool Recommendation

[0833] Microsoft Visual Studio 6.0

[0834] Rational Rose 98

[0835] Visio 5.0

[0836] Visual Modeler 2.0 (Only valid for VB and VC++)

[0837] Packaged Component Integration

[0838] Description

[0839] Packaged components are generally thought of as third party applications or services that provide ready-made business logic that is customizable and reusable. Additionally, legacy applications can be included in these discussions when there is a desire to reuse portions of or an entire pre-existing application. One of the benefits of component-based systems is the ability to separate the component interfaces from their implementation. This simple feature can help enormously with access to both third party components and legacy applications. The concept of putting an object or component interface on a non-object piece of software is called ‘wrapping.’

[0840] There are several arguments for putting a wrapper around an third party application or legacy system instead of custom building or replacing the functionality that they provide:

[0841] The wrapped component may provide functionality that requires deep technical expertise or knowledge to develop. (e.g. hardware drivers, EDI applications)

[0842] The provided functionality may only be temporary. With a wrapper in place, the underlying implementation may change without affecting the consuming application.

[0843] The wrapped component can now be reused within additional applications without additional effort.

[0844] Wrapping can take considerably less time and effort than building the third party component or legacy application over again. The more complex the application being wrapped, the greater the cost savings in time and effort.

[0845] Within wrapped components, it is possible to consolidate several existing applications into a single new service. (e.g. customer details from a ERP package as well as from the new system)

[0846] Procedures/Standards

[0847] Pure Component Integration

[0848] Component standards are maturing, particularly in eCommerce Applications. Although plug and play is not yet a reality, more application and ISV vendors are developing component based solutions for the eCommerce market place. Generally, this is the simplest form of integration if leading-edge eCommerce architectures are being deployed.

[0849] Care should be taken to allow for the migration from one vendor to another. To allow for this, the application developer should investigate encapsulating the component within an application wrapper.

[0850] Wrapped Component Integration

[0851] Many of today's vendors provide ActiveX or Java classes that provide a direct component interface into their application or services. Some vendors such as SAP expose component interfaces which can be accessed by ORBs e.g. Microsoft's DCOM connector. The underlying architecture however is not component-based. This is not a problem providing the package provides scalable and robust application execution.

[0852] Another example is the use of Microsoft's COM Transaction Integrator 3700 and the Microsoft SNA Server for NT 3702. These products allow for the wrapping of CICS transactions in COM component stubs 3704 that can be invoked from MTS components. See FIG. 37, which illustrates directly calling a wrapped CICS component 3706.

[0853] Batch and Indirect Integration

[0854] This process of integration relies on the use of Message Oriented Middleware (MOM) to provide asynchronous messaging to and from the packaged application. This can be accomplished using Microsoft's Message Queue (MSMQ) 3800, IBM's MQ/Series 3802 and Level 8's Falcon Bridge 3804 (to provide MSMQ to MQ/Series communication). See FIG. 38, which illustrates indirectly calling a wrapped CICS component 3806.

[0855] Data Integration

[0856] This is the most common form of integration but restrictive because it involves development of duplicated business logic, risks breaking application integrity and causes maintenance overheads.

[0857] Construction

[0858] Construction tools and processes are used to program or build the application: client and server source code, windows, reports, and database. ReTA based development should use a base set of naming and coding standards.

[0859] Tool Recommendation

[0860] Visual Studio 6.0

[0861] Rational Rose 98

[0862] Test

[0863] Testing applications (client/server or NetCentric) remains a complex task because of the large number of integrated components involved (i.e., multi-platform clients, multi-platform servers, multi-tiered applications, communications, distributed processing, and data). The large number of components result in a large number and variety of testing tools.

[0864] Test Data Management

[0865] Description

[0866] Members of the technology infrastructure and data architecture teams are often the ones who create and maintain the common test data. This requires full-time personnel, especially when a large number of test databases must be kept in synchronization. Many of the automated testing tools available on the market today provide test data management functionality.

[0867] At a minimum, vendor or custom applications and processes should be in place to perform the following:

[0868] Database Schema Export & Import

[0869] Individual or Bulk Table Deletion and Population

[0870] Data Refresh/Restore

[0871] Additional functionality may include data generation or conversion, versioning and validation.

[0872] Tool Recommendation

[0873] Many testing tools are available on the market today, some of which provide test data management functionality.

[0874] Procedures/Standards

[0875] The ReTA Component Test Workbook Plan-Prep provides the mechanism for maintaining component test data required during test execution. When creating the test data, all attempts should be made to make the test data reusable.

[0876] Test Data Manipulation

[0877] Description

[0878] There are a few avenues for the manipulation of test data. When considering this function during the component and assembly testing phases consider the following:

[0879] Create test data if the physical data model is stable.

[0880] Use the existing application if it can create valid data.

[0881] Convert production data if the Data Conversion Application and the production data are reliable.

[0882] Tool Recommendation

[0883] If possible, leverage any existing data manipulations that were included with the database suite. Many database vendors provide data management and manipulation applications with their database systems. Additionally, many development packages, including Microsoft Visual Studio™, provide database access and manipulation functionality.

[0884] For data generation, PLATINUM TESTBytes™ is a test data generation tool that connects to your database to create test data for your relational databases. With point-and-click action, one can specify the type of data needed. TESTBytes automatically generates up to millions of rows of meaningful test data, eliminating days or weeks of time-consuming effort and reducing costs.

[0885] Procedures/Standards

[0886] For data conversion, the best approach is to:

[0887] If data is going to be shared with an existing application, attempts should be made to reuse test data from the legacy system.

[0888] Use the existing data store capabilities to extract or massage the data into a format that is easily integrated into the new application.

[0889] Create one-time extract and formatting applications to extract the legacy data, perform formatting and business operations, and import the newly modified data into the new data store.

[0890] The ReTA Component Test Workbook Plan-Prep provides the mechanism for maintaining component test data required during test execution. When creating the test data, all attempts should be made to make the test data reusable.

[0891] Test Planning

[0892] Description

[0893] The test planning function during a ReTA engagement provides an opportunity to define the approaches, tools, environments and process to test the application and its individual components for functional and technical validation. This process is typically assigned to someone with experience in application development using similar technologies as those to be used on the new system.

[0894] Tool Recommendation

[0895] The ReTA Component Test Workbook Plan-Prep provides the mechanism for maintaining and communicating component test information. Component test planning information such as component test cycles and component test conditions are included. Both worksheets are to be completed during the design phase by the designer.

[0896] Test Execution

[0897] Description

[0898] If testing environments have been created, application testing scenarios and scripts should be created to evaluate the application functions as designed. Actual results are compared against expected results portion of the present description with the test conditions. The use of automated testing tools is essential for fast, accurate regression and performance testing. Ensure the tool used for automated testing is easily configured. Also, ensure the scripts can be quickly updated to allow for user interface changes.

[0899] Tool Recommendation

[0900] Component Test Workbook

[0901] The ReTA Component Test Workbook Plan-Prep provides the mechanism for maintaining and communicating component test information. Component test planning information such as component test cycles and component test conditions are included. Both worksheets are to be completed during the design phase by the designer.

[0902] Automated Testing Tool

[0903] There are many automated, web-based testing tools on the market today. Many tools provide record and playback scripting functionality. See FIG. 39 which illustrates RSW eTest Automated Testing Tool 3900. Recommended features include:

[0904] Auto record and playback of test scripts

[0905] Data driven testing

[0906] Easy test modification (many tools have proprietary scripting languages)

[0907] Cross-browser support

[0908] Multi-user simulation for load & performance testing

[0909] Test summaries and reporting

[0910] Procedures/Standards

[0911] In addition to the test planning elements of the CT workbook, component test execution worksheets are also included: component test script, test data, and expected & actual results worksheets. These worksheets are to be completed by the developer during the build phase. These scripts may be used by the developer/tester to execute the individual component tests. In theory, since the steps of the component test are portion of the present description, any developer or tester should be able to execute the test by simply following the steps outlined in the test script.

[0912] Performance Management

[0913] Description

[0914] Performance Management tools support application performance testing. These tools monitor the real-time execution and performance of software. They help to maximize transactions and response time to the end user. They are also useful in identifying potential bottlenecks or processing anomalies.

[0915] Procedures/Standards

[0916] During the automated test execution process, the testing tool may automatically verify the current state of the system (i.e. actual results) against the expected state of the system (i.e. expected results) for each test case defined in the test script. Execution status may be reported through the reporting function of the toolset. In the case of performance or lead testing, the testing tool may provide a summary report including graphic illustrations describing the overall performance of the system.

[0917] Test Results Comparison

[0918] Description

[0919] Whether using automated or manual testing processes, after the completion of each testing cycle it should be clear as to what defects still exist within the system. By comparing actual results with expected results, the application tester and developer can quickly detect design and development errors within the system.

[0920] Tool Recommendation

[0921] The ReTA Component Test Plan-Prep Workbook provides the mechanism for maintaining expected and actual results. The Expected and Actual Results worksheet outlines the expected result for each condition and lists the actual result encountered during the test execution.

[0922] Procedures/Standards

[0923] During the automated test execution process, the testing tool may automatically verify the current state of the system (i.e. actual results) against the expected state of the system (i.e. expected results) for each test case defined in the test script. Execution status may be reported through the reporting function of the toolset.

[0924] Test Coverage Measurement

[0925] Description

[0926] Test Coverage Measurement tools are used to analyze which parts of each module are used during the test. Coverage analyzing tools are active during program operation and provide comprehensive information about how many times each logic path within the program is run. This Test Management and Quality Management tool ensures that all components of an application are tested, and its use is a vital and often overlooked component of the test process.

[0927] Tool Recommendation

[0928] Rational's Visual PureCoverage™ is an easy-to-use code-coverage analysis tool that automatically pinpoints areas of code that code that have and have not been exercised during testing. This greatly reduces the amount of time and effort required to test an entire application and its components, increases the effectiveness of testing efforts by providing insight into overall program execution, and helps ensure greater reliability for the entire program, not just part of it.

[0929] Procedures/Standards

[0930] Test coverage measurement ensures is used to ensure that the entire application or system is completely tested. A manual approach can be applied to ensure that every path of logic within the application is completely tested. To reduce the test preparation time, an automated testing tool that provides this functionality should be leveraged.

[0931] SIR Management

[0932] Description

[0933] SIR Management Tools help track each system investigation request from problem detection through portion of the present description resolution.

[0934] Tool Recommendation

[0935] SIR Management Tools help track each system investigation request from problem detection through portion of the present description resolution. During the testing phases of the engagement, it may be desirable to reuse the SIR tools and processes developed for and used for overall problem tracking SIR Workbench

[0936] The SIR Workbench is a Microsoft Access based tool that has been used on various component and client/server engagements. It provides basic functionality of entering, modifying and reporting of architecture and application problems encountered during the testing phases of the project life cycle.

[0937] Procedures/Standards

[0938] For a full description of the tool and its use, refer to the SIR Workbench.

[0939] Development Architecture Physical Model

[0940] Purpose

[0941] The ReTA Development Architecture Physical Model portion of the description shows the actual components comprising the Development Architecture and their relative location and interfaces. Additionally, the model depicts the platforms on which the components may reside as well as the distribution across the environment. The components in the Physical Model may support a portion of a function or more than one function from the functional model.

[0942] Physical Configuration

[0943] FIG. 40 is an illustration that describes the physical configuration necessary for ReTA development. The development environment was composed of the following hardware and software configurations:

[0944] Build Model

[0945] FIG. 41 illustrates the application & architecture configuration for a typical ReTA Build environment 4100. Each development workstation 4102 should be configured to provide systems management, configuration management and systems building support. In this model, all architecture and application components & services reside on the developer workstation. This allows the developer to design, build, debug and test independently of other developers.

[0946] Assembly Test Model

[0947] FIG. 42 illustrates the application & architecture configuration for a typical ReTA Build environment 4200. In this model, the testing workstation 4202 is configured to provide presentation services by way of an HTML 3.2 & JavaScript 1.2 compatible web browser. The web/application server 4204 is configured with the current assembly test versions of ReTA application and architecture components.

[0948] Security Management Architecture

[0949] Overview

[0950] The ReTA Security Management Architecture includes security issues, concerns and recommendations associated with Net-Centric Computing. The Security Management Architecture deliverable is used to illustrate the potential security implications. The ReTA Security Management Architecture portion of the present description is divided into three main portions in order to encompass security requirements for Development, Execution and Operation Architecture.

[0951] Development Architecture Security Management

[0952] Preserving security of information as it travels across the Internet, or even your own intranet, has become increasingly complex. The Internet is a public resource accessible worldwide, and is built on a foundation of inherently insecure technologies. Information which is available across the Internet is becoming more and more sensitive as business continue to deploy to the Internet. Implementing effective security in our new Net Centric computing environments presents some challenges without a doubt, but not insurmountable ones. By designing security into your Net Centric solution, and implementing the appropriate application, infrastructure, and procedural controls, security can be appropriately aligned with business risk. See FIG. 43, which illustrates an IDEA Framework 4300 with components in scope ReTA Phase 1.

[0953] Everyone today is talking about Net Centric security. Keeping up with all of the security issues surrounding Net Centric technologies is more than a full time job, it has become a full time obsession. When designing a Net Centric solution, security is always at the forefront of everyone's mind, but what are the important things to consider? How do I know that I've addressed all the appropriate questions? How may my solution affect the security of my computing environment? How may that security impact my business? This paper may answer these questions, providing an overview of “things to consider” when designing a Net Centric solution. It may not attempt to provide detailed technical solutions, but it may navigate one to the right path to find that information.

[0954] Impacts

[0955] Security Impacts

[0956] There is no question that the trend toward Net Centric computing may impact the traditional computing environment. Systems are much more distributed, and applications are being used by a larger number of people to reach new objectives every day. Along with all of these changes come significant security impacts. So what is it about Net Centric computing that can lead to security problems?

[0957] First of all, the Internet is a public resource. Traditionally our computer systems were only used or accessible by a small audience which we knew and could control. Now our computer environment is linked to the Internet, which is accessible to virtually anyone who has the time and the money to invest. While most of these people have good intentions when it comes to using your resources, some have an evil purpose. Threats can come from many sources: teenage hackers, spies from other companies, even curious people who inadvertently cause damage. The public nature of the Internet also increases the ability of these malicious individuals to collaborate and recruit others, thus strengthening their cause. The Internet contains a wide variety of information that people are interested in, from public information resources to sensitive customer databases.

[0958] In addition to the very lure of interesting information on the Internet, there are vulnerabilities inherent to Internet technologies which can make that information more easily compromised. In fact, the original intent of the Internet was to share information, not to be used as a business tool. Security weaknesses are widespread and present in nearly all Internet related technologies. The very communication protocol used, TCP/IP, was designed with few provisions to protect the security of the data packet.

[0959] Of course, security problems weren't created with the Internet; many of our standalone computer systems have the same types of security exposures. However, the global nature of the Internet now transfers these insecure services rapidly around the world. Weaknesses that before could only have been exploited by a small number of users with access to the system, can now be exploited by virtually anyone. These breaches are also now publicized to the entire Internet community. For example, many high profile web pages have recently been attacked, including NASA, the Department of Justice, and the CIA. Although these attacks were limited to vandalizing their web pages, (as far as we know), the publicity generated from the attacks has raised questions about the security of their systems in general. Internet access not only made these attacks possible, it also publicized the attack around the world.

[0960] This rapid transfer of information raises an issue regarding the dynamic nature of today's environment. The Net Centric environment includes traditional long term users of systems, as well as one time users who require instant logons and immediate connections. Security may stand in the way of business objectives if it is not flexible and dynamic enough to adapt to ever-changing business and technology requirements. In addition, new threats and risks evolve quickly in the Net Centric environment, and security programs may become ineffective and obsolete if not reviewed and updated regularly.

[0961] The Internet also brings with it a whole new set of legal issues, and topping the list are potential privacy implications. Businesses can now track your every movement on the Internet, from your email and IP addresses, to each site you surfed to and which ad one clicked. Does this constitute an invasion of your privacy? One may have freely given other businesses sensitive information aboutonerself, such as one's credit card number or one's social security number. To what lengths must that business go to in order to protect that information? If and when that information is compromised, who is liable? What is the penalty for breaking into a computer to which one is not granted access? What if one just looks around and does not cause any damage? These questions are just beginning to be addressed as cases are introduced in court and legislation is passed in Congress. But we are a long way from finding all the answers.

[0962] All of these security concerns have been widely publicized in the media, to the extent that the public now perceives security as a major issue on the Internet. These concerns may have the effect of impeding the success of an Internet solution, or even delaying a business decision to deploy to the Internet. Even as new technology emerges to solve many Internet related security problems, public opinion, legitimate or not, may still impact the success of any Internet solution.

[0963] Application Impacts

[0964] There are obviously a myriad of security implications from the move towards Net Centric computing. The Internet, and the growth of local intranets, has made our computing environment look much different today than it did five years ago. So what does this mean? When designing a business solution in this new environment, security implications have to be considered at every step of the process. Application design presents a specific set of security related challenges.

[0965] Application Design

[0966] The underlying theme in application design, from a security perspective, is to design in security from the beginning. Talk to Information Security representatives, and even internal auditors early on, and get their approval for your design. This can save retrofitting costs in order to achieve an adequate level of security, and may also end up giving one a more secure solution by integrating security right into the design of the application.

[0967] Once one is considering security, what is the best way to design it into your application? Even the most pompous security expert should recognize that your primary goal is not to build an application with really good security, it is to build an application that achieves a specific business goal. The challenge is to integrate security into that business goal so that it may not impede efficiency. Often security is tacked on a the last minute and impedes performance in the application, such that users may bypass security if possible, and curse it if not possible.

[0968] The next step is to consider the basic parameters of your application and how security applies to each of them.

[0969] Who needs access to the application, i.e. what is your user group? Is it all Internet users or some authorized subset? Does one only have one type of user or are multiple levels of authorization required?

[0970] Where may your application may be accessed from, the Internet or your intranet? How much control do one has over the security of that location and PC?

[0971] What is the confidentiality of the information your application may be transmitting or accessing? What implication would there be if that information fell into the wrong hands?Once these questions have been answered one can begin to choose the appropriate tools or mechanisms to provide an adequate level of protection.

[0972] When designing your application, consider implementing the minimum level of functionality and authority required to meet your business goal. This is often contradictory to basic instinct when designing a new solution, but consider the potential implications. If your application does not need to allow users to execute arbitrary operating system commands, don't let it. If your application does not need to run as root or supervisor, don't let it. Designing for minimum functionality may obviously be a tradeoff between business and security benefits, but in general, it is better meet the level of authority required, not exceed it.

[0973] Security Integration

[0974] When designing security into your application, remember that one may not have to re-invent the proverbial wheel. Most information security groups may have corporate security strategies with which one can integrate. For example, an enterprise wide authentication scheme may be in use, with which one can integrate for remote access. Or there may be a single sign-on product with which your application may need to be compatible. Even if there is not a corporate security strategy in place today, consider the direction that the company is moving toward, and provide for future integration if possible.

[0975] Auditing and Logging

[0976] Application auditing and logging is often overlooked because it is less than glamorous, but it does provide security administrators with a crucial tool for monitoring use of an application. Good logs should be searchable for known or suspected patterns of abuse, and should be protected from alteration. Logs can monitor a virtual myriad of data, including access times, user IDs, locations from where the application was accessed, actions the user performed, and whether or not those actions were successfully completed.

[0977] Web Browser Security

[0978] While web browsers may not be exactly part of your application design, they are intimately related to many of the design decisions one may make, such as the programming tools one uses and the format your user interfaces take. The application programming tools portion of the description, above, discussed some possible ways a Web browser can exploit application security flaws. There are also design anomalies within the Web browsers themselves which can be exploited. Microsoft has fixed many of these flaws in their newest release of Internet Explorer, but their older versions are still vulnerable. This type of problem demonstrates that when considering integration with the major commercial web browsers, it is important to monitor news releases for recent security flaws. One may want to consider requiring your users to use the latest, most secure version of their Web browser if possible.

[0979] Infrastructure Impacts

[0980] Today's Net Centric computing infrastructure requires a complex mix of operating systems, web servers, database servers, firewalls, management tools, routers, and underlying network components. Each different component of this infrastructure has specific security considerations which need to be addressed. These requirements are always growing and changing, as are the solutions which can be implemented. When designing this complex infrastructure, similar to designing an application, security should be considered early on in the process.

[0981] Operating System Security

[0982] It is crucial to choose an operating system (OS) which can provide adequate security; and once chosen it is just as important to configure that OS in a secure manner. Any OS must address the same basic security questions, such as restricting permissions for what each user can access, limiting what actions each user can perform, providing monitoring and logging of user access, and restricting what services are available. Windows NT is without exception.

[0983] NT has been publicly available for over three years now, and while security issues may have appeared, fresh out of the box NT is a very secure OS. But there are still steps to take to improve this security. Configure your OS securely from the start, implement tools where appropriate, and continue to monitor the bulletin boards and vendor announcements for problems as they come up.

[0984] Web Server Security

[0985] Many of the OS security guidelines apply to web servers as well. Regardless of your choice of web server, it is important to configure that server securely. The server should be set to run under an ID which is used only by that web server, and never as root. Directory permissions should be assigned according to a need to know philosophy, and your portion of the present description root (where published information is stored) should be different from your server root (where server binaries and configuration files are stored.)

[0986] In addition to these somewhat generic operating system security tips, there are several features which are specific to a web server which could create security exposures. In general, if one doesn't need a feature, don't turn it on; and if one does need a feature, make sure the potential security risks are understood. Server side includes allow HTML authors to place commands inside their portion of the present descriptions that cause output to be modified whenever that portion of the present description is accessed by a user. Hackers can take advantage of server side includes if they are able to place arbitrary HTML statements on your server and then execute them.

[0987] Legacy System Integration

[0988] In order to truly take advantage of the power of Net Centric computing, new technologies need to be mixed and integrated with existing systems. More sophisticated intranets and extranets often require on line transactions or database inquiries of legacy environments which may not have the level of granular control required for secure access. In some cases, it may be possible to mirror the information from an existing platform to a more securable web server or database. This may protect the integrity of your sensitive systems while still providing the access for your on-line transactions. If a mirror system is not possible, a thorough audit should be performed of the security of your legacy system, to ensure that one is providing access to only those resources which are allowed.

[0989] Network Security

[0990] Now one has chosen your access control mechanisms, configured your OS, and it's time to connect to your network. This action may strike fear into the heart of many network and system administrators, because this may create one more way network security can be compromised. Contrary to popular belief, it is possible to establish and maintain effective network security. The first step is to understand what all of your network components are, and how they are connected. By examining your network topology, one can determine where all of your access points are, and (hopefully) the way that access to them is controlled. If remote access directly into your network is required, the use of your modems must be appropriately restricted. Don't rely on knowledge of the phone number or a single static password as effective security controls.

[0991] In addition to identifying one's access points, one should examine the path that one's traffic follows, and determine if that path is vulnerable to snooping and attack. One of the more infamous hacker gangs, the Masters of Deception, once infiltrated a major telecommunication provider's data network, and had access to the corporate secrets of hundreds of companies as information was sent across the lines. Even if your data is just traveling over internal links, a network management station could still be monitoring traffic, or a sniffer could illicitly be installed anywhere along the line. There are two major security controls that mitigate these risks: firewalls to restrict who can access your secure network, and encryption to protect your data as it's sent over an insecure network.

[0992] Firewalls

[0993] Firewalls are often thought of as THE answer to network security. There is a common misconception that purchasing and installing the “best” firewall available may automatically protect your network from the Internet. This is not necessarily true. In fact there are many factors to consider when choosing a firewall, and when placing and configuring that firewall in your environment. First of all, consider the type of network connection your are trying to protect. Firewalls are not only used to separate your intranet from the Internet, they can also be used to segregate a particularly sensitive or particularly insecure area of your intranet from the rest of your network. Depending on the services one wants to provide your users and what risk one is willing to accept, your choice of the “best” firewall implementation may change.

[0994] There are many different components of the firewall architecture to consider. Packet Filtering Systems selectively route packets between internal and external hosts by either the type of packet, the originating host address, or the target host address. Packet filtering is typically implemented on a specific type of router called a screening router.

[0995] Proxy Services are specialized applications or server programs that run on a firewall host, which take users' requests for Internet services (such as ftp and telnet) and forward them, as appropriate according to the site's security policy, to the actual services. The proxies provide replacement connections and act as gateways to the services. For this reason, proxies are sometimes known as Application Level Gateways.

[0996] A Bastion Host is typically a dual-homed gateway with one interface on the internal network and one on the external network. It can be used to run proxy services or perform stateful packet inspection. The bastion host typically acts as the main point of contact for incoming connections from the outside world, including email, ftp and telnet requests, and DNS queries about the site.

[0997] A Perimeter Network or DMZ refers to a small network between your internal network and the Internet which provides an extra layer of security. Any publicly available resources one provides, such as a Web server or an ftp server, may typically be located in the DMZ, and restricted from one's internal network by a firewall machine or bastion host.

[0998] There are many commercially available firewall products that provide some or all of these features. Which product or firewall configuration is right for one may depend on what one's network looks like, what one is trying to protect, and what your users require.

[0999] Event Monitoring

[1000] Before an incident can be responded to, it must first be detected. In the Net Centric environment, your firewall, routers, web servers, database servers, applications, and network management tools must be monitored to ensure they are working correctly and no violations have occurred. Monitoring packages can be configured to take different actions on a series of specified events, such as sending an email message if a log fills up, flashing an icon on a system administrator's screen if someone's user ID is disabled, or paging a network administrator if a link to the ISP goes down. Once this initial notification takes place, there should be escalation procedures to decide whom to notify next. For example, if the link to the ISP goes down, how long does one wait before notifying one's manager? one's users? In addition, not all monitoring needs to be reactive. There are proactive monitoring tools available which can detect patterns of abuse or failure which may lead to larger problems, and can help one detect those problems before they affect your users.

[1001] Backup and Recovery

[1002] People kick over servers, accidentally delete files, and spill coffee on machines. For these reasons and a host of others, Net Centric resources must be backed up in a manner so that they can be recovered. This does not mean dumping a bunch of files onto data tapes and stacking them in a comer of the server room. An effective backup and recovery strategy should address how backups may be taken, the media on which they may be stored, the location where they may be stored, and the frequency with which they may be taken. Backups should also be periodically tested to make sure that they are recoverable, for example to make sure the backup tape drive is still working. When designing your backup strategy one should also consider the specific types of applications, databases, and hardware which are in use in your environment. For example an Oracle database may probably not be recoverable from a .tar file. In addition to software resources, consider what would happen if your router or your ISP link were to go down. It may be necessary to maintain a backup link to a secondary service provider in the event that your ISP goes down for an extended period of time.

[1003] Execution Architecture Security Management

[1004] The Execution Architecture Security focuses on Authorization, Encryption and Authentication in order to securely support applications and ensure data integrity throughout the life cycle of a single transaction. The ReTA Effort chose the Netcentric Architecture Framework (NCAF) to identify the appropriate components to focus on within the Execution Architecture. See FIG. 44 which illustrates a NCAF Framework 4400 with the shaded components 4402 in scope for Phase 1.

[1005] Authentication

[1006] Regardless of the operating system that one is using, access control is a major security concern. NT authenticate users by their knowledge of an ID and password that can be used multiple times however, all passwords are vulnerable in some manner. The advent of sniffing technologies allows passwords to be monitored and read over the network. Even if passwords are encrypted as they are sent, a keystroke capturing program could be installed at the client PC and used to capture passwords before they are encrypted. Perhaps advanced client side security can mitigate this threat as well, but even with the highest technology solution, a user could write his password down and stick it to the side of his PC, thereby defeating all of the technology just implemented.

[1007] The solution to this problem is some type of two factor authentication, meaning that users are authenticated with something they have, and something they know. The “something they know” can still be a password, and the “something they have” can range from the high end being a one time password generator, to the low end being an ID file stored on the user's PC or on a disk. In choosing an appropriate solution, one should consider ease of management and ease of distribution, the required strength of the solution, and integration into your environment. There are several examples of technologies which can meet your requirements, including the use of one-time passwords, time based passwords, or challenge response schemes. Once chosen and implemented, a secure authentication mechanism can be incorporated with both your operating system and your application to remove the risks associated with static passwords. Some authorization options are depicted in this Authentication Matrix:

[1008] Encryption

[1009] In Net Centric computing it is likely that eventually your data may pass through a network that is not secure, where your data can be snooped or even changed. In order to guarantee confidentiality over any insecure network, including the Internet, some type of encryption must be used. Encryption may ensure that data cannot be read by anyone other than the secure target server, and that the data being transferred has not been altered. Today there are so many different strategies for implementing encryption, it is often difficult to choose which scheme is most appropriate. The specific encryption strategy chosen may rely on a number of factors.

[1010] What information exactly needs to be encrypted? If one is running a smart store over the Internet, maybe one only needs to encrypt the single piece of data that has the customer's credit card information. If one is allowing their system administrators to dial into their network via the Internet, one may probably want to encrypt the whole session.

[1011] How many users are there? If one want to just encrypt data between a few users and one's system, a private or secret key encryption scheme may be appropriate. If one is in a multi-user environment one may probably want to consider public key encryption, and the key management strategies that go along with it.

[1012] What does one's computing environment look like? If your applications or operating systems provide native encryption, these may be the easiest and most secure to implement.

[1013] Based on your answers to these questions, there are a number on encryption solutions available for implementation. If one is running a Netscape web server, one may want to consider Secure Sockets Layer, or SSL, which provides data encryption, server authentication, message integrity, and optional client authentication for a TCP/IP connection. Another WWW security solution is Secure Hypertext Transfer Protocol (S-HTTP), which is a security-enhanced version of HTTP, developed by Enterprise Integration Technologies (EIT). S-HTTP supports end-to-end secure transactions by incorporating cryptographic enhancements to messaging at the application level. Pretty Good Privacy, or PGP, is a common encryption solution for electronic mail. PGP may both authenticate the sender of the message, and encrypt the contents of the message through the use of a public key/private key pair. In electronic commerce solutions, the Secure Electronic Transactions (SET) specification which is being jointly developed by Visa and MasterCard may be considered. SET may require authentication of all parties involved with a credit card transaction through the use of digital signatures and certificates, and may use a separate encryption handshake in order to guarantee both confidentiality and integrity. Other encryption solutions include Point to Point Tunneling Protocol (PPTP), Private Communication Protocol (PCT), or the use of CryptoAPI. Some available encryption options are depicted in the following Encryption Matrix:

[1014] Authorization

[1015] When a user requests access to network resources, the Authorization service determines if the user has the appropriate permissions and either allows or disallows the access. (This occurs after the user has been properly authenticated.)

[1016] The following are examples of ways to implement Authorization services:

[1017] Network Operating Systems—Authorization services are bundled with all network operating systems in order to control user access to network resources.

[1018] Servers, Applications, and Databases—Authorization can occur locally on a server to limit access to specific system resources or files. Applications and databases can also authorize users for specific levels of access within their control. (This functionality is within the Environment Services grouping in the execution architecture.)

[1019] Firewall Services protect sensitive resources and information attached to an Intxxnet network from unauthorized access by enforcing an access control policy.

[1020] Recommendation

[1021] ReTA may utilize all Windows NT-based resources, including those accessed using a Web browser, are represented as objects that can be accessed only by authorized Windows NT-based users. Access may be controlled through an Access Control List (ACL).

[1022] Operations Architecture Security Management

[1023] The Operations Architecture is a combination of tools, support services, procedures, and controls required to keep a production system up and running efficiently. Unlike the Execution and Development Architectures, its primary users are the system administrators and the production support personnel.

[1024] All components of the Operations Architecture are integral to the successful management of a distributed environment. Any processes, procedures, or tools developed or chosen as an operational management solution for a specific operational area must be able to integrate with any existing or planned process, procedure, tool solutions for other Operations Architecture areas. See FIG. 45 which illustrates a MODEnc Framework 4500 with an event processing component 4502 and an event and data generation component 4504.

[1025] Execution Architecture Design

[1026] Overview

[1027] The Netcentric Architecture Framework (NCAF) identifies the run-time services required by Netcentric applications. The ReTA design effort used this framework to define the ReTA Execution Architecture requirements. Taken in the NCAF context, this portion of the present description describes the ReTA Execution Architecture implementation (through custom and/or vendor components) of the required run-time services.

[1028] The NCAF categorizes the runtime services into the following logical areas (see FIG. 46 which illustrates the NCAF Framework 4600):

[1029] Presentation Services 4602

[1030] Information Services 4604

[1031] Communication Services 4606

[1032] Communication Fabric Services 4608

[1033] Transaction Services 4610

[1034] Environment Services 4612

[1035] Base Services 4614

[1036] Business Logic 4616

[1037] Execution Architecture Component Design

[1038] Purpose

[1039] The Execution Architecture Component Design portion of the description describes the ReTA implementation of the NCAF defined run-time services. This portion of the description also maps the ReTA application architecture frameworks into the appropriate NCAF service component descriptions.

[1040] The ReTA Application Architecture comprises the following frameworks:

[1041] Base Services

[1042] Base Services provide server-based support for delivering applications to a wide variety of users over the Internet, intranet, and extranet.

[1043] Web Server Services

[1044] Description

[1045] Enables organizations to manage and publish information and deploy Netcentric applications over the Internet and Intranet environments. These services support the following: managing portion of the present descriptions in multiple formats, handling of client requests for HTML pages, processing server-side scripts, and caching web pages to improve performance.

[1046] ReTA implementation

[1047] ReTA implements web server services through Microsoft's Internet Information Server 4.0 (IIS). IIS provides the following services:

[1048] Process requests for static and dynamic web pages and graphics.

[1049] Implement appropriate security and authentication to public and private areas of a web site.

[1050] Execute application specific Active Server Pages.

[1051] Implement web activity tracking and reporting.

[1052] Implement application state and management capability.

[1053] ReTA uses the IIS Session object to hold references to architecture and application components during the user session.

[1054] Communication Services

[1055] Network services provided by the Communications Services layer are grouped into four major categories of functionality: Virtual Resource, Directory, Messaging, and Security services. The Virtual Resources Component is not implemented by ReTA Phase 1.

[1056] Directory Services

[1057] A full-featured Directory Service organizes, categorizes and names networked resources in order to provide a comprehensive picture of clients, servers, users, applications and other resources. The service typically includes a database of objects, representing all nodes and resources on a network. The database manages relationships between users and networks, network devices, network applications, and information on the network. The Directory service performs the following functions:

[1058] Stores information about network resources and users and tracks relationships

[1059] Organizes resource access information in order to aid resources in locating and accessing other resources throughout the network

[1060] Provides location transparency, since resources are accessed through a directory rather than based on their physical location

[1061] Converts between logical resource names and physical resource addresses

[1062] Interacts with Security services such as authentication and authorization track identities and permissions

[1063] Provides single network logon to file and print resources; can provide single network logon for network applications that are integrated with the Directory service

[1064] Distributes directory information throughout the enterprise (for reliability and location-independent access)

[1065] Synchronizes multiple directory databases

[1066] Enables access to heterogeneous systems (integration of various network operating systems, platforms, etc.)

[1067] Domain Services

[1068] Description

[1069] A network domain is a set of network nodes under common control (i.e., common security and logins, unified addressing, coordinated management, etc.). Domain services manage these types of activities for the network nodes in a domain. Domain services may be limited in their ability to support heterogeneous systems and in the ability to scale to support the enterprise.

[1070] ReTA implementation

[1071] ReTA implements domain services through Microsoft's NT 4.0 Server.

[1072] Name Services

[1073] Description

[1074] The Name service creates a logical “pronounceable” name in place of a binary machine number. These services could be used by other communications services such as File Transfer, Message Services, and Terminal Services. A Name service can be implemented on its own, or as part of a full-featured Directory service.

[1075] ReTA implementation

[1076] ReTA implements name services through Microsoft's NT 4.0 Server.

[1077] Messaging Services (Core)

[1078] Broadly defined, Messaging services enable information or commands to be sent between two or more recipients. Recipients may be computers, people, or processes within a computer. Core Messaging services are categorized by the characteristics of the information being transferred:

[1079] File Transfer

[1080] RPC

[1081] File Transfer

[1082] Description

[1083] File Transfer services enable the sending and receiving of files or other large blocks of data between two resources. In addition to basic file transport, features for security, guaranteed delivery, sending and tracking sets of files, and error logging may be needed if a more robust file transfer architecture is required.

[1084] ReTA implementation

[1085] ReTA implements file transfer services through Microsoft's Internet Information Server 4.0 (IIS) using the HyperText Transfer Protocol (HTTP). Within a Web-based environment, Web servers transfer HTML pages to clients using HTTP. HTTP can be thought of as a lightweight file transfer protocol optimized for transferring small files. HTTP reduces the inefficiencies of the FTP protocol. HTTP runs on top of TCP/IP and was developed specifically for the transmission of hypertext between client and server.

[1086] RPC (Remote Procedure Calls)

[1087] Description

[1088] RPCs (Remote Procedure Calls) are a type of protocol by which an application sends a request to a remote system to execute a designated procedure using the supplied arguments and return the result. RPCs emulate the function call mechanisms found in procedural languages. This means that control is passed from the main logic of a program to the called function, with control returning to the main program once the called function completes its task.

[1089] ReTA implementation

[1090] ReTA implements RPC services through Microsoft's COM/DCOM mechanism and the Internet Information Server 4.0 (IIS) using HTTP.

[1091] Messaging Services (Specialized)

[1092] Specialized Messaging services extend the Core Messaging services to provide additional functionality, including:

[1093] Provides messaging among specialized systems by drawing upon basic messaging capabilities

[1094] Defines specialized message layouts

[1095] Defines specialized inter-system protocols

[1096] Suggests ways in which messaging draws upon directory and security services in order to deliver a complete messaging environment

[1097] Database Access

[1098] Description

[1099] Database Messaging services (also known as Database Access Middleware) provide connectivity for clients to access databases throughout the enterprise. Database messaging software draws upon basic inter-process messaging capabilities (e.g., RPCs) in order to support database connectivity.

[1100] ReTA implementation

[1101] ReTA implements Database Messaging services through Microsoft's Open Database Connectivity (ODBC) mechanism. ReTA abstracts database connection from the application developer through the Microsoft Transaction Server (MTS) 2.0 connection pooling mechanism.

[1102] Object Messaging

[1103] Description

[1104] Object Messaging enables objects to transparently make requests of and receive responses from other objects located locally or remotely. Objects communicate through an Object Request Broker (ORB). An ORB enables client objects to access server objects either locally or remotely over a network and invoke operations (i.e. functions and methods) on them. ORBs typically provide interoperability between heterogeneous client and server environments: across languages and/or operating systems and/or network protocols.

[1105] ReTA implementation

[1106] ReTA implements Object Messaging services through Microsoft's COM/DCOM mechanism.

[1107] Security Services

[1108] Communications Security services control access to network-attached resources. Combining network Security services with security services in other parts of the system architecture (e.g., application and database layers) results in robust security.

[1109] Authentication

[1110] Description

[1111] Authentication services verify network access requests by validating that users are who they claim to be. For secure systems, one or more authentication mechanisms can be used to validate authorized users and to verify to which functions and data they have access.

[1112] ReTA implementation

[1113] ReTA implements Authentication services through Microsoft's NT 4.0 Server (and IIS).

[1114] Authorization

[1115] Description

[1116] Authorization services determine if users have appropriate permissions and either allows or disallows the access.

[1117] ReTA implementation

[1118] ReTA implements Authorization services through Microsoft's NT 4.0 Server (and IIS). ReTA also supports application defined “required workflow sequence” web page access authorization through the ReTA Session framework.

[1119] Encryption

[1120] Description

[1121] Encryption services encrypt data prior to network transfer to prevent unauthorized interception. Encryption has two main components: the encryption algorithm, which is the series of steps that is performed to transform the original data; and the key, which is used by the algorithm in some way to encrypt the message. Typically, the algorithm is widely known, while the key is kept secret. There are several types of encryption in use today, including:

[1122] Secret key cryptography—uses one key (the secret key) both to encrypt the message on one side and to decrypt the message on the other side.

[1123] Public key cryptography—uses two keys, the public key and the private key. The public key and private key are mathematically related so that a message encrypted with the recipient's public key may be decrypted with the recipient's private key. Therefore, the public key can be widely published, while the private key is kept secret.

[1124] ReTA implementation

[1125] ReTA implements Encryption services through the Secure Sockets Layer (SSL) mechanism. ReTA also implements encryption for the User ID and User Password used by the ODBC mechanism through the ReTA Session framework.

[1126] Environment Services

[1127] Environment Services provide miscellaneous application and system level services that do not deal directly with managing the user-interface, communicating to other programs, or accessing data. Sub-components covered during the Phase 1 of ReTA include: Application Services, Component Framework, Operating System, Runtime Services, and System Services.

[1128] Application Services

[1129] Application Services are miscellaneous services which applications can use for common functions. These common functions can apply to one application or can be used across applications. They include: Application Security Services, Error Handling/Logging Services, State Management Services, Help Services, and Other Common Services.

[1130] Application Security

[1131] Description

[1132] Besides system level security such as logging into the network, there are additional security services associated with specific applications. These include:

[1133] User Access Services—set of common functions that limit application access to specific users within a company or external customers.

[1134] Data Access Services—set of common functions that limit access to specific data within an application to specific users or user types (e.g., secretary, manager).

[1135] Function Access Services—set of common functions that limit access to specific functions within an application to specific users or user types (e.g., secretary, manager).

[1136] ReTA implementation

[1137] ReTA implements Application Security through the ReTA Session and Activity frameworks. The Session framework provides “Session level Page access authorization”, “User identification” and “session timeout” services. The Activity framework provides “Activity level Page access authorization”.

[1138] Codes Table Services

[1139] Description

[1140] Codes Table Services enable applications to utilize externally stored parameters and validation rules. For example, an application may be designed to retrieve the tax rate for the State of Illinois. When the user enters “Illinois” on the screen, the application first validates the user's entry by checking for its existence on the “State Tax Table”, and then retrieves the tax rate for Illinois. Note that codes tables provide an additional degree of flexibility. If the tax rates changes, the data simply needs to be updated; no application logic needs to be modified.

[1141] ReTA implementation

[1142] ReTA implements Codes Table Services through the ReTA Codes Table framework.

[1143] Error Handling/Logging

[1144] Description

[1145] Error Handling Services support the handling of fatal and non-fatal hardware and software errors for an application. An error handling architecture takes care of presenting the user with an understandable explanation of what has happened and coordinating with other services to ensure that transactions and data are restored to a consistent state.

[1146] Logging Services support the logging of informational, error, and warning messages. Logging Services record application and user activities in enough detail to satisfy any audit trail requirements or to assist the systems support team in recreating the sequence of events that led to an error.

[1147] ReTA implementation

[1148] ReTA implements Error Handling/Logging Services through the ReTA Event Handler and Persistence frameworks.

[1149] Other Common Services

[1150] Description

[1151] Catchall category for additional reusable routines useful across a set of applications (e.g., Date Routines, Time Zone Conversions, Field Validation Routines).

[1152] ReTA implementation

[1153] ReTA implements client side Field Validation Services through the ReTA UI framework.

[1154] State Management

[1155] Description

[1156] State Management Services enable information to be passed or shared among windows and/or Web pages and/or across programs. In Netcentric environments, the HTTP protocol creates a potential need for implementing some form of Context Management Services (storing state information on the server). The HTTP protocol is a stateless protocol. Every connection is negotiated from scratch, not just at the page level but for every element on the page. The server does not maintain a session connection with the client nor save any information between client exchanges (i.e., web page submits or requests). Each HTTP exchange is a completely independent event. Therefore, information entered into one HTML form must be saved by the associated server application somewhere where it can be accessed by subsequent programs in a conversation.

[1157] ReTA implementation

[1158] ReTA implements State Management Services through Microsoft's IIS Session component and the ReTA Session, Activity and UI frameworks.

[1159] Component Framework

[1160] Description

[1161] Component Framework Services provide an infrastructure for building components so that they can communicate within an application and across applications, on the same machine or on multiple machines across a network, to work together. COM/DCOM and CORBA described in Communication Services are the two leading component industry standards. These standards define how components should be built and how they should communicate.

[1162] Object Request Broker (ORB) services, based on COM/DCOM and CORBA, focus on how components communicate. Component Framework Services, also based on CORBA and COM/DCOM, focus on how components should be built.

[1163] ReTA implementation

[1164] ReTA implements Component Framework Services through the ReTA Activity framework.

[1165] Operating System

[1166] Description

[1167] Operating System Services are the underlying services such as multi-tasking, paging, memory allocation, etc., typically provided by today's modem operating systems. Where necessary, an additional layer or Application Programming Interface (API) may be provided to gain either operating system independence or a higher level of abstraction for application programmers.

[1168] ReTA implementation

[1169] ReTA implements Operating System Services through the NT 4.0 operating system.

[1170] Runtime Services

[1171] Runtime services convert non-compiled computer languages into machine code during the execution of a program. They include: Language Interpreter Service and Virtual Machine Service.

[1172] Language Interpreter

[1173] Description

[1174] Language Interpreter Services decompose a 4th generation and/or a scripting languages into machine code (executable code) at runtime.

[1175] ReTA implementation

[1176] ReTA implements Language Interpreter Services through NT server 4.0 and IIS 4.0.

[1177] Virtual Machine

[1178] Description

[1179] Typically, a Virtual Machine is implemented in software on top of an operating system, and is used to run applications. The Virtual Machine provides a layer of abstraction between the applications and the underlying operating system and is often used to support operating system independence.

[1180] ReTA implementation

[1181] ReTA implements Virtual Machine Services through NT 4.0 Virtual Machine component.

[1182] System Services

[1183] Services which applications can use to perform system-level functions. These services include: System Security Services, Profile Management Services, Task and Memory Management Services, and Environment Verification Services.

[1184] Environment Verification

[1185] Description

[1186] Environment Verification Services ensure functionality by monitoring, identifying and validating environment integrity prior and during program execution. (e.g., free disk space, monitor resolution, correct version). These services are invoked when an application begins processing or when a component is called. Applications can use these services to verify that the correct versions of required Execution Architecture components and other application components are available.

[1187] Profile Management

[1188] Description

[1189] Profile Management Services are used to access and update local or remote system, user, or application profiles. User profiles, for example, can be used to store a variety of information such as the user's language and color preferences to basic job function information which may be used by Integrated Performance Support or Workflow Services.

[1190] ReTA implementation

[1191] ReTA implements Profile Management Services through ReTA Session framework.

[1192] System Security

[1193] Description

[1194] System Security Services allow applications to interact with the operating system's native security mechanism. The basic services include the ability to login, logoff, authenticate to the operating system, and enforce access control to system resources and executables.

[1195] Task & Memory Management

[1196] Description

[1197] Task & Memory Management Services allow applications and/or other events to control individual computer tasks or processes, and manage memory. They provide services for scheduling, starting, stopping, and restarting both client and server tasks (e.g., software agents).

[1198] ReTA implementation

[1199] ReTA implements Task & Memory Management Services through MTS 2.0.

[1200] Information Services

[1201] Information Services manage electronic data assets and enable applications to access and manipulate data stored locally or remotely in portion of the present descriptions or databases. They minimize an application's dependence on the physical storage and location within the network. Information Services can be grouped into two categories: Database Services, and Portion of the present description Services. Portion of the present description Services may not be covered during ReTA Phase 1.

[1202] Database Services

[1203] Database Services are responsible for providing access to a local or a remote database, maintaining integrity of the data within the database and supporting the ability to store data on either a single physical platform, or in some cases across multiple platforms. Database Services include: Access Services, Indexing Services and Security Services.

[1204] Access

[1205] Description

[1206] Access Services enable an application to retrieve data from a database as well as manipulate (insert, update, delete) data in a database. This can be done through the following:

[1207] Standards Based Structured Query Language (SQL) API

[1208] SQL Gateways

[1209] Distributed Relational Data Access (DRDA)

[1210] ReTA implementation

[1211] ReTA implements Database Access Services through the ReTA Persistence framework, which utilizes the Standards Based SQL API approach through ODBC.

[1212] Indexing

[1213] Description

[1214] Indexing Services provide a mechanism for speeding up data retrieval. In relational databases one or more fields can be used to construct the index. So when a user searches for a specific record, rather than scanning the whole table sequentially the index is used to find the location of that record faster.

[1215] ReTA implementation

[1216] ReTA implements Database Indexing Services through the Database Management System (either Oracle or SQL Server).

[1217] Security

[1218] Description

[1219] Security Services enforce access control to ensure that records are only visible or editable by authorized people for approved purposes. Most database management systems provide access control at the database, table, or row level as well as concurrency control.

[1220] ReTA implementation

[1221] ReTA implements Database Security Services through the Database Management System (either Oracle or SQL Server).

[1222] Presentation Services

[1223] Presentation Services enable an application to manage the human-computer interface. This includes capturing user actions and generating resulting events, presenting data to the user, and assisting in the management of the dialog flow of processing. Typically, Presentation Services are only required by client workstations. Sub-components covered during the Phase 1 of ReTA include: Window System, Desktop Manager, Form, Web Browser, Report & Print, and Direct Manipulation.

[1224] Desktop Manager

[1225] Description