Software Environments are physical or logical configurations fallen around different development phases. From analysis to maintenance an application goes through diverse Software Environments. See this chart, [table id=4 /]
Tag: Software Engineering
Why to Document? Software Development vs Engineering
Some people doesn’t like to write what they do. Documentations are set of rules that software guys need to adhere to ensure the quality of the software being developed. What happens if your driving along a road that do not have any traffic rules? Accidents! Time wasting! Left away from where you wanna reach. Same… Continue reading Why to Document? Software Development vs Engineering
Agile Software Development – What happens actually? – In Detail
Agile they said. Embrace changes they said. Agile development conquered the world of SLDC. More than 80% of the softwares being developed via agile methodologies nowadays. What is Agile? Agile focus on releasing urgent solutions required to the client in a faster manner. Minimal documentation practice needs to be adapted and team members needs to… Continue reading Agile Software Development – What happens actually? – In Detail
QA – Quality Assurance Factors- Defect vs Fault vs Failure
Quality Assurance (QA) makes sure obstacles such as Defect, Fault and Failure are eliminated in a controlled manner. All three are somewhat negative towards a positive goal. Remember that equal positivity against a specific negativity result in neutral. To out perform and to glitter apart QA team needs to work systematically. Defect vs Fault vs… Continue reading QA – Quality Assurance Factors- Defect vs Fault vs Failure
Why Custom Built?
When a software is started building from the scratch or with basic options and focus towards a specific ideas of a client; we are working on client’s satisfaction. Rather than the whole system we are prioritizing the important business functions first and never sat back to redo when necessary. 100% mapping with business functions and… Continue reading Why Custom Built?
Test Planning
Test Plan is created and maintained by the test lead/ QA lead. Only the QA lead should be able edit in a controlled manner. Inputs are got from Functional Requirement Document(FRD) to create the Test Plan. It is impossible to add, review, document, update, and maintain the Test Plan on his/her own. So developers plays… Continue reading Test Planning