Scribd
Upload
8 views10 pages

Madhu Software Report-1

The micro-project report by Shubhada Sanjay Bhosale focuses on software testing related to credits and debits, outlining the aims, methodology, and expected outcomes of the project. It emphasizes the importance of balancing feature development with addressing bugs and technical debt, while also detailing the process of creating test cases and tracking progress. The report includes acknowledgments, a rationale for the project, and a literature review on the definitions of credits and debits in software development.

Uploaded by

joshisamruddhi14
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views10 pages

Madhu Software Report-1

The micro-project report by Shubhada Sanjay Bhosale focuses on software testing related to credits and debits, outlining the aims, methodology, and expected outcomes of the project. It emphasizes the importance of balancing feature development with addressing bugs and technical debt, while also detailing the process of creating test cases and tracking progress. The report includes acknowledgments, a rationale for the project, and a literature review on the definitions of credits and debits in software development.

Uploaded by

joshisamruddhi14
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Micro-Project Report

Subject – Software testing

Topic- Credits and Debits

Submitted By

Student Name :- Shubhada Sanjay


Bhosale.

UNDER THE GUIDANCE OF

Lecturer-Mrs.Dolas S.G

“Department of computer engineering”

Yashoda Shikshan Prasarak Mandal’s

Yashoda Techanical Campus, Satara

2024-25
CERTIFICATE

This is to certify that Shubhada Sanjay Bhosale, working under my guidance.


They have satisfactorily carried out and completed the report entitled in the
fulfillment of award of Third year Polytechnic as laid down by MSBTE for the
academic year 2024-25.

Date: / /2024

Guide Examiner Head of Dept.


Acknowledgement
We wish to express our deep sense of gratitude to our guide
Mrs. Dolas S.G her continuous encouragement, keen interest and able
guidance during the entire period of completion of Project work.

Weare verymuch thankful to our Head of Department Ms. Palkar


N.M. for her kind co-operation and for providing all the facilities for
completing the Project work.

We feel highly indebted to the “Hon. Principal. P. P.Gavade ” for


this motivation. We thanks also to teaching and Non-teaching staff of
ourcollege and we would like to express our special thanks to my friends
for their constant encouragement for completing the same project.
Micro-Project Proposal
1.0 Aims/Benefits of the Micro-Project

1.Understanding Requirements

 Review business requirements for credit and debit transactions.


 Identify the rules for different transaction types (e.g., limits, user permissions).

2. Test Case Development

 Create test cases for various scenarios, including:


o Valid credit and debit transactions.
o Invalid transactions (e.g., exceeding limits, insufficient balance).
o Edge cases (e.g., zero transactions, negative amounts).

2.0 Course outcomes Addressed:-

 Apply various software testing method.


 Prepare test cases for different types and levels of testing.
 Prepare test plan for an application.

2.1 Proposed Methodology


Define Objectives
Purpose: Establish clear goals for tracking credits (new features, enhancements) and debits (bugs,
technical debt) in the software testing lifecycle.

2. Identify Stakeholders

 Engage Teams: Collaborate with product managers, developers, and QA teams to understand their
needs and expectations regarding credits and debits.

3. Establish a Tracking System

 Choose Tools: Select project management tools (like Jira, Trello, or Azure DevOps) to track credits
and debits.
 Custom Fields: Set up custom fields to categorize features (credits) and bugs (debits) effectively.

4. Categorization

 Define Categories: Create categories for different types of credits (new features, enhancements)
and debits (bug fixes, technical debt).

Planning

Testing and Quality Assurance

 Test Planning: Create test cases for all new features (credits) and regression tests for bug fixes
(debits).
 Automated Testing: Implement automated testing frameworks to cover new functionalities and
ensure bugs are resolved without introducing new issues.
.Monitoring and Reporting

 Dashboards: Use dashboards to provide real-time visibility of credits and debits, helping teams
track progress and identify bottlenecks.
 KPI Tracking: Define and track key performance indicators (KPIs) related to credits (e.g., feature
delivery rate) and debits (e.g., bug resolution time).
4.0 Action Plan

