Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Process-Centered Requirements Engineering
Process-Centered Requirements Engineering
An Industrial Survey of Requirements Interdependencies in Software Product Release Plannin
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Security and Privacy Requirements Analysis within a Social Setting
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Identification of Crosscutting Requirements Based on Feature Dependency Analysis
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Integration needs and consistency evaluation for requirement analysis in CIM development
International Journal of Computer Applications in Technology
On the requirements of new software development
International Journal of Business Intelligence and Data Mining
Analysis of prediction performance of training-based models using real network traffic
International Journal of Computer Applications in Technology
Recognising 2.5D manufacturing feature using neural network
International Journal of Computer Applications in Technology
Fault diagnosis of nuclear power plant based on genetic-RBF neural network
International Journal of Computer Applications in Technology
Hi-index | 0.00 |
We believe that the requirements at the leaf-node level of the requirements tree structure cannot be viewed in isolation and that dependencies between them exist. We pursued this notion in order to find a coherent set of requirement dependencies that would facilitate the formation of a requirements network at the leaf-node level. This network could well be aristocratic or egalitarian. An aristocratic network will highlight a vital few nodes (requirements) with a high degree of connectivity. Such vital few requirements work as 'hubs' and are expected to have a decisive influence on the success of the product/system, to which the requirements structure points. Such critical information may provide a more effective resolution to issues such as release planning, prioritisation, reuse, change management and so on, enhance systems engineering implementation and thereby make system development more effective. In this paper, we discuss the formulation of a mechanism to identify the dependencies between requirements and we discuss the process to connect them using a series of steps in order to form a network of requirements at the leaf-node level of the requirement tree structure.