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