Software Development, Programming, Testing & Implementation

1. Software Development, Programming, Testing & Implementation

2. Sub-stages • Software Development • Testing • Installation

3. Software Development CIE Computing Syllabus, Page 33:

4. Software Development CIE Computing Syllabus, Page 35:

5. Software Development CIE Computing Syllabus, Page 37:

6. Software Development • Code Listing - Complete listing of original code which must be annotated. Use comments and indentation throughout the code to make it readable. • Variables must have meaningful names, use indentation and formatting to show the control structures used. • The code must match the algorithms produced at the Design stage. Annotations should be used to illustrate this matching up. • Remember: Your annotations (using a comment facility from the compiler) should explain the purpose of each part or line of code to the reader. • Your annotations should be complex enough to demonstrate the skills that you have developed as well as solving the problem. • Data structures - With descriptions and evidence of implementation must be included. • Development of Database - Show screen dumps in Design View and Data Sheet View of each table in the new system before and after data has been entered. • Development of Input Methods - Show screen dumps in Design View and Run View of each form in the new system and describe what each control/field on the form does (annotations). • Development of Output Methods - Show screen dumps in Design View and Run View of each report in the database and describe what each field on the report does (annotations). • Development of Database Queries/Filters - Show screen dumps in Design View and SQL View of each query in the database and describe what each query does (annotations). Ensure that you have uncluttered screens and clear instructions.

7. Software Development Points to remember: • In the event of problems occurring, where changes must be made, return to the design, change the design to match what is going to be necessary and then get agreement for the change from the client. • A project that shows continual process of adapting to changing needs reflects a real situation and will earn you credit.

8. Programming • The code listing you provide in the Software Development section would also be used to mark the Programming aspect. • CIE Computing Syllabus, Page 37:

9. Testing • CIE Computing Syllabus, Page 38:

10. Testing • CIE Computing Syllabus, Page 38:

11. Testing • Test Strategy • What is the aim of testing the new system? • What particular features of the new system do you intend to test? • What kind of testing will you be performing yourself? (dry run, variable dumps, black box). • Testing strategy should relate to the problem and the proposed solution. • Test Plan • A table showing the data that will be used for testing, its expected results, the actual results and the • actions that were taken if the actual results didn’t match the expected results. • See example on the next slide.

12. Testing • Example • Provide screen dumps of at least 15 tests from the above table. Make sure these are cross referenced to the above table and annotated.

13. Testing • You also need to produce evidence of user testing (beta testing). The evidence could include: • user comments • photographs • screenshots • interview data • Beta testing must be part of the test plan. Read Section 4.4 g Beta Testing Page 317 (Text)

14. Installation • CIE Computing Syllabus, Page 38:

15. Installation • CIE Computing Syllabus, Page 38: • Read Section 4.4 g Installation Page 317 (Text)

16. Installation • Implementation Plan • A plan for the installation of the necessary hardware and software • A plan for creating the data files • Evidence that the different forms of implementation (e.g. direct implementation, parallel implementation, phased implementation, and pilot implementation) have been explained to the client, that a recommendation has been made and that a client has decided which to choose and why. • What resources/preparations, if any, are needed for the implementation? • How did the implementation go? Were there any problems? If yes, document them. • Evidence of system implementation. • User Training • Is there any need for user training? • If yes, what methods have you identified for user training? • Evidence of user training. • User Testing • Prepare a set of tests that user can perform on the new system. • The user provides you feedback on whether the tests were successful or not. • In case there were some problems, you must fix the problems with the system and communicate to the user that these have been fixed. • Continues on next slide Read Section 4.4 g Installation Page 317 - 318 (Text)

17. Installation • User Acceptance • A letter from the user, on the company letterhead, accepting the software stating that the software works as (or close to) what was originally decided. • In case there are gaps in the original requirements and the new finished system these must be outlined. • Read Section 4.4 g Installation Page 317 - 318 (Text)

18. Installation • Appropriateness of Structure and Exploitation of Available Resources • Use of Available Resources • Briefly mention what type of hardware and software were available to you for developing the system. • These are NOT the hardware and software that you mentioned in the Hardware/Software • Requirements. This is the hardware/software at your home or school where you developed the system. • Briefly discuss whether the available hardware and software was adequate and if you were able to take full advantage from it. • Problem Log • You need to clarify any problems that you have faced during the development of the new system. • These problems must be mentioned in form of a chronologically arranged list. • example: • January 12, 2009: I started working on the user interface but the TAB control on my Access were not properly installed. I had to take it to the school lab’s administrator to get it fixed. Wasted two days. • January 27, 2009: Database is complete but now I am finding a lot of validation errors in the coding. I used the original specifications to check the validation one by one and it took me four days worth of work to finally fix all validation errors. • Read Section 4.4 g Installation Page 317 - 318 (Text)

19. Project Approval Form • This should be used after every stage. • However, you must list ALL the deliverables you created. • Failure to list all may result in obtaining a lower mark. • Also put in a Project Approval Form immediately after the deliverable where it is absolutely necessary to have client approval (such as the Design Objectives, Output Design and Input Design.