1 / 15

Comprehensive Guide to Design Methodology in VCE IT

This presentation provides an in-depth overview of the design methodology within VCE IT, covering essential topics such as what needs designing, tools available for design, solution functionality, and interface visualization. Key considerations include hardware and software requirements, training and documentation needs, and evaluation criteria. The slideshow details various design tools, including data dictionaries, IPO charts, flowcharts, and pseudocode, and emphasizes the importance of documenting designs for future development phases. This resource is beneficial for both teachers and students involved in Information Technology education.

shina
Télécharger la présentation

Comprehensive Guide to Design Methodology in VCE IT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Problem Solving Metholodogy 2 DESIGN VCE IT Theory Slideshows By Mark Kelly McKinnon Secondary College Vceit.com

  2. Contents • What needs designing? • Design tools

  3. Design... • How the solution will work • What interfaces and outout will look like

  4. Need to design • Hardware needs • Software needs • Training and documentation requirements • Procedures that need to be created or changed • Evaluation criteria

  5. Tools • data dictionaries and data structure diagrams, • input-process-output (IPO) charts, • flowcharts, • pseudocode, • object descriptions.

  6. Designing how bits of the solution fit together – e.g. • Website pages, style sheets, scripts; • Database queries, forms, reports; • Program modules, procedures, functions.

  7. Useful tools for this • Website: storyboards, site maps • Database: entity-relationship diagrams, data flow diagrams, structure charts, • Multipurpose: hierarchy charts, context diagrams, use cases.

  8. Design • Consider alternative designs • More than one way to skin a cat • Some designs may be technically great, but unacceptable because of constraints

  9. Design • Every solution has both pros and cons • What’s acceptable to a developer might be impossible for the client • Selecting a design strategy means achieving maximum “pros” with minimum “cons” • What is a pro or con varies from client to client

  10. Physical Design Tools • These actually plan how to build a system • They give instructions on what to do • Physical data dictionaries (e.g. “Customer_Surname is string, 25 characters”) • Data Flow Diagrams...

  11. Physical Design Tools • Storyboards • Flow Charts, Nassi-Shneiderman charts • Structure Charts • IPO charts • Layout diagrams / mockups • Pseudocode

  12. Designing appearances • layout diagrams, • annotated diagrams/mock ups • prototypes

  13. Designing the evaluation criteria • What measures will be used to judge whether or not the solution requirements have been met? • Should relate to the solution requirements identified in the analysis stage’s logical design.

  14. Design • Must be documented • If successful, will lead to Development phase. If not, cancel the project. • Is used as a strict instruction manual during the following phases, particularly during Development

  15. VCE IT THEORY SLIDESHOWS By Mark Kelly McKinnon Secondary College vceit.com These slideshows may be freely used, modified or distributed by teachers and students anywhere on the planet (but not elsewhere). They may NOT be sold. They must NOT be redistributed if you modify them.

More Related