COMP 3004 Lecture Notes - Lecture 2: Software Development Process, Finger Tips, Agile Software Development

• School: Carleton University
• Department: Computer Science
• Course: COMP 3004
• Professor: Olga Baysal

Document Summary

Lea(cid:396)(cid:374) f(cid:396)o(cid:373) othe(cid:396)"s e(cid:454)pe(cid:396)ie(cid:374)(cid:272)es: extension of training material, promotes common vision and culture, provides roadmap for applying tools, delivers information on-line, at your finger tips. Low management overhead: process used should depend on type of product which is being developed, for large systems, management is usually the principal problem so you need a strictly managed process. For smaller systems, more informality is possible: high costs may be incurred if you force an inappropriate process on a development team, waterfall (blank slide) Maintenance: steps, specification: talk to stakeholders, document requirements, design: translate system requirements into system architecture, development and testing, maintenance. Integration and system testing: very linear and sequential process and cannot go back. Waterfall: quadrant 4: planning for next steps (ex. future release) and review, this is all one spiral but can do multiple spirals, good for government and military, ex. Implementation model verified by test model: process workflows: business modelling, requirements, architecture and design,