Difference between revisions of "Quantifying risks associated with programming technologies (Working Title)"

From Master Projects
Jump to: navigation, search
(New page: {{Masterproject |Master name=Software Engineering |Student name=Anne Jon Schoonhoven |Project start date=2013/02/15 |Project end date=2013/07/31 |Supervisor=Eric Bouwers |Second supervisor...)
 
(Removing all content from page)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Masterproject
 
|Master name=Software Engineering
 
|Student name=Anne Jon Schoonhoven
 
|Project start date=2013/02/15
 
|Project end date=2013/07/31
 
|Supervisor=Eric Bouwers
 
|Second supervisor=Patricia Lago
 
|Second reader=
 
|Company=Software Improvement Group
 
|Finished=No
 
|Thesis=
 
|Poster=
 
}}
 
==== Motivation ====
 
“Architectures allow or preclude nearly all of a system’s quality attributes.” -- Clements et al, 2005
 
  
But how we do we judge whether the architectural choices we have made have been the right ones, and are still the right ones?
 
 
SIG has conducted extensive research into the evaluation of implemented architecture of software systems.
 
 
We are looking for a student to design and validate a model to assess technology risks in software architectures.
 
 
Possible research questions include (but are not limited to):
 
 
* How can risks associated with a particular programming technologies be quantified?
 
* How can risks associated with combinations of programming technologies be quantified?
 
* How can these risks be incorporated into existing models for assessing architecture related risks?
 
 
Apart from building the model, you will need to validate it, for instance through a number of cases studies involving large-scale industrial software systems.
 

Latest revision as of 08:02, 5 November 2015