{"title":"Modeling behavioral patterns of concurrent software architectures using Petri nets","authors":"IV RobertG.Pettit, H. Gomaa","doi":"10.1109/WICSA.2004.1310690","DOIUrl":"https://doi.org/10.1109/WICSA.2004.1310690","url":null,"abstract":"To address behavioral modeling issues specific to concurrent software architectures, this paper outlines an approach for systematically modeling behavioral patterns found in concurrent software designs by applying colored Petri net (CPN) templates with UML artifacts. In this approach, CPNs are used as an underlying representation of the dynamic object-oriented architecture. These CPNs are then used to provide a simulated functional flow of the architecture and to analyze the concurrent behavior. By applying the results from the CPN analysis to the original UML model, an engineer can enhance the quality of the design and thereby gain additional insight to the behavioral properties of the software design prior to implementation.","PeriodicalId":262908,"journal":{"name":"Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122779391","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
M. Ionita, P. America, D. Hammer, J. Obbink, J. Trienekens
{"title":"A scenario-driven approach for value, risk, and cost analysis in system architecting for innovation","authors":"M. Ionita, P. America, D. Hammer, J. Obbink, J. Trienekens","doi":"10.1109/WICSA.2004.1310709","DOIUrl":"https://doi.org/10.1109/WICSA.2004.1310709","url":null,"abstract":"We present a quantitative method for scenario-driven value, risk, and cost analysis when proposing new system architectures for innovation projects. The method helps to articulate the relative benefits and/or disadvantages of the proposed set of scenarios in the early architecting phases of a new system. It provides the arguments on which to base an informed decision to select the final architectural scenarios for further consideration in the design. In this paper we present a case study in which we applied the proposed method.","PeriodicalId":262908,"journal":{"name":"Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122207626","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Resolving requirement conflicts through non-functional decomposition","authors":"E. Poort, P. D. With","doi":"10.1109/WICSA.2004.1310698","DOIUrl":"https://doi.org/10.1109/WICSA.2004.1310698","url":null,"abstract":"A lack of insight into the relationship between (non) functional requirements and architectural solutions often leads to problems in real life projects. This paper presents a model that concentrates on the mapping of nonfunctional requirements onto functional requirements for architecture design. We build a framework that both provides a model and a repeatable method to transform conflicting requirements into a system decomposition. This paper presents the framework, and discusses two cases onto which the method is applied. In one case, the method is successfully used to reconstruct the high-level structure of a system from its requirements. The second case is one in which the method was actually used to create a system design fitting the stakeholders' needs, and that is reproducible from its requirements.","PeriodicalId":262908,"journal":{"name":"Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131788673","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"ASAAM: aspectual software architecture analysis method","authors":"B. Tekinerdogan","doi":"10.1109/WICSA.2004.1310685","DOIUrl":"https://doi.org/10.1109/WICSA.2004.1310685","url":null,"abstract":"Software architecture analysis methods aim to predict the quality of a system before it has been developed. In general, the quality of the architecture is validated by analyzing the impact of predefined scenarios on architectural components. Hereby, it is implicitly assumed that an appropriate refactoring of the architecture design can help in coping with critical scenarios and mending the architecture. This paper shows that there are also concerns at the architecture design level which inherently crosscut multiple architectural components, which cannot be localized in one architectural component and which, as such, can not be easily managed by using conventional abstraction mechanisms. We propose the aspectual software architecture analysis method (ASAAM) to explicitly identify and specify these architectural aspects and make them transparent early in the software development life cycle. ASAAM introduces a set of heuristic rules that help to derive architectural aspects and the corresponding tangled architectural components from scenarios. The approach is illustrated for architectural aspect identification in the architecture design of a window management system.","PeriodicalId":262908,"journal":{"name":"Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004)","volume":"202 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-03-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116175837","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}