Sentence examples for requirements acquisition from inspiring English sources

Sorting techniques, picture sorts in particular, have been employed for customer requirements acquisition during product redesign process.

It concerns both breadth and depth perspectives of customer requirements acquisition as well as customer and marketing analysis.

By applying such a systematic knowledge or requirements acquisition technique, some objectives and constraints of product redesign can then be identified.

In the PCGS, general sorting was adapted for initial requirements acquisition and platform definition; while a fuzzy c-means (FCM) algorithm was integrated with a design alternatives generation strategy for clustering design options and selecting preferred product concepts.

The integration of requirements specification has addressed, in particular: the integration of requirements acquisition and specification with ontology acquisition and specification, the relations between requirements specifications and specifications of task models and problem solving methods, and the relation of requirements specification to verification.

For product platform generation and eliciting bidding criteria, a well-established requirement acquisition technique known as general sorting was adapted and employed.

The product platform of a specific product is first generated by designers or domain experts using general sorting, a requirement acquisition technique, and design knowledge hierarchy (DKH), a knowledge representation structure.

There are no formal requirements for acquisition of the title, but normally persons called by it have had some training in a madrasah, or religious school.

The private sector needs to forecast demand for transportation services to anticipate, among others, future financial requirements, equipment acquisition and labour requirements.

When considering the staffing hours that are saved by using an automated liquid handler, the upfront resource requirements (instrument acquisition and training) can be properly accounted for.

The strategy recognizes that traditional DoD methods of requirements development, acquisition oversight, and especially systems engineering are inadequate to produce results in the desired timeframe, in a manner that is receptive to more frequent decision points and opportunities to change direction.