sexta-feira, 6 de maio de 2016

Software Design: Architecture Specification

Architecture Specification (activity) consists of mainly 3 sub-activities:


  1. Define Meta-Architecture Options: Principles, Style, Key Mechanisms; also: select key technologies; specify architectural guidebooks and standards (or identify the external ones to be reused); key mechanisms: coupling control strategy (layers), OOP approach, n-tier approach, layer comm., authentication, authorization, data editing strat., data id. strat., error handling, etc.) 
  2. Define Conceptual Architecture: Partition of the system, allocate responsibilities; On some guidance on how to perform the partition of the system (into subsystems / modules) read more at: http://silvaonsoftware.blogspot.com/2016/05/software-design-design-principles-and.html 
  3. Define Logical Architecture: Model collaborations, design interfaces


Additional Info on the SW Design Process

The SW Design Process has these 3 main tasks:

  1. Architectural Requirements Sub-Activity: Establish architectural relevant requirements - org./functional/non-functional - and this implies: Establish org. goals and constraints, review functional requirements (complement with use cases), review non-functional requirements (associate measurable qualities with use cases) 
  2. Architecture Specification Sub-Activity: (this topic)
  3. Architecture Validation Sub-Activity: Includes Architecture Peer Reviews, Brainstorming Key Decisions, Reuse, Traceability Matrices.


Further information can be found on your "favorite QMS" and here:
Visual Architecting Process (Web version and PDF).