CS330 Chapter Notes - Chapter 13-14: Work Breakdown Structure, User Interface Design, Design Strategy
5 Aug 2016
School
Department
Course
Professor
Document Summary
Project mgmt: accomplish specific objective through interrelated tasks and utilization of resources application of knowledge, skills, tools, and techniques in order to meet project requirements. Bottom-up estimation: estimate time of each task element, like wbs. Monitor progress and compared to planned progress take corrective action if behind schedule / overrunning budget / not meeting expectations. Closure: hand over deliverables, passing documentation to business, releasing staff and equipment. Analysis models: (analysis + system concept + model = system proposal) typical use of the system. Process model: step by step of each use case. Object-oriented: data + process into one graph. Use flow charts: oval = start/end, parallelogram = input/output, rectangle = process, diamond = decision (if statement) Cohesion: how tightly two modules are bound to each other how closely processes in a program are related. Acceptance testing: final certification that system is ready to go system testing: test entire system to see if modules work together.
