Software Architect

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 6348 Experts worldwide ranked by ideXlab platform

Matthew R Mcbride - One of the best experts on this subject based on the ideXlab platform.

  • The Software Architect
    Communications of the ACM, 2007
    Co-Authors: Matthew R Mcbride
    Abstract:

    Leadership is the defining characteristic in an unforgiving technology arena.

  • the Software Architect essence intuition and guiding principles
    Conference on Object-Oriented Programming Systems Languages and Applications, 2004
    Co-Authors: Matthew R Mcbride
    Abstract:

    Software Architecture is a distinct and developing discipline in the Software profession. Many practitioners have apparently entered the field with little effort; adding the word "Architect" to a title is easy to do. However, beneath the surface appearance, distinct approaches and toolsets are required to succeed. Reports of IT overspending and project failures emphasize the fact that these skills must be leveraged and developed. The practical application of this growing body of knowledge will continue to play an important role in the maturing of our profession, and its ability to deliver effective solutions. The Software Architect possesses a unique perspective and mental framework that guides the development of Software systems. Additionally, strong interpersonal skills are vital to the Software Architect's success. In this paper, I explore the unique approaches and characteristics of the successful Software Architect.

  • OOPSLA Companion - The Software Architect: essence, intuition, and guiding principles
    Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems languages and applications - OOPSLA '04, 2004
    Co-Authors: Matthew R Mcbride
    Abstract:

    Software Architecture is a distinct and developing discipline in the Software profession. Many practitioners have apparently entered the field with little effort; adding the word "Architect" to a title is easy to do. However, beneath the surface appearance, distinct approaches and toolsets are required to succeed. Reports of IT overspending and project failures emphasize the fact that these skills must be leveraged and developed. The practical application of this growing body of knowledge will continue to play an important role in the maturing of our profession, and its ability to deliver effective solutions. The Software Architect possesses a unique perspective and mental framework that guides the development of Software systems. Additionally, strong interpersonal skills are vital to the Software Architect's success. In this paper, I explore the unique approaches and characteristics of the successful Software Architect.

Chengzheng Sun - One of the best experts on this subject based on the ideXlab platform.

  • CollaborateCom - Real-Time Collaborative Software Modeling Using UML with Rational Software Architect
    2006 International Conference on Collaborative Computing: Networking Applications and Worksharing, 2006
    Co-Authors: Siyuan Liu, Yang Zheng, Haifeng Shen, Steven Xia, Chengzheng Sun
    Abstract:

    Modeling is commonly used in the process of Software development. UML (Unified Modeling Language) is a standard Software modeling language and has been widely adopted for Software analysis and design. As Software systems are getting lager and more complex nowadays, Software modeling using UML often requires collective and collaborative efforts from multiple Software designers. In contrast, most of today's Software modeling applications are still single-user-oriented and do not offer much help to coordinate interaction and collaboration among team members. In this paper, we will present the technical challenges and solutions in providing advanced collaboration capabilities and transparently integrating them into mainstream Software modeling applications to effectively facilitate collaboration among geographically dispersed Software designers. The work has been tested and demonstrated by the design of CoRSA (Collaborative Rational Software Architect) ? an experimental collaborative Software modeling prototype based on RSA, one of the most widely used commercial Software modeling applications in the market.

  • Real-Time Collaborative Software Modeling Using UML with Rational Software Architect
    2006 International Conference on Collaborative Computing: Networking Applications and Worksharing, 2006
    Co-Authors: Siyuan Liu, Yang Zheng, Haifeng Shen, Steven Xia, Chengzheng Sun
    Abstract:

    Modeling is commonly used in the process of Software development. UML (Unified Modeling Language) is a standard Software modeling language and has been widely adopted for Software analysis and design. As Software systems are getting larger and more complex nowadays, Software modeling using UML often requires collective and collaborative efforts from multiple Software designers. In contrast, most of today's Software modeling applications are still single-user-oriented and do not offer much help to coordinate interaction and collaboration among team members. In this paper, we will present the technical challenges and solutions in providing advanced collaboration capabilities and transparently integrating them into mainstream Software modeling applications to effectively facilitate collaboration among geographically dispersed Software designers. The work has been tested and demonstrated by the design of CoRSA (Collaborative Rational Software Architect) - an experimental collaborative Software modeling prototype based on RSA, one of the most widely used commercial Software modeling applications in the market

