MoSCoW

MoSCoW for Visual Report is not created as the project has been suspended prior to any requirements establishing.

ID	Requirement	Type	Category	Priority
Design Guide
DGm1	The design guide shall follow professional medical colour scheme guidelines	Functional	Design Guide	Must
DGm2	The design guide shall contain components and code examples with guidelines	Functional	Design Guide	Must
DGm3	The design guide shall contain design elements guidelines	Functional	Design Guide	Must
DGs1	The design guide shall be consistent with the client's design philosophies	Non-functional	Design Guide	Should
DGc1	The design guide shall be scalable and compatible with mobile devices	Functional	Design Guide	Could
DGc2	The design guide shall be updated following changes to project parameters such as framework selection adjustments	Non-functional	Design Guide	Could
DGw1	The design guide shall be built as a static site with Middleman	Functional	Design Guide	Would
Form Renderer
FRs1	Form renderer shall support constructing forms through components fed through the backend	Functional	Form Renderer	Should
FRs2	Form renderer shall push input data back into the backend	Functional	Form Renderer	Should
FRc1	Form renderer shall reject inappropriate input formats	Functional	Form Renderer	Could
FRw1	Form renderer shall be scalable	Functional	Form Renderer	Would
Dashboard
Dm1	Data visualisation shall visualise data through basic graph types	Functional	Dashboard	Must
Ds1	Data visualisation shall be linked with the backend database and output data	Functional	Dashboard	Should
Dc1	Data visualisation shall contain dynamic features	Functional	Dashboard	Could
Dc2	Data visualisation shall contain interactive features	Functional	Dashboard	Could
Dc3	Data visualisation shall be scalable	Functional	Dashboard	Could
Dw1	Data visualisation shall visualise data through more advanced custom graphs	Functional	Dashboard	Would
Others
Om1	All projects are interfaced through a browser, hence web app	Non-Functional	Compliance to standard	Must
Om2	Code to be well documented and annotated	Non-Functional	Compliance to standard	Must
Om3	Methods, choices and research findings are documented	Non-Functional	Compliance to standard	Must
Os1	The front end shall have a consistent theme and design	Non-Functional	Ease of use	Should
Os2	The front end shall have a uptime of 99% if project has finished successfully with other peach sub-teams	Non-Functional	Availability	Should
Oc1	The front end shall be documented with a setup tutorial for non-technical individuals	Non-Functional	Deployment	Could
Oc2	The front end shall have a user satisfaction of 85%	Non-Functional	Ease of use	Could
Oc3	An online manual for use of system with videos outlining features	Non-Functional	Compliance to standard	Could
Ow1	The front end shall prompt the user with the appropriate error messages when triggered	Non-Functional	Ease of use	Would
Ow2	The overall front end shall be scalable to allow expansion of concurrent users	Non-Functional	Capacity	Would
MDT Front-end
FEm1	The UI Team shall mockup the MDT Front-end	Functional	MDT Front-end	Must
FEw1	The MDT front end shall have a log in system for MDT staff and clinicians	Functional	MDT Front-end	Would
FEw2	The MDT front end shall have a search function for patients	Functional	MDT Front-end	Would
FEw3	The MDT front end shall have a messages feature	Functional	MDT Front-end	Would
FEw4	The MDT front end shall have all the core features namely: patients, referrals and meetings	Functional	MDT Front-end	Would
FEw5	The MDT front end shall have scalable interface	Functional	MDT Front-end	Would

The MDT is the multidisciplinary dashboard which provides the frame to hold data visualisation (Dashboard) and Form Renderer. Even though the MDT development is outside of our project scope, our client has advised us to produce some mockups and or wireframes to gain understanding to the environment in which the Form Renderer and data visualisation (Dashboard) will sit.

Tags

background research testing dashboard plans for term 2 our project architecture research