Monday March 28th, 2011

Lecture Notes:

• Analysis of the progress and visual measurement of thus is a must for Wiki
• Verifiability of correctness and completion of the requirement
• Consistency: reference to original requirements
• Traceability: a creditation for the work done.
• User stories/cases describe user events and how the system responds to an event
• User cases should be short clear and consistent in the format
• Realistic expectations
• Measurement of project velocity is highly meaningful
• Design patterns, coding standards
• "Every cut and paste code is a newly introduced bug to the code"
• As an exercise -- Pick large task and complete by the end of the week no matter what - test sprint
• Understanding clearly the boundary of the the problem, understanding of protocols on server/client communication
• Re-factor code and try to build into components
• Centralize, localize code and run tons
• UML diagrams
• Other team project disc.: proposed content is too broad; too vague; it was had to summarize and give a description of the project.