{'fraction_non_alphanumeric': 0.02527075812274368, 'fraction_numerical': 0.0, 'mean_word_length': 5.523529411764706, '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}}
Architectural Decisions in e-Services Design

The design of e-services requires software architects to analyze many domain-specific requirements; the required architectural decisions recur. Many of them are motivated by cross-cutting concerns such as security, transactionality, and reliability. The decision making is driven by many forces; no single design fits all purposes. Some of these concerns can be expressed as model-and code-level aspects; others are better tackled by more conservative implementation practices. In this talk, we present architectural decision modeling as an emerging technique to transform such architectural knowledge from tacit, tribal knowledge into an explicit, manageable form. We present a three-step decision making framework, which supports the semi-automatic identification of decisions in requirements models and the injection of decisions into model and code aspects. We outline a reusable decision model for service-oriented architecture and e-services design, currently being harvested from completed projects. We conclude with a call to action for further research.