Why Consider Implementation-Level Decisions in Software Architectures?
(Nikunj R. Mehta, Nenad Medvidovic, Marija Mikic-Rakic) • Nikunj R. Mehta, Nenad Medvidovic, Marija Mikic-Rakic, “Why Consider Implementation-Level Decisions in Software Architectures?” submitted to 4th International Workshop on Software Architectures, Limerick, Ireland, June 2000 (pdf) Software architecture provides a high-level abstraction of the structure, behavior, and properties of a software system aimed at enabling early analysis of the system and its easier implementation. Often, however, important details about a system are left to be addressed in its implementation, resulting in differences between conceptual and concrete architectures. This paper describes an approach towards bringing these two closer by making certain implementation-level decisions explicit in the architecture. Specifically, we focus on the choices made in modeling and implementing component interactions. The process is based on a taxonomy of software connectors that the authors have developed to better und
Related Questions
- What kind of consolidation decisions and work will the software do automatically or will the eprentise team do for us? What will we have to do?
- How has legislation mandating scientifically based research affected district software purchasing decisions?
- What software methodology and group mechanics decisions worked out well, and which ones didn ?
