Q.2.5 Identify four use cases that have the Consumer/Public as an actor and create a matching user story for each use case You do not have to include any Acceptance Criteria
• The system must have monitoring tools to make sure that products and services being sold
by financial services providers do meet the needs of the consumers/public.
• The system must have auditing processes to ensure that consumers/the public are given
clear and factual information as approved by the FSCA. Where advice is given, it must be
suitable and be appropriate for the client’s circumstances.
• As part of the end-to-end
public online portal and mobile app so that they are able to log/register complaints and
have those complaints be dealt with accordingly by the commissioners.
• The system should allow consumers/the public to track their current complaints
including a functionality to search all the historical complaints and their resolution.
• Consumers/the public should also be able to access awareness content in form of
research articles and videos.
• The commissioners will have their own back-office admin module/sub system to perform
their day-to-day duties. The sub system should be quick and responsive. Commisioners
can Log/Register complaints on behalf of the public. Especially for matters that are
reported via telephone and not logged on the public online portal.
• The system must have a content publication module/sub system that allows
commissioners to record and publish their findings. All recorded findings should be peer
reviewed and approved by other commissioners before the publication process can take
place.
• The Consumers/the public should be able to access the findings on the online portal and
mobile app once they are published. The online portal should be able to handle a load of
500 users concurrently at any point in time.
• The online portal and mobile app should have a functionality that allows Consumers/the
public to download articles about online ponzi schemes, cybercrime, online fraud and
scams.
Q.2.5 Identify four use cases that have the Consumer/Public as an actor and create a
matching user story for each use case
You do not have to include any Acceptance Criteria
Step by step
Solved in 2 steps
