System fundamentals

From Computer Science Wiki
Revision as of 12:18, 8 April 2016 by Bmackenty (talk | contribs) (Created page with "The big ideas in system fundamentals are: * 1.1.1 Identify the context for which a new system is planned. Level: 2 * 1.1.2 Describe the need for change management. Level: 2 *...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

The big ideas in system fundamentals are:

  • 1.1.1 Identify the context for which a new system is planned. Level: 2
  • 1.1.2 Describe the need for change management. Level: 2
  • 1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers. Level: 2
  • 1.1.4 Compare the implementation of systems using a client’s hardware with hosting systems remotely. Level: 3
  • 1.1.5 Evaluate alternative installation processes. Level: 3
  • 1.1.6 Discuss problems that may arise as a part of data migration. Level: 3
  • 1.1.7 Suggest various types of testing. Level: 3
  • 1.1.8 Describe the importance of user documentation. Level: 2
  • 1.1.9 Evaluate different methods of providing user documentation. Level: 3
  • 1.1.10 Evaluate different methods of delivering user training. Level: 3
  • 1.1.11 Identify a range of causes of data loss. Level: 2
  • 1.1.12 Outline the consequences of data loss in a specified situation. Level: 2
  • 1.1.13 Describe a range of methods that can be used to prevent data loss. Level: 2
  • 1.1.14 Describe strategies for managing releases and updates. Level: 2
  • 1.2.1 Define the terms: hardware, software, peripheral, network, human resources. Level: 1
  • 1.2.2 Describe the roles that a computer can take in a networked world. Level: 2
  • 1.2.3 Discuss the social and ethical issues associated with a networked world. Level: 3
  • 1.2.4 Identify the relevant stakeholders when planning a new system. Level: 2
  • 1.2.5 Describe methods of obtaining requirements from stakeholders. Level: 2
  • 1.2.6 Describe appropriate techniques for gathering the information needed to arrive at a workable solution. Level: 2
  • 1.2.7 Construct suitable representations to illustrate system requirements. Level: 3
  • 1.2.8 Describe the purpose of prototypes to demonstrate the proposed system to the client. Level: 2
  • 1.2.9 Discuss the importance of iteration during the design process. Level: 3
  • 1.2.10 Explain the possible consequences of failing to involve the end-user in the design process. Level: 3
  • 1.2.11 Discuss the social and ethical issues associated with the introduction of new IT systems. Level: 3
  • 1.2.12 Define the term usability. Level: 1
  • 1.2.13 Identify a range of usability problems with commonly used digital devices. Level: 2
  • 1.2.14 Identify methods that can be used to improve the accessibility of systems. Level: 2
  • 1.2.15 Identify a range of usability problems that can occur in a system. Level: 2
  • 1.2.16 Discuss the moral, ethical, social, economic and environmental implications of the interaction between humans and machines. Level: 3