Readings Newsletter
Become a Readings Member to make your shopping experience even easier.
Sign in or sign up for free!
You’re not far away from qualifying for FREE standard shipping within Australia
You’ve qualified for FREE standard shipping within Australia
The cart is loading…
Seminar paper from the year 2016 in the subject Computer Science - Software, grade: 1,0, University of Cologne (Seminar fur Wirtschaftsinformatik und integrierte Informationssysteme), course: Bachelorseminar Requirements Engineering, language: English, abstract: The goal of this work was to provide a holistic overview of current frameworks for requirements elicitation. They can be catogrized as goal- or process-oriented ones. For achieving this goal, I conducted a structured literature review and summarized the results within in tables. Hence, this work can serve as reference manual for quickly getting an overview of possbile requirements elicitation approaches. There exist a couple of approaches for the elicitation of requirements for software projects. Usually, it is difficult to identify the most relevant ones in order to have a coherent software development process. In general, it is distinguished between functional and non-functional requirements. Functional ones describe what a system has to do, what a system has to perform. Non-functional ones put constraints on the software, meaning they are quality attributes such as availability and security.
$9.00 standard shipping within Australia
FREE standard shipping within Australia for orders over $100.00
Express & International shipping calculated at checkout
Seminar paper from the year 2016 in the subject Computer Science - Software, grade: 1,0, University of Cologne (Seminar fur Wirtschaftsinformatik und integrierte Informationssysteme), course: Bachelorseminar Requirements Engineering, language: English, abstract: The goal of this work was to provide a holistic overview of current frameworks for requirements elicitation. They can be catogrized as goal- or process-oriented ones. For achieving this goal, I conducted a structured literature review and summarized the results within in tables. Hence, this work can serve as reference manual for quickly getting an overview of possbile requirements elicitation approaches. There exist a couple of approaches for the elicitation of requirements for software projects. Usually, it is difficult to identify the most relevant ones in order to have a coherent software development process. In general, it is distinguished between functional and non-functional requirements. Functional ones describe what a system has to do, what a system has to perform. Non-functional ones put constraints on the software, meaning they are quality attributes such as availability and security.