JPI UML Software Modeling
Kaydedildi:
| Yayımlandı: | International Journal of Advanced Computer Science and Applications vol. 6, no. 12 (2015), p. n/a |
|---|---|
| Yazar: | |
| Diğer Yazarlar: | , , , , |
| Baskı/Yayın Bilgisi: |
Science and Information (SAI) Organization Limited
|
| Konular: | |
| Online Erişim: | Citation/Abstract Full Text - PDF |
| Etiketler: |
Etiket eklenmemiş, İlk siz ekleyin!
|
| Özet: | Aspect-Oriented Programming AOP extends object-oriented programming OOP with aspects to modularize crosscutting behavior on classes by means of aspects to advise base code in the occurrence of join points according to pointcut rules definition. However, join points introduce dependencies between aspects and base code, a great issue to achieve an effective independent development of software modules. Join Point Interfaces JPI represent join points using interfaces between classes and aspect, thus these modules do not depend of each other. Nevertheless, since like AOP, JPI is a programming methodology; thus, for a complete aspect-oriented software development process, it is necessary to define JPI requirements and JPI modeling phases. Towards previous goal, this article proposes JPI UML class and sequence diagrams for modeling JPI software solutions. A purpose of these diagrams is to facilitate understanding the structure and behavior of JPI programs. As an application example, this article applies the JPI UML diagrams proposal on a case study and analyzes the associated JPI code to prove their hegemony. |
|---|---|
| ISSN: | 2158-107X 2156-5570 |
| DOI: | 10.14569/IJACSA.2015.061231 |
| Kaynak: | Advanced Technologies & Aerospace Database |