Membrane Computing Model for Software Requirement Engineering

Pavanasam, Velayutham; Subramaniam, Chandrasekaran; Srinivasan, Thulukkanam; D, Jitendra Kumar Jain

doi:10.1109/iccnt.2010.129

Cited by 3 publications

(2 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Not only this technique can perfectly identify the requirements changes, but also becomes handy when someone has to find the complex HTML structure. Pavanasam and Subramaniam [15] propose a model for requirements inspection and state that the requirements change management and requirements analysis phases play an important role in this process. JDesigner tool is used for verification of different requirements engineering processes which consist of requirement transformation and system requirement representation phases.…”

Section: Literature Reviewmentioning

confidence: 99%

Review of Requirements Management Issues in Software Development

Khan¹,

Khalid²,

Haq³

2013

IJMECS

View full text Add to dashboard Cite

A requirement is a capability to which a product or service should conform to. A meticulous consideration to requirements engineering acts as a backbone of software projects. Ambiguous and unrealistic requirements are major source of failure in the software-intensive systems. Requirements engineering processes are complex as most of the requirements engineering documentation is written in natural languages which are less formal and often distract the designers and developers. Requirements management is a continuous process throughout the project lifecycle and relates to documenting, analyzing, tracing and prioritizing requirements and then finally controlling changes. The main issues related to requirements management are usually social, political and cultural. Software requirement engineers who gather the requirements generally consider that such issues are beyond the scope of their profession as they deem them within the project management ambit. In this study, we highlight the management issues that arise in the requirements engineering process and explore the possibilities to tackle them amicably. The study is supplemented with a critical review of the existing methodologies for resolving and managing software requirements.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Review of Requirements Management Issues in Software Development

Khan¹,

Khalid²,

Haq³

2013

IJMECS

View full text Add to dashboard Cite

show abstract

“…Pavanasam and Subramaniam [15] proposed a membrane computing model for software requirement. Tchidi and He [4] used Six Sigma technique and proposed a RE process model based on DFSS.…”

Section: Literature Review and Critical Evaluationmentioning

confidence: 99%

An Assessment of Extreme Programming Based Requirement Engineering Process

Khalid¹,

Haq²,

Khan³

2013

IJMECS

View full text Add to dashboard Cite

Abstract-Comprehensive requirement engineering (RE) process acts as a backbone of any successful project. RE processes are very complex because most of the requirement engineering documentation is written in natural languages, which are less formal and often distract the designers and developers of the system. To streamline different phases of the software lifecycle, first we need to model the requirement document so that we can analyze and integrate the software artifacts. Designers can ensure completeness and consistency of the system by generating models using the requirement documents. In this paper, we have made an attempt to analyze extreme programming based RE approach to understand its utility in the requirement elicitation phase. In this study, different RE process models are evaluated and a comparison of the extreme programming technique is drawn to highlight the merits of the latter technique over the conventional RE techniques.

show abstract

Proposing a Systematic Approach to Verify Software Requirements

Al-Khanjari¹

2014

JSEA

View full text Add to dashboard Cite

Identifying stakeholder's needs, eliciting, categorizing and translating them into specifications is the requirement analysis process. Requirement analysis can be a long and arduous process during which many delicate psychological skills are involved. For any software, it is important to identify all stakeholders, collect their requirements and ensure they understand the implications of the software. The gap between stakeholders' vision of the proposed software and the analysis's depiction of that software is the cause of shortcomings in analysis. If the requirements specified by analysts can be tested against stakeholders' expectations, then this gap might be narrowed, and better solutions might be resulted. This paper discusses the impact of the activities of the analysis phase on the development process and on the software itself. It describes the development of the ReqVerifier tool and proposes a systematic approach on how to test software requirements and verify them against stakeholders' vision in order to develop a good software requirement for a quality software.

show abstract

Membrane Computing Model for Software Requirement Engineering

Cited by 3 publications

References 3 publications

Review of Requirements Management Issues in Software Development

Review of Requirements Management Issues in Software Development

An Assessment of Extreme Programming Based Requirement Engineering Process

Proposing a Systematic Approach to Verify Software Requirements

Contact Info

Product

Resources

About