当碰到某个未知的遗留系统的源代码时，工程师如何能够知道软件元素的什么组合将生成某种有意义的架构描述？
When confronted with the source code of some unknown legacy system, how can an engineer know what grouping of software elements will produce some meaningful description of the architecture?
我们看到“系统工程师”会对一切事情负责，从计划到需求获取，到架构获取，到集成再到测试。
We've seen "Systems Engineers" responsible for everything from planning, to requirements elicitation, to architecture capture, to integration and testing.
通过清晰的验证我们已经描述过的关系，系统工程师最好能够理解他们的努力是怎样被全体的企业架构限制，以及对其有所贡献的。
By clearly illustrating the relationships we've described, systems engineers are better able to understand how their efforts are constrained by, and contribute to, the overall enterprise architecture.
应用推荐