The Impact of Architectural Design Decisions on Non-Functional Properties of Software Systems

OOP 2010

Autoren: Nenad Medvidovic

Explicit treatment of software architecture allows engineers to codify non-functional properties (NFPs) early on and maintain their traceability throughout a system’s lifespan.

Explicit treatment of software architecture allows engineers to codify non-functional properties (NFPs) early on and maintain their traceability throughout a system’s lifespan. In this talk I will provide a set of guidelines one can follow in pursuing several common NFPs: efficiency, complexity, scalability, adaptability, and dependability. I will provide a definition of each NFP, discuss its impact on a software systems architecture, and outline the role of architectural elements and styles in satisfying the NFP. Whenever appropriate, I will illustrate the discussion with concrete examples from existing architectures.


Target Audience: Architects, software developers
Prerequisites: a background in software development, familiarity with software architecture and UML 2.0
Level: Intermediate

zur Anmeldung/wissen/registrierung.html?redirect_url=%2Fwissen%2Fsuche-login%2Fkonferenzbeitraege.html%3Ftx_mwknowledgebase_pi2%255BshowUid%255D%3D278

zurück


Newsletter abonnieren



Empfehlung an diese E-Mail-Adresse senden:


 

 

 

Ihre eigenen Angaben:

 

 

 

 

Diese Seite empfehlen Sie weiter: