<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif"">Good morning,
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">First year SD teacher - so my apologies if this has been discussed and resolved in the past.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">I've noticed that Context Diagrams, Data Flow Diagrams and Use Case Diagrams are all mentioned in both the Analysis and Design sections of the PSM, page 17 in the study design.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">Analysis involves:
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">• Determining the solution requirements. What information does the solution have to provide? What data is needed to produce the information? What functions does the solution
have to provide? These requirements can be classified as being functional, namely what the solution is required to do, and non-functional, which describes the attributes the solution should possess, such as userfriendliness, reliability, portability, robustness,
maintainability. Tools to assist in determining the solution requirements include
<b><span style="background:yellow;mso-highlight:yellow">context diagrams, data flow diagrams and use cases.</span></b><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black"><snip><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">Design involves:<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Calibri","sans-serif";
color:black">• Planning how the solution will function, and the appearance of the resulting information. The solution design typically involves identifying what specific data is required
and how the data will be named, structured, validated and manipulated. Typical design tools for this purpose include data dictionaries and data structure diagrams, input-process-output (IPO) charts, flowcharts, pseudocode, object descriptions. Solution design
also involves, where appropriate, showing how the various components of a solution relate to one another, for example web pages, style sheets, scripts; queries, forms, reports; modules, procedures, functions. Typical design tools used to show relationships
include storyboards, site maps, entity-relationship diagrams, <b><span style="background:yellow;mso-highlight:yellow">data flow diagrams</span></b>, structure charts, hierarchy charts,
<b><span style="background:yellow;mso-highlight:yellow">context diagrams, use cases</span></b>. Planning the solution also involves determining the appearance of information generated from a solution. This typically involves identifying the position of text,
images and graphics, font sizes, colours and text enhancements. Design tools used for this purpose include layout diagrams, annotated diagrams/mocks up.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It’s my understanding that context diagrams, data flow diagrams and use cases should only appear in the analysis stage of the PSM.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is this correct?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter Langham<o:p></o:p></p>
<p class="MsoNormal">Narre Warren South P-12 College<o:p></o:p></p>
</div>
<p></p><p><b>Important - </b>This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.</p>
</body>
</html>