



Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
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
1 / 6
This page cannot be seen from the preview
Don't miss anything!




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...
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.
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