{'fraction_non_alphanumeric': 0.017225747960108794, 'fraction_numerical': 0.0009066183136899365, 'mean_word_length': 5.5325443786982245, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A PROPOSAL FOR SPECIFYING BUSINESS COMPONENTS 1

Component-based software development is a potential reuse paradigm for the future. While the required technologies for a component-style system development are widely available, for instance Sun’s Enterprise Java Beans, a problem inhibits the breakthrough of the component paradigm in business application domains: compared to traditional engineering disciplines there is a lack of standardized methods to describe business components. Such a description has to address several aspects: What services are offered and requested by a business component? How can these services be used? Are there any interdependencies between the services of a set of business components? What quality characteristics do the offered services fulfill? And so on. In this paper, we present a holistic approach to specify a business component. This approach consists of seven specification levels which address both technical and business aspects. Furthermore, we show the application of this method by specifying a simple business component that deals with German bank codes.