Inquiry-Based Learning | Glossary

Definition:

Inquiry-based learning is a form of active learning. This starts by posing questions, making observations, problems or scenarios- rather than simply presenting facts. This process is mostly assisted by a facilitator. This can be done in multiple formats like field-work, case studies, investigations, individual and group projects, research projects, requirement gathering.

To develop knowledge or solutions, inquirers are done to identify and research issues. Questions are developed which includes problem-based learning which is generally used in projects as well as research. Inquiry-based learning is principally very closely related to the development and practice of thinking skills. Specific learning processes that people engage during inquiry-learning  is by creating questions of their own, obtaining supporting evidence to answer the questions, explaining the evidence collected, connecting the explanation to the knowledge obtained from the investigative process, creating an argument and justification for the explanation. There are four different levels  of Inquiry based learning i.e. Confirmation Inquiry, Structured Inquiry, Guided Inquiry and Open/True Inquiry. Inquiry requires multiple cognitive processes and variables, such as causality and co-occurrence that enrich with age and experience.

Further Reading:

https://en.wikipedia.org/wiki/Inquiry-based_learning

System Context | Glossary

Definition:

Environment of a system is termed as a system context. A System is connected to it’s environment, it never stands on its own. In order to decide who and what exerts influence on the system being developed, the system context needs to be defined. Knowing the system boundaries, you know the scope of the system.

If you define boundaries of a system you get the clarity on system you are developing, how it impacts the development process and what can be disregarded during development. On analysing the system context it determines stakeholders, processes, documents and events relevant for the system. Demarcating the system boundary defines what functionalities of a system it is supposed to offer and what interfaces to external system exist. Requirement is identified systematically, identifying the relevant context by defining systems border.  This builds foundation for evaluation of the requirements for the new system. If the context is not defined properly during requirements engineering, the system relies on incomplete and inaccurate assumptions which might lead to a faulty behaviour.

Further Reading:

https://www.microtool.de/en/what-is-the-system-context/
https://www.flamelab.de/article/defining-the-system-context/