Practical no 10

-

 Practical No 10: Write test case to validate requirement of assign project from srs document.


In software engineering, a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing.

Formal test cases

In order to fully test that all the requirements of an application are met, there must be at least two test cases for each requirement: one positive test and one negative test. If a requirement has sub-requirements, each sub-requirement must have at least two test cases.


Informal test cases

For applications or systems without formal requirements, test cases can be written based on the accepted normal operation of programs of a similar class. In some schools of testing, test cases are not written at all but the activities and results are reported after the tests have been run.




Banking Manangement system  Testing is a software testing process of a banking application for functionality, performance, and security. The main purpose of testing banking application is to ensure that all the activities and functionalities of a banking software run smoothly with no errors and it remains protected.


 It is mandatory that all the activities performed by banking software run smoothly and without any error. Banking software perform various functions like transferring and depositing fund, balance inquiry, transaction history, withdrawal and so on. Testing banking application assures that these activities are not only executed well but also remain protected.

Result: Hence we have written validation requirement of bank management system using srs document.

Popular posts from this blog

Practical No 11

-
 Practical 11 - Identify the risk involve in the project and prepare RMMM plan. A risk management technique is usually seen in the software Project plan. This can be divided into Risk Mitigation, Monitoring, and Management Plan (RMMM). In this plan, all works are done as part of risk analysis. As part of the overall project plan project manager generally uses this RMMM plan.  Risk : Due to the large size of some banks, overexposure to risk can cause bank failure and impact millions of people. By understanding the risks posed to banks, we can set better regulations to encourage prudent management and decision-making. The ability of a bank to manage risk also affects investors’ decisions. Even if a bank can generate large revenues, lack of risk management can lower profits due to losses on loans. Value investors are more likely to invest in a bank that is able to provide profits and is not at an excessive risk of losing money. Risk Mitigation :   It is an activity used to avoid problems
Read more

Practical No 7

-
Image
 Develop a activity diagram to represent a flow from one activity to anotyher for software develpment Activity diagram for Bank management system Activity diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. The control flow is drawn from one operation to another. This flow can be sequential, branched, or concurrent. Activity diagrams deal with all type of flow control by using different elements such as fork, join, etc.i t captures the dynamic behavior of the system. The purpose of an activity diagram can be described as − Draw the activity flow of a system. Describe the sequence from one activity to another. Describe the parallel, branched and concurrent flow of the system. Result - Hence,We have developed activity diagram to represent the flow of one activity to another for bank management system.
Read more

Practical No 12

-
 Practical No 12 -  Evaluate the size of a project using functional point metric for the assign project. Estimation of the size of the software is an essential part of Software Project Management. It helps the project manager to further predict the effort and time which will be needed to build the project. Various measures are used in project size estimation.  Function Point Analysis:  Is the method in which, the number and type of functions supported by the software are utilized to find FPC(function point count). The steps in function point analysis are:    Count the number of functions of each proposed type. Compute the Unadjusted Function Points(UFP). Find Total Degree of Influence(TDI). Compute Value Adjustment Factor(VAF). Find the Function Point Count(FPC). The explanation of the above points is given below:    Count the number of functions of each proposed type:  Find the number of functions belonging to the following types:  External Inputs: Functions related to data entering t
Read more