Skip to Main Content
Value-oriented requirements play key role for the success of real time database systems. Specifying value oriented-requirements is crucial for real-time database systems. As real-time database systems have lot of constraints, we cannot control real-time database system at run time, but we can collect value-oriented requirements to improve and develop next version of real-time database system. Quality requirements are elicited from stakeholders, and stakeholders define requirements qualitatively. Qualitatively defined requirements are not measurable and difficult to verify. So there is need to create a value-oriented approach to specify high quality requirements to develop next version of real-time database system. Not so many results have been reported for supporting value-oriented requirements to develop next version of real-time database system. We address issues on non-functional and functional requirements, will try to prove how non-functional requirement can be value-oriented requirements and present a model to get value-oriented requirements. We tried to improve iterative and incremental development by merging value-oriented model, in response to the weaknesses of waterfall model.