CSC302H1 Lecture 8: 2014.01.30
Document Summary
Software quality = fitness for its purpose: software is designed for a purpose. Requirements analysis needed to identify this purpose. Misunderstood purpose = poor quality software: purpose found in human activities. Many different kinds of people and activites. Ex. purpose of banking systems comes from business activites of banks and needs of their customers. Software design process: hard system view. Requirements can be represented formally in a specification correct. Specification can be validated to ensure its. Correct program = satisfies this specification: soft system view. Software design part of ongoing learning process by context goals organization. Requirements can"t be adequately captured in a specification. Participation of users during development = essential: problem & solution. Can be used to evaluate design choices. Problem situation = in the real world. Validation checks if the implemented system solves the real world problem. Problem statement = formalized problem situation, corresponds to the needs of the stake holders.
