Real-Time Example: Defect vs Bug

Example 1: Internet Banking Application

Requirement: User should be able to transfer up to ₹1,00,000 per day.

Actual Implementation: The application allows transfers up to ₹10,00,000 per day.

Defect: The code does not comply with the business requirement.

Bug: QA tests a ₹5,00,000 transfer, observes it succeeds, and logs a bug in Jira.

Interview Statement: "The incorrect implementation is the defect. Once the tester discovers and reports it, it becomes a bug."

---

Example 2: Healthcare Application

Requirement: Patient date of birth must not be a future date.

Actual Behavior: System accepts a future date such as 01-Jan-2030.

Defect: Validation logic is missing.

Bug: Tester enters a future date and reports the issue.

---

Example 3: E-Commerce Website

Requirement: Apply 10% discount on orders above ₹5,000.

Actual Behavior: System applies only 5% discount.

Defect: Discount calculation logic is incorrect.

Bug: Customer or tester notices the wrong discount and raises a bug ticket.

---

Project Manager / Delivery Manager Interview Answer

"A defect is a flaw in the design, code, or requirement implementation. When the defect is identified during testing or by a customer and logged for resolution, it is referred to as a bug. For example, if a banking application allows transactions beyond the approved limit, the incorrect code is the defect, and the issue reported by QA is the bug."

Comments

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

4 T's - Technology, Time, Teamwork, Transparency

1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished. 3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...

High-Tech Yuga

Search This Blog