BIM建模技术概论试题三
BIM建模技术概论试题三
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （1）defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （2）in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The（3） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （4）may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （5）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
（3）是（）A:enterprise architecture B:technical architecture C:infrastructure architecture D:business architecture
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （1）defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （2）in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The（3） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （4）may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （5）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
（4）是（）A:enterprise architecture B:data architecture C:application architecture D:information architecture
A system's architecture is a representation of a system in which there is a mapping of (1) onto hardware and software components, a mapping of the (2) onto the hardware architecture, and a concem for the human interaction with these components. That is, system architecture is concerned with a total system, including hardware, software, and humans. Software architectural structures can be divided into three major categories, depending on the broad nature of the elements they show.1) (3) embody decisions as a set of code or data units that have to be constructed or procured. 2) (4) embody decisions as to how the system is to be structured as set of elements that have runtime behavior and interactions. 3) (5) embody decisions as to how the system will relate to nonsoftware structures in its environment (such as CPUs, file systems, networks, development teams, etc. ).
空白（2）处应选择（）A:physical components B:network architecture C:software architecture D:interface architecture
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (1) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (2) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (3) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (4) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (5) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
空白（3）处应选择（）A:enterprise architecture B:technical architecture C:infrastructure architecture D:business architecture
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (1) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (2) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (3) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (4) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (5) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
空白（4）处应选择（）A:enterprise architecture B:data architecture C:application architecture D:information architecture
A system’s architecture is a representation of a system in which there is a mappingof （）onto hardware and software components, a mapping of the （）onto thehardware architecture, and a concern for the human interaction with these components. That is,system architecture is concerned with a total system, including hardware, software, andhumans. Software architectural structures can be divided into three major categories,depending on the broad nature of the elements they show.
1.（） embody decisions as aset of code or data units that have to be constructed or procured.
2.（） embody decisionsas to how the system is to be structured as set of elements that have runtime behavior andinteractions.
3.（） embody decisions as to how the system will relate to nonsoflwarestructures in its environment (such as CPUs, file systems, networks, development teams, etc.).
A:physical components B:network architecture C:software architecture D:interface architecture
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (71) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (72) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (73) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (74) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (75) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
（73）处填（）。A:enterprise architecture B:technical architecture C:infrastructure architecture D:business architecture
The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (71) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (72) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (73) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (74) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (75) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
（75）处填（）。A:product-line architecture B:reference architecture C:technology architecture D:infrastructure architecture
The software architecture is a set of software components, subsystems, relationships,interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （） defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （） in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The （） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
The （） defines the key strategiesA:enterprise architecture B:technical architecture C:infrastructure architecture D:business architecture
The software architecture is a set of software components, subsystems, relationships,interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （） defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （） in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The （） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.
the （） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise.A:enterprise architecture B:data architecture C:application architecture D:information architecture
