Mohd. Sadiq

Software Risk Assessment and Estimation Model

Just like any development projects, there is inherent risk in software development projects. Most of the softwares fails due to over budget, delay in the delivery of the softwares and so on. In this paper we have proposed a software risk assessment and estimation model (SRAEM). Using this model it is possible to predict the possible results of software projects with good accuracy. Proposed model not only assess the risk but it also estimate the risk. In this paper the risk is estimated using risk exposure and software metrics of risk management and this metric is based on mission critical requirements stability risk metrics (MCRSRM). This software metrics is used when there are changes in requirements such as addition, subtraction, or deletion. The proposed model gives the incremental risk for every phase and also the total cumulative risk as the software progress from phase to phase.

An Approach for Eliciting Software Requirements and its Prioritization Using Analytic Hierarchy Process

Most software engineering methods presume that requirements are explicitly and completely stated; however, experience shows that requirements are rarely complete and usually contain implicit requirements. The failure or success of a software system depends on the quality of the requirements. The quality of the requirements is influenced by the techniques employed during requirements elicitation. Requirements elicitation is most critical part of the software development because errors at this beginning stage propagate through the development process and the hardest to repair later. In this paper we have proposed an algorithmic approach to elicit the software requirements and its prioritization of the requirements using analytic hierarchy process (AHP).

Applying fuzzy preference relation for requirements prioritization in goal oriented requirements elicitation process

Goal oriented requirements elicitation processes are used to identify the requirements of software according to the need of stakeholders. A system may have thousands of requirements and it is difficult to prioritize such a large number of requirements when several stakeholders participate in requirements elicitation process. In literature, we identify that existing goal oriented requirements elicitation processes like KAOS, i*, AGORA do not support to prioritize the requirements when stakeholder’s preferences are in the form of linguistic variable and multi-criteria decision making approach is used in requirements elicitation process. Therefore, to address this issue, we present a method for prioritization of requirements using fuzzy based approach in goal oriented requirements elicitation process by combining α-level weighted F-preference relation and extent fuzzy analytic hierarchy process in group decision making process; and then we use binary tree sort method to get the prioritized list of requirements. Finally, the utilization of the proposed approach is demonstrated with the help of an example.

More on Elicitation of Software Requirements and Prioritization Using AHP

The first method developed to translate customer requirements into software specification was the Quality Function deployment (QFD) and the second approach to the identification of software specification comes from the software engineering. Requirements may be defined as a demand or need. In software engineering, a requirement is a description of what a system should do. System may have dozen to thousands of requirements. Software requirements stipulate what must be accomplished, transformed, produced or provided. It is well documented that requirement engineering saves money. There are several techniques to elicit the software requirements like JAD, misuse, RAD, Web Surveys etc. In this paper we have used the Web Surveys approach to elicit the software requirements for a railway projects. The main objective of this paper is to improve the effectiveness and the efficiency of the freight transportation between source and destination using optimization algorithm.

An Insight into Requirements Engineering Processes

Requirements Engineering (RE) determines the requirements of software according to the needs of customers. Requirements engineering process includes requirements elicitation, requirements modeling, requirements analysis, requirements verification & validation, and requirements management. Among these sub-processes, requirements elicitation plays an important role in extracting the needs of stakeholders, since it is the first requirements engineering sub-process and has cascading effect. It means errors occurring during requirements elicitation will affect the remaining RE processes. Improper understanding of requirements engineering processes may lead to failure of software projects. This article presents an insight into requirements engineering processes.

A fuzzy based approach for the selection of goals in goal oriented requirements elicitation process

Goal selection in goal oriented requirements elicitation process (GOREP) like KAOS, i*, AGORA etc., is a multi-criteria decision making problem. In literature, we identify that existing GOREP do not support to choose and adopt a goal out of the alternatives of the decomposed goals when multi-criteria decision making approaches are used and stakeholders’ preferences are in the form of linguistic variables. Therefore, this paper presents a fuzzy based approach to address the above issue by using α-level weighted F-preference relation in group decision making process. Finally, the utilization of the proposed approach is demonstrated with the help of an example.

GUI of esrcTool: A tool to estimate the Software Risk and cost

Function Point is a well known established method to estimate the size of software projects. There are several areas of the software engineering in which we can use the function point analysis (FPA) like project planning, project construction, software implementation etc. In this paper we have used the function point approach in order to develop the architecture of the esrcTool. This tool is used for two different purposes, firstly, to estimate the risk in the software and secondly to estimate the cost of the software. In the literature of software engineering there are so many models to estimate the risk in the software like Soft Risk Model, SRAM, SRAEM and so on. But in the esrcTool we have used SRAEM i.e. Software Risk Assessment and Estimation Model, because in this model FP is used as an input variable, and on the other hand side, in order to determine the cost of the software we have used the International Software Benchmarking Standards Group Release Report (ISBSG).

Adding Threat during Software Requirements Elicitation and Prioritization

Requirements may be defined as a demand or need. In software engineering, a requirement is a description of what a system should do. System may have dozen to thousands of requirements. Software requirements stipulate what must be accomplished, transformed, produced or provided. In the field of software engineering researchers, academicians and scientist have developed many models and framework to elicit and prioritize the software requirements. It is well documented that requirement engineering saves money. There are several techniques to elicit the software requirements like JAD, misuse, RAD etc. In this paper we have used the JAD approach to elicit the software requirements. In this paper we have proposed a framework to elicit the software requirements and also to prioritize the software requirements. The proposed framework will rank the requirements by the relative level of threat associated with each requirement.

Analysis of black box software testing techniques: A case study

Software testing is a process of verifying and validating that a software application or program works as per the users expectations. It is used to find out the important defects, flaws, or errors in the application code. In this paper we have developed a tool to generate different test cases automatically. To show the validity of the tool, we have considered the line equation problem and generated different test cases, and finally we conclude that Robustness Technique is better than Boundary Value Analysis, because the expected output (number of times) in case of Robustness Technique for intersecting lines, parallel lines and coincident lines are 12, 12 and 1 respectively while in case of Boundary Value Analysis it is 8, 8 and 1 respectively.

Prediction of software project effort using fuzzy logic

Software development effort estimation is a branch of forecasting that has received increased interest in academia as well as in the field of research and development. Predicting software effort with any acceptable degree remains challenging. In this paper we have developed 2 different linear regression models using fuzzy function point (FFP) and non fuzzy function point in order to predict the software project effort and further we have also considered that the entire projects are organic in nature i.e. the project size lies between 2 to 50 KLOC. After obtaining the software effort, project manager can control the cost and ensures the quality more accurately.