Google

Rational Unified Process - Defining Software Architecture

  • Analysis: The purpose of this activity is to define candidate architecture for the system based on experience gained from similar systems or in similar problem domains. The architectural patterns, key mechanisms, modeling conventions, reuse strategy for the system is defined. It provides input to the planning process.
  • Design Elements: The purpose of this activity is to analyze interactions of analysis classes to identify Design Model elements.
  • Design Mechanisms: The purpose of this activity is to refine the analysis mechanism into design mechanisms based on the constraints imposed by the implementation.
  • Run-Time Architecture: The purpose of this activity is to analyze concurrency requirements, to identify processes, identify inter-process communication mechanisms, allocate inter-process coordination resources, identify process lifecycles, and distribute model elements among processes.
  • Distribution: The purpose of this activity is to describe how the functionality of the system is distributed across physical nodes. This is required only for distributed systems.
  • Communication: A means to make different elements exchange data among themselves.
  • Persistency: A means to make an element persistent (i.e. exists after the application that is created it ceases to exist)
Analysis-To-Design-To-Implementation Mechanisms Map

Analysis Mechanisms Design Mechanisms Implementation Mechanisms
Communication HLA-RTI PitchRTI 1516
Persistence Relational DBMS MySQL 5.4