click below
click below
Normal Size Small Size show me how
SOFT ENG
Chapter 2
| Question | Answer |
|---|---|
| is a Standard way to build and deploy applications. | Framework |
| is a foundation of complete software engineering process. | Software Process Framework |
| includes all set of umbrella activities. It also includes number of framework activities that are applicable to all software projects. | Software Process Framework |
| Eliminate snowball effect. Ans, Works best if we have direct access to client | Iterative Process Flow |
| Large projects, Working on different steps at the same time. Breaking larger projects into small ones. | Parallel Process flow |
| found as part of agile development | Evolutionary Process flow |
| defines the actual work to be done to accomplish the objectives of a software engineering action. | task set |
| describes a process-related problem that is encountered during software engineering work, | process pattern |
| defines a problem associated with a framework activity for the process. | Stage patterns |
| defines a problem associated with a software engineering action or work task and relevant to successful software engineering practice | Task patterns |
| define the sequence of framework activities that occur with the process, even when the overall flow of activities is iterative in nature. | Phase patterns |
| provides a five step process assessment model that incorporates five phases: initiating, diagnosing, establishing, acting and learning. | Standard CMMI Assessment Method for Process Improvement (SCAMPI) |
| provides a diagnostic technique for assessing the relative maturity of a software organization; uses the SEI CMM as the basis for the assessment [Dun01] | CMM-Based Appraisal for Internal Process Improvement (CBA IPI) |
| standard defines a set of requirements for software process assessment. The intent of the standard is to assist organizations in developing an objective evaluation of the efficacy of any defined software process | SPICE—The SPICE (ISO/IEC15504) |
| a generic standard that applies to any organization that wants to improve the overall quality of the products, systems, or services that it provides. Therefore, the standard is directly applicable to software organizations and companies. | ISO 9001:2000 for Software |
| advocate an structure and orderly approach to software engineering | Prescriptive Models |
| Classic life cycle. Forward progress. You can not go back. Blocked state. | Waterfall model |
| Subdivide the project into sub projects that can be worked on at the same time. | Parallel Development Methodology |
| Similar to both siquential and parallel. Good for large projects. | Incremental model |
| the process to apply when reuse is a development objective | Component based development |
| emphasizes the mathematical specification of requirements | Formal methods |
| provides a process and methodological approach for defining, specifying, designing, and constructing aspects | AOSD |
| a “use-case driven, architecture-centric, iterative and incremental” software process closely aligned with the Unified Modeling Language (UML) | Unified Process |
| This activity isolates requirements and develops both size and resource estimates. In addition, a defect estimate (the number of defects projected for the work) is made. | Planning |
| External specifications for each component to be constructed are developed and a component design is created. Prototypes are built when uncertainty exists. All issues are recorded and tracked. | High-level design |
| Formal verification methods (Chapter 21) are applied to uncover errors in the design. Metrics are maintained for all important tasks and work results. | High-level design review |
| The component level design is refined and reviewed. Code is generated, reviewed, compiled, and tested. Metrics are maintained for all important tasks and work results. | Development |
| In the realm of software development, a post-mortem, often referred to as a retrospective, is a structured meeting held at the conclusion of a project or a significant phase to analyze the successes, failures, and lessons learned. | Postmortem |
| Build self-directed teams that plan and track their work, establish goals, and own their processes and plans. | Team Software Process (TSP) |