Posts

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,
Read more

Practical No 13

-
 Practical No 13 -  Estimate the cost of the project using COCMOII approach for assign project. Cocomo (Constructive Cost Model) is a regression model based on LOC, i.e  number of Lines of Code . It is a procedural cost estimate model for software projects and is often used as a process of reliably predicting the various parameters associated with making a project such as size, effort, cost, time, and quality. It was proposed by Barry Boehm in 1981 and is based on the study of 63 projects, which makes it one of the best-documented models. The key parameters which define the quality of any software products, which are also an outcome of the Cocomo are primarily Effort & Schedule: Effort:  Amount of labor that will be required to complete a task. It is measured in person-months units. Schedule:  Simply means the amount of time required for the completion of the job, which is, of course, proportional to the effort put in. It is measured in the units of time such as weeks, months. Ther
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

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 9

-
Image
 Practical No 9 :Draw class diagram sequence diagram state transition diagram for assign project. Class diagram is a static diagram. It represents the static view of an application. Class diagram is not only used for visualizing, describing, and documenting different aspects of a system but also for constructing executable code of the software application. Class diagram describes the attributes and operations of a class and also the constraints imposed on the system.Class diagram shows a collection of classes, interfaces, associations, collaborations, and constraints. It is also known as a structural diagram. Purpose of Class Diagrams The purpose of class diagram is to model the static view of an application. Class diagrams are the only diagrams which can be directly mapped with object-oriented languages and thus widely used at the time of construction. Sequence Diagram Sequence diagrams show an overview of the interactions between objects in a system over time.  Also called event diag
Read more