DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • Application Mapping: 5 Key Benefits for Software Projects
  • Caching Across Layers in Software Architecture
  • Where Does Middleware Stand in Web Development?
  • 6 Easy Ways to Start Coding Accessibly

Trending

  • Spring Authentication With MetaMask
  • Log Analysis Using grep
  • Automated Testing Lifecycle
  • Docker and Kubernetes Transforming Modern Deployment
  1. DZone
  2. Software Design and Architecture
  3. Microservices
  4. Software Architecture Analysis Method (SAAM)

Software Architecture Analysis Method (SAAM)

Todd Merritt user avatar by
Todd Merritt
·
Jan. 07, 13 · Interview
Like (1)
Save
Tweet
Share
15.12K Views

Join the DZone community and get the full member experience.

Join For Free
Software Architecture Analysis Method (SAAM) is a methodology used to determine how specific application quality attributes were achieved and how possible changes in the future will affect quality attributes based on hypothetical cases studies. Common quality attributes that can be utilized by this methodology include modifiability, robustness, portability, and extensibility.

Quality Attribute: Application Modifiability

The Modifiability quality attribute refers to how easy it changing the system in the future will be. This to me is a very open-ended attribute because a business could decide to transform a Point of Sale (POS) system in to a Lead Tracking system overnight. (Yes, this did actually happen to me) In order for SAAM to be properly applied for checking this attribute specific hypothetical case studies need to be created and review for the modifiability attribute due to the fact that various scenarios would return various results based on the amount of changes. In the case of the POS change out a payment gateway or adding an additional payment would have scored very high in comparison to changing the system over to a lead management system.

I personally would evaluate this quality attribute based on the S.O.I.L.D Principles of software design. I have found from my experience the use of S.O.I.L.D in software design allows for the adoption of changes within a system.

Quality Attribute: Application Robustness

The Robustness quality attribute refers to how an application handles the unexpected. The unexpected can be defined but is not limited to anything not anticipated in the originating design of the system. For example: Bad Data, Limited to no network connectivity, invalid permissions, or any unexpected application exceptions.

I would personally evaluate this quality attribute based on how the system handled the exceptions.

Robustness Considerations

  • Did the system stop or did it handle the unexpected error?
  • Did the system log the unexpected error for future debugging?
  • What message did the user receive about the error?

Quality Attribute: Application Portability

The Portability quality attribute refers to the ease of porting an application to run in a new operating system or device. For example, It is much easier to alter an ASP.net website to be accessible by a PC, Mac, IPhone, Android Phone, Mini PC, or Table in comparison to desktop application written in VB.net because a lot more work would be involved to get the desktop app to the point where it would be viable to port the application over to the various environments and devices.

I would personally evaluate this quality attribute based on each new environment for which the hypothetical case study identifies. I would pay particular attention to the following items.

Portability Considerations

  • Hardware Dependencies
  • Operating System Dependencies
  • Data Source Dependencies
  • Network Dependencies and Availabilities 

Quality Attribute: Application Extensibility

The Extensibility quality attribute refers to the ease of adding new features to an existing application without impacting existing functionality.

I would personally evaluate this quality attribute based on each new environment for the following

Extensibility  Considerations

  • Hard coded Variables versus Configurable variables
  • Application Documentation (External Documents and Codebase Documentation.)
  • The use of Solid Design Principles
Software architecture operating system Attribute (computing) application

Opinions expressed by DZone contributors are their own.

Related

  • Application Mapping: 5 Key Benefits for Software Projects
  • Caching Across Layers in Software Architecture
  • Where Does Middleware Stand in Web Development?
  • 6 Easy Ways to Start Coding Accessibly

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: