System fundamentals: Difference between revisions
Mr. MacKenty (talk | contribs) |
Mr. MacKenty (talk | contribs) |
||
| Line 54: | Line 54: | ||
=== Standards === | === Standards === | ||
* 1.1.1 Identify the context for which a new system is planned. Level: 2 | * 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.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.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.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.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.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.7 Suggest various types of testing. [[Level: 3]] | ||
* 1.1.8 Describe the importance of user documentation. Level: 2 | * 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.9 Evaluate different methods of providing user documentation. [[Level: 3]] | ||
* 1.1.10 Evaluate different methods of delivering user training. 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.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.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.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.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.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.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.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.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.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.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.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.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.9 Discuss the importance of iteration during the design process. [[Level: 3]] | ||
== References == | == References == | ||
Revision as of 12:54, 3 June 2016
System Fundamentals[1]
This is pretty straight forward stuff. Nothing especially technical. We are concerned with the big picture related how systems integrate into organisations and how people use them. I used the standards from the IB[2], but added some other topics I think fit into this category (but not included by the IB).
The big ideas in system fundamentals[edit]
Systems in Organizations[edit]
A computer program or computer system is used by people who work in organizations. It is very helpful to understand how people, computers, and organizations work together.
Planning and system installation[edit]
- System planning
- Change management
- Legacy system
- Testing implementation
- Installation process
- Data migration
- Testing
User Focus[edit]
System Backup[edit]
Software Deployment[edit]
System Design[edit]
Components of a computer system[edit]
- Hardware, software, peripheral, network, human resources
- Computers in a networked world
- Social and ethical issues in a networked world (also see ethics)
System Design and analysis[edit]
- Planning and stakeholder involvement
- Getting requirements from stakeholders (see also design process)
- Gathering information for solutions (see also design process)
- Illustrate system requirements (see also design process)
- Prototypes (see also design process)
- Iteration (see also design process)
- Why end-users matter so much (see also design process)
- Social and ethical issues associated with the introduction of new IT systems (see also design process)
Human interaction with the system[edit]
- Usability
- Problems with usability
- Improving usability
- Moral, ethical, social, economic and environmental implications of the interaction between humans and machines (see also ethics)
Standards[edit]
- 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