Unified Modeling Language

Unified Modeling Language (UML) is a standardized visual language for specifying, visualizing, constructing, and documenting software systems. Its diagram types represent both system structure and behavior.

Class diagram: A diagram showing classes, their attributes and operations, and relationships among them. It captures the static structure of object-oriented software in UML.
UML metamodel: A formal model defining UML’s modeling concepts and the relationships among them. It specifies the language elements from which UML diagrams are built.
Grady Booch: A software engineer who developed an influential object-oriented analysis and design method. His method contributed concepts and notation to UML’s formation.
Software architecture: The fundamental structures of a software system and the principles guiding its design and evolution. UML diagrams can describe architectural components, interfaces, and interactions.
Business Process Model and Notation: A standardized graphical notation for specifying business processes. BPMN focuses on business workflows, while UML covers broader software structures and behaviors.
Sequence diagram: A diagram showing how participants exchange messages over time. It represents the order of interactions between system parts.
UML profile: A set of extensions that adapts UML for a particular domain or purpose. Profiles customize UML without replacing its underlying metamodel.
James Rumbaugh: A computer scientist who created the Object Modeling Technique for software analysis and design. His OMT method was one of the approaches unified into UML.
Software design: The process of defining a software system’s components, interfaces, and internal organization. UML provides visual notations for expressing design decisions.
Systems Modeling Language: A modeling language derived from UML for systems engineering across hardware, software, and people. SysML adapts UML concepts for systems engineering rather than software alone.

Linked from 1 page