Key Project Disciplines

Engineering assignments and development projects variety considerably in terms of the formality, size, scope, duration and team make-up. As such it is important that all team members share a common core set of skills and understanding in order to work effectively together. Method Maker are pro-active in ensuring each and every team member understands and applies the following disciplines.


USED FOR - Requirements Capture, Conceptual Modelling, System Documentation, and Design Specifications.

BENEFIT/DESCRIPTION - Improving team communication, Unambiguous specification of designs and system documentation.


USED FOR - Analysis and Design.

BENEFIT/DESCRIPTON - Common solutions can be named and referenced by team members, allowing tried and tested work to be leveraged and reused.


USED FOR - Verifying important features, Requirements Feedback, Mitigating key risks, Release Planning.

BENEFIT/DESCRIPTION - Objective assessment of progress through the iterative release and validation of a systems evolutionary development.


USED FOR - Initialising an project with a set of pre-fabricated components of known value.

BENEFITS/DESCRIPTION - Pre-existing sub-systems that are used to reduce the amount of work that needs to be done.


USED FOR - Capturing the essential qualities of a system and constraining the solutions function, form and run-time characteristics.

BENEFIT/DESCRIPTION - Provides the technical backbone for a project; establishing key mechanisms, reference frameworks, and extension points that serve as the foundation for further work.


USED FOR - Defining the roles, activities, artefacts and tool chains to be used on a project.

BENEFIT/DESCRIPTION - Establishes the projects organisational structure and defines consistent terminology around who does what, when and how.