Sr.No Details of Activity Planned start Planned finish Name of responsible


date date members
1 Topic Search / /2024 / /2024 Shubhada Sanjay Bhosale

2 Information of topic / /2024 / /2024 Shubhada Sanjay Bhosale

3 Project Making / /2024 / /2024 Shubhada Sanjay Bhosale

4 Report Making / /2024 / /2024 Shubhada Sanjay Bhosale

5.0 Resources Require

Sr.No Name of Specifications Quantity Remarks


Resource/material

1 Expert Instruction Topic Info _

2 Training Materials Including


presentation,
documentation,
and reference
materials
Micro-Project Report
1.0 Rationle

1. Promotes Balanced Development

 Equitable Focus: By tracking credits and debits, teams can ensure that they are not overly focused
on feature development at the expense of maintaining code quality.

2. Enhanced Quality Assurance

 Quality Monitoring: Regularly addressing debits (bugs and technical debt) ensures that the
software remains robust and reliable, reducing the likelihood of production issues.

3. Improved Resource Allocation

 Prioritization: Tracking credits and debits allows teams to prioritize their work based on business
value, technical necessity, and urgency, ensuring optimal use of resources

4. Risk Management

 Identifying Technical Debt: Tracking debits helps teams identify areas of technical debt that may
pose risks in the future, allowing for proactive management.
 Mitigating Future Issues: Addressing bugs and performance issues promptly reduces the risk of
more significant problems arising later in the development lifecycle.

Aims/Benefits of the Micro-Project


1) Balance Development Efforts:

 Ensure an equitable focus on developing new features (credits) while addressing bugs and
technical debt (debits).
 Foster a culture that values both innovation and maintenance.

2) Enhance Software Quality:

 Improve overall software reliability and performance by systematically managing defects


and technical issues.
 Facilitate the creation of high-quality, user-friendly applications.

Course outcomes:-

1. understanding the concept of credits and debits.


 We learnt about test plan and development of it.
 We learnt about test cases and development of them.
 We learnt procedure followed by companies for their products.
 We learnt importance of testing before and after deployment of products.
5.0 Literature Review
1) Conceptual Framework

Credits and Debits Definition:

 Credits refer to new features, enhancements, and improvements that add value to the software
product. These are often driven by user requirements and market demands.
 Debits encompass bugs, technical debt, and maintenance tasks that need to be addressed to
ensure the software’s quality and longevity (Petersen & Wohlin, 2010).

6.0 Actual Methodology Followed

Details of Activity Planned start Planned finish Name of responsible team


date date members
1 Topic Search / /2024 / /2024 Shubhada Sanjay Bhosale.

2 Information of topic / /2024 / /2024 Shubhada Sanjay Bhosale.

3 Project Making / /2024 / /2024 Shubhada Sanjay Bhosale.

4 Report Making / /2024 / /2024 Shubhada Sanjay Bhosale.


7.0 Outputs of the Micro-Projects

Test Case Results

Pass/Fail Status:
Clear documentation indicating whether each test case has passed or failed based on the expected
outcomes.
Test Coverage Metrics:
Metrics showing the percentage of requirements covered by test cases, ensuring comprehensive testing.

Defect Reports

Detailed Defect Documentation:


Comprehensive reports on identified defects, including severity, reproduction steps, screenshots, and
any relevant logs.
Defect Status Tracking:
An overview of defect statuses (e.g., open, resolved, in progress) for effective management.

8.0 Applications of this Microproject

Test Data Management

Version Control: Maintain different versions of test data sets. This helps in testing different scenarios
without overwriting existing data.
Data Inventory: Keep track of various data sets used for testing, including configurations, parameters,
and expected outcomes.

Test Case Management

Cataloging Test Cases: Organize and manage test cases as inventory items, allowing easy access and
updates.
Traceability: Ensure that each test case is linked to specific requirements, making it easier to track
coverage and results.

You might also like