Part 4

Question 1

• Impossible to separate or disentangle
• It’s often used to describe things that are so closely linked or connected that they can’t be considered independently

Answer 1

Inextricably

Question 2

• An architectural model presents an abstract view of the sub-systems making up a system
• May include major information flows between sub-systems
• Usually presented as a block diagram
• May identify different types of functional component in the model

Answer 2

System Modelling

Question 3

• Typically parallel projects developing the hardware, software and communications
• May involve some COTS (Commercial Off-the-Shelf) systems procurement
• Lack of communication across implementation teams

Answer 3

Sub-system Development

Question 4

Refers to ready-made products that are sold to the general public and can be used as-is, without needing custom development

Answer 4

Commercial Off-the-Shelf (COTS)

Question 5

• The process of putting hardware, software and people together to make a system
• Should be tackled incrementally so that sub-systems are integrated one at a time
• Interface problems between sub-systems are usually found at this state
• May be problems with uncoordinated deliveries of system components

Answer 5

System Integration

Question 6

• Environmental assumptions may be incorrect
• May be human resistance to the introduction of a new system
• System may have to coexist with alternative systems for some time

Answer 6

System Installation

Question 7

• Refers to the process of gradual change, development, adaptation, or improvement of a system over time
• It encompasses the modifications, updates, enhancements, and transformations that occur as a system responds to various internal and external factors

Answer 7

System Evolution

Question 8

Refers to an outdated software application, platform, or technology that is still in use within an organization despite being outdated or no longer actively supported

Answer 8

Legacy Systems