2011
DOI: 10.1016/j.infsof.2010.11.006
|View full text |Cite
|
Sign up to set email alerts
|

Pattern-based framework for modularized software development and evolution robustness

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
6
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
3
1
1

Relationship

0
5

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 18 publications
0
6
0
Order By: Relevance
“…The IC1, IC2, EC4, EC5, and EC6 criteria were applied. Finally, after applying the three rounds and the IC and EC, 36 primary studies were obtained (see Table 3 ). The data extraction and synthesis processes for the 36 primary studies were conducted by using a form in which each study was identified with ID [13–15, 18, 22–53 ] and classified according to its context, validation, terminology, and usefulness in answering each research question.…”
Section: Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…The IC1, IC2, EC4, EC5, and EC6 criteria were applied. Finally, after applying the three rounds and the IC and EC, 36 primary studies were obtained (see Table 3 ). The data extraction and synthesis processes for the 36 primary studies were conducted by using a form in which each study was identified with ID [13–15, 18, 22–53 ] and classified according to its context, validation, terminology, and usefulness in answering each research question.…”
Section: Methodsmentioning
confidence: 99%
“…Considering this premise, some papers in the SLR present technology implementations or report lessons learned, but without any validity study. On the other hand, eight research works [18, 22, 25, 29–31, 47 ] are considered to have a high level of rigor and relevance, because these papers are applied to large‐sized applications.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…Framework also includes a set of abstract and concrete classes that work together and contains their interface definitions of instances. These classes are constructed as reusable components for a domain . The goal of patterns creates a common interface to help software developers resolve recurring problems encountered throughout all aspects of software development.…”
Section: Design Principles Of Pattern Based Multi‐dgas Educational Frmentioning
confidence: 99%
“…Modularity—ability for plug in or to be integrated with other sub‐systems. Distribution—enabling deployment to the internet .…”
Section: Design Principles Of Pattern Based Multi‐dgas Educational Frmentioning
confidence: 99%