SIT (System Integration Testing) and UAT (User Acceptance Testing) are the parts of the testing process where SIT is responsible for testing the interfaces between the components and interactions to various parts of the systems like hardware, software (operating system and file system) and interfaces among systems. Conversely, UAT (User Acceptance Testing) is a validation testing performed from the user end where user requirements and business-related processes are checked to find whether the … [Read more...]

The use case and test case are the terms frequently used in the software testing field, which are also closely related. A use case is used to specify how to use the system designed for performing a specific task. As against, a test case is a group of test inputs, execution conditions, and expected results developed for a particular test objective. Furthermore, the use case does not run or execute as it is a textual or diagrammatic presentation of a document which specifies how to accomplish a … [Read more...]

Earlier for testing software products, the one and only method used was manual testing, in which the human itself find defects in the software. The tester performing the manual test acts as an end user who is allowed to use all of the software features and verifies its behaviour. By the advancement in the technology, automated testing came in existence which involves a testing tool (i.e, a software program) to test the software's output against its expected output. The manual and automated … [Read more...]

Static and dynamic testing are the types of testing techniques completes each other in which static testing is performed in the initial stages of the software development whereas dynamic testing is carried out after the completion of the development process. Dynamic testing is like validating a software but static testing is verification of the software. Testing is a combination of multiple software life cycle activities related to planning, designing and evaluation of the software product in … [Read more...]

Testing and debugging processes in software development are used to improve the quality of the software product and make it error and fault free. The testing and debugging processes are differentiated by the fact that testing finds the software defects devoiding its correction. Conversely, debugging is a more profound process where the bugs are not only identified but segregated and fixed from the code. While performing testing, we can use any of its types like unit, integration, and system … [Read more...]

The COCOMO 1 and COCOMO 2 are the cost estimation models developed by Barry Boehm for computing the cost of the developing software. Initially, COCOMO basic model was introduced, followed by the enhanced versions of the COCOMO model. The main difference between these COCOMO models is that the COCOMO 1 is completely premised on the linear reuse formula and the hypothetical idea about the stable set of requirements. In contrast, the COCOMO 2 is founded on the non-linear reuse formula, and also … [Read more...]

The System and Integration testing are the types of testing or test levels required to perform to detect the defects before the launch or delivery of the software product. The system and integration testing are distinguished depending on the which part of the developed software or product the test has been performed. System testing tests the behaviour of the entire system as specified by the scope of a development product. On the contrary, the integration testing tests the interfaces exists or … [Read more...]

The Waterfall and Spiral models are the process models used for developing software in a well-defined, systematic and cost-effective way. The major difference between these software process models waterfall and the spiral is that the waterfall model is comprised of the separate and isolate phases of specification and development. On the other hand, in a spiral model the different specification, development and validation phases are interleaved. These process model are a crucial part of … [Read more...]

Cardinality and Modality are the two data modelling concepts used for understanding the information domain of the problem. For analysing the data objects, data attributes and relationships structures, the terms given above are very important. The major difference between cardinality and modality is that the cardinality is defined as the metric used to specify the number of occurrences of one object related to the number of occurrences of another object. On the contrary, modality signifies … [Read more...]

The Agile and Waterfall are the highly used SDLC (Software Development Life Cycle) models to develop software or web-based product. The process in an agile method involves iterations in which requirements are validated, designed and tested during the iterations. Conversely, in waterfall projects the requirements are fixed at the beginning then the other phases occur. With an agile method, the new requirements and changes can be implemented in the next iteration while this is not possible in the … [Read more...]