Sample project plan (Gantt chart)
A Gantt chart that includes a column called Task (with four tasks listed including Analysis, Design, Development and Evaluation), a column called Duration (in Weeks) (with each task having a duration of four weeks), a column called Dependencies (with the task of Design having a dependency of Analysis, the task of Development having a dependency of Design and the task of Evaluation having a dependency of Development).
There are 16 columns, one for each week. For the task of Analysis Weeks 1-4 are highlighted with a diamond symbol in Week 4 representing a milestone and an arrow pointing to the start of Week 5 for the task of Design to show that Design is dependent on Analysis. For the task of Design Weeks 5-8 are highlighted with a diamond symbol in Week 8 representing a milestone and an arrow pointing to the start of Week 9 for the task of Development to show that Development is dependent on Design. For the task of Development Weeks 9-12 are highlighted with a diamond symbol in Week 12 representing a milestone and an arrow pointing to the start of Week 13 for the task of Evaluation to show that Evaluation is dependent on Development. For the task of Evaluation Weeks 13-16 are highlighted with a diamond symbol in Week 16 representing a milestone.
Process for designing infographics and/or dynamic data visualisations
A block diagram in three columns. The first column has three squares. The top square is labelled Design idea 1. The second square is labelled Design idea 2 and the third square (with dashed lines) is labelled Design idea 3. These three squares have lines connecting to a square in the second column that is labelled Evaluation criteria. This square has an arrow connecting to a rectangle in the third column labelled Detailed designs.
Sample context diagram
A rectangle labelled Entity A has an arrow (labelled Data flow 1) that is pointing to a circle labelled System. A second rectangle labelled Entity B has an arrow (labelled Data flow 3) that is pointing to the circle labelled System. An arrow (labelled Data flow 2) is pointing from the circle labelled System to the rectangle labelled Entity B. A third rectangle labelled Entity C has an arrow (labelled Data flow 5) pointing to the circle labelled System. An arrow (labelled Data flow 4) is pointing from the circle labelled System to the rectangle labelled Entity C.
Sample data flow diagram
A rectangle labelled Entity A has an arrow (labelled Data flow 1) that flows to a circle labelled Process 1. From this circle an arrow (labelled Data flow 2) flows to another circle labelled Process 2. From this circle an arrow (labelled Data flow 3) flows into an open rectangle labelled Data store 1. From this open rectangle an arrow (labelled Data flow 4) flows into a circle labelled Process 3. Coming into this circle is an arrow (labelled Data flow 5) that comes from another circle (labelled Process 4) that has an arrow flowing into it (labelled Data flow 6) coming from a rectangle labelled Entity B. From the circle labelled Process 3 an arrow (labelled Data flow 7) flows into a circle labelled Process 5. From this circle an arrow (labelled Data flow 8) flows into an open rectangle labelled Data store 2. From this open rectangle an arrow (labelled Data flow 9) flows into a circle labelled Process 6. From this circle an arrow (labelled Data flow 11) flows into a rectangle labelled Entity C. From the rectangle an arrow (labelled Data flow 10) flows into the circle labelled Process 6.
Sample use case diagram
A rectangle is labelled System. Inside the rectangle and at the bottom is an ellipse labelled Use case 5. This ellipse has a solid line that connects it to a stick figure of a person outside the rectangle labelled Actor 2. A solid line connects from the stick figure labelled Actor 2 to an ellipse inside the rectangle labelled Use case 4. From the ellipse labelled Use case 5 a dashed arrow (labelled <<extends>>) connects to an ellipse labelled Use case 3. A solid line connects from the ellipse labelled Use case 3 to a stick figure of a person outside the rectangle labelled Actor 3. A dashed arrow (labelled <<includes>>) connects from the ellipse labelled Use case 3 to an ellipse labelled Use case 1. A dashed arrow (labelled <<includes>>) connects the ellipse labelled Use case 5 to the ellipse labelled Use case 1. A stick figure of a person labelled Actor 1 is outside the rectangle. This stick figure connects with a solid line to an ellipse inside the rectangle labelled Use case 2. A dashed arrow (labelled <<includes>>) connects from the ellipse labelled Use case 2 to the ellipse labelled Use case 1.
Process for designing a software solution
A block diagram has 5 rectangles. The first solid rectangle is labelled Design ideas. An arrow connects to a second dotted-line rectangled labelled 'client/user feedback'. An arrow connnected to a third solid rectangle labelled 'Evaluation criteria'. An arrow connects to a fourth dotted-line rectangle labelled 'client/user feedback'. An arrow connects to a fifth solid rectangle labelled 'Detailed design'.
Store Value Ratings (Bar chart)
A bar chart labelled Store Rating Values. The vertical axis is labelled RATING and it in increments of 2 from 0-10. The horizontal-axis is labelled CUSTOMERS and displays the following names: Joe (with a vertical bar with a Rating of 9), Carlos (with no vertical bar), Anton (with a vertical bar with a Rating of 5), a space with a name missing, Dejan (with a vertical bar with a Rating of 10) and Harvey (with a vertical bar with a Rating of 4).