基于追踪矩阵获取完整性需求的研究

Study on Complete Requirement Acquiring Based on Tracking Matrix

分布式系统自提出以来,逐渐发展成为软件工程中一个重要的研究领域,因此分布性需求成为软件系统的主要特征,同时系统的分布性需求与功能需求又紧密相关。目前,通常使用RUP(Rational Unified Process)推荐的“4+1”视图方法分别将两种需求建模在不同的模型中,此方法在软件工程实践中已经取得了良好的效果,但是也在一定程度上导致了功能需求和分布性需求的分割性,这不利于获取完整的系统需求。针对以上问题,文中首先给出需求追踪的整体框架,从3个层面阐述需求在软件生命周期各个阶段间追踪关系的演变。其次,通过分析需求到其他制品的传播途径,得到需求追踪关系,建立需求追踪矩阵。最后,凭借矩阵计算,描述需求变化追踪的具体实现。通过上述研究,在功能需求模型和分布性需求模型间建立可追踪性链接,不仅能够获取完整性需求,还解决了由需求建模分割性导致的需求变更困难的问题。

Distributed system has gradually developed into an important research field in software engineering since it was proposed.Nowadays,distributed requirements become the main features of the software systems,and distributed requirements and functional requirements are closely related.Currently,the“4+1”views method recommended by RUP(Rational Unified Process)is usually used to model two kinds of requirements in different models.This method has already produced positive feedback and achieved good results in software engineering practice.However,distributed requirements and functional requirements are modeled separately,which leads to the segregation of functional and distri-buted requirements to a certain degree.This segmented requirements modeling method is not conducive to obtain complete software requirements when doing requirements analysis work.In response to the above questions,first of all,this paper gave the overall framework of requirements tracking.It illustrated the evolution of requirements tracking relationships across all phases of the software life cycle from three levels.Secondly,by analyzing the transmission route from requirements to other artifacts,requirements tracking relationships were obtained and requirements tracking matrices were established.Finally,with the matrix calculation,the specific implementation of the requirements change tracking was described.Therefore,through the above research,this paper established tracking links between distributed requirements models and functional requirements models eventually,which not only captures requirements completely,but also solves the problem of difficult requirements changes caused by requirements segmentation.