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 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday? • What will I do today? • What obstacles are impeding my progress? Some people are talkative and tend to wander off into Story Telling . Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. Here are few tips for running a smooth daily meeting: • Everyone should literally stand-up and no one should sit down ...

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)

High-Tech Yuga

Search This Blog