Philippe Kruchten - One of the best experts on this subject based on the ideXlab platform.

  • Controversy Corner: What do Software Architects really do?
    Journal of Systems and Software, 2008
    Co-Authors: Philippe Kruchten
    Abstract:

    To be successful, a Software Architect-or a Software Architecture team, collectively-must strike a delicate balance between an external focus-both outwards: Listening to customers, users, watching technology, developing a long-term vision, and inwards: driving the development teams-and an internal, reflective focus: spending time to make the right design choices, validating them, and documenting them. Teams that stray too far away from this metastable equilibrium fall into some traps that we describe as antipatterns of Software Architecture teams.

  • the Software Architect
    IEEE IFIP International Conference on Software Architecture, 1999
    Co-Authors: Philippe Kruchten
    Abstract:

    Much has been written recently about Software Architecture, how to represent it, and where design fits in the Software development process. In this article I will focus on the people who drive this effort: the Architect or a team of Architects—the Software Architecture team. Who are they, what special skills do they have, how do they organise themselves, and where do they fit in the project or the organisation?

  • the Software Architect and the Software Architecture team
    1999
    Co-Authors: Philippe Kruchten
    Abstract:

    Much has been written recently about Software Architecture, how to represent it, and where design fits in the Software development process. In this article I will focus on the people who drive this effort: the Architect or a team of Architects-the Software Architecture team. Who are they, what special skills do they have, how do they organise themselves, and where do they fit in the project or the organisation?

  • WICSA - The Software Architect
    Software Architecture, 1999
    Co-Authors: Philippe Kruchten
    Abstract:

    Much has been written recently about Software Architecture, how to represent it, and where design fits in the Software development process. In this article I will focus on the people who drive this effort: the Architect or a team of Architects—the Software Architecture team. Who are they, what special skills do they have, how do they organise themselves, and where do they fit in the project or the organisation?

Len Bass - One of the best experts on this subject based on the ideXlab platform.

  • The Software Architect and DevOps
    IEEE Software, 2017
    Co-Authors: Len Bass, Kieran Taylor, Aruna Ravichandran, Peter Waterhouse
    Abstract:

    DevOps practices deal with such things as the velocity of releases, how fast incidents are handled, and the enforcement of organizationally specified security practices. All these are critical for success in today's environment, and the Architect is critical for success in adopting DevOps practices. This instalment of the Pragmatic Architect explains why.

  • devops a Software Architect s perspective
    2015
    Co-Authors: Len Bass, Ingo Weber, Liming Zhu
    Abstract:

    The First Complete Guide to DevOps for Software Architects DevOps promises to accelerate the release of new Software features and improve monitoring of systems in production, but its crucial implications for Software Architects and Architecture are often ignored. In DevOps: A Software Architects Perspective, three leading Architects address these issues head-on. The authors review decisions Software Architects must make in order to achieve DevOps goals and clarify how other DevOps participants are likely to impact the Architects work. They also provide the organizational, technical, and operational context needed to deploy DevOps more efficiently, and review DevOps impact on each development phase. The authors address cross-cutting concerns that link multiple functions, offering practical insights into compliance, performance, reliability, repeatability, and security. This guide demonstrates the authors ideas in action with three real-world case studies: datacenter replication for business continuity, management of a continuous deployment pipeline, and migration to a microservice Architecture. Comprehensive coverage includes Why DevOps can require major changes in both system Architecture and IT roles How virtualization and the cloud can enable DevOps practices Integrating operations and its service lifecycle into DevOps Designing new systems to work well with DevOps practices Integrating DevOps with agile methods and TDD Handling failure detection, upgrade planning, and other key issues Managing consistency issues arising from DevOps independent deployment models Integrating security controls, roles, and audits into DevOps Preparing a business plan for DevOps adoption, rollout, and measurement

  • Designing Software Architecture to Achieve Business Goals
    2010
    Co-Authors: Len Bass
    Abstract:

    Abstract : This presentation, which Len Bass gave to the Academy of Software Engineering Education and Training on March 12, 2010, is based on the truism Software systems are constructed to satisfy business goals. The presentation also answers the questions raised by this truism: Why does the Software Architect need to know business goals? How does the Software Architect determine business goals for a system? Where in your curriculum is the material taught?

  • Proceedings of the first international workshop on Leadership and management in Software Architecture
    2008
    Co-Authors: Brian Berenbach, Len Bass
    Abstract:

    It is our great pleasure to welcome you to the 1st International Workshop on Leadership and Management in Software Architecture -- LMSA08. This year's workshop is the first one that we can recall that was devoted exclusively to leadership and management skills of the Software Architect. The mission of our workshop is to provide vital information to the community at large in two areas -- how can Software engineering education and internal training in industry be improved to get the Architects of tomorrow ready for the management challenges that they will face. Our workshop is off to an inauspicious start, with only 5 presenters. However, we expect a lively workshop and we feel that the attendees and the presenters have some very important things to say; information that can make a real impact on the Software engineering profession. The attendees and chairs cumulatively have extensive experience in the field. Co-chair Len Bass, for example, has written two books on Software Architecture. Co-chair Brian Berenbach, from 1975 to 1993 was a senior solution Architect designing and installing industrial and power plant control systems, first for American Cyanamid Company and then for ABB Corporation. Several of the presenters and attendees have also worked in industry as engineering managers or solution Architects. As project size increases, the chief solution Architect becomes less of a technologist and more of a manager. On very large projects, he becomes the technical management linchpin that can drive a project to successful completion or utter failure. Without awareness of the challenges he or she faces, prior apprenticeships and good people skills, a senior Architect may be unprepared for the challenges of managing diverse teams, complex system construction, with aggressive schedules and rapidly changing technologies. We expect to address these issues in our workshop, and, hopefully, make a real contribution in terms of checklists and guides. Moreover, the Architect and the development team do not exist in a vacuum within an organization. Organizations must provide support for the career development of an Architect, they must understand the importance of Software Architecture in the development life cycle beginning with project feasibility and including project budget and scheduling. Our presented papers touch on some of these issues -- the Architect skill set and the training of the Architect. The papers by Berenbach, Creighton and Singer, Islam and Dong and Ali Babar deal with the skills of the Software Architect. The paper by Sangwan and Ros touches on the organizational implications associated with global development. We expect the workshop to deal not only with the individual skills of the Architect and how they develop them but the educational and organizational infrastructure to nurture and support them.

