Handling variant requirements in domain modeling
暂无分享,去创建一个
[1] P. Bassctt. Framing software reuse - lessons from real world , 1997 .
[2] Ivar Jacobson,et al. Unified Modeling Language , 2020, Definitions.
[3] Will Tracz,et al. DSSA (Domain-Specific Software Architecture): pedagogical example , 1995, SOEN.
[4] David Lorge Parnas,et al. On the Design and Development of Program Families , 2001, IEEE Transactions on Software Engineering.
[5] Ivar Jacobson,et al. Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).
[6] Kyo Chul Kang,et al. Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .
[7] Ivar Jacobson,et al. The unified modeling language reference manual , 2010 .
[8] Jaejoon Lee,et al. FORM: A feature-;oriented reuse method with domain-;specific reference architectures , 1998, Ann. Softw. Eng..
[9] Desmond D'Souza,et al. Objects, Components, and Frameworks with UML: The Catalysis Approach , 1998 .
[10] Shailey Minocha,et al. Supporting Scenario-Based Requirements Engineering , 1998, IEEE Trans. Software Eng..
[11] Pamela Zave,et al. Feature interactions and formal specifications in telecommunications , 1993, Computer.
[12] Krzysztof Czarnecki,et al. Generative programming - methods, tools and applications , 2000 .
[13] Stan Jarzabek,et al. Modelling Variant User Requirements in Domain Engineering for Reuse , 1998, EJC.
[14] Gregor Kiczales,et al. Aspect-oriented programming , 2001, ESEC/FSE-9.