Index[A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] teams architects CM (configuration management) role collaborating across developers ownership of project plan, establishing sense of project managers interaction with other organizations project managers from development roles project managers from nontechnical backgrounds qualifications for team interaction proposal teams, forming quality assurance personnel requirements analysts software project teams staffing principles technical leads testers toolsmiths technical interchange meetings technical leads technical risks discovering unknown technical risks identifying managing real-world example testers testing 2nd acceptance testing contractor's checklist outsourcing organization's checklist in Waterfall lifecycle migrated data verifying quality in with iterative development 2nd advantages best practices change management needs common mistakes configuration management needs feedback functional testing goals of Independent Validation and Verification (IV&V) ineffective party-party testing little or no performance/load/stress testing performance/stress testing pipelining reliability testing relying on developers requirements management needs resources and defect discovery rates staffing 2nd succumbing to pressure third-party testing unit testing usability testing The Rational Edge three-tiered architecture time, cultural differences tools change request management tools customizable behavior customizable change request lifecycle process customizable data fields customizable e-mail notification integration with other tools metrics collection querying and reporting Web-based interfaces client PCs commercial tools advantages of disadvantages of configuration management tool features and capabilities parallel development management workspace managements configuration management tools custom "in-house" tools advantages of disadvantages of deploying requirements management tools additional capabilities core capabilities requirements changes, tracking servers backup software and media requirements for security shareware toolsmiths tracking requirements changes risks training transaction risks transferring legacy data Transition phase acceptance testing contractor's checklist outsourcing organization's checklist change requests data migration analyzing cleansed data data cleansing extracting legacy data planning points to remember shutting down legacy systems testing migrated data transferring legacy data goals of 2nd installation scripts IOC, deploying online help staffing considerations training user groups, identifying advanced users general users special needs users transitioning to use cases trends configuration management defects requirements management troubleshooting [See mistakes in RUP (Rational Unified Process) implementation.] two-stage procurement processes, implementing artifacts for contractors business and system use cases executables produced by iterations list of risks and risk history other information project glossaries Software Architecture Document supplementary requirements UML models Vision Statements contract types cultural changes for small projects second phase bids |