defining the needs for human activity systems, publishing new perspectives on a variety of topics, consulting, training, and special projects.

A variety of curricula is available, classified by topics that are usually requested and are understood generally in the sectors concerned. The various sections discuss courses or training available, and the kinds of consulting projects that have been undertaken.

Enterprise Architecture

An enterprise is a human activity system that results in the provision of one or more products or services. Its architecture is a high-level description of the static real or abstract components of the enterprise and their relationships (including applicable principles and policies) along with a summary of the key processes and dynamics involved in its strategy and operations. Most enterprise architectures are created for one legally bounded entity, but this is not necessarily so, particularly when the product or service is the result of more than one interacting legal entity.

Information Architecture

Information Architecture is concerned with the overall information needs and work of the organization or enterprise. The scope of information architecture includes the use of information for all kinds of information work, whether computer-aided or not. The approach taken to information architecture is a layered approach with different layers dealing with issues right from information needs to systems that enable associated information work. The systems may or may not be computer-supported information systems.

Enterprise Architecture is a concept that followed on from earlier information architecture work. Information Architecture and Enterprise Architecture come together at the level of Business Architecture (one of the components of the Information Architecture layered model presented here).

Enterprise and Information Architecture

Many courses, workshops, and lectures have been given about enterprise and information architecture. Typically, these are customized for specific client needs or context.

The Enterprise and Information Architecture Curriculum includes topics that are the subject of both consulting and training.

Here is a sample curriculum that can be used as a basis to discuss needs and context. Many of the topics are essential for enterprise and information architecture work, but are missing from many mainstream or 'popular' approaches to architecture.

Requirements Engineering is concerned with all matters related to eliciting, representing, and analyzing requirements. The curriculum represented here is independent of any particular tools. As PSL/PSA is the primary tool used by Requirements Analytics, there is a separate curriculum section for that. Related topics can be found in the Meta Modelling curriculum.


  1. Requirements Engineering Overview
  2. Eliciting Requirements
  3. Requirements and Standards


  1. System Requirements
  2. Software Requirements
  3. Defining Completeness and Consistency


  1. Practical Ethnography for Discovering Requirements
  2. Representation of Requirements
  3. Analysis of Requirements
  4. Definition of Completeness Standards

Software Engineering is concerned with all the activities needed from identifying business needs, deciding which of those needs could be assisted by software running on compter-based hardware through to implementation of a required solution. Requirements Analytics™ is not concerned with the whole scope of that cycle. The Software Engineering curriculum in concerned with the earlier actvities from business or organizational needs down to product in dependent designs. The main elements in the curriculum are:


  1. Software Engineering Overview
  2. CASE Fundamentals: Issues, Concepts, and Practice
  3. Introduction for Managers to the Business Use of Computers
  4. Introduction to CSCW


  1. Software Engineering Foundation
  2. Professional Issues in Software Engineering
  3. Method Engineering
  4. Choosing a Development Method


  1. Strategy, Analysis, and Design
  2. Analysis Principles
  3. Design Principles

Requirements modelling usually results in a model of a required system (or software). The notation used for creating such a model can be defined as a meta modelling language. Many notations used for requirements models are graphical. Generally, graphical notations are not well-formed languages. Other modelling languages are linguistic. A linguistic approach to modelling is mcuh more likely to use a well-formed language with the additional properties that the models can be subjected to substantial checking for completeness and consistency.

Meta modellling languages can all be seen as instantiations of a higher form of model, which is a meta meta model. The skill of meta meta modelling is very important to understand what is feasible (and what is not) using any particular meta model notation.


  1. Overview of Models, Meta-models, and Meta-meta Models


  1. Defining a Meta Model
  2. Defining Completeness Standards


  1. Meta Meta Modelling Workshop

Problem Statement Language/Problem Statement Analyzer (PSL/PSA) is one output from what was probably the world's largest research project in requirements modelling. Requirements Analytics™ has a project underway to make PSL/PSA available again as an open source project.

PSL/PSA has been used for both small and large (some very large) projects. It is normally used to model software requirements, but it is not restricted to that. Where a client prefers a variation from the standard PSL/PSA that can be generated, or a client can develop a required variation in a workshop that also acts as a training environment for those likely to use the language.


  1. PSL/PSA Introduction


  1. Using PSL/PSA to Establsih Requirements
  2. Understanding Completeness and Consistency Standards
  3. Creating Corporate Data Models


  1. Using the Problem Statement Language
  2. Analyzing Requirements with the Problem Statement Analyzer
  3. Implementing Completeness Standards
  4. Using PSL/PSA to Create Standards Compliant Requirements Specifications
  5. View Integration System

Classroom Emotional Abuse is one aspect of child safeguarding that receives little attention in safeguarding training and related material, yet it may be the most important in terms of the numbers of people affected and the likely length of time effects can subsist.

Officially, emotional abuse is one important aspect of safeguarding, child protection and safer recruitment. There is our book, Emotional Abuse in the Classroom: the forgotten dimension of safeguarding, child protection, and safer recruitment, which provides essential background reading and should be read by everyone involved in such work.

Overview Seminars

  • What is emotional abuse, and what does it look like in a classroom setting?
  • Recognizing and Managing emotional abuse in the classroom
  • School and Local Authority actions to incorporation abuse into the local curriculum
  • Children Rights
  • Emotional Abuse in Safeguarding for Governors and School Management


  • Teacher Self-Evaluation
  • Pupil Self-Evaluation


  • Audit of the state of classroom conduct in one, or a group of schools


Please contact us with any specific requirements you have for this subject area. We are able to put together any combination of summaries, short training, whole school training, local authority sponsored training, workshops, and audits.