Software

 1.Single Responsible Principle 2.Open-Closed Principle 3.Liskovo-Substitution Principle 4.Interface Segregation Principle 5.Dependency Inversion Principle  1.Single Responsible Principle One class one Repository 2.Open-Closed Principle Open for extension, closed for Modification 3.Liskovo-Substitution Principle Types derived from same parent are inter-changeable 4.Interface Segregation Principle Seperate interfaces for seperate functionality 5.Dependency Inversion Principle Depend on abstraction, not on concretion

  Software development methodologies are approaches or frameworks used to structure, plan, and control the process of developing software. These methodologies provide guidelines and best practices for managing tasks, processes, and resources throughout the software development life cycle. Some common software development methodologies include: Waterfall Model : The Waterfall model follows a linear sequential flow, where each phase must be completed before the next one begins. It typically includes phases such as requirements gathering, design, implementation, testing, deployment, and maintenance. Agile : Agile methodologies emphasize flexibility, iterative development, and collaboration between cross-functional teams. Agile methods include Scrum, Kanban, Extreme Programming (XP), and Lean Development. Agile promotes adaptive planning, evolutionary development, early delivery, and continuous improvement. Spiral Model : The Spiral model combines elements of both the Waterfall model a...

  The Bug Life Cycle, also known as the Defect Life Cycle, describes the stages that a software bug or defect goes through from its identification to its resolution. While specific steps may vary depending on the organization and its processes, the typical bug life cycle includes the following stages: New : The bug is reported for the first time by a tester, user, or other stakeholder. It is logged into the bug tracking system with details such as a description of the issue, steps to reproduce it, severity, and priority. Assigned : The bug is assigned to a developer or development team responsible for fixing it. This assignment may be based on factors such as the developer's expertise, workload, or the nature of the bug. Open : The developer begins investigating the bug to understand its cause and potential solution. This may involve reproducing the issue, analyzing code, and identifying the root cause. In Progress : The developer actively works on fixing the bug, implementing chan...

Stackholder   -  Budget Release Product  owner - All features Business Analyst - Function,Access,VI,Documentation Developers/Technical Team Testers Ready for Release VAT Performance Production

Software Development Life Cycle RequirementAnalysis Design Implementation Testing Release to production The Software Development Life Cycle (SDLC) is a structured approach to software development that outlines the processes, stages, and methodologies involved in building software. While specific SDLC models can vary, they typically include the following phases: Planning : In this initial phase, project objectives, scope, requirements, timelines, and resources are defined. This phase involves gathering requirements from stakeholders and determining the feasibility of the project. Analysis : During this phase, the requirements gathered in the planning phase are analyzed in detail. The goal is to understand the needs of the end-users and document functional and non-functional requirements. Design : In the design phase, the software architecture is developed based on the requirements gathered in the previous phases. This includes defining system architecture, data structures, interfaces, a...