Name
Abstract | ||
|---|---|---|
Design of an enterprise information system significantly impacts its development and maintenance efforts. The research shows that maintenance consumes about 65--75% of the software development time and about 40--60% of maintenance efforts are devoted to software understanding [2, 9]. This paper compares the Aspect-driven design approach as applied to the three-layered architecture to the MVC-like design approach implemented by many conventional web frameworks. While both approaches strive to avoid information restatement, they differ greatly in the underlying idea; thus, this work compares based on development efficacy and ease of maintenance. We highlight their differences and qualities, such as information cohesion, coupling and restatement, and discuss their maintenance efforts. We also investigate their ease of use, deployments, and provide recommendations on when to use each approach. |
Year | DOI | Venue |
|---|---|---|
2015 | 10.1145/2811411.2811477 | RACS |
Field | DocType | Citations |
Enterprise architecture,Aspect-oriented programming,Model–view–controller,Computer science,Usability,Knowledge management,Real-time computing,Risk analysis (engineering),Enterprise information system,Software,Enterprise life cycle,Software development | Conference | 1 |
PageRank | References | Authors |
0.36 | 2 | 4 |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Karel Cemus | 1 | 21 | 4.58 |
| Tomás Cerný | 2 | 73 | 23.16 |
| Lubos Matl | 3 | 1 | 0.70 |
| Michael J. Donahoo | 4 | 137 | 52.31 |