Scribd Logo
Upload

Welcome to Scribd!

  • 190 views

    Software Architecture AntiPatterns

    Uploaded by

    Jon A Cohn
    Architectural knowledge has played a role in discussions on design, reuse, and evolution for over a decade. Over the past few years, the term has significantly increased in popularity and attempts are being made to properly define what constitutes ‘architectural knowledge’.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Software Architecture AntiPatterns

    Uploaded by

    Jon A Cohn
    190 views3 pages
    Architectural knowledge has played a role in discussions on design, reuse, and evolution for over a decade. Over the past few years, the term has significantly increased in popularity and attempts are being made to properly define what constitutes ‘architectural knowledge’.

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Architectural knowledge has played a role in discussions on design, reuse, and evolution for over a decade. Over the past few years, the term has significantly increased in popularity and attempts are being made to properly define what constitutes ‘architectural knowledge’.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    190 views3 pages

    Software Architecture AntiPatterns

    Uploaded by

    Jon A Cohn
    Architectural knowledge has played a role in discussions on design, reuse, and evolution for over a decade. Over the past few years, the term has significantly increased in popularity and attempts are being made to properly define what constitutes ‘architectural knowledge’.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Software Architecture AntiPatterns

    Architecture AntiPatterns focus on the system-level and enterprise-level structure


    of applications and components. Although the engineering discipline of software
    architecture is relatively immature, what has been determined repeatedly by
    software research and experience is the overarching importance of architecture
    in software development
    Architecture AntiPatterns focus on the system-level and enterprise-level structure
    of applications and components. Although the engineering discipline of software
    architecture is relatively immature, what has been determined repeatedly by
    software research and experience is the overarching importance of architecture
    in software development:
    1. Good architecture is a critical factor in the success of the system
    development.
    2. Architecture-driven software development is the most effective approach to
    building systems. Architecture-driven approaches are superior to requirementsdriven, document-driven, and methodology-driven approaches. Projects often
    succeed in spite of methodology, not because of it.
    Software architecture is a subset of the overall system architecture, which
    includes all design and implementation aspects, including hardware and
    technology selection. Important principles of architecture include the following:
    1. Architecture provides a view of the whole system. This distinguishes
    architecture from other analysis and design models that focus on parts of a
    system.
    2. An effective way to model whole systems is through multiple viewpoints. The
    viewpoints correlate to various stakeholders and technical experts in the systemdevelopment process.
    The following AntiPatterns focus on some common problems and mistakes in the
    creation, implementation, and management of architecture.
    Autogenerated Stovepipe
    This AntiPattern occurs when migrating an existing software system to a
    distributed infrastructure. An Autogenerated Stovepipe arises when converting
    the existing software interfaces to distributed interfaces. If the same design is
    used for distributed computing, a number of problems emerge.
    Stovepipe Enterprise
    A Stovepipe System is characterized by a software structure that inhibits change.
    The refactored solution describes how to abstract subsystem and components to
    achieve an improved system structure. The Stovepipe Enterprise AntiPattern is
    characterized by a lack of coordination and planning across a set of systems.

    Jumble

    When horizontal and vertical design elements are intermixed, an unstable


    architecture results. The intermingling of horizontal and vertical design elements
    limits the reusability and robustness of the architecture and the system software
    components.
    Stovepipe System
    Subsystems are integrated in an ad hoc manner using multiple integration
    strategies and mechanisms, and all are integrated point to point. The integration
    approach for each pair of subsystems is not easily leveraged toward that of other
    subsystems. The Stovepipe System AntiPattern is the single-system analogy of
    Stovepipe Enterprise, and is concerned with how the subsystems are coordinated
    within a single system.
    Cover Your Assets
    Document-driven software processes often produce less-than-useful
    requirements and specifications because the authors evade making important
    decisions. In order to avoid making a mistake, the authors take a safer course
    and elaborate upon alternatives.
    Vendor Lock-In
    Vendor Lock-In occurs in systems that are highly dependent upon proprietary
    architectures. The use of architectural isolation layers can provide independence
    from vendor-specific solutions.
    Wolf Ticket
    A Wolf Ticket is a product that claims openness and conformance to standards
    that have no enforceable meaning. The products are delivered with proprietary
    interfaces that may vary significantly from the published standard.
    Architecture by Implication
    Management of risk in follow-on system development is often overlooked due to
    overconfidence and recent system successes. A general architecture approach
    that is tailored to each application system can help identify unique requirements
    and risk areas.
    Warm Bodies
    Software projects are often staffed with programmers with widely varying skills
    and productivity levels. Many of these people may be assigned to meet staff size
    objectives (so-called warm bodies). Skilled programmers are essential to the
    success of a software project. So-called heroic programmers are exceptionally
    productive, but as few as 1 in 20 have this talent. They produce an order of
    magnitude more working software than an average programmer.

    Design by Committee
    The classic AntiPattern from standards bodies, Design by Committee creates
    overly complex architectures that lack coherence. Clarification of architectural
    roles and improved process facilitation can refactor bad meeting processes into
    highly productive events.

    Swiss Army Knife


    A Swiss Army Knife is an excessively complex class interface. The designer
    attempts to provide for all possible uses of the class. In the attempt, he or she
    adds a large number of interface signatures in a futile attempt to meet all
    possible needs.
    Reinvent the Wheel
    The pervasive lack of technology transfer between software projects leads to
    substantial reinvention. Design knowledge buried in legacy assets can be
    leveraged to reduce time-to-market, cost, and risk.
    The Grand Old Duke of York
    Egalitarian software processes often ignore peoples talents to the detriment of
    the project. Programming skill does not equate to skill in defining abstractions.
    There appear to be two distinct groups involved in software development:
    abstractionists and their counterparts the implementationists.

    Source : sourcemaking.com
    Recommended by :
    Jon Cohn ,CTO , VP IT Architecture
    https://www.linkedin.com/in/jonacohn
    joncohn@comcast.net

    "Jon Cohn Exton PA" "Jon Cohn Exton" "Jon Cohn Evolution"

    You might also like