PPT-Chapter 4 Program Input and the Software Design Process

Chapter 4 Topics Input Statements to Read Values into a Program using gtgt and functions get ignore getline Prompting for Interactive InputOutput IO Using Data Files for Input and Output. Program Development. Asserting Java © Rick Mercer. Outline. Goals . Understand an example of program development. Understand the characteristics of a good algorithm. Understand how algorithmic patterns can help design programs. Development. Methodologies. Damian Gordon. Timeline of Methodologies. 1950s . Code . & Fix. 1960s . Design-Code-Test-Maintain. 1970s . Waterfall . Model. 1980s . Spiral . Lecture 1. 1. Chapter 24 Quality management. Topics covered. Software quality. Software standards. Reviews and inspections. Software measurement and metrics. 2. Chapter 24 Quality management. Software quality management. Lecture 1. 1. Chapter 8 Software testing. Topics covered. Development testing. Test-driven development. Release testing. User testing . 2. Chapter 8 Software testing. Program testing. Testing is intended to show that a program does what it is intended to do and to discover program defects before it is put into use. . Construct, Deliver, and Maintain Systems Projects. Objectives for Chapter 14. Be able to identify the sequence of events that constitutes the in-house development phase of SDLC.. Be familiar with tools used to improve the success of systems construction and delivery activities including prototyping, CASE tools, and the use of PERT and Gantt charts.. Course Outcome 6. says “. Using a . software process model. , . design. and implement a significant . software . application in C. .”. Waterfall . process model . (see Wikipedia). Procedural design – aka . Lecture 1. 1. Chapter 2 Software Processes. Topics covered. Software process models. Process activities. Coping with change. The Rational Unified Process. An example of a modern software process. . 2. Lecture 1. 1. Chapter 6 Architectural design. Topics covered. Architectural design decisions. Architectural views. Architectural patterns. Application architectures. 2. Chapter 6 Architectural design. Lecture 1. 1. Chapter 9 Software evolution. Topics covered. Evolution processes. Change processes for software systems . Program evolution dynamics. Understanding software evolution. Software maintenance. Topics covered. Software processes and process models. Generic models:. Waterfall. i. ncremental development. Reuse-oriented software engineering. Basic process activities:. Specification. Development. Introduction. Steve Chenoweth. Office: . Moench. Room F220. Phone: (812) 877-8974 Cell (937) 657-3885. Email: chenowet@rose-hulman.edu. Agenda. 5:00pm . – Introductions. Syllabus and schedule. Epic Software Quality Failures. Robert reaves. File Input and Output. File. is a named area in a secondary storage that holds a collection of information.. Why would we want to read from a file instead of a keyboard?. Little mistakes.. 1.1 The Software Life Cycle . 1.2 Using Abstraction to Manage Complexity. 1. Attendance Quiz #5. Software Design. 2. Tip #6: Local Declarations. Should I declare locals in the middle of a function or at the top? . Lecture 1. 1. Chapter 8 Software testing. Topics covered. Development testing. Test-driven development. Release testing. User testing . 2. Chapter 8 Software testing. Program testing. Testing is intended to show that a program does what it is intended to do and to discover program defects before it is put into use. .