The purpose of this document is to provide information and guidance to the regulators regarding the discipline of software engineering.
The document provides an introductory rationale that addresses the nature of practice in software engineering, in comparison with common software development.
It is intended to help enforcement and compliance officials to identify software engineering practice that should be regulated – where it is reasonable to expect that somebody is taking professional responsibility for the work, but should not be taken to limit the validity of software engineering work that falls outside this scope.
Note that this document does not attempt to describe the entire scope and depth of the software engineering discipline.
They are not regulations or rules; they seek to define or explain discrete topics related to the practice and regulation of engineering in Canada.
White Paper Computer Term Dissertations In Education
The national guidelines and white papers do not establish a legal standard of care or conduct, and they do not include or constitute legal or professional advice.
Clearly there is a wide range of risk levels presented by such hazards, and this can be a factor in determining if it is software engineering.
For example, software that directly controls hazardous hardware would be classed as  and so development of such software would almost certainly be considered to be the practice of software engineering.
However software engineering practitioners seeking licensure are less likely to be graduates of an accredited program in software engineering, and come from a wide range of backgrounds in industry.
There are thousands of software developers practising in industry, many of whom lack the knowledge, skills and experience to practise engineering.