CIS 2250 Lecture Notes - Lecture 4: Quality Assurance, Stack Overflow, Local Variable
26 Feb 2019
School
Department
Course
Professor
Document Summary
/ what"s your role: developer, maintenance, quality assurance, tester, manager, student/ trainee. Reading techniques: use of a checklist, checklist contains questions that need to be answered and what to look for to answer these questions, using your [ ] What to look for first: name of functions and variables, loops particularly how they begin and end, libraries used, third-party code integrated with the program. If the code is long then break it into chunks (maybe the authors of the software should have done this) to read it and then see if indeed it should have been modularized more. Difficult to maintain & extend ---- high cohesion / loose coupling ----> easier to maintain & understand. Investigate known problems with code (this particular code or code in general). Example checklist of issues: gets() (in c, break, goto, all loops, all references (pointers in c, error handling (use signals in c, try and catch in java to do error handling)
