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.
? Tutorial for this page

Hossein Tajalli

dblp:70/8310 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 2014
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 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.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%
Theoretical computer science
1 paper
Automated reasoning and model checking · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture › self-adaptive systems
architecture-based adaptation
0.112010
PLASMA: a plan-based layered architecture for software model-driven adaptation · ASE 2010
Requirements engineering and software design › software architecture › architecture description
architecture description language
0.112010
PLASMA: a plan-based layered architecture for software model-driven adaptation · ASE 2010
Requirements engineering and software design
software architecture
0.112010
PLASMA: a plan-based layered architecture for software model-driven adaptation · ASE 2010
Automated reasoning and model checking
model checking
0.012010
PLASMA: a plan-based layered architecture for software model-driven adaptation · ASE 2010

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

planning as model checking · 0.2
YearPublicationVenuePosition
2014 iDARE - a reference architecture for integrated software environments
abstract
SUMMARY Traditionally, software development environments have tended to treat a system's development‐time activities separately from its run‐time. After a system is in operation, it frequently needs to be maintained and evolved. In traditional environments, this results in frequent relocations of a system between the disjoint development and run‐time environments, which is undesirable for several reasons. A more effective solution is to couple the development and run‐time environments to directly monitor and adapt running systems. Given the growing need for interaction between development‐time and run‐time aspects of modern software systems, it is important to understand development and run‐time environments, and their relationship. To this end, we study and classify a wide range of software development environments on the basis of their level of interaction with the corresponding run‐time environments. Particularly, we identify, study, and characterize Self‐Adaptive Life‐cycle Environments (SALEs), an emerging class of modern development environments that are tightly integrated with run‐time environments. We reify our study of the development environments into a novel reference architecture, iDARE, that captures and differentiates the architectures of software environments – from those, such as traditional development environments, that have no interaction with the run‐time environments, to the ones, such as SALEs, that are tightly integrated with the run‐time environments. We use iDARE to highlight several shortcomings of existing SALEs. Adherence to iDARE has the potential to improve certain quality properties of the integrated development and run‐time environments, such as adaptability, fault‐tolerance, robustness, availability, and resource consumption. We identify a number of opportunities for future research. Copyright © 2013 John Wiley & Sons, Ltd.
Hossein Tajalli, Nenad Medvidovic
Softw. Pract. Exp.1
2010 PLASMA: a plan-based layered architecture for software model-driven adaptation
abstract
Modern software-intensive systems are expected to adapt, often while the system is executing, to changing requirements, failures, and new operational contexts. This paper describes an approach to dynamic system adaptation that utilizes plan-based and architecture-based mechanisms. Our approach utilizes an architecture description language (ADL) and a planning-as-model-checking technology to enable dynamic replanning. The ability to automatically generate adaptation plans based solely on ADL models and an application problem description simplifies the specification and use of adaptation mechanisms for system architects. The approach uses a three-layer architecture that, while similar to previous work, provides several significant improvements. We apply our approach within the context of a mobile robotics case study.
Hossein Tajalli, Joshua Garcia, George Edwards, Nenad Medvidovic
ASE1
2010 An architecture-driven software mobility framework
Sam Malek, George Edwards, Yuriy Brun, Hossein Tajalli, Joshua Garcia, Ivo Krka, Nenad Medvidovic, Marija Mikic-Rakic, Gaurav S. Sukhatme
J. Syst. Softw.4