To implement any plug-in for the WAF, it is necessary to create the WAF first. That's why the requirements are split up into three parts: the WAF, the Sort Code System and the Google Contact Application.
To prioritise the features and to show something like a hierarchical structure (some features may part-depend on others) the MoSCoW method is used in this section.
The Sort Code System is about the German bank sort codes. It should be a sort code information system which receives all German bank branches with the linked sort codes and provide them to the WCA user in a searchable interface. It must also be possible to amend the imported sort code and branch data from the administration area.
The MoSCoW method can't be used for the requirements of this application, because they are depending on each other. Without requirement A, requirement B doesn't make any useful sense. The requirements are ordered into a hierarchical structure to show the dependencies (the higher numbers depends on the lower ones).
We have a three-tier structure here. Without the first and the second part, the rest would be useless and not realisable. The tasks from the third section describes the specific features of the sort code system, which the user can directly access and see on the screen (use cases).
The Google Contact Application is a client application of the Google Contacts which are provided from a Google Account. That means in detail that this WCA should provide similar functionalities like the official Google Contacts Client on http://www.google.com/contacts:
This WCA application doesn't need an administrative interface like the sort code program has.