Requirements in Conflict: Player vs. Designer vs. Cheater
Abstract
- Requirements in Conflict: Player vs. Designer vs. Cheater
Recommendations
Conflict of requirements: a pattern for the treatment of conflicting non-functional requirements
SugarLoafPLoP '12: Proceedings of the 9th Latin-American Conference on Pattern Languages of ProgrammingSoftware development is an activity that works several aspects of Software Engineering. One of them is requirements elicitation and its writing in an understandable notation for software developers. Non-Functional Requirements are those associated to ...
Requirements for Requirements Engineering Technique
ICRE '96: Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)The first argument presented in this paper is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second ...
Impact of Non-functional Requirements on Requirements Evolution
ICETET '13: Proceedings of the 2013 6th International Conference on Emerging Trends in Engineering and TechnologySoftware impacts almost every aspect of modern society. Developers of a software system are responsible for identifying the requirements of the application, developing software that implements the requirements, and for allocating appropriate resources (...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
Publisher
IEEE Computer Society
United States
Publication History
Qualifiers
- Article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 0Total Downloads
- Downloads (Last 12 months)0
- Downloads (Last 6 weeks)0