초록 ▼

A system and method are provided for providing base service patterns for use in a component-based architecture. A batch job pattern is provided for structuring batch components such that common architectural services are implemented uniformly across the batch components. A batch unit of work pattern

A system and method are provided for providing base service patterns for use in a component-based architecture. A batch job pattern is provided for structuring batch components such that common architectural services are implemented uniformly across the batch components. A batch unit of work pattern is utilized for structuring work to be processed by the batch components so that the work is treated uniformly by the batch components. A processing pipeline pattern is implemented for structuring batch activities for simplified reconfiguration of the batch activities, including preparing to perform a series of processing steps on input objects, encapsulating each of the processing steps within a filter, receiving and processing the input objects in one of filters; delivering results from the filters incrementally during processing of the input objects, utilizing connectors for connecting at least two of the plurality of filters, and using connectors for connecting input and output filters of different processes for forming a scalable system. An abstraction factory is used to encapsulate differences between objects such that only activities that need to understand the difference between the objects have to deal with the differences.

대표청구항 ▼

A system and method are provided for providing base service patterns for use in a component-based architecture. A batch job pattern is provided for structuring batch components such that common architectural services are implemented uniformly across the batch components. A batch unit of work pattern

A system and method are provided for providing base service patterns for use in a component-based architecture. A batch job pattern is provided for structuring batch components such that common architectural services are implemented uniformly across the batch components. A batch unit of work pattern is utilized for structuring work to be processed by the batch components so that the work is treated uniformly by the batch components. A processing pipeline pattern is implemented for structuring batch activities for simplified reconfiguration of the batch activities, including preparing to perform a series of processing steps on input objects, encapsulating each of the processing steps within a filter, receiving and processing the input objects in one of filters; delivering results from the filters incrementally during processing of the input objects, utilizing connectors for connecting at least two of the plurality of filters, and using connectors for connecting input and output filters of different processes for forming a scalable system. An abstraction factory is used to encapsulate differences between objects such that only activities that need to understand the difference between the objects have to deal with the differences. ubsystems', and components' function, functional failure, failure effect and failure cause related to an actual failure, said system is further defined by at least one function, where said definition is stored as data in at least one database; b identifying potential failures of said system according to said definition by allowing a user to select portions of data from said at least one database; c. categorizing said failure effect as one of Evident Safety, Evident Operational, Evident Economic, Hidden Safety, and Hidden Non-Safety; d. identifying maintainability and reliability data for said components, said data including predicted mean time between failure (MTBF), predicted mean time between unscheduled removals (MTBUR), historical MTBF and historical MTBUR; e. identifying tasks which may eliminate or reduce the possibility of said potential failure occurring and detecting hidden failures that have occurred; f. selecting said tasks based on applicability and effectiveness; g. automatically updating said system in response to at least one user request, said at least one user request comprising at least one of a system operation, a subsystem operation, and a parts operation, wherein said system operation comprises at least one of a selection operation, an add operation, an edit operation, a delete operation, a description and an operation operation, and a reliability data operation, said subsystem operation comprises at least one of a selection operation, an add subsystem operation, an add sub-subsystem operation, an edit operation, a delete operation, a description and an operation operation, and a reliability data operation and said parts operation comprises at least one of a selection operation, an add operation, an edit operation and a delete operation and permitting said at least one user request and said automatic updates to be performed in parallel; h. iteratively refining said tasks in response to said at least one user request and automatically updating said system; and i. providing a maintenance program comprised of said tasks to at least one user, wherein said maintenance program is used to eliminate or reduce the occurrence of failures by determining said tasks for scheduled maintenance or intervals related to standards set by regulatory authorities, equipment operators, or manufacturers and said method may be performed concurrently by multiple users; wherein multiple users may concurrently access and change various data of the database and may then update said database with said changed data. 16. The method for developing a maintenance program for a system according to claim 15, wherein said function is further defined by at least one failure.17.