4.9(top 5%)
impact factor
763(top 20%)
papers
34.6K(top 10%)
citations
91(top 5%)
h-index
5.0(top 5%)
impact factor
1.0K
all documents
37.8K
doc citations
160(top 5%)
g-index
Top Articles
# | Title | Journal | Year | Citations |
---|---|---|---|---|
1 | Two case studies of open source software development | ACM Transactions on Software Engineering and Methodology | 2002 | 1,249 |
2 | Developing multiagent systems | ACM Transactions on Software Engineering and Methodology | 2003 | 944 |
3 | A formal basis for architectural connection | ACM Transactions on Software Engineering and Methodology | 1997 | 912 |
4 | Alloy | ACM Transactions on Software Engineering and Methodology | 2002 | 835 |
5 | The STATEMATE semantics of statecharts | ACM Transactions on Software Engineering and Methodology | 1996 | 778 |
6 | Discovering models of software processes from event-based data | ACM Transactions on Software Engineering and Methodology | 1998 | 716 |
7 | A safe, efficient regression test selection technique | ACM Transactions on Software Engineering and Methodology | 1997 | 570 |
8 | A methodology for controlling the size of a test suite | ACM Transactions on Software Engineering and Methodology | 1993 | 539 |
9 | Four dark corners of requirements engineering | ACM Transactions on Software Engineering and Methodology | 1997 | 528 |
10 | An experimental determination of sufficient mutant operators | ACM Transactions on Software Engineering and Methodology | 1996 | 507 |
11 | Automated consistency checking of requirements specifications | ACM Transactions on Software Engineering and Methodology | 1996 | 448 |
12 | The design and implementation of hierarchical software systems with reusable components | ACM Transactions on Software Engineering and Methodology | 1992 | 429 |
13 | Protecting privacy using the decentralized label model | ACM Transactions on Software Engineering and Methodology | 2000 | 396 |
14 | Model driven security | ACM Transactions on Software Engineering and Methodology | 2006 | 392 |
15 | Specification matching of software components | ACM Transactions on Software Engineering and Methodology | 1997 | 387 |
16 | A model for spectra-based software diagnosis | ACM Transactions on Software Engineering and Methodology | 2011 | 377 |
17 | Runtime Verification for LTL and TLTL | ACM Transactions on Software Engineering and Methodology | 2011 | 365 |
18 | Parameterized object sensitivity for points-to analysis for Java | ACM Transactions on Software Engineering and Methodology | 2005 | 345 |
19 | Investigations of the software testing coupling effect | ACM Transactions on Software Engineering and Methodology | 1992 | 275 |
20 | Recovering traceability links in software artifact management systems using information retrieval methods | ACM Transactions on Software Engineering and Methodology | 2007 | 269 |
21 | The chaining approach for software test data generation | ACM Transactions on Software Engineering and Methodology | 1996 | 265 |
22 | The ASTOOT approach to testing object-oriented programs | ACM Transactions on Software Engineering and Methodology | 1994 | 259 |
23 | An empirical study of regression test selection techniques | ACM Transactions on Software Engineering and Methodology | 2001 | 253 |
24 | A theoretical analysis of the risk evaluation formulas for spectrum-based fault localization | ACM Transactions on Software Engineering and Methodology | 2013 | 253 |
25 | Modeling software architectures in the Unified Modeling Language | ACM Transactions on Software Engineering and Methodology | 2002 | 249 |
26 | Law-governed interaction | ACM Transactions on Software Engineering and Methodology | 2000 | 232 |
27 | Signature matching | ACM Transactions on Software Engineering and Methodology | 1995 | 226 |
28 | Reducing the effort of bug report triage | ACM Transactions on Software Engineering and Methodology | 2011 | 226 |
29 | UML-B | ACM Transactions on Software Engineering and Methodology | 2006 | 219 |
30 | A meta-environment for generating programming environments | ACM Transactions on Software Engineering and Methodology | 1993 | 215 |
31 | Software process validation | ACM Transactions on Software Engineering and Methodology | 1999 | 208 |
32 | Some Code Smells Have a Significant but Small Effect on Faults | ACM Transactions on Software Engineering and Methodology | 2014 | 208 |
33 | LIME | ACM Transactions on Software Engineering and Methodology | 2006 | 206 |
34 | Views | ACM Transactions on Software Engineering and Methodology | 2013 | 202 |
35 | Mixin layers | ACM Transactions on Software Engineering and Methodology | 2002 | 197 |
36 | Many-Objective Software Remodularization Using NSGA-III | ACM Transactions on Software Engineering and Methodology | 2015 | 197 |
37 | Designing data marts for data warehouses | ACM Transactions on Software Engineering and Methodology | 2001 | 196 |
38 | Formalizing style to understand descriptions of software architecture | ACM Transactions on Software Engineering and Methodology | 1995 | 192 |
39 | Programming pervasive and mobile computing applications | ACM Transactions on Software Engineering and Methodology | 2009 | 180 |
40 | Toward an engineering discipline for grammarware | ACM Transactions on Software Engineering and Methodology | 2005 | 177 |
41 | A revisit of fault class hierarchies in general boolean specifications | ACM Transactions on Software Engineering and Methodology | 2011 | 167 |
42 | From business process models to process-oriented software systems | ACM Transactions on Software Engineering and Methodology | 2009 | 164 |
43 | Conjunction as composition | ACM Transactions on Software Engineering and Methodology | 1993 | 160 |
44 | A Large-Scale Evaluation of Automated Unit Test Generation Using EvoSuite | ACM Transactions on Software Engineering and Methodology | 2014 | 157 |
45 | Symbolic model checking of UML activity diagrams | ACM Transactions on Software Engineering and Methodology | 2006 | 156 |
46 | An Empirical Study on Learning Bug-Fixing Patches in the Wild via Neural Machine Translation | ACM Transactions on Software Engineering and Methodology | 2019 | 151 |
47 | Power laws in software | ACM Transactions on Software Engineering and Methodology | 2008 | 149 |
48 | Reasoning about inconsistencies in natural language requirements | ACM Transactions on Software Engineering and Methodology | 2005 | 146 |
49 | Representing concerns in source code | ACM Transactions on Software Engineering and Methodology | 2007 | 143 |
50 | Automated assistance for program restructuring | ACM Transactions on Software Engineering and Methodology | 1993 | 142 |