Siyuan Liu - One of the best experts on this subject based on the ideXlab platform.

  • CollaborateCom - Real-Time Collaborative Software Modeling Using UML with Rational Software Architect
    2006 International Conference on Collaborative Computing: Networking Applications and Worksharing, 2006
    Co-Authors: Siyuan Liu, Yang Zheng, Haifeng Shen, Steven Xia, Chengzheng Sun
    Abstract:

    Modeling is commonly used in the process of Software development. UML (Unified Modeling Language) is a standard Software modeling language and has been widely adopted for Software analysis and design. As Software systems are getting lager and more complex nowadays, Software modeling using UML often requires collective and collaborative efforts from multiple Software designers. In contrast, most of today's Software modeling applications are still single-user-oriented and do not offer much help to coordinate interaction and collaboration among team members. In this paper, we will present the technical challenges and solutions in providing advanced collaboration capabilities and transparently integrating them into mainstream Software modeling applications to effectively facilitate collaboration among geographically dispersed Software designers. The work has been tested and demonstrated by the design of CoRSA (Collaborative Rational Software Architect) ? an experimental collaborative Software modeling prototype based on RSA, one of the most widely used commercial Software modeling applications in the market.

  • Real-Time Collaborative Software Modeling Using UML with Rational Software Architect
    2006 International Conference on Collaborative Computing: Networking Applications and Worksharing, 2006
    Co-Authors: Siyuan Liu, Yang Zheng, Haifeng Shen, Steven Xia, Chengzheng Sun
    Abstract:

    Modeling is commonly used in the process of Software development. UML (Unified Modeling Language) is a standard Software modeling language and has been widely adopted for Software analysis and design. As Software systems are getting larger and more complex nowadays, Software modeling using UML often requires collective and collaborative efforts from multiple Software designers. In contrast, most of today's Software modeling applications are still single-user-oriented and do not offer much help to coordinate interaction and collaboration among team members. In this paper, we will present the technical challenges and solutions in providing advanced collaboration capabilities and transparently integrating them into mainstream Software modeling applications to effectively facilitate collaboration among geographically dispersed Software designers. The work has been tested and demonstrated by the design of CoRSA (Collaborative Rational Software Architect) - an experimental collaborative Software modeling prototype based on RSA, one of the most widely used commercial Software modeling applications in the market