An Exhaustive Requirement Analysis Approach to Estimate Risk Using Requirement Defect and Execution Flow Dependency for Software Development

2021 ◽  
pp. 1405-1425
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta
Keyword(s):  
Software Development ◽  
Requirement Analysis ◽  
Design And Implementation ◽  
Whole Process ◽  
Failure Risk ◽  
Clear Vision ◽  
Flow Dependency ◽  
Software Engineers ◽  
Business Requirements

Requirement defects are one of the major sources of failure in any software development process as they prevent smooth operation and is taxing both in terms of tracking and validation. The objective of this article is to make requirement analysis phase exhaustive by estimating risk at requirement level using requirement defect information and execution flow dependency as early as possible to inhibit them from being incorporated in design and implementation. The proposed approach works as a two-fold process which computes risk involved with each requirement twice. The whole process is divided into a three-layered framework to finalize requirements with clear vision and scope of a project. The entire process has been supported by a software case study. The results of the proposed work are promising and will help software engineers in ensuring that all business requirements are captured correctly with clear vision and scope. It will also help in decreasing the chances of failure, risk, and conflicts between stakeholder and developer and other challenges involved to develop the project.

An Exhaustive Requirement Analysis Approach to Estimate Risk Using Requirement Defect and Execution Flow Dependency for Software Development

2018 ◽  
Vol 11 (2) ◽  
pp. 68-87 ◽  
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta
Keyword(s):  
Software Development ◽  
Development Process ◽  
Requirement Analysis ◽  
Software Development Process ◽  
Whole Process ◽  
Clear Vision ◽  
Flow Dependency ◽  
Software Engineers ◽  
Business Requirements

Requirement defects are one of the major sources of failure in any software development process as they prevent smooth operation and is taxing both in terms of tracking and validation. The objective of this article is to make requirement analysis phase exhaustive by estimating risk at requirement level using requirement defect information and execution flow dependency as early as possible to inhibit them from being incorporated in design and implementation. The proposed approach works as a two-fold process which computes risk involved with each requirement twice. The whole process is divided into a three-layered framework to finalize requirements with clear vision and scope of a project. The entire process has been supported by a software case study. The results of the proposed work are promising and will help software engineers in ensuring that all business requirements are captured correctly with clear vision and scope. It will also help in decreasing the chances of failure, risk, and conflicts between stakeholder and developer and other challenges involved to develop the project.

SERIES

2022 ◽  
pp. 1139-1153
Author(s):  
Chetna Gupta ◽  
Priyanka Chandani
Keyword(s):  
Early Identification ◽  
Requirement Analysis ◽  
Domain Modeling ◽  
Design And Implementation ◽  
Preventive Actions ◽  
Clear Vision ◽  
Software Engineers ◽  
Risk Estimator ◽  
Business Requirements

Requirement defects are one of the major sources of failure in any software development process, and the main objective of this chapter is to make requirement analysis phase exhaustive by estimating risk at requirement level by analyzing requirement defect and requirement inter-relationships as early as possible to using domain modeling to inhibit them from being incorporated in design and implementation. To achieve this objective, this chapter proposes a tool to assist software developers in assessing risk at requirement level. The proposed tool, software risk estimator, SERIES in short, helps in early identification of potential risk where preventive actions can be undertaken to mitigate risk and corrective actions to avoid project failure in collaborative manner. The entire process has been supported by a software case study. The results of the proposed work are promising and will help software engineers in ensuring that all business requirements are captured correctly with clear vision and scope.

SERIES

2021 ◽  
pp. 238-252
Author(s):  
Chetna Gupta ◽  
Priyanka Chandani
Keyword(s):  
Early Identification ◽  
Requirement Analysis ◽  
Domain Modeling ◽  
Design And Implementation ◽  
Preventive Actions ◽  
Clear Vision ◽  
Software Engineers ◽  
Risk Estimator ◽  
Business Requirements

Requirement defects are one of the major sources of failure in any software development process, and the main objective of this chapter is to make requirement analysis phase exhaustive by estimating risk at requirement level by analyzing requirement defect and requirement inter-relationships as early as possible to using domain modeling to inhibit them from being incorporated in design and implementation. To achieve this objective, this chapter proposes a tool to assist software developers in assessing risk at requirement level. The proposed tool, software risk estimator, SERIES in short, helps in early identification of potential risk where preventive actions can be undertaken to mitigate risk and corrective actions to avoid project failure in collaborative manner. The entire process has been supported by a software case study. The results of the proposed work are promising and will help software engineers in ensuring that all business requirements are captured correctly with clear vision and scope.

A Framework for the Generation of Class Diagram from Text Requirements using Natural language Processing

2021 ◽  
Vol 10 (1) ◽  
pp. 25-31
Keyword(s):  
Natural Language Processing ◽  
Software Development ◽  
Natural Language ◽  
Language Processing ◽  
English Language ◽  
Software Requirements ◽  
Class Diagram ◽  
Requirement Analysis ◽  
Part Of Speech ◽  
Software Engineers

The software development procedure begins with identifying the requirement analysis. The process levels of the requirements start from analysing the requirements to sketch the design of the program, which is very critical work for programmers and software engineers. Moreover, many errors will happen during the requirement analysis cycle transferring to other stages, which leads to the high cost of the process more than the initial specified process. The reason behind this is because of the specifications of software requirements created in the natural language. To minimize these errors, we can transfer the software requirements to the computerized form by the UML diagram. To overcome this, a device has been designed, which plans can provide semi-automatized aid for designers to provide UML class version from software program specifications using natural Language Processing techniques. The proposed technique outlines the class diagram in a well-known configuration and additionally facts out the relationship between instructions. In this research, we propose to enhance the procedure of producing the UML diagrams by utilizing the Natural Language, which will help the software development to analyze the software requirements with fewer errors and efficient way. The proposed approach will use the parser analyze and Part of Speech (POS) tagger to analyze the user requirements entered by the user in the English language. Then, extract the verbs and phrases, etc. in the user text. The obtained results showed that the proposed method got better results in comparison with other methods published in the literature. The proposed method gave a better analysis of the given requirements and better diagrams presentation, which can help the software engineers. Key words: Part of Speech,UM

A Model-Driven Approach for the Design and Implementation of Software Development Methods

2012 ◽  
Vol 3 (4) ◽  
pp. 86-103 ◽  
Author(s):  
Mario Cervera ◽  
Manoli Albert ◽  
Victoria Torres ◽  
Vicente Pelechano
Keyword(s):  
Software Development ◽  
Method Engineering ◽  
Model Driven ◽  
Design And Implementation ◽  
Two Phases ◽  
Definition Of ◽  
Model Driven Approach ◽  
Development Methods ◽  
Software Development Methods

The Situational Method Engineering (SME) discipline emerged two decades ago to address the challenge of the in-house definition of software development methods and the construction of the corresponding supporting tools. Unfortunately, current SME approaches still have limitations that are hindering their adoption by industry. One of these limitations is that most approaches do not properly encompass two phases of the SME lifecycle, which refer to the method design and the method implementation. To address this limitation, this paper demonstrates how Model-Driven Development (MDD) techniques can contribute to successfully cover both phases. The proposal is illustrated by a real case study that is currently being used at the Valencian Regional Ministry of Infrastructure, Territory and Environment.

Speaking of Software

2009 ◽  
pp. 75-97 ◽  
Author(s):  
Ann Brady
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Case Studies ◽  
Interdisciplinary Collaboration ◽  
Technical Communicators ◽  
Software Engineers ◽  
Problematic Situations ◽  
Post Hoc ◽  
Cross Fertilization

We describe our recent efforts to generate and use case studies to teach communication skills in software development. We believe our work is innovative in several respects. The case studies touch on rhetorical issues that are crucial to software development yet not commonly associated with the field of software engineering. Moreover, they present students with complex, problematic situations, rather than sanitized post hoc interpretations often associated with case study assignments. The case study project is an interdisciplinary collaboration that interweaves the expertise of software engineers and technical communicators. Our software engineering and technical communication curricula have been enhanced through this cross-fertilization.

Virtual instrument designed for data acquisition

2020 ◽  
Vol 65 (1) ◽  
pp. 179-186
Author(s):  
Mihaela Dorica Stroia
Keyword(s):  
Software Development ◽  
Data Acquisition ◽  
Virtual Instrument ◽  
Virtual Instrumentation ◽  
Design And Implementation ◽  
Adequate Design

Current software development directions open up a world of possibilities, especially in the engineering field. Present paper is meant to highlight the advantages and in particular the ease of using virtual instrumentation facilities, with a proper and adequate design and implementation of desired instrument. In this idea we bring into discussion a design for virtual instrument which can be used for data acquisition that can be stored for further simulations according to the needs required by the process in discussion.

come_NET

2018 ◽  
Author(s):  
Konstantin Aal ◽  
Anne Weibert ◽  
Kai Schubert ◽  
Mary-Ann Sprenger ◽  
Thomas Von Rekowski
Keyword(s):  
Social Media ◽  
Design Process ◽  
Participatory Design ◽  
Controlled Environment ◽  
Design And Implementation ◽  
Neighborhood Contexts ◽  
Study Results ◽  
Computer Club ◽  
Close Cooperation

The case study presented in this chapter discusses the design and implementation of an online platform, “come_NET,” in the context of intercultural computer clubs in Germany. This tool was built in close cooperation with the children and adult computer club participants. It was designed to foster the sharing of ideas and experiences across distances, support collaboration, and make skills and expertise accessible to others in the local neighborhood contexts. In particular, the participatory-design process involving the children in the computer clubs fostered a profound understanding of the platform structure and functionalities. The study results show how younger children in particular were able to benefit, as the closed nature of the platform enabled them to gather experience as users of social media, but in a safe and controlled environment.

Sign in / Sign up

Export Citation Format

Share Document