CMMI - SE/SW/IPPD/SS - V1.1 - Software Engineering Institute ...

More documents

Recommendations

Info

CMMI-SE/SW/IPPD/SS, v1.1 Staged Representation SP 1.1 Select Products for Validation Select products and product components to be validated and the validation methods that will be used for each. [PA149.IG101.SP101] Products and product components are selected for validation on the basis of their relationship to user needs. For each product component, the scope of the validation (e.g., operational behavior, maintenance, training, and user interface) should be determined. [PA149.IG101.SP101.N104] The requirements and constraints for performing validation are collected. Then, validation methods are selected based on their ability to demonstrate that user needs are satisfied. The validation methods not only define the technical approach to product validation, but also drive the needs for the facilities, equipment, and environments. This may result in the generation of lower level product-component requirements that are handled by the requirements development processes. Derived requirements, such as interface requirements to test sets and test equipment, may be generated. These requirements are also passed to the requirements development processes to ensure that the product or product components can be validated in an environment that supports the methods. [PA149.IG101.SP101.N101] Validation methods should be selected early in the life of the project so they are clearly understood and agreed to by the relevant stakeholders. [PA149.IG101.SP101.N102] The validation methods address the development, maintenance, support, and training for the product or product component as appropriate. [PA149.IG101.SP101.N103] Typical Work Products 1. Lists of products and product components selected for validation [PA149.IG101.SP101.W101] 2. Validation methods for each product or product component [PA149.IG101.SP101.W102] 3. Requirements for performing validation for each product or product component [PA149.IG101.SP101.W103] 4. Validation constraints for each product or product component [PA149.IG101.SP101.W104] Subpractices 1. Identify the key principles, features, and phases for product or product-component validation throughout the life of the project. [PA149.IG101.SP101.SubP101] 302 Maturity Level: 3, Validation
2. Determine which categories of user needs (operational, maintenance, training, or support) are to be validated. [PA149.IG101.SP101.SubP102] CMMI-SE/SW/IPPD/SS, v1.1 Staged Representation The product or product component must be maintainable and supportable in its intended operational environment. This specific practice also addresses the actual maintenance, training, and support services that may be delivered along with the product. [PA149.IG101.SP101.SubP102.N101] An example of evaluation of maintenance concepts in the operational environment is a demonstration that maintenance tools are operating with the actual product. [PA149.IG101.SP101.SubP102.N102] 3. Select the product and product components to be validated. [PA149.IG101.SP101.SubP105] 4. Select the evaluation methods for product or product-component validation. [PA149.IG101.SP101.SubP103] 5. Review the validation selection, constraints, and methods with relevant stakeholders. [PA149.IG101.SP101.SubP104] SP 1.2 Establish the Validation Environment Establish and maintain the environment needed to support validation. [PA149.IG101.SP102] The requirements for the validation environment are driven by the product or product components selected, by the type of the work products (e.g., design, prototype, final version), and by the methods of validation. These may yield requirements for the purchase or development of equipment, software, or other resources. These requirements are provided to the requirements development processes for development. The validation environment may include the reuse of existing resources. In this case, arrangements for the use of these resources must be made. Examples of the type of elements in a validation environment include the following: [PA149.IG101.SP102.N101] • Test tools interfaced with the product being validated (e.g., scope, electronic devices, probes) • Temporary embedded test software • Recording tools for dump or further analysis and replay • Simulated subsystems or components (by software, electronics, or mechanics) • Simulated interfaced systems (e.g., a dummy warship for testing a naval radar) Maturity Level: 3, Validation 303
Page 1 and 2:
Pittsburgh, PA 15213-3890 Capabilit
Page 3:
In Memory of Carolyn Marie Tady our
Page 6 and 7:
CMMI-SE/SW/IPPD/SS, v1.1 Staged Rep
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267: CMMI-SE/SW/IPPD/SS, v1.1 Staged Rep
Page 325 and 326: Verifying Implementation CMMI-SE/SW
Page 329 and 330: For Integrated Product and Process
Page 335 and 336: Typical Work Products 1. Commitment
Page 341 and 342: GP 2.4 (AB 4) Assign Responsibility
Page 343 and 344: Elaboration: CMMI-SE/SW/IPPD/SS, v1
Page 347 and 348: GP 2.9 (VE 1) Objectively Evaluate
Page 355 and 356: 3. Design and implement the measure
Page 359 and 360: Directing Implementation CMMI-SE/SW
Page 361 and 362: GP 2.10 (VE 2) Review Status with H
Page 365 and 366: Specific Practices by Goal CMMI-SE/
Page 367 and 368:
Subpractices CMMI-SE/SW/IPPD/SS, v1
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Elaboration: CMMI-SE/SW/IPPD/SS, v1
Page 377 and 378:
Page 379 and 380:
For Supplier Sourcing CMMI-SE/SW/IP
Page 381 and 382:
SG 3 Use the Project's Shared Visio
Page 383 and 384:
• Organizational process needs an
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
SP 2.2 Manage Dependencies CMMI-SE/
Page 395 and 396:
Page 397 and 398:
• the conditions and outcomes the
Page 399 and 400:
SP 4.1 Determine Integrated Team St
Page 401 and 402:
Page 403 and 404:
SP 4.3 Establish Integrated Teams C
Page 405 and 406:
Page 407 and 408:
GP 2.5 (AB 5) Train People Elaborat
Page 409 and 410:
For Integrated Product and Process
Page 411 and 412:
Page 413 and 414:
Practice-to-Goal Relationship Table
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
GG 3 Institutionalize a Defined Pro
Page 435 and 436:
Typical Work Products 1. List of di
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Typical Work Products CMMI-SE/SW/IP
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Refer to the Requirements Managemen
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
SP 2.3 Revise the Supplier Agreemen
Page 457 and 458:
GP 2.2 (AB 2) Plan the Process Elab
Page 459 and 460:
GP 2.8 (DI 3) Monitor and Control t
Page 461 and 462:
Page 463 and 464:
Related Process Areas CMMI-SE/SW/IP
Page 465 and 466:
Examples of when to use a formal ev
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Commitment to Perform CMMI-SE/SW/IP
Page 473 and 474:
GP 2.7 (DI 2) Identify and Involve
Page 475 and 476:
Page 477 and 478:
Specific Practices by Goal CMMI-SE/
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
SG 2 Manage People for Integration
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Ability to Perform CMMI-SE/SW/IPPD/
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Page 503 and 504:
Page 505 and 506:
Page 507 and 508:
GP 2.4 (AB 4) Assign Responsibility
Page 509 and 510:
Page 511 and 512:
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Page 529 and 530:
SP 2.3 Monitor Performance of the S
Page 531 and 532:
Typical Work Products 1. Statistica
Page 533 and 534:
Directing Implementation CMMI-SE/SW
Page 535 and 536:
GP 2.10 (VE 2) Review Status with H
Page 537 and 538:
Page 539 and 540:
Page 541 and 542:
Page 543 and 544:
Page 545 and 546:
Page 547 and 548:
Page 549 and 550:
SP 2.1 Plan the Deployment CMMI-SE/
Page 551 and 552:
Page 553 and 554:
Page 555 and 556:
Page 557 and 558:
Page 559 and 560:
Page 561 and 562:
SP 1.1 Select Defect Data for Analy
Page 563 and 564:
Examples of cause groups, or catego
Page 565 and 566:
Page 567 and 568:
Page 569 and 570:
Page 571 and 572:
Appendices CMMI-SE/SW/IPPD/SS, v1.1
Page 573 and 574:
A. References CMMI-SE/SW/IPPD/SS, v
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
B. Acronyms CMMI-SE/SW/IPPD/SS, v1.
Page 581 and 582:
Page 583 and 584:
C. Glossary CMMI-SE/SW/IPPD/SS, v1.
Page 585 and 586:
Page 587 and 588:
Page 589 and 590:
Page 591 and 592:
Page 593 and 594:
Page 595 and 596:
Page 597 and 598:
Page 599 and 600:
Page 601 and 602:
Page 603 and 604:
Page 605 and 606:
Page 607 and 608:
technical requirements test procedu
Page 609 and 610:
Page 611 and 612:
Page 613 and 614:
SP 1.4 Maintain Bidirectional Trace
Page 615 and 616:
Page 617 and 618:
SP 2.7 Establish the Project Plan E
Page 619 and 620:
Page 621 and 622:
SP 1.3 Monitor Project Risks Monito
Page 623 and 624:
Page 625 and 626:
SG 2 Satisfy Supplier Agreements CM
Page 627 and 628:
Verifying Implementation CMMI-SE/SW
Page 629 and 630:
SP 1.3 Specify Data Collection and
Page 631 and 632:
GP 2.7 (DI 2) Identify and Involve
Page 633 and 634:
SG 2 Provide Objective Insight CMMI
Page 635 and 636:
Page 637 and 638:
SP 1.3 Create or Release Baselines
Page 639 and 640:
Page 641 and 642:
Page 643 and 644:
Page 645 and 646:
Page 647 and 648:
Page 649 and 650:
Page 651 and 652:
Page 653 and 654:
SP 1.3 Establish Product Integratio
Page 655 and 656:
GP 2.5 (AB 5) Train People CMMI-SE/
Page 657 and 658:
Page 659 and 660:
Page 661 and 662:
Page 663 and 664:
GP 2.3 (AB 3) Provide Resources CMM
Page 665 and 666:
Page 667 and 668:
Page 669 and 670:
Page 671 and 672:
GP 2.5 (AB 5) Train People CMMI-SE/
Page 673 and 674:
Page 675 and 676:
Page 677 and 678:
Page 679 and 680:
SG 3 Use the Project's Shared Visio
Page 681 and 682:
Page 683 and 684:
SP 1.3 Establish a Risk Management
Page 685 and 686:
Page 687 and 688:
SG 2 Govern Team Operation CMMI-SE/
Page 689 and 690:
Page 691 and 692:
SG 2 Coordinate Work with Suppliers
Page 693 and 694:
GP 3.2 (DI 4) Collect Improvement I
Page 695 and 696:
SP 1.5 Evaluate Alternatives CMMI-S
Page 697:
Page 700 and 701:
Page 702 and 703:
Page 704 and 705:
Page 706 and 707:
Page 708 and 709:
Page 710 and 711:
Page 712 and 713:
Page 714 and 715:
Page 716 and 717:
Page 718 and 719:
Page 720 and 721:
Page 722 and 723:
Page 724 and 725:
Page 726 and 727:
Page 728 and 729:
show all

CMMI - SE/SW/IPPD/SS - V1.1 - Software Engineering Institute ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?