2013 · 15 citations · 13 references
ComputingArchitectural DesignRequirements EngineeringSoftware EngineeringSystems ArchitectureRequirements TraceabilitySoftware ArchitectureSoftware DesignSoftware Quality AssuranceTraceabilityArchitecture Impact AnalysisDesign RationalesImpact AnalysisRequirements Trace LinksSoftware TraceabilityStakeholder SatisfactionTraceability In Software EngineeringTraceability Links
We present an architecture-centric approach for achieving traceability between stakeholders' quality concerns, architecturally significant requirements, design rationales, and source code. In Decision-Centric Traceability (DCT), all trace links are focused around architectural decisions that include factors as varied as platforms, languages, frameworks, patterns, and lower-level architectural tactics. We show how DCT supports critical software engineering activities such as safety-case construction, impact analysis, stakeholder satisfaction analysis, requirements validation, and architectural preservation. Our approach is illustrated and validated with examples drawn from the architectural decisions and subsequent design of the TraceLab project funded by the US National Science Foundation under a Major Research Infrastructure grant.
13
Software Architecture as a Set of Architectural Design Decisions
How do software architects consider non-functional requirements: An exploratory study
David Ameller, Claudia Ayala, Jordi Cabot et al. · 2012 · 113 citations · Full text