SPMS Documentation¶

The Science Project Management System (SPMS) is DBCA’s project documentation, approval and reporting platform.

Documentation for common SPMS workflows is split by user role:

Project owners and teams: Research Scientists and their colleagues create Projects and are primary authors of Project documentation.
Reviewers: Program Leaders, Regional Leaders, Branch Managers and equivalent heads of SPMS Programs review Project documentation.
Approvers: Directors as heads of SPMS Divisons approve Project documentation.
Administrators: SPMS Administrators act system wide with unrestricted permissions.

See also Frequently Asked Questions. The above should enable SPMS users to fulfil their tasks and operate SPMS.

If you need help or contact anyone about a specific Project or Document in SPMS, please make their lives easier and include the URL to the Project or Document. The URL is shown in your browser when you look at the thing you have a question about and starts with https://scienceprojects.dbca.wa.gov.au/.

Interested readers may learn from the Functional Specification in full detail about the User roles (governing permissions and available actions), and how to advance projects through their life cycles through document approvals.

In tech speak, every feature, button, and workflow of SPMS should be defined in the Functional Specification, we should have a test case covering each requirement and most of the application code (badge “Test Coverage”), and all tests should pass (badge “Test Status”).

Installing, running and maintaining SPMS is documented in the Maintainer Documentation; the software architecture and design decisions are discussed in the Developer Documentation.