49 citations · 70 across the 13 of their papers we have counts for
17 papers
Lessons from Formally Verified Deployed Software Systems (Extended version)
Li Huang, Sophie Ebersold, Alexander Kogtenkov +2
The technology of formal software verification has made spectacular advances, but how much does it actually benefit the development of practical software? Considerable disagreement…
Object-Oriented Requirements: a Unified Framework for Specifications, Scenarios and Tests
Maria Naumcheva, Sophie Ebersold, Alexandr Naumchev +3
A paradox of requirements specifications as dominantly practiced in the industry is that they often claim to be object-oriented (OO) but largely rely on procedural (non-OO) techniq…
Extracting Software Requirements from Unstructured Documents
Vladimir Ivanov, Andrey Sadovykh, Alexandr Naumchev +2
Requirements identification in textual documents or extraction is a tedious and error prone task that many researchers suggest automating. We manually annotated the PURE dataset an…
Code Review in the Classroom
Victor Rivera, Hamna Aslam, Alexandr Naumchev +3
This paper presents a case study to examine the affinity of the code review process among young developers in an academic setting. Code review is indispensable considering the posi…
Seamless Object-Oriented Requirements
Alexandr Naumchev
Design by Contract enables seamless software development by unifying software requirements with their implementations. In its pure form, however, Design by Contract leaves some pro…
The role of formalism in system requirements (full version)
Jean-Michel Bruel, Sophie Ebersold, Florian Galinier +3
A major determinant of the quality of software systems is the quality of their requirements, which should be both understandable and precise. Most requirements are written in natur…
The Anatomy of Requirements
Bertrand Meyer, Jean-Michel Bruel, Sophie Ebersold +2
Requirements 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…
DevOps and its Philosophy : Education Matters!
Evgeny Bobrov, Antonio Bucchiarone, Alfredo Capozucca +4
DevOps processes comply with principles and offer practices with main objective to support efficiently the evolution of IT systems. To be efficient a DevOps process relies on a set…
Object-oriented requirements: reusable, understandable, verifiable
Alexandr Naumchev
Insufficient requirements reusability, understandability and verifiability jeopardize software projects. Empirical studies show little success in improving these qualities separate…
Teaching DevOps in Corporate Environments: An experience report
Manuel Mazzara, Alexandr Naumchev, Larisa Safina +2
This paper describes our experience of training a team of developers of an East-European phone service provider. The training experience was structured in two sessions of two days…
Towards operational natural language
Alexandr Naumchev
The multiplicity of software projects' stakeholders and activities leads to the multiplicity of software specification views and thus creates the need to establish mutual consisten…
Teaching Programming and Design-by-Contract
Daniel de Carvalho, Rasheed Hussain, Adil Khan +7
This paper summarizes the experience of teaching an introductory course to programming by using a correctness by construction approach at Innopolis University, Russian Federation.…
AutoReq: expressing and verifying requirements for control systems
Alexandr Naumchev, Bertrand Meyer, Manuel Mazzara +3
The considerable effort of writing requirements is only worthwhile if the result meets two conditions: the requirements reflect stakeholders' needs, and the implementation satisfie…
A contract-based method to specify stimulus-response requirements
Alexandr Naumchev, Manuel Mazzara, Bertrand Meyer +3
A number of formal methods exist for capturing stimulus-response requirements in a declarative form. Someone yet needs to translate the resulting declarative statements into impera…
Seamless Requirements
Alexandr Naumchev, Bertrand Meyer
Popular notations for functional requirements specifications frequently ignore developers' needs, target specific development models, or require translation of requirements into te…
Unifying Requirements and Code: an Example
Alexandr Naumchev, Bertrand Meyer, Victor Rivera
Requirements and code, in conventional software engineering wisdom, belong to entirely different worlds. Is it possible to unify these two worlds? A unified framework could help ma…
Complete contracts through specification drivers
Alexandr Naumchev, Bertrand Meyer
Existing techniques of Design by Contract do not allow software developers to specify complete contracts in many cases. Incomplete contracts leave room for malicious implementation…