The Software Development Process Title in Jotter The Steps Describe and Exemplify Steps Iterative Process
ADITDEM <ul><li>A </li></ul><ul><li>D ance  </li></ul><ul><li>I n </li></ul><ul><li>T he  </li></ul><ul><li>D ark </li></u...
A - Analysis <ul><li>Produce a A  Software Specification </li></ul><ul><li>Details exactly what the program will do </li><...
Dance - Design <ul><li>Design the solution what it will look like </li></ul><ul><li>Modular Design  – fit into modules, ca...
Dance - Design <ul><li>Bottom up Design </li></ul><ul><li>Prototyping  </li></ul><ul><li>Design modules and procedures fir...
Design Notations <ul><li>Flow Chart </li></ul>I pure love programming me!
Design Notations <ul><li>Structure Diagrams </li></ul>I pure love programming me!
Design Notations <ul><li>Pseudocode </li></ul><ul><li>1. ask user to enter selection </li></ul><ul><li>2. do while out of ...
Design Notations <ul><li>Data Flow </li></ul><ul><li>To show data flow of information sent between sub programs </li></ul>...
In - Implementation <ul><li>Programming the solution </li></ul><ul><li>Choose language to implement in </li></ul><ul><li>T...
The - Testing <ul><li>Test to make sure it meets Software Specification </li></ul><ul><li>Systematic Testing  develop a te...
The - Testing <ul><li>Comprehensive Testing  test as thoroughly and completely as you can </li></ul><ul><li>Exhaustive Tes...
Test Data <ul><li>Normal Test –  test within the boundaries of expected input </li></ul><ul><li>Should be accepted </li></...
Test Data <ul><li>Extreme Test –  test at the boundaries of expected input </li></ul><ul><li>Should be accepted </li></ul>...
Test Data <ul><li>Exceptional Test –  test out with the expected input </li></ul><ul><li>Shouldn’t be accepted </li></ul>I...
Testing <ul><li>Field Testing  allow users to have a go using the program </li></ul><ul><li>Alpha  testing distributed in ...
Dark - Documentation <ul><li>Technical and User Guide  must be written </li></ul><ul><li>Technical Guide  explains how to ...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Robustness </li></ul><ul><li>Is it able to cope wit...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Reliability </li></ul><ul><li>Does it work regardle...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Portability </li></ul><ul><li>Can it be used on dif...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Maintainability </li></ul><ul><li>How easy is it to...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Readability </li></ul><ul><li>How easy can someone ...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Fitness For Purpose </li></ul><ul><li>Does it fulfi...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>User Interface </li></ul><ul><li>You should conside...
Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Efficiency </li></ul><ul><li>This evaluates the amo...
Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Corrective Maintenance </li></ul><ul><li>Fixing ...
Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Adaptive Maintenance </li></ul><ul><li>Changing ...
Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Perfective Maintenance </li></ul><ul><li>Improvi...
Iterative Nature <ul><li>Repeat Until Ready </li></ul><ul><li>Iteration, repeat, repeat, repeat. </li></ul><ul><li>Any sta...
Upcoming SlideShare
Loading in...5
×

Aditdem

1,166

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,166
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Aditdem

  1. 1. The Software Development Process Title in Jotter The Steps Describe and Exemplify Steps Iterative Process
  2. 2. ADITDEM <ul><li>A </li></ul><ul><li>D ance </li></ul><ul><li>I n </li></ul><ul><li>T he </li></ul><ul><li>D ark </li></ul><ul><li>E very </li></ul><ul><li>M onday </li></ul><ul><li>This is a mnemonic to remember the steps in the correct order </li></ul>I pure love programming me! Monday
  3. 3. A - Analysis <ul><li>Produce a A Software Specification </li></ul><ul><li>Details exactly what the program will do </li></ul><ul><li>Needs to be correct as mistakes are difficult to fix later </li></ul><ul><li>Legally binding contract – must meet specification </li></ul>I pure love programming me!
  4. 4. Dance - Design <ul><li>Design the solution what it will look like </li></ul><ul><li>Modular Design – fit into modules, can be designed by multiple programmers at same time </li></ul><ul><li>Top Down Design – break down into smaller parts </li></ul><ul><li>Step wise refinement until broken down into one line of code </li></ul>I pure love programming me!
  5. 5. Dance - Design <ul><li>Bottom up Design </li></ul><ul><li>Prototyping </li></ul><ul><li>Design modules and procedures first </li></ul>I pure love programming me!
  6. 6. Design Notations <ul><li>Flow Chart </li></ul>I pure love programming me!
  7. 7. Design Notations <ul><li>Structure Diagrams </li></ul>I pure love programming me!
  8. 8. Design Notations <ul><li>Pseudocode </li></ul><ul><li>1. ask user to enter selection </li></ul><ul><li>2. do while out of range </li></ul><ul><li>3. ask user to re-enter selection </li></ul><ul><li>4. loop </li></ul>I pure love programming me!
  9. 9. Design Notations <ul><li>Data Flow </li></ul><ul><li>To show data flow of information sent between sub programs </li></ul>I pure love programming me!
  10. 10. In - Implementation <ul><li>Programming the solution </li></ul><ul><li>Choose language to implement in </li></ul><ul><li>Take account of features which platform and processor it must run on </li></ul><ul><li>Produce Internal Documentation ( Comments ) </li></ul>I pure love programming me!
  11. 11. The - Testing <ul><li>Test to make sure it meets Software Specification </li></ul><ul><li>Systematic Testing develop a test plan – not random </li></ul>I pure love programming me!
  12. 12. The - Testing <ul><li>Comprehensive Testing test as thoroughly and completely as you can </li></ul><ul><li>Exhaustive Testing where you test every part of the program with every type of test data </li></ul>I pure love programming me!
  13. 13. Test Data <ul><li>Normal Test – test within the boundaries of expected input </li></ul><ul><li>Should be accepted </li></ul>I pure love programming me!
  14. 14. Test Data <ul><li>Extreme Test – test at the boundaries of expected input </li></ul><ul><li>Should be accepted </li></ul>I pure love programming me!
  15. 15. Test Data <ul><li>Exceptional Test – test out with the expected input </li></ul><ul><li>Shouldn’t be accepted </li></ul>I pure love programming me! <ul><li>If you are exceptionally drunk you don’t get in the club </li></ul>
  16. 16. Testing <ul><li>Field Testing allow users to have a go using the program </li></ul><ul><li>Alpha testing distributed in company </li></ul><ul><li>Beta testing (acceptance testing) put on general release </li></ul><ul><li>ITG! Independent Test Group – no ties to client or Software Development Company </li></ul><ul><li>Keep a record of testing and any errors found. These are reported to programmer </li></ul>I pure love programming me!
  17. 17. Dark - Documentation <ul><li>Technical and User Guide must be written </li></ul><ul><li>Technical Guide explains how to install the software onto a computer system and the requirements of the system </li></ul><ul><li>User Guide explains how to use software when installed </li></ul>I pure love programming me!
  18. 18. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Robustness </li></ul><ul><li>Is it able to cope with errors during execution without failing </li></ul>I pure love programming me!
  19. 19. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Reliability </li></ul><ul><li>Does it work regardless of design faults </li></ul>I pure love programming me!
  20. 20. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Portability </li></ul><ul><li>Can it be used on different platforms other than the one it was designed for? </li></ul>I pure love programming me!
  21. 21. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Maintainability </li></ul><ul><li>How easy is it to update a program. To correct mistakes and add new features </li></ul>I pure love programming me!
  22. 22. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Readability </li></ul><ul><li>How easy can someone else come and understand your code. Using comments, meaningful variable names, indentation, blank lines, modules </li></ul>I pure love programming me!
  23. 23. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Fitness For Purpose </li></ul><ul><li>Does it fulfil the original software specification? </li></ul>I pure love programming me!
  24. 24. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>User Interface </li></ul><ul><li>You should consider </li></ul><ul><li>Help screens and instruction screens, visual appeal and screen layout, prompts for user </li></ul>I pure love programming me!
  25. 25. Every - Evaluation <ul><li>8 Criteria for assessment </li></ul><ul><li>Efficiency </li></ul><ul><li>This evaluates the amount of memory and processor time the software requires. </li></ul>I pure love programming me!
  26. 26. Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Corrective Maintenance </li></ul><ul><li>Fixing errors by changing the software </li></ul>I pure love programming me!
  27. 27. Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Adaptive Maintenance </li></ul><ul><li>Changing program to run on a new OS, or when updates in hardware require change to the program </li></ul>I pure love programming me!
  28. 28. Monday - Maintenance <ul><li>Three types of Maintenance </li></ul><ul><li>Perfective Maintenance </li></ul><ul><li>Improving the software to enhance how it performs. Increase its speed of operation. Adding in new features </li></ul>I pure love programming me!
  29. 29. Iterative Nature <ul><li>Repeat Until Ready </li></ul><ul><li>Iteration, repeat, repeat, repeat. </li></ul><ul><li>Any stage of the Software Development Process can be revisited again and again and again </li></ul><ul><li>Revisiting again to improve the solution </li></ul><ul><li>Repeat stages in the process when you discover new information </li></ul>I pure love programming me!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×