Übersetzung für 'requirements analysis' von Englisch nach Deutsch

requirements analysis

Bedarfsanalyse {f}spec.

requirements analysis <RA>

Erhebung {f} der Anforderungencomp.econ.

Anforderungs­erhebung {f}comp.econ.QM

Erheben {n} der Anforderungencomp.econ.QM

Anforderungs­analyse {f} <AA>econ.QMtech.

---

Werbung

analysis of educational requirements

Bildungs­bedarfsanalyse {f}

---

receiver-operating characteristic / characteristics curve analysis <ROC curve analysis>

ROC-Kurvenanalyse {f} [z. B. Medizinstatistik]stat.

X-ray fluorescence analysis <XRF analysis>

Röntgenfluoreszenzanalyse {f} <RFA>MedTech.

requirements

Bestimmungen {pl}

Auflagen {pl}

Notwendigkeiten {pl}

Belange {pl}

Bedingungen {pl} [Voraussetzungen]tech.

Bedarfe {pl} [nur fachspr.] [Bedürfnisse]

Voraussetzungen {pl}

Anforderungen {pl}

Erfordernisse {pl}

requirements {pl}

Bedarf {m}

finance requirements {pl}

Finanzbedarf {m}fin.

formal requirements

Formvorschriften {pl}

training requirements {pl}

Schulungs­bedarf {m}educ.

financial requirements {pl}

Finanzbedarf {m}fin.

statutory requirements

staatliche Auflagen {pl}

borrowing requirements {pl}

Finanzierungs­bedarf {m}fin.

funding requirements {pl}

Finanzierungs­bedarf {m}fin.

financing requirements {pl}

Finanzierungs­bedarf {m}fin.

• These activities can include requirements analysis, software design, software development, and unit testing.
• Though separating functionality from efficiency is a valid separation of concerns, it can lead to a situation where end users will complete and document the requirements analysis and prototyping of the tool, without the involvement of business analysts.
• A specification language is a formal language in computer science used during systems analysis, requirements analysis, and systems design to describe a system at a much higher level than a programming language, which is used to produce the executable code for a system.
• Before beginning the ICONIX process there needs to have been some requirements analysis done. From this analysis use cases can be identified, a domain model produced and some prototype GUIs made.
• To prepare the organization properly a requirements analysis of both IT-requirements as well as organizational requirements is necessary.

• As in test-driven development, test cases are written "before" coding, as part of requirements analysis, rather than afterward as part of testing.
• Entity-relationship models were being used in the first stage of information system design during the requirements analysis to describe information needs or the type of information that is to be stored in a database.
• Activities within the group include requirements analysis, cross-mission planning and architecture development, strategic awareness planning, cross-program engineering, and systems acquisition development.
• Additional Block 3 capabilities were being defined through the requirements analysis and roadmap phase.
• Concepts like business process reengineering, product software market analysis, and requirements analysis are commonly known and extensively used in this context.

• The FIP standard is based on a French initiative in 1982 to create a requirements analysis for a future field bus standard.
• Operational feasibility is the measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development.
• The first step in most formal software development processes is requirements analysis, followed by testing to determine value modeling, implementation, and failure elimination (debugging).
• This process is one which is generally considered part of requirements analysis, and requires skill on the part of the database designer to elicit the needed information from those with the domain knowledge.
• Requirements engineering may involve a feasibility study or a "conceptual analysis phase" of the project and requirements elicitation (gathering, understanding, reviewing, and articulating the needs of the stakeholders) and requirements analysis, analysis (checking for consistency and completeness), specification (documenting the requirements) and validation (making sure the specified requirements are correct).