Software requirements: analysis and specification
Software requirements: analysis and specification
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Viewpoints: principles, problems and a practical approach to requirements engineering
Annals of Software Engineering
COTS Integration: Plug and Pray?
Computer
Acquiring COTS Software Selection Requirements
IEEE Software
Requirements Engineering, Expectations Management, and the Two Cultures
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
COTS Tenders and Integration Requirements
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Structured Analysis and System Specification
Structured Analysis and System Specification
Opportunistic Problem Solving in Software Engineering
IEEE Software
Information and Software Technology
Using Wikis to Tackle Reuse in Software Projects
IEEE Software
A methodology for ERP misfit analysis
Information and Management
Training students to be agile information systems developers: a pedagogical approach
Proceedings of the 2008 ACM SIGMIS CPR conference on Computer personnel doctoral consortium and research
Athena: A collaborative approach to requirements elicitation
Computers in Industry
Ontology-Based Requirements Conflicts Analysis in Activity Diagrams
ICCSA '09 Proceedings of the International Conference on Computational Science and Its Applications: Part II
CDADE: Conflict detector in activity diagram evolution based on speech act and ontology
Knowledge-Based Systems
PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
Non-formal techniques for requirements elicitation, modeling, and early assessment for services
Proceedings of the 29th Annual European Conference on Cognitive Ergonomics
Expanding the horizons of software development processes: a 3-D integrated methodology
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
A graph based requirements clustering approach for component selection
Advances in Engineering Software
Applying ontology-based blog to detect information system post-development change requests conflicts
Information Systems Frontiers
Software architects' experiences of quality requirements: what we know and what we do not know?
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Hi-index | 0.00 |
Before developing any system, you have to understand what the system is supposed to do and how it its use can support the goals of the business or individuals that will pay for that system. This involves understanding the application domain (telecommunications, railways, retail banking, games, etc.), the system's operational constraints, the specific functionality required by stakeholders and essential system characteristics such as performance, security and dependability. Requirements engineering is the name given to a structured set of activities that help develop this understanding and that document the system specification for system stakeholders and engineers involved in the system development.This article is a short tutorial that introduces the fundamental activities of requirements engineering and discusses how it has evolved as part of the software engineering process. However, rather than focus on established RE techniques, I discuss how the changing nature of software engineering has led to new challenges for requirements engineering. I then introduce a number of new techniques that help meet these challenges by integrating requirements engineering more closely with other systems implementation activities.