暗記メーカー
ログイン
Enterprise Architecture
  • jordan arrivado

  • 問題数 39 • 10/6/2023

    記憶度

    完璧

    5

    覚えた

    17

    うろ覚え

    0

    苦手

    0

    未解答

    0

    アカウント登録して、解答結果を保存しよう

    問題一覧

  • 1

    from the tradition of ultra-reliable, fault-tolerant systems.

    Dependability

  • 2

    from the traditions of the government, banking and academic communities.

    Security

  • 3

    Another important objective of business is to achieve growth.

    GROWTH

  • 4

    the conditions surrounding the stimulus. Might be normal operation, degraded operation, overload, and so on.

    Environment

  • 5

    frequently includes partners, suppliers, and customers.

    Extended enterprise

  • 6

    how the response can be measured and test.

    Response Measure

  • 7

    An enterprise ontology and is a fundamental structure for Enterprise Architecture which provides a way of viewing an enterprise and its information systems from different perspectives, and showing how the components of the enterprise are related.

    ZACHMAN FRAMEWORK

  • 8

    requires complex thinking and strategizing to ascertain which legacy systems can be updated, what software or hardware can be replaced and which services or products will support business operations across each department.

    Enterprise architect role

  • 9

    Hence, a Government may be considered as an

    Enterprise of Enterprise

  • 10

    A business should always try to achieve the best in its field.

    EFFICIENCY

  • 11

    Designed to help businesses collaborate, build reports, run tests and create simulations too manages current enterprise architecture and any future technology that IT might bring into the business.

    ENTERPRISE ARCHITECTURE SOFTWARE

  • 12

    to facilitate shared development of common processes and information among Federal Agencies and other government agencies.

    FEAF - FEDERAL ENTERPRISE ARCHITECTURE FRAMEWORK

  • 13

    the part or parts of the system stimulated.

    Artifact

  • 14

    leverages existing data, technology and process assets as services.

    Reuse

  • 15

    Reuse is possible when a shared service is discoverable, reliably available and accessible

    Interoperability

  • 16

    A business should have the capability to survive markets jolts or shocks

    SURVIVAL

  • 17

    Conceptual integrity, correctness and completeness.

    ARCHITECTURAL QUALITIES

  • 18

    promotes delivery of services rather than tactical point systems/applications.

    Service orientation

  • 19

    Availability, modifiability, performance, security, testability, usability, others.

    SYSTEM QUALITIES

  • 20

    a detailed method and a set of supporting tools - for developing an enterprise architecture.

    TOGAF

  • 21

    Are not related to individual use cases, but rather to system-wide attributes like performance.

    NON-FUNCTIONAL REQUIREMENTS

  • 22

    can help create visualizations, organize data, catalogue IT assets and help with inter-departmental communication

    EA software

  • 23

    from the tradition of hard real-time systems and capacity planning.

    Performance

  • 24

    responsible for the upkeep and maintenance of an organization’s IT networks and services.

    Enterprise architect

  • 25

    work across the organization, determining the needs of a range of business units and processes.

    Enterprise architects

  • 26

    Is a methodology and toolset primarily to support the effective adoption of SOA.

    SAP

  • 27

    Describe what a system should do.

    FUNCTIONAL REQUIREMENTS

  • 28

    means continuity of business. organization can easily handle changing dynamics of markets.

    STABILITY

  • 29

    serves as a guide on how to build a holistic view of all the technology in your enterprise.

    framework

  • 30

    the entity generating the stimulus. Could be an actor, an actuator, a sensor, and so on.

    Source of Stimulus

  • 31

    tools help organizations to make use of agile practices at scale to achieve enterprise-class agile development.

    Gartner EAP

  • 32

    the response the system takes to the stimulus.

    Response

  • 33

    a condition arriving at a system. Includes faults, stated intentions by actors, and so on.

    Stimulus

  • 34

    This is one of the most important objectives of business. We normally setup business to achieve profits for its owner or shareholders.

    PROFITABILITY

  • 35

    from the tradition of hazard analysis and system safety engineering.

    Safety

  • 36

    Designed to help businesses collaborate, build reports, run tests and create simulations too manages current enterprise architecture and any future technology that IT might bring into the business.

    ENTERPRISE ARCHITECTURE SOFTWARE

  • 37

    Time to market, cost and benefit, product lifetime, target market, roll-out schedule, integration, others.

    BUSINESS QUALITIES

  • 38

    Developers of critical systems are responsible for identifying the requirements of the application, developing software that implements the requirements, and for allocating appropriate resources (processors and communication networks).

    SOFTWARE QUALITY ATTRIBUTES

  • 39

    is a collection of organizations that has a common set of goals.

    Enterprise