Your browser does not support JavaScript!
AMA University Answers
Login Register

System Integration and Architecture 1

Showing 1-75 of 160 answers

"An architectural style represents a family of related systems"
  • Style Correct
"An operational concept is a shared vision from the perspective of the system’s stakeholders of how the system will be:"
  • Developed, Produced, Deployed, Trained, Used and maintained, Refined, Retired Correct
"Characteristics of Distributed System"
  • Resource Sharing, Openness, Concurrency, Scalable, Fault Tolerant and Transparent Correct
"Conditions that must be true once the use case is run e.g. ;"
  • Post Correct
"Data flow or control flow diagrams"
  • Relationship Model Correct
"Defines subsystem interfaces"
  • Interface Model Correct
"Describes the proposed functionality of the new system"
  • Use Case Correct
"Description of the system output by architectural design"
  • Software Architecture Correct
"Design is the essence of engineering."
  • System Design Correct
"Designed to run on a single user system"
  • Personal System Correct
"Ensures that specific hardware/software components fit together smoothly in a stated configuration"
  • System Integration Correct
"Graphs of components and connectors"
  • System Correct
"Identified subsystems decomposed into modules"
  • Modular Decomposition Correct
"Is an interaction diagram that emphasizes the time ordering of messages"
  • Sequence Diagram Correct
"Is essential to the development of large, complex engineered systems."
  • System Integration Correct
"Is the design upon which many general purpose computers are based."
  • "Von Neumann Architecture" Correct
"May run on a single processor"
  • Embedded System Correct
"Measures of performance (MOP) and measures of effectiveness (MOE) are obtained"
  • Evaluation Phase Correct
"Model of control relationships among system components is established"
  • Control Modeling Correct
"No distinctions made between clients and servers"
  • Distributed Object Correct
"Offer distributed services which may be called by clients"
  • Client/Server Correct
"People who do similar tasks, have similar skills and/or jobs in an organization"
  • Functional Stucture Correct
"Process for identifying the subsystems that make up a system"
  • Architectural Design Correct
"Represent the non-structural information about the parts of an architecture description"
  • Properties Correct
"Requires the coordination of preexisting and coexisting system components with newly developed ones"
  • System Integration Correct
"Sequence diagram to depict the workflow – as above but graphically portrayed"
  • Scenarios Diagram Correct
"Shows major system components"
  • Static Structural Model Correct
"Shows process structure of the system"
  • Dynamic Process Model Correct
"System decomposed into several subsystems"
  • System Structuring Correct
"System software runs on loosely integrated group of cooperating processors linked by a network"
  • Distributed System Correct
"Team members are given more autonomy and expected to take more responsibility for their work."
  • Matrix Structure Correct
"The computational elements and data stores of the system"
  • Components Correct
"The design process begins with the identification of a human need and the reduction of this need to a precise set of specifications for the system to be built."
  • Problem Definition Correct
"The ranking of design alternatives and the ultimate selection of the most preferred design involves the selection of the best parameterization of the best conceptual design."
  • Ranking and Selection Correct
"The result of design synthesis is the selection of a promising set of preliminary or conceptual designs for the system."
  • Parameterization Correct
"The static representatives of the functional and physical"
  • Analysis Phase Correct
"The ultimate step in the design process involves the fabrication and testing of a prototype or system."
  • Prototype and Testing Correct
"These are the formal rules an limitations that a use case operates under, and includes pre-post and invariant conditions."
  • Contraints Correct
"These design concepts need to be converted into for all components and subsystems."
  • Analysis Correct
"Things that the use case must allow the user to do, such as"
  • Requirements Correct
"This involves generating alternative designs, or that might reasonably satisfy system specifications."
  • Design Synthesis Correct
"This kind of structure will ensure greater output of varieties of similar products."
  • Divisional Structure Correct
1st features of System Control Component
  • Management Tools Correct
1st System Integration Life Cycle
  • Requirements definition and specification Correct
1st System Integration Life Cycle : System architecture development ; Requirements definition and specification ; Management plan:program and project plan ; Feasibility analysis
  • Requirements definition and specification Correct
2nd features of System Control Component
  • Directory Tools Correct
2nd System Integration Life Cycle
  • Feasibility analysis Correct
2nd System Integration Life Cycle : Management plan:program and project plan ; Feasibility analysis ; System architecture development ; Requirements definition and specification
  • Feasibility analysis Correct
3rd features of System Control Component
  • Commitment control management mechanism Correct
3rd System Integration Life Cycle
  • System architecture development Correct
3rd System Integration Life Cycle : Management plan:program and project plan ; System design: logical and physical design ; System architecture development ; System
  • System architecture development Correct
4th features of System Control Component
  • Strong support for metadata management Correct
4th System Integration Life Cycle
  • Management plan: program and project plan Correct
4th System Integration Life Cycle : Management plan: program and project plan ; program ; feasibility ; system
  • Management plan: program and project plan Correct
5th System Integration Life Cycle
  • "Systems design: logical and physical design" Correct
5th System Integration Life Cycle : Design ; Command ; Systems design: logical and physical design; System
  • Systems design: logical and physical design Correct
6th System Integration Life Cycle
  • "Implementation: design implementation, system tests, and operational deployment" Correct
6th System Integration Life Cycle : Design ; Feasibility Analysis ; Evaluation ; Implementation: design implementation, system tests, and operational deployment
  • Implementation: design implementation, system tests, and operational deployment Correct
7th System Integration Life Cycle
  • "Evaluation: system review and plan for replacement/retirement" Correct
7th System Integration Life Cycle : Problem Definition ; System Design ; Evaluation: system review and plan for replacement/retirement ; Feasibility Analysis
  • Evaluation: system review and plan for replacement/retirement Correct
A variety of segmentsintended to achieve a specific goal as indicated by plan.
  • System Correct
Acronym: CAE
  • Computer-Aided Engineering Correct
Acronym: CAM
  • Computer-Aided Manufacturing Correct
Acronym: CIM
  • Computer-Integrated Manufacturing Correct
Acronym: CIR
  • Current Instruction Register Correct
Acronym: MAR
  • Memory Address Register Correct
Acronym: MDR
  • Memory Data Register Correct
Acronym: SDLC
  • System Development Life Cycle Correct
Advantages of EA
  • Cost Effectiveness, Time to market, Scability and Ability to deal with complex environment Correct
Advantages of Object-Oriented approach: Allows flexibility in the design as it evolves over time
  • True Correct
Are the peopleinvolved in or affected by project activities
  • Stakeholders Correct
Aremore complex in that they group people in two different ways: by the functionthey perform and by the product team they are working with.
  • Matrix Structure Correct
Characteristics of Distributed System : Resource Sharing, Openness, Concurrency, Scalable, Fault Tolerant and Transparent; System, Openness, Concurrency, Scalable, Fault Tolerant and Transparent ; Resource Sharing, Personal System, Concurrency, Scalable, Fault Tolerant and Transparent
  • Resource Sharing, Openness, Concurrency, Scalable, Fault Tolerant and Transparent Correct
Components expected to demonstrate a product engineering include
  • Segments, Connectors, Systems, Properties, Styles Correct
Conditionsthat must be true once the use case is run e.g. <order is modified andconsistent>;
  • Post Correct
All courses