Skip to main content

IEEE standard for describing the system intensive architecture

 IEEE 1471  Describes the standard for software intensive application modeling also known as software architecture, this standard standardize the common patterns and symbols to architect  simple to complex system architecture .

This standard mainly define the system architecture as a close definition to the stakeholder  description of the system rather then the technical implementation details and focus more on the own side of the story.

It expresses view and viewpoint as a field where viewpoint refers to all the data and the business logic and view refers to its implementation and there is always 1 to 1 correspondence. 

Archimate tool for System modeling

Also in a nutshell: 

IEEE 1471's contributions can be summarized as follows (in this list, items in italics are terms defined by and used in the standard):

  • It provides definitions and a meta-model for the description of architecture
  • It states that an architecture should address a system's stakeholders concerns
  • It asserts that architecture descriptions are inherently multi-view, no single view adequately captures all stakeholder concerns
  • It specifies the notions of view and viewpoint, where a viewpoint identifies the set of concerns and the representations/modeling techniques, etc. used to describe the architecture to address those concerns and a view is the result of applying a viewpoint to a particular system.
  • It establishes content requirements for architecture descriptions and the idea that a conforming architecture description has a 1-to-1 correspondence between its viewpoints and its views.
  • It provides guidance for capturing architecture rationale and identifying inconsistencies/unresolved issues between the views within an architecture description

IEEE 1471 is superseded by ISO/IEC/IEEE 42010:2011, which is the current standardized definition for system modeling and design

Comments

Popular posts from this blog

A dream to program sleep?

I once had a thought: what if we had to program sleep at some point in the future? How are we going to do it? are we able to? I enquired of one of my friends! How would you design a sleep if you had the chance...? (I'm hoping you're one of the unnamed readers) Is there anything you might suggest? The story does not come to an end with these questions. If everything slowed down, or if a pattern stopped reacting the way it usually does, it must be sleep, since when a human is sleeping, they stop reacting to their surroundings, or to any changes in their environment. If this is the case, we are not even close to so-called sleep programming. Because even in my dreams, I can't solve a basic mathematical series that calculates the sum of the nth term. BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT BUT I can go deep into space, but not too close to the sun or too far from the moon; all I know about the moon is a little part ...