Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Problem Solving Methodology (PSM)

Analysis - Design - Development - Evaluation (ADDE)
by

Kieran Skewes

on 30 May 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Problem Solving Methodology (PSM)

Problem-solving methodology Analysis Design Development Evaluation Solution Requirements Solution Constraints Scope of Solution Identify the features and the funtionality that need to be included in the solution
What information it needs to produce
And the data needed to produce said information Identify possible limitations on the development of the solution
These can include: Cost (to develop and maintain)
Needs of the user
Legal issues
Security needs
Equipment (both hardware and software) Outlining what the solution will do, what it won't do and how the solution will benefit the user Solution Design Designing how the solution will look and function. Designs should clearly show what the solution will look like, the structure of the solution and how it will be constructed.
Tools used to show how the data will be structured include: IPO charts and flowcharts.
Tools used to show relationships between components/data inlcude: Entity-relationship diagrams (ERDs) and sitemaps.
And Tools used to show the appearance and layout of the solutions include: Storyboards and Layout Diagrams. Evaluation
Criteria Establish the criteria that will be used at a later date to assess how well the solution has met its requirements. Manipulation
(coding) Validation Testing Documentation Manipulate (code) data, which basically means create the solution according to the tools used in the design phase. Check the accuracy of all data that has been used. This can be via manual validation (proofreading) or electronic validation (testing the solution itself). Testing the solution to ensure all aspects function appropriately. Usually done via a testing table.
Data to be tested includes: formulas, validation, functionality and layout/appearance. Document how to use the solution. Write how the user operates the solution, generates reports and troubleshooting. Strategy Report Create a strategy for when various elements of the solution will be evaluated and how data will be collected to see if it meets the criteria specified in the design phase. Based on the findings from the evaluation stage (whether or not it meets the oulined criteria), provide the user with feedback about how well the solution meets their requirements. By Kieran Skewes
Full transcript