Results 211 to 220 of about 473,501 (260)
Some of the next articles are maybe not open access.
Monitoring and diagnosing software requirements
Automated Software Engineering, 2008We propose a framework adapted from Artificial Intelligence theories of action and diagnosis for monitoring and diagnosing failures of software requirements. Software requirements are specified using goal models where they are associated with preconditions and postconditions. The monitoring component generates log data that contains the truth values of
Y. Wang +3 more
openaire +2 more sources
Software requirements prioritizing
Proceedings of the Second International Conference on Requirements Engineering, 2002The importance of candidate software requirements can vary by orders of magnitude, yet most software providers do not have accurate and efficient means for selecting among them. The paper describes a case study at Ericsson Radio Systems AB of two techniques for software requirements prioritizing as a means for determining the importance of candidate ...
openaire +1 more source
Journal on Educational Resources in Computing, 2002
This module describes course SWE 2623 on software systems requirements given at the School of Computing and Software Engineering Southern Polytechnic State University. The process of extracting, deriving, and validating software requirements from a customer are explored, including levels of user/customer involvement, effective means of documenting ...
openaire +1 more source
This module describes course SWE 2623 on software systems requirements given at the School of Computing and Software Engineering Southern Polytechnic State University. The process of extracting, deriving, and validating software requirements from a customer are explored, including levels of user/customer involvement, effective means of documenting ...
openaire +1 more source
REQUIREMENTS FOR DEVELOPMENT OF SOFTWARE REQUIREMENTS
INCOSE International Symposium, 1994AbstractThis paper (1) describes what the current literature identifies as qualities of good software requirements, (2) identifies and examines different categories of software requirement methods, and (3) concludes that methods used to develop software requirements, though not perfect, have advantages that can improve the development of requirements ...
openaire +1 more source
Improvement of Quality of Software Requirements with Requirements Ontology
2009 Ninth International Conference on Quality Software, 2009We have developed a requirements ontology for requirements elicitation of a certain problem domain. This ontology includes functional hierarchy and relationship between functions such as mutual/partial complementary, exclusion, and so on. Using the ontology, we have established a method of checking the quality of a SRS (Software Requirements ...
Dang Viet Dzung, Atsushi Ohnishi
openaire +1 more source
Software requirements for architectured systems
Journal of Lightwave Technology, 2004Recently, increased attention has been paid to how to establish and strengthen the relationships between requirements and architectural design. In particular, how the process must encompass changes to requirements over time and their effects upon a system's architecture. We sketch our work-in-progress in this field, which we concern about a methodology
Elena Navarro 0001 +2 more
openaire +1 more source
Acquisition and validation of software requirements
Knowledge Acquisition, 1994Abstract This paper presents a knowledge-based software engineering tool, DASERT (Detection of Anomalies in Software Engineering Requirements Texts), to acquire and validate functional requirements in natural language. The user describes the functional specifications through informal methods, using graphics with comments in natural language.
Brigitte Biébow, Sylvie Szulman
openaire +1 more source
Software requirements and acceptance testing
Annals of Software Engineering, 1997In this paper we 1) review industry acceptance testing practices and 2) present a systematic approach to scenario analysis and its application to acceptance testing with the aim to improve the current practice. It summarizes the existing practice into categories and identifies the serious weakness.
Pei Hsia, David Chenho Kung, Chris Sell
openaire +1 more source
Relating Software Requirements and Architectures
2011Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form.
Avgeriou, Paris +4 more
openaire +3 more sources
Automatic monitoring of software requirements
Proceedings of the 19th international conference on Software engineering - ICSE '97, 1997Automatic run-time monitoring of software systems’ design/ purchase/ installationtime requirements and assumptions is a key step towards making those systems more robust, maintainable, and self-evolving. A concise language has been designed to permit the convenient expression of a wide range of requirements and assumptions.
Don Cohen +3 more
openaire +1 more source

