System fundamentals: Difference between revisions

From Computer Science Wiki
No edit summary
 
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[file:sql.png|right|frame|SQL programming language<ref>http://www.flaticon.com/</ref>]]
[[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]]


This is pretty straight forward stuff. Nothing especially technical. We are concerned with a the big picture related how systems integrate into organisations and how people use them.  
We are concerned with how systems integrate into organizations and how people use them.  


<html>
<iframe width="560" height="315" src="https://www.youtube.com/embed/IIUbn4avDgA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</html>
== The big ideas in system fundamentals ==  
== The big ideas in system fundamentals ==  
=== Systems in Organizations ===
=== Systems in Organizations ===
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.
=== System Design ===
==== Components of a computer system ====
* [[Hardware, software, peripheral, network, human resources]]
* [[Computers in a networked world]]
* [[Ethics]]
==== System Design and analysis ====
* [[Planning and stakeholder involvement]]
* [[Getting requirements from stakeholders]]
* [[Gathering information for solutions]]
* [[Illustrate system requirements]]
* [[Prototypes]]
==== Planning and system installation ====
==== Planning and system installation ====
* 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
* [[Change management]]
* 1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers. Level: 2
* [[Legacy system]]
* 1.1.4 Compare the implementation of systems using a client’s hardware with hosting systems remotely. Level: 3
* [[Testing implementation|Testing]]
* 1.1.5 Evaluate alternative installation processes. Level: 3
* [[Implementation methods]]
* 1.1.6 Discuss problems that may arise as a part of data migration. Level: 3
* [[Data migration]]
* 1.1.7 Suggest various types of testing. Level: 3
* [[Compare the implementation of systems using a client’s hardware with hosting systems remotely]]


==== User Focus ====
==== User Focus ====


* 1.1.8 Describe the importance of user documentation. Level: 2
* [[User documentation]]
* 1.1.9 Evaluate different methods of providing user documentation. Level: 3
* [[User training]]
* 1.1.10 Evaluate different methods of delivering user training. Level: 3


==== System Backup ====
==== System Backup ====


* 1.1.11 Identify a range of causes of data loss. Level: 2
* [[Data loss]] and preventing data loss
* 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


==== Software Deployment ====  
==== Software Deployment ====  


* 1.1.14 Describe strategies for managing releases and updates. Level: 2
* [[Managing releases and updates]]
 
 


=== System Design ===
==== Components of a computer system ====
* 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
==== System Design and analysis ====
* 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
==== Human interaction with the system ====
==== Human interaction with the system ====
* 1.2.12 Define the term usability. Level: 1
* [[Usability]]
* 1.2.13 Identify a range of usability problems with commonly used digital devices. Level: 2
* [[Problems with usability]]
* 1.2.14 Identify methods that can be used to improve the accessibility of systems. Level: 2
* [[Improve the accessibility of a system]]
* 1.2.15 Identify a range of usability problems that can occur in a system. Level: 2
* [[Moral, ethical, social, economic and environmental implications of the interaction between humans and machines]] (see also [[ethics]])
* 1.2.16 Discuss the moral, ethical, social, economic and environmental implications of the interaction between humans and machines. Level: 3
 
=== Standards ===
 
* Identify the relevant stakeholders when planning a new system.
* Describe methods of obtaining requirements from stakeholders.
* Describe appropriate techniques for gathering the information needed to arrive at a workable solution.
* Construct suitable representations to illustrate system requirements.
* Describe the purpose of prototypes to demonstrate the proposed system to the client.
* Discuss the importance of iteration during the design process.
* Explain the possible consequences of failing to involve the end-user in the design process.
 
 
* Identify the context for which a new system is planned.
* Describe the need for change management.
* Outline compatibility issues resulting from situations including legacy systems or business mergers.
* Compare the implementation of systems using a client’s hardware with hosting systems remotely.
* Evaluate alternative installation processes.
* Discuss problems that may arise as a part of data migration.
* Suggest various types of testing.
* Describe the importance of user documentation.
* Evaluate different methods of providing user documentation.
* Evaluate different methods of delivering user training.
* Identify a range of causes of data loss.
* Outline the consequences of data loss in a specified situation.
* Describe a range of methods that can be used to prevent data loss.
* Describe strategies for managing releases and updates.
* Define the terms: hardware, software, peripheral, network, human resources.
* Describe the roles that a computer can take in a networked world.
* Discuss the social and ethical issues associated with a networked world.  
* Discuss the social and ethical issues associated with the introduction of new IT systems
* Define the term usability.
* Identify a range of usability problems with commonly used digital devices.  
* Identify methods that can be used to improve the accessibility of systems.
* Identify a range of usability problems that can occur in a system.  
* Discuss the moral, ethical, social, economic and environmental implications of the interaction between humans and machines.
 
== References ==
<references />


[[Category:System fundamentals]]
[[Category:System fundamentals]]

Latest revision as of 08:24, 7 November 2024

System Fundamentals[1]

We are concerned with how systems integrate into organizations and how people use them.

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.

System Design[edit]

Components of a computer system[edit]

System Design and analysis[edit]


Planning and system installation[edit]

User Focus[edit]

System Backup[edit]

Software Deployment[edit]


Human interaction with the system[edit]

Standards[edit]

  • Identify the relevant stakeholders when planning a new system.
  • Describe methods of obtaining requirements from stakeholders.
  • Describe appropriate techniques for gathering the information needed to arrive at a workable solution.
  • Construct suitable representations to illustrate system requirements.
  • Describe the purpose of prototypes to demonstrate the proposed system to the client.
  • Discuss the importance of iteration during the design process.
  • Explain the possible consequences of failing to involve the end-user in the design process.


  • Identify the context for which a new system is planned.
  • Describe the need for change management.
  • Outline compatibility issues resulting from situations including legacy systems or business mergers.
  • Compare the implementation of systems using a client’s hardware with hosting systems remotely.
  • Evaluate alternative installation processes.
  • Discuss problems that may arise as a part of data migration.
  • Suggest various types of testing.
  • Describe the importance of user documentation.
  • Evaluate different methods of providing user documentation.
  • Evaluate different methods of delivering user training.
  • Identify a range of causes of data loss.
  • Outline the consequences of data loss in a specified situation.
  • Describe a range of methods that can be used to prevent data loss.
  • Describe strategies for managing releases and updates.
  • Define the terms: hardware, software, peripheral, network, human resources.
  • Describe the roles that a computer can take in a networked world.
  • Discuss the social and ethical issues associated with a networked world.
  • Discuss the social and ethical issues associated with the introduction of new IT systems
  • Define the term usability.
  • Identify a range of usability problems with commonly used digital devices.
  • Identify methods that can be used to improve the accessibility of systems.
  • Identify a range of usability problems that can occur in a system.
  • Discuss the moral, ethical, social, economic and environmental implications of the interaction between humans and machines.

References[edit]