Pair programming is a technique where two developers work together on the same code. Explanation:
A code smell is a symptom in code that indicates potential design flaws or bad practices. Explanation: Example (Bad Code – Code Smell) java int calc(int a, int b) { return a * b * 3.14; // Magic number (3.14 should be a constant)} Fix (Refactored Code): javafinal double PI = 3.14;int calc(int a, int…
Non-functional requirements (NFRs) define the quality attributes of a system, such as performance, security, and usability. Explanation: Example: For a banking app, an NFR could be:
Functional requirements define what a system should do, describing features, capabilities, and behavior. Explanation: Example:
A stakeholder is any individual, group, or organization that has an interest or influence in a software project. Explanation: Example:
Requirements gathering is the process of collecting user needs and defining software specifications. Explanation:
Risk management in software development identifies, assesses, and mitigates potential risks. Explanation:
Software prototyping is the early-stage development of a working model before full implementation. Explanation:
Build automation refers to automating software compilation, packaging, and deployment. Explanation: Example Maven Build (pom.xml) xml<project> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <artifactId>my-app</artifactId> <version>1.0</version></project>
Release management is the process of planning, testing, and deploying software updates. Explanation: