[Year 12 SofDev] (no subject)

[Mark]

It is an interesting point because there are logical design tools (e.g.
UCD, context diagram) which are used during analysis to plan the
requirements of a solution.
Then there are physical design tools which are used during design to plan
the mechanics of a solution - e.g. IPO, pseudocode.

I'd only ever used DFDs as logical design tools, so it's interesting that
Kevork (and Wikipedia) say that DFDs can be used in analysis and design.
 Further research (e.g.
http://www.ask.com/question/difference-between-logical-and-physical-dfd)
says there are both logical and physical DFDs.

Old dog:  one new trick.

Cheers
Mark


On 9 October 2013 11:07, Kevork KROZIAN <kkrozian at ringwoodsc.vic.edu.au>wrote:

>  Hi Peter,
>
>
>
> Yes, you make a good point. UCDs are in analysis only. However Context and
> Data Flow diagrams are found in both analysis and design.
>
>
>
> Kind Regards
>
>
>
> Kevork Krozian
>
> IT Pathways Manager
>
> Ringwood Trade Training Facility
>
> Tel: 0419 356 034
>
>
>
> *From:* sofdev-bounces at edulists.com.au [mailto:
> sofdev-bounces at edulists.com.au] *On Behalf Of *Langham, Peter P
> *Sent:* Wednesday, 9 October 2013 8:49 AM
> *To:* Year 12 Software Development Teachers' Mailing List
> *Subject:* [Year 12 SofDev] (no subject)
>
>
>
> Good morning,
>
>
>
> First year SD teacher - so my apologies if this has been discussed and
> resolved in the past.
>
>
>
> 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.
>
>
>
> Analysis involves:
>
> • 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 *context diagrams, data flow diagrams and use cases.*
>
> <snip>
>
> Design involves:
>
> • 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, *data flow diagrams*, structure charts,
> hierarchy charts, *context diagrams, use cases*. 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.
>
>
>
> It’s my understanding that context diagrams, data flow diagrams and use
> cases should only appear in the analysis stage of the PSM.
>
>
>
> Is this correct?
>
>
>
> Thanks,
>
>
>
> Peter Langham
>
> Narre Warren South P-12 College
>
>
> --
Mark Kelly
mark AT vceit DOT com
http://vceit.com

Day 19, I have successfully conditioned my master to smile and write in his
book every time I drool.- Pavlov's Dog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20131009/0d929f77/attachment-0001.html