Abstract: A system and method for testing a software development activity of an enterprise application is disclosed. In one embodiment, the method includes obtaining a software structure specification for an enterprise application and automatically generating test plans using the software structure specification. The method also includes automatically determining at least one test path in each test plan using the software structure specification, and automatically deriving a plurality of test cases using each test path. Further, the method includes executing each of the plurality of test cases and recording test results.

Abstract: A system monitors software development processes. In an embodiment, key components are identified in a requirements specification, verification rules are applied to delivered requirements, and entities is the requirements specification are validated. In another embodiment, a standard set of review types are generated, review checklists are generated, the review checklists are allocated, and review points are collected and tracked. In a further embodiment, a standard work break down structure and standard work products are defined, a high level plan is formed, and a planning template is formed. In another embodiment, the planning and tracking of a software development process and software product quality are stored in an integrated system, work products are reviewed, defects in the work products are recorded, and any defects are tracked until the completion of the software development process.

Abstract: A system and method to analyze interactions among software artifacts within enterprise applications. The system includes an artifact analyzer module an artifact code parsing module and an artifact token processing module. The artifact analyzer module generates artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object in the enterprise application and an interaction token repository for storing artifact tokens. The artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object. These artifact tokens are stored within an interaction token repository for later use.

Abstract: In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.

Abstract: In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.

Abstract: A software model is used to capture and store software system attributes resulting in a repository of system architecture elements. After creation of the model, changes may be proposed to the system, the impact of those changes analyzed using the repository, and a decision made based on the analysis whether to go forward with the proposed changes or take some alternative action.

Abstract: A system monitors software development processes. In an embodiment, key components are identified in a requirements specification, verification rules are applied to delivered requirements, and entities is the requirements specification are validated. In another embodiment, a standard set of review types are generated, review checklists are generated, the review checklists are allocated, and review points are collected and tracked. In a further embodiment, a standard work break down structure and standard work products are defined, a high level plan is formed, and a planning template is formed. In another embodiment, the planning and tracking of a software development process and software product quality are stored in an integrated system, work products are reviewed, defects in the work products are recorded, and any defects are tracked until the completion of the software development process.

Abstract: An aspect of the present invention provides a method of handling a financial transaction in a transaction switch. The method includes receiving a primary transaction request from an initiator, identifying a host from a routing table for receiving the primary transaction request based on details provided in the primary transaction request, transmitting the primary transaction request to the identified host, receiving a response from the identified host, determining a need for transmitting the primary transaction request to another host and interpreting the response received and transmitting a final outcome back to the initiator.

Abstract: A system and method to perform planning and control/estimation for software modules within an automated development system are disclosed. The system has a software coding and testing module for defining and testing software applications, a software module database for maintaining software modules that may be part of software applications, and a software estimation module for estimating software development activity. The software estimation module comprises a release set estimation module and a function point analysis module.

Abstract: A system and method to analyze interactions among software artifacts within enterprise applications. The system includes an artifact analyzer module an artifact code parsing module and an artifact token processing module. The artifact analyzer module generates artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object in the enterprise application and an interaction token repository for storing artifact tokens. The artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object. These artifact tokens are stored within an interaction token repository for later use.

Abstract: In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.

Abstract: A method and apparatus to afford a technical application for gathering, storing, tracking, and using requirements, engineering software for those requirements, and releasing finished enterprise software. A method is described that gathers requirements into a constrained data structure designed to facilitate the engineering of pre-specified definitions of the work to be done. A data structure and schema are described that organizes the gathering of requirements, the engineering of software that meet those requirements, and the orderly release of the software components. A computer readable medium is described, the medium having computer executable instruction to cause a system perform the method.

Abstract: A method to independently test and develop a component based software system. The method captures software specifications of the system in a model. It then loads technical specifications of the components of the system into a code generation repository, and generates platform specific code for the components. In a separate embodiment, the generated code is in a standalone format for ease of testing. In another embodiment, the generated code is integrated with one or more other components, thereby permitting integration testing. The method can be used, among other things, to produce user interfaces that are standardized.

Abstract: A non-intrusive enterprise application audit trail has the ability to configure and track only data that is selected, thereby conserving system resources.

Abstract: A system and method to perform planning and performing testing for software modules within an automated development system are described. The system includes a testing module containing an automated test case generation module, a test case execution and analysis module, a regression test planning module a test plan generation module and an automated test plan management module. These modules work together to provide an integrated test platform for creating and managing the test environment, creating test plans and test cases, performing unit level testing, module integration testing and system testing within a single development environment.

Abstract: User interfaces created for software systems are used as the basis for gathering and/or disseminating requirements, behavioral specifications, review processes, and documentation. A computer readable medium is described, the medium having computer executable instruction to cause a system perform the method.

Abstract: A method and apparatus to afford a technical application for gathering, storing, tracking, and using requirements, engineering software for those requirements, and releasing finished enterprise software. A method is described that gathers requirements into a constrained data structure designed to facilitate the engineering of pre-specified definitions of the work to be done. A data structure and schema are described that organizes the gathering of requirements, the engineering of software that meet those requirements, and the orderly release of the software components. A computer readable medium is described, the medium having computer executable instruction to cause a system perform the method.

Abstract: A method and apparatus for data flow control of a transmission port includes processing that begins by obtaining, for the transmission port over time, input data rate of at least one data transport type and output data rate of the at least one data transport type. The data type transport type is one of available bit rate (ABR), variable bit rate (VBR), constant bit rate (CBR), and unspecified bit rate (UBR). The data flow control continues by deriving a difference term from the input data rate and the output data rate and using the difference term and a previous generic explicit rate to generate a current generic explicit rate. The current generic explicit rate may further be generated from the previous generic explicit rate, the difference term, and an error term, where the error term is derived from a current queue value and a target queue value.

Abstract: The method for servicing queues holding messages, such as ATM data packets, for subsequent processing or transmission to a resource such as a communications link having a finite processing capability comprises the steps of servicing each queue by forwarding the messages thereof to the resource at time intervals corresponding to a guaranteed service rate of the queue, provided the queue is non-empty; and, during time intervals when none of the queues have messages being forwarded to the resource in conformance with the above step, servicing the queues in accordance with a proportion of a remaining or idle resource bandwidth allocated to each queue.