Results 221 to 230 of about 719,114 (264)
Some of the next articles are maybe not open access.
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
An approach to software requirement specification
Proceedings COMPSAC 88: The Twelfth Annual International Computer Software & Applications Conference, 2003An approach to software requirement specification using a structured bipartite inheritance network is presented. A bipartite inheritance network is a network with two different kinds of basic nodes, data entity and action, which are independent of each other and structured into an inheritance hierarchy.
Stephen S. Yau, Chung-Shyan Liu
openaire +1 more source
Checking Sanity of Software Requirements
2012In the last decade it became a common practice to formalise software requirements to improve the clarity of users' expectations. In this work we build on the fact that functional requirements can be expressed in temporal logic and we propose new techniques that automatically detect flaws and suggest improvements of given requirements.
Jiri Barnat, Petr Bauch, Lubos Brim
openaire +1 more source
Tracing requirements in software design
Proceedings of the 2017 International Conference on Software and System Process, 2017Software requirement analysis is an essential step in software development process, which defines what is to be built in a project. Requirements are mostly written in text and will later evolve to fine-grained and actionable artifacts with details about system configurations, technology stacks, etc.
Zeheng Li +4 more
openaire +1 more source
Politeness as a Social Software Requirement
International Journal of Virtual Communities and Social Networking, 2009If politeness makes society a nicer place to be, by lubricating the interaction of its human parts, then the same is important for online society. As the Internet becomes more social, software can mediate social interactions, serve as a social agent or act as a personal assistant, but to succeed in these roles it must learn a new skill - politeness ...
openaire +1 more source
Towards an Anatomy of Software Requirements
2019Requirements engineering is crucial to software development but lacks a precise definition of its fundamental concepts. Even the basic definitions in the literature and in industry standards are often vague and verbose. To remedy this situation and provide a solid basis for discussions of requirements, this work provides precise definitions of the ...
Bertrand Meyer 0001 +4 more
openaire +1 more source
Adaptive monitoring of software requirements
2010 First International Workshop on Requirements@Run.Time, 2010Requirements monitoring continuously probes system components and sensors to assess whether the system satisfies its requirements and to detect conditions conducive to a requirement violation. Monitoring, however, is typically computationally expensive, intrusive, and presents tradeoffs between monitoring costs and accuracy, or the degree of coverage ...
Andres J. Ramirez +2 more
openaire +1 more source
Problems and requirements [software development]
Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95), 2002Requirements, specifications, and programs are distinguished by the phenomena they concern. Requirements are about phenomena of the application domain and describe properties of the domain that the machine is required to bring about and maintain. The application domain is informal, and serious difficulties are encountered both in describing it and in ...
openaire +1 more source