- Volume 9 Issue 4
In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn't guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.