| dc.contributor.author | Hatebur, Denis | |
| dc.contributor.author | Heisel, Maritta | |
| dc.contributor.editor | Münch, Jürgen | |
| dc.contributor.editor | Liggesmeyer, Peter | |
| dc.date.accessioned | 2019-02-20T10:13:01Z | |
| dc.date.available | 2019-02-20T10:13:01Z | |
| dc.date.issued | 2009 | |
| dc.identifier.isbn | 978-3-88579-244-4 | |
| dc.identifier.issn | 1617-5468 | |
| dc.identifier.uri | http://dl.gi.de/handle/20.500.12116/20395 | |
| dc.description.abstract | We show how software architectures (including interface descriptions) can be derived from artifacts set up in the analysis phase of the software lifecycle. The analysis phase consists of six steps, where various models are constructed. Especially, the software development problem is decomposed into simple subproblems. The models set up in the analysis phase form the basis for (i) defining software architectures related to single subproblems, (ii) merging the subproblem architectures to obtain the overall software architecture, and (iii) to define the interfaces between the components of the overall architecture. The approach is based on problem patterns (problem frames) and the architectural style of layered software architectures. | en |
| dc.language.iso | en | |
| dc.publisher | Gesellschaft für Informatik e.V. | |
| dc.relation.ispartof | Software Engineering 2009 - Workshopband | |
| dc.relation.ispartofseries | Lecture Notes in Informatics (LNI) - Proceedings, Volume P-150 | |
| dc.title | Deriving software architectures from problem descriptions | en |
| dc.type | Text/Conference Paper | |
| dc.pubPlace | Bonn | |
| mci.reference.pages | 383-392 | |
| mci.conference.sessiontitle | Regular Research Papers | |
| mci.conference.location | Kaiserslautern | |
| mci.conference.date | 02.-06. März 2009 | |