Results 211 to 220 of about 1,683,526 (269)

From Evidence to Requirements: The Implementation-Aware Target Product Profile (iTPP) for Specifying Mobile Outreach Cancer Testing Pathways

Kierkegaard P, Su B, Moghul M, Cahill D, James ND.   +4 more
europepmc   +1 more source

Some of the next articles are maybe not open access.

Related searches:

To be or not to be required: Yeast vitaminic requirements in winemaking

Food Microbiology, 2023
Although vitamins are prime actors in yeast metabolism, the nature and the extent of their requirement in Saccharomyces cerevisiae in winemaking remains little understood. To fill this gap, the evolution of 8 water-soluble vitamins and their diverse vitamers during its alcoholic fermentation in a synthetic must medium was monitored, providing the first
Evers, Marie, Ramousse, Louise, Morge, Christophe, Sparrow, Celine, Gobert, Antoine, Roullier-Gall, Chloé, Alexandre, Hervé   +6 more
openaire   +3 more sources

(Requirement) evolution requirements for adaptive systems

2012 7th International Symposium on Software Engineering for Adaptive and Self-Managing Systems (SEAMS), 2012
It is often the case that stakeholders want to strengthen/weaken or otherwise change their requirements for a system-to-be when certain conditions apply at runtime. For example, stakeholders may decide that if requirement R is violated more than N times in a week, it should be relaxed to a less demanding one R-.
V. Souza, Lapouchnian, Alexei, Mylopoulos, Ioannis   +2 more
openaire   +2 more sources

Requirements engineering with GRAIL/KAOS: tell the requirements, all the requirements, and nothing else but the requirements

Proceedings IEEE Joint International Conference on Requirements Engineering, 2003
Software engineering tools currently available on the market are focused on solution design rather than on problem description. So-called requirement engineering (RE) tools enable companies to manage their requirements only once they got them out. But poor requirements, even well managed, will cause projects to fail.
Robert Darimont, Emmanuelle Delor, Jean-Luc Roussel, André Rifaut   +3 more
openaire   +1 more source

Requirement reprioritisation for pairwise compared requirements

International Journal of Computer Aided Engineering and Technology, 2014
Prioritisation and reprioritisation are the two main activities in incremental developments of evolving software systems for mass markets. Reprioritisation is very effortful and time consuming activity aiming at re-allotment of priorities to already prioritised requirements as well as changed, delayed, modified and newly arrived ones. Conceptual models
Varun Gupta 0001, Durg Singh Chauhan, Kamlesh Dutta   +2 more
openaire   +1 more source

A Reflective Requirements Specification for Requirements Evolving

2009 Third International Conference on Genetic and Evolutionary Computing, 2009
The classic requirement engineering provides limited technology and inefficient methods for requirements evolution, which leads to great restriction on finish the task of requirements evolution with high-efficiency and high-quality. For resolving above problem, this paper presents a reflective requirements specification for requirements evolution.
Wen-jie Yuan, Shi Ying
openaire   +1 more source

Requirements for requirements engineering techniques

Proceedings of the Second International Conference on Requirements Engineering, 2002
The first argument presented is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second argument is that a key objective of the RE process is to specify a system which will ultimately be successful ...
openaire   +1 more source