Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.

Nima Kaveh

dblp:18/710 · DBLP profile ↗
← Back
4ranked-venue papers
2as first author
0since 2021 · last 2002
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 2 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
3 papers
Distributed systems · 100%
Software engineering, system software, and programming languages
4 papers
Requirements engineering and software design · 65% Program verification · 26% Services computing and microservices · 9%
Theoretical computer science
1 paper
Automated reasoning and model checking · 50% Distributed computing theory · 50%

Topics — the 10 heaviest of 12, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture › component-based software engineering
component-based development
0.122002
Component technologies: Java beans, COM, CORBA, RMI, EJB and the CORBA component model · ICSE 2002
Component technologies: Java Beans, COM, CORBA, RMI, EJB and the CORBA Component Model · ESEC / SIGSOFT FSE 2001
Program verification
model checking
0.012001
Model Checking Distributd Objects Design · ICSE 2001
Distributed systems › middleware › distributed object middleware
CORBA
0.012001
Model Checking Distributd Objects Design · ICSE 2001
Distributed systems › concurrency control
deadlock detection
0.012001
Deadlock detection in distribution object systems · ESEC / SIGSOFT FSE 2001
Distributed systems › middleware
distributed object middleware
0.012001
Model Checking Distributd Objects Design · ICSE 2001
Distributed systems
distributed object systems
0.012001
Deadlock detection in distribution object systems · ESEC / SIGSOFT FSE 2001
Distributed computing theory › predicate detection › stable property detection
deadlock detection
0.012001
Deadlock detection in distribution object systems · ESEC / SIGSOFT FSE 2001
Automated reasoning and model checking
model checking
0.012001
Deadlock detection in distribution object systems · ESEC / SIGSOFT FSE 2001
Services computing and microservices › middleware
distributed object middleware
0.012002
Component technologies: Java beans, COM, CORBA, RMI, EJB and the CORBA component model · ICSE 2002
Requirements engineering and software design › model-driven engineering
UML
0.012001
Deadlock detection in distribution object systems · ESEC / SIGSOFT FSE 2001

Methods — techniques the papers use, named apart from their topics

process algebra · 0.1UML stereotypes · 0.1model checking · 0.1
YearPublicationVenuePosition
2002 Component technologies: Java beans, COM, CORBA, RMI, EJB and the CORBA component model
abstract
This one-day tutorial is aimed at software engineering practitioners and researchers, who are familiar with object-oriented analysis, design and programming and want to obtain an overview of the technologies that are enabling component-based development. We introduce the idea of component-based development by defining the concept and providing its economic rationale. We describe how object-oriented programming evolved into local component models, such as Java Beans and distributed object technologies, such as the Common Object Request Broker Architecture (CORBA), Java Remote Method Invocation (RMI) and the Component Object Model (COM). We then address how these technologies matured into distributed component models, in partiuclar Enterprise Java Beans (EJB) and the CORBA Component Model (CCM). We give an assessment of the maturity of each of these technologies and sketch how they are used to build distributed architectures.
Wolfgang Emmerich, Nima Kaveh
ICSE2
2001 Model Checking Distributd Objects Design
abstract
Potential advantages brought about by distributed system architectures has given rise to the number of applications being based around it. Advantages include an increase in fault tolerance due to replicated components and achieving cost effective scalability by distributing the execution of a task over several relatively cheap hosts rather than a central mainframe. The construction of distributed applications via the direct use of network operating system primitives is no longer feasible and middleware technologies are fast becoming the alternative approach. We note that amongst the different form of middleware, distributed object middleware offers the richest support to application designers and incorporates primitives for distributed transaction management and asynchronous message passing. From the set of distributed object middleware approaches, we concentrate on CORBA because it offers the richest set of synchronization and threading primitives.
Nima Kaveh
ICSE1
2001 Component technologies: Java Beans, COM, CORBA, RMI, EJB and the CORBA Component Model
abstract
This one-day tutorial is aimed at software engineering practitioners and researchers, who are familiar with object-oriented analysis, design and programming and want to obtain an overview of the technologies that are enabling component-based development. We introduce the idea of component-based development by defining the concept and providing its economic rationale. We describe how object-oriented programming evolved into local component models, such as Java Beans and distributed object technologies, such as the Common Object Request Broker Architecture (CORBA), Java Remote Method Invocation (RMI) and the Component Object Model (COM). We then address how these technologies matured into distributed component models, in particular Enterprise Java Beans (EJB) and the CORBA Component Model (CCM). We give an assessment of the maturity of each of these technologies and sketch how they are used to build distributed architectures.
Wolfgang Emmerich, Nima Kaveh
ESEC / SIGSOFT FSE2
2001 Deadlock detection in distribution object systems
abstract
The behaviour of a distributed system is largely determined by the use of synchronization primitives and threading policies of the underlying middleware. The inherent parallel nature of distributed systems may cause liveness problems, such as deadlocks and livelocks. An increasing number of distributed systems is built using object middleware. We exploit the fact that modern object middleware offers only a few built-in synchronization and threading primitives by suggesting UML stereotypes to represent each of these primitives in distributed object design. We define the semantics of the stereotypes using a process algebra. We use that semantics to translate UML diagrams into behaviourally equivalent process algebra representations and can then use model checking techniques to find potential deadlocks. The paper also shows how the model checking results can be related back to the original UML diagrams.
Nima Kaveh, Wolfgang Emmerich
ESEC / SIGSOFT FSE1