Intro to prog


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Intro to prog

  1. 1. An Introduction to Program Design CISPROG 1 Hegeman
  2. 2. Introduction <ul><li>A program is a step-by-step series of instructions for a computer </li></ul><ul><li>Computer programming is the process of writing these instructions </li></ul><ul><li>Programmers, or developers, design and write programs using a programming language or development tool </li></ul><ul><li>Java is a programming language that provides the structure for efficient and economical programs </li></ul>
  3. 3. Programming a Computer <ul><li>Companies need developers to build general application software packages </li></ul><ul><li>Custom applications are built for specific needs </li></ul><ul><li>Existing programs need maintenance, monitoring, and upgrades </li></ul><ul><li>New applications will be needed due to emerging technologies </li></ul>
  4. 4.
  5. 5. Program Development Cycle
  6. 6. Phase 1 – Analyze the Requirements <ul><li>Verify that the requirements are clear and complete </li></ul><ul><li>Evaluate the problem to determine that it is solvable using a program </li></ul><ul><li>List the required input and output data </li></ul><ul><li>Determine whether the input data is available for testing </li></ul>
  7. 7. Phase 1 – Analyze the Requirements <ul><li>Ensure that a solution, or algorithm, can be developed with the information provided in the requirements </li></ul><ul><li>Verify the user interface specifications </li></ul>
  8. 8. Phase 2 – Design the Solution <ul><li>Develop a logical model that illustrates the sequence of steps you will take to solve the problem </li></ul><ul><li>Use design tools such as storyboards, class diagrams, flowcharts, and pseudocode to outline the logic of the program </li></ul>
  9. 9. Phase 2 – Design the Solution <ul><li>Storyboards are sketches of the user interface </li></ul>
  10. 10. Phase 2 – Design the Solution <ul><li>Class Diagrams illustrate the attributes and methods of a class of objects </li></ul><ul><ul><li>Attributes define the characteristics of a class </li></ul></ul><ul><ul><li>Methods are instructions a class uses to manipulate values, generate outputs, or perform actions </li></ul></ul>
  11. 11. Phase 2 – Design the Solution
  12. 12. Phase 2 – Design the Solution <ul><li>Flowcharts graphically represent the logic used to develop an algorithm </li></ul><ul><li>Control structures allow the programmer to specify the code that will execute only if a condition is met </li></ul><ul><li>Flowcharts use pseudocode, English, or mathematical notation inside symbols to represent the steps of a solution </li></ul>
  13. 13.
  14. 14.
  15. 15. Phase 2 – Design the Solution <ul><li>Pseudocode is an English representation of how the program code should be written </li></ul>
  16. 16. Phase 3 – Validate the Design <ul><li>The programmer steps through the solution with test data </li></ul><ul><li>The user agrees that the program design solves the problem put forth in the requirements </li></ul><ul><li>The user verifies that the initial requirements document contains all necessary requirements </li></ul>
  17. 17. Phase 4 – Implement the Design <ul><li>Write the code that translates the design into a program </li></ul><ul><li>Create the user interface </li></ul><ul><li>Create comments within the code that explains the purpose of the code </li></ul><ul><li>Unit testing </li></ul><ul><ul><li>Test the code as it is written </li></ul></ul><ul><li>Test related code </li></ul>
  18. 18. Phase 5 – Test the Solution <ul><li>Create a test plan with test cases of sample input data and expected output </li></ul><ul><li>Perform integration testing to ensure that components interact correctly </li></ul><ul><li>Test boundary values </li></ul><ul><li>Document any problems </li></ul><ul><ul><li>If results are unsatisfactory, a new iteration of the development cycle begins </li></ul></ul>
  19. 19. Phase 6 – Document the Solution <ul><li>Requirements documents, program design documents, user interface documents, and documentation of the code </li></ul><ul><li>Test cases and proof of successful completion of testing </li></ul><ul><li>Program code should be archived electronically </li></ul>