Personal tools
You are here: Home → Knowledge Model → REPOSITORY of Terms → R → Requirements Engineering
ICSE 2012
scube_icse_small

Final Workshop @ ICSE 2012

Proceedings are availabe from here.

 

Requirements Engineering

by Benedikt Liegener — last modified Apr 26, 2012 12:05
— filed under:

Definitions

Term:
Requirments Engineering		 Domain: Cross-cutting issues
Engineering and Design
(KM-ED)		 Adaptation and Monitoring
(KM-AM)		 Quality Definition, Negotiation and Assurance
(KM-QA)		 Generic
(domain independent)
D
o
m
a
i
n
:
L
a
y
e
r
s
 Business Process Management
(KM-BPM)



Service Composition and Coordination
(KM-SC)



Service Infrastructure
(KM-SI)



Generic
(domain independent)		 Requirements Engineering is one activity in the software development lifecycle, which aims to identify, document, agree upon and verify the purpose of the system to be. [CD-JRA-1.1.2]

Requirements Engineering can be defined as the systematic process of developing requirements through an iterative co-operative process of analyzing the problem, documenting the resulting observations in a variety of representation formats, and checking the accuracy of the understanding gained [INTEROP]. 

Requirements Engineering is concerned with the elicitation, analysis, specification, and validation of software requirements. It is widely acknowledged within the software industry that software engineering projects are critically vulnerable when these activities are performed poorly [SWEBOK].

 

Competencies

External Competencies


 

 

References

Document Actions
  • Send this
  • Print this
  • Bookmarks
 

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.