Decomposition of the task brief

Remember the work done in Activity A(ii) where the concept of Decomposition, Abstraction, and Modularisation were described.

Note

The Task Brief will explicitly mention these as a component that is of value in the design documentation.

In the proposal, you will have explained the approach you will take to the decomposition of the application's functional requirements into smaller component parts to make the code more robust and easier to create and maintain.

In the portfolio you will briefly evaluate the 2 main methods and state which one you will be using. This will be 'Top Down' decomposition.

Having said how it will be done. now it's time to lay out the elements that will be abstracted using a 'top-down' approach.

The content in the elements created will have very string links to the Functional Requirements list from Activity A(ii).

You can review that section here Functional Requirements