Skip to content Skip to navigation

Connexions

You are here: Home » Content » The Software Architect

Navigation

Content Actions
  • Download module PDF
  • Add to ...
    Add the module to:
    • My Favorites
    • A lens
    • An external social bookmarking service
    • My Favorites (What is 'My Favorites'?)
      'My Favorites' is a special kind of lens which you can use to bookmark modules and collections directly in Connexions. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need a Connexions account to use 'My Favorites'.
    • A lens (What is a lens?)

      Definition of a lens

      Lenses

      A lens is a custom view of Connexions content. You can think of it as a fancy kind of list that will let you see Connexions through the eyes of organizations and people you trust.

      What is in a lens?

      Lens makers point to Connexions materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

      Who can create a lens?

      Any individual Connexions member, a community, or a respected organization.

    • External bookmarks
  • E-mail the author

Recently Viewed

This feature requires Javascript to be enabled.

The Software Architect

Module by: Guilherme Mauro Germoglio Barbosa

Summary: This chapter describes the role of the software architect during the software development life cycle.

!!!! PLACEHOLDER FOR SOFTWARE ARCHITECT CHAPTER !!!!

Objectives

By the end of this chapter, the reader must be able to:

  • Understand the role of the software architect during software life cycle; and
  • Identify desirable characteristics for a software architect.

The role and capabilities of an architecture must be understood. So, this chapter is dedicated to this stakeholder. The chapter's messages are:

  1. The architect is an stakeholder to be considered when designing an architecture.
  2. The architect must have expert knowledge of the full system lifecycle including the ability to consider tradeoffs between process and products factors influencing the system.
  3. The architect must have experience and awareness of various architectural approaches with their benefits and drawbacks; the skill to combine the best of each approach into a single system.
  4. The architect must have competence to employ tools and technologies to deal with enormous complexities while constructing and altering architectures.
  5. The architect must be capable to communicate the architecture fundamentals to the team, including marketing and return on investment analysis of the proposed architectural changes.
  6. The architect must be capable to devise solutions and models to supplement and enhance existing systems.
  7. The architects need to think about their software in three ways simultaneously Entry 1:
    • How it is structured as a set of implementation units.
    • How it is structured as a set of elements that have runtime behavior and interactions.
    • How it relates to non-software structures in its environment.

References

  1. Rozanski, Nick and Woods, Eóin. (2005, April). Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional.

Comments, questions, feedback, criticisms?

Send feedback