Software Requirements Engineering

Thayer, Richard H.; Dorfman, Merlin; Bailin, Sidney C.

doi:10.1109/9781118156674

Cited by 69 publications

(40 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…1. The classic V model for system development (adapted from [13]). Each development phase is subject to a corresponding V&V phase-horizontal layers-as the software is built and integrated.…”

Section: The Classic V Model For System Developmentmentioning

confidence: 99%

“…Software testing methods can be very effective both in revealing failures and assessing the reliability of software systems, but cannot provide evidence of the absence of faults [13,15]. More rigorous and effective strategies to reason about the program correctness employ model checking, graph-based, and other model-based software testing and verification methods [16][17][18][19].…”

Section: The Classic V Model For System Developmentmentioning

confidence: 99%

See 1 more Smart Citation

Towards Practical Runtime Verification and Validation of Self-Adaptive Software Systems

Tamura

Villegas

Müller

et al. 2013

Software Engineering for Self-Adaptive Systems II

View full text Add to dashboard Cite

Abstract. Software validation and verification (V&V) ensures that software products satisfy user requirements and meet their expected quality attributes throughout their lifecycle. While high levels of adaptation and autonomy provide new ways for software systems to operate in highly dynamic environments, developing certifiable V&V methods for guaranteeing the achievement of self-adaptive software goals is one of the major challenges facing the entire research field. In this chapter we (i) analyze fundamental challenges and concerns for the development of V&V methods and techniques that provide certifiable trust in self-adaptive and self-managing systems; and (ii) present a proposal for including V&V operations explicitly in feedback loops for ensuring the achievement of software self-adaptation goals. Both of these contributions provide valuable starting points for V&V researchers to help advance this field.

show abstract

Section: The Classic V Model For System Developmentmentioning

confidence: 99%

Section: The Classic V Model For System Developmentmentioning

confidence: 99%

Towards Practical Runtime Verification and Validation of Self-Adaptive Software Systems

Tamura

Villegas

Müller

et al. 2013

Software Engineering for Self-Adaptive Systems II

View full text Add to dashboard Cite

show abstract

“…According to [9], requirements engineering regards establishing and documenting software requirements. Through this process it is possible defining what the system should be able to do and the constraints in which it needs to operate.…”

Section: Methodsmentioning

confidence: 99%

Requirements Analysis and Definition for Eco-factories: The Case of EMC2

Taisch¹,

Stahl²

2013

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. Climate change mitigation and the EU2020 strategy foster energy efficiency in Europe's future manufacturing landscape. These challenges make high demands to SMEs as well to MNCs. The paper gives insight to an approach on Eco-factories based on the EU-funded FP7 project EMC2. Ecofactories will enable the quantum leap in integrating environmental issues in brownfield and greenfield factory planning and factory operation. The paper focuses on the identification, structuring and definition of requirements for Ecofactory simulation approaches. Requirements for developing a simulation environment for integrating energy and material flows for detailed analysis but also wide user spectrum is presented. The paper shows that demands are twofold requesting integrated, modular and detailed simulation solutions as well as emphasize on user-friendliness and low complexity.

show abstract

“…Realizing the crucial role of requirements to the design and development of the software, requirements discovery and analysis activities came to be recognized as 'Requirements Engineering (RE)' with the publication of selected papers on RE in Ref. [5] and establishment of regular conferences on RE by IEEE Society. This helped in organizing and bringing discipline to various process models for RE activities and frameworks for analysing requirements.…”

Section: Introductionmentioning

confidence: 99%

Grounding Functional Requirements Classification in Organizational Semiotics

Sharma¹

2017

Interdisciplinary Approaches to Semiotics

View full text Add to dashboard Cite

An information system has its requirements rooted in organizational policies and behaviour, the complexity of which is governed by the hierarchy and the dependencies of the activities within the organization. This complexity makes requirements analysis for an envisioned information system an intricately challenging task. The absence of well-deined body of knowledge clearly specifying which requirements must be looked for further deepens the challenge of requirements analysis. Though requirements are broadly classiied as functional and non-functional, a special concern is required for functional requirements as the information system is expected to meet the behaviour of the organization. We explore the role of organizational semiotics in extracting and analysing functional requirements for an envisioned information system. We also report the results of supervised learning to automatically extract the functional requirements from the existing available documentation.Keywords: organizational semiotics, requirements engineering, functional requirements, business rules IntroductionSoftware Engineering has come a long way after its inception in 1960 with the famous NATO conferences [1,2]. The discussions in these conferences are credited with bringing discipline to the activity of software development and laying down the foundations of this ield by relating it to mathematics. There have been further developments and innovations in an atempt to realize the goals of systematic, disciplined and quantiiable approach to software development.The earliest proposed waterfall process model for software development evolved towards iterative process models and is now being replaced by the latest agile methodologies. In addition © 2017 The Author(s). Licensee InTech. This chapter is distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.to process models, programming paradigms have evolved from procedural approach of structured programming [3] to object-oriented programming [4]. However, the goal of a systematic, disciplined and quantiiable approach is still far away. A key role in realizing this goal is played by the requirements, that is the main input to the (engineering) process of software development. Realizing the crucial role of requirements to the design and development of the software, requirements discovery and analysis activities came to be recognized as 'Requirements Engineering (RE)' with the publication of selected papers on RE in Ref. [5] and establishment of regular conferences on RE by IEEE Society. This helped in organizing and bringing discipline to various process models for RE activities and frameworks for analysing requirements. However, the proposed as well as practiced methodologies to ensure consistent, correct, complete and unambiguous requirements have not exhibited the three deining parameters of an engineering...

show abstract

Software Requirements Engineering

Cited by 69 publications

References 0 publications

Towards Practical Runtime Verification and Validation of Self-Adaptive Software Systems

Towards Practical Runtime Verification and Validation of Self-Adaptive Software Systems

Requirements Analysis and Definition for Eco-factories: The Case of EMC2

Grounding Functional Requirements Classification in Organizational Semiotics

Contact Info

Product

Resources

About