System quality attributes have been of interest to the software community since at least the 1970s. Various published taxonomies and definitions exist, and many have their own research and practitioner communities. From the perspective of a system（architect）, there are three common problems with previous discussions of system quality attributes:
The definitions provided for each attribute are not operational. For example, it is （meaningless） to claim that a system is modifiable unless it is clearly stated with respect to which changes it is modifiable and which changes it is not. Other quality attributes face similar issues.
Discussions often focus on which quality attribute a particular issue belongs to. For example, is a system failure an availability issue, a security issue, or a usability issue? All three attribute communities may claim ownership of such a failure.
Each attribute community has developed its own terminology. The（performance）community speaks of "events" arriving at the system, the security community describes "attacks", the availability community discusses "failures", and the usability community refers to "user input". These may all describe the same phenomenon but use different terms.
A solution to the first two problems—non-operational definitions and overlapping concerns—is to use quality attribute（scenarios）to characterize quality attributes in a more structured way. To solve the third problem, a brief discussion of each attribute focusing on its underlying concerns and community（perspectives）can be helpful.
系统质量属性是软件架构设计的核心考量维度，系统架构师是主导其结构化分析、权衡与落地的核心角色，这类工作区别于开发人员聚焦的功能实现与测试人员负责的验证环节。质量属性的定义必须具备可操作性，若仅笼统提出如“系统需具备可修改性”却未明确具体修改范围，这类表述无实际指导意义，会导致需求模糊且无法验证。不同质量属性的研究与实践社区因对系统行为的关注视角存在差异，形成了各自的专属术语体系，比如性能领域用“events”指代系统接收的输入负载，安全社区将同类系统刺激描述为“attacks”，可用性社区称其为“failures”，易用性社区则用“user input”表述，这些术语常指向同一系统现象却表述各异。质量属性场景是解决定义非操作性与关注重叠问题的标准方法，它通过源、刺激、环境、响应、度量等结构化要素，将抽象的质量需求转化为可落地、可验证的具体内容。而要消解不同社区的术语壁垒，需从各社区的核心关注视角切入，明确其对系统行为的不同侧重点，从而实现术语体系的有效对齐。
本题是专业英语完型填空，考查软件工程语境下的术语语义、固定搭配和上下文逻辑。
语境定位：原句为 “From the perspective of a system ____ , there are three common problems with previous discussions of system quality attributes:”。空前 From the perspective of a system；空后 there are three common problems with 是判断本空的关键。
答案判断：上下文强调的专业概念是“架构师，从系统架构角度关注质量属性”，该词能把前后语义自然衔接起来。因此应选 architect。
选项辨析：
A. user：表示或侧重“user 所对应的概念”，但本空需要“架构师，从系统架构角度关注质量属性”，语义范围不匹配。
B. architect：表示“架构师，从系统架构角度关注质量属性”，能准确补足本句语义。
C. developer：表示或侧重“developer 所对应的概念”，但本空需要“架构师，从系统架构角度关注质量属性”，语义范围不匹配。
D. tester：表示或侧重“tester 所对应的概念”，但本空需要“架构师，从系统架构角度关注质量属性”，语义范围不匹配。
因此，选项 B 正确。