COIS 3030H Lecture Notes - Lecture 5: System Context Diagram, Waterfall Model

• School: Trent University
• Department: Computing & Information Systems
• Course: COIS 3030H
• Professor: Omar Alam

Document Summary

Midterm review: 1 hour and 50mins, 10% knowledge , 10% understanding. Important things: software process activities, classic waterfall model (there is no overlapping of activities) , (when you finish a step, such as specification and analysis, and move on to the next, you cant go back) Iterative software development (do not carry out activities in sequence: knew difference between waterfall and iterative. Optimal benefit area: the cost of developing software should be less then the benefit, difference between software solution and business problem, 3 types of requirements : functional, non- functional, and constraints. Remember the format of writing business events ( event name, input and output: you get the input and output from the work context diagram. Cost assessment: one determinant of the needed functionality is the data stored by the work, be able to list the classes. How-now deals with the current implementation of the project. *requirement elicitation is only focused on determining the business problem, not the operations.