ACM Transactions on Computer Systems (TOCS)
Communications of the ACM
On internal and external characterizations of PT-net building block behavior
Advances in Petri Nets 1988
Modern structured analysis
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Using style to understand descriptions of software architecture
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
A Syntactic Theory of Software Architecture
IEEE Transactions on Software Engineering - Special issue on software architecture
Correct Architecture Refinement
IEEE Transactions on Software Engineering - Special issue on software architecture
IEEE Transactions on Software Engineering - Special issue on software architecture
Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Dynamic structure in software architectures
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Formal Models for Computer Security
ACM Computing Surveys (CSUR)
Petri Net Theory and the Modeling of Systems
Petri Net Theory and the Modeling of Systems
Fundamentals of Algebraic Specification I
Fundamentals of Algebraic Specification I
The 4+1 View Model of Architecture
IEEE Software
An Event-Based Architecture Definition Language
IEEE Transactions on Software Engineering
A Formal Definition of Hierarchical Predicate Transition Nets
Proceedings of the 17th International Conference on Application and Theory of Petri Nets
A Client-Server Protocol for the Composition of Petri Nets
Proceedings of the 14th International Conference on Application and Theory of Petri Nets
Architecture-based specification-time software evolution
Architecture-based specification-time software evolution
Using Software Architecture for Code Testing
IEEE Transactions on Software Engineering
Responsibilities and Rewards: Specifying Design Patterns
Proceedings of the 26th International Conference on Software Engineering
Improving Performance of Virtual Reality Applications Through Parallel Processing
The Journal of Supercomputing
Automatic Inclusion of Middleware Performance Attributes into Architectural UML Software Models
IEEE Transactions on Software Engineering
The Journal of Supercomputing
Hi-index | 0.00 |
Concurrent and distributed software applications are complex software systems that exploit highly parallel and distributed infrastructure to improve the quality of systems in cost-effective way. In order to assist the development of affordable concurrent and distributed software systems, a more effective approach of utilizing single-based architectural description languages (ADLs) is needed. In this paper, we describe an architectural modeling framework that can be used for specifying and analyzing distributed and concurrent software applications. Our key contribution is an architectural specification framework that integrates four important concepts: (1) an architectural description language known as syntactic theory (ST), (2) a high level Petri nets modeling language known as Hierarchical Predicate Transition Nets (HPrTNs), (3) a Pattern-Based Refinement Technique (PBRT), and (4) a systematic process for deriving architectural specifications from requirement specifications. Moreover, the method is heterogeneous modeling approach that specifies software architecture of a distributed and concurrent system in a top-down manner. The immediate benefits of our heterogeneous approach include: increased system analyzability, comprehensibility, reusability, and flexibility. We describe a case study to show the applicability of our approach.