CMPE 131 Exam 1 Study Guide: Software Engineering Principles and Practices, Exams of Social Sciences

This study guide covers key concepts in software engineering, including software development life cycle, software quality, software process models, and ethical considerations. It provides definitions and explanations of important terms and principles, such as the 4 p's of software engineering (people, product, project, and process), different software process models (waterfall, iterative), and software engineering ethics. The guide also touches on software disasters, metrics, and inspection roles, offering a comprehensive overview for exam preparation.

Typology: Exams

2025/2026

Available from 12/29/2025

ROCKY-B
ROCKY-B 🇰🇪

4.4

(16)

40K documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CMPE 131 EXAM 1 STUDY GUIDE
Reliable, Efficient, Maintainable, and meet the needs of customers - Answer -Creation
of software systems that are
Schedule and Budget - Answer -Production of system meets
Engineering discipline - Answer -the design, analysis and construction of an artifact for
some practical purpose
IEEE Definition - Answer -the application of a systematic, disciplined, quantifiable
approach to the development, operation and maintenance of software; that is the
application of engineering to software
NATO Study Group - Answer -One of the first uses of the phrase software engineering
Programming Management - Answer -Continue to
deserve its current poor reputation for cost and schedule effectiveness until such time
as a more complete understanding of the program design process is achieved."
Software Disasters - Answer -Ariane Project
1990 AT&T Disastr
Radiation overdose
CHAOS
Tata Consultancy
Chaos Study - Answer -Although the U.S spent over $250 billion
on software projects, approximately...
- 31% were cancelled before completion
- 53% were completed but over budget, over schedule, & did not meet original
specifications
• For mid-size companies, average cost overruns were 182%, while average schedule
overruns
were 202%!
Failure to meet expectations - Answer -- Over budget
- Exceeds schedule / misses market window
- Doesn't meet stated customer requirements
- Lower quality than expected
- Performance doesnt meet expectations
- Too difficult to use
- Unrealistic or unarticulated project goals - Inaccurate estimates of needed resources
- Poor project management
4 P's of Software Engineering - Answer -People, Product, Project, and Process
pf3
pf4
pf5

Partial preview of the text

Download CMPE 131 Exam 1 Study Guide: Software Engineering Principles and Practices and more Exams Social Sciences in PDF only on Docsity!

CMPE 131 EXAM 1 STUDY GUIDE

Reliable, Efficient, Maintainable, and meet the needs of customers - Answer - Creation of software systems that are Schedule and Budget - Answer - Production of system meets Engineering discipline - Answer - the design, analysis and construction of an artifact for some practical purpose IEEE Definition - Answer - the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software; that is the application of engineering to software NATO Study Group - Answer - One of the first uses of the phrase software engineering Programming Management - Answer - Continue to deserve its current poor reputation for cost and schedule effectiveness until such time as a more complete understanding of the program design process is achieved." Software Disasters - Answer - Ariane Project 1990 AT&T Disastr Radiation overdose CHAOS Tata Consultancy Chaos Study - Answer - Although the U.S spent over $250 billion on software projects, approximately...

  • 31% were cancelled before completion
  • 53% were completed but over budget, over schedule, & did not meet original specifications
  • For mid-size companies, average cost overruns were 182%, while average schedule overruns were 202%! Failure to meet expectations - Answer -- Over budget
  • Exceeds schedule / misses market window
  • Doesn't meet stated customer requirements
  • Lower quality than expected
  • Performance doesnt meet expectations
  • Too difficult to use
  • Unrealistic or unarticulated project goals - Inaccurate estimates of needed resources
  • Poor project management 4 P's of Software Engineering - Answer - People, Product, Project, and Process

People - Answer - Project Stakeholders Product - Answer - The software product plus associated documents Project - Answer - The activities carried out to produce the product Process - Answer - Framework within which the team carries out the activities necessary to build the product Project Documentation - Answer - Produced during software definition and development Code - Answer - Source and object Test documents - Answer - Plans, cases, and results Customer documents - Answer - Documents explaining how to use and operate product Productivity measurements - Answer - Analyze project productivity System development life cycle - Answer - Planning Analysis Design Implementation Maintenance & Support Software Project Activities - Answer - Planning Requirements analysis Design Implementation Testing Maintenance Planning - Answer - Plan, monitor and control the software project Requirement analysis - Answer - define what to build Design - Answer - how to build the software Implementation - Answer - program the software Testing - Answer - Validate software meets the requirements Maintenance - Answer - Resolve problems, adapt software to meet new requirements Object orientation - Answer - Real world concepts

Confidentiality - Answer - Engineers should normally respect the confidentiality of their employers or clients irrespective of whether or not a formal confidentiality agreement has been signed. Ethical Dilemmas - Answer - Disagreement in principle with senior management policies.

  • Your employer acts in an unethical way and releases a safety-critical system without finishing the testing of the system.
  • Participation in the development of military weapons systems or nuclear systems. Software Quality - Answer - Software will contain defects Concerns the severity and extent of defects Defects - Answer - deviation from requirements Quality goals - Answer - Remove as many defects as is reasonably possible before project is completed Remove as many of these defects as early in the development process as possible easier and saves money - Answer - Finding defects early _____ Verification - Answer - Ensuring that each artifact is built in accordance with its specifications Validation - Answer - Checking that each completed artifact satisfies its specification Metrics - Answer - Numerical measures that quantify the degree to which software or a process possesses a certain attribute Collected and analyzed throughout software project Quality Metrics - Answer - Defect density Mean time to failure Customer problems Customer satisfaction software process - Answer - prescribes the order and frequency of phases specifies criteria for moving from one phase to the next defines the deliverables of the project Umbrella Activities - Answer - Generic activities implemented throughout the life of a project

Iterative - Answer - repeated execution of the waterfall phases, in whole or in part, resulting in a refinement of the requirements, design and implementation Incremental - Answer - operational code produced at the end of an iteration supports a subset of the final product functionality and features Communication - Answer - Customer on site Pair programming Coding standards Simplicity - Answer - Metaphor: entity names drawn from common metaphor Simplest design for current requirements Refactoring Feedback - Answer - Continual testing Continuous integration (daily at least ) Small releases (smallest useful feature set) Courage - Answer - Planning and estimation with customer user stories Collective code ownership Sustainable pace SCRUM - Answer - Development team empowered to define and execute the necessary tasks to successfully develop software Inspection Roles - Answer - • Moderator

  • Author
  • Recorder
  • Reader
  • Inspector Inspection Metrics - Answer - • Number of defects discovered, by severity and type
  • Number of defects discovered by each category of stakeholder inspecting the artifact
  • Number of defects per page reviewed • Review rate (number of pages/hour Urgent - Answer - Failure causes system crash, unrecoverable data loss; or jeopardizes personnel High - Answer - Causes impairment of critical system functions, and no workaround solution does exist