| 2009 |
|---|
| 57 | EE | Shuichiro Yamamoto,
Komon Ibe,
June M. Verner,
Karl Cox,
Steven J. Bleistein:
Actor Relationship Analysis for the i* Framework.
ICEIS 2009: 491-500 |
| 2008 |
|---|
| 56 | EE | Tracy Hall,
Sarah Beecham,
June M. Verner,
David Wilson:
The impact of staff turnover on software projects: the importance of understanding what makes software practitioners tick.
CPR 2008: 30-39 |
| 55 | EE | Bee Bee Chua,
Danilo Valeros Bernardo,
June M. Verner:
Criteria for Estimating Effort for Requirements Changes.
EuroSPI 2008: 36-46 |
| 54 | EE | Barry W. Boehm,
Sunita Chulani,
June M. Verner,
Bernard Wong:
Sixth workshop on software quality.
ICSE Companion 2008: 1035-1036 |
| 53 | EE | June M. Verner,
Jennifer Sampson,
Narciso Cerpa:
What factors lead to software project failure?
RCIS 2008: 71-80 |
| 52 | EE | Abdul Babar,
Karl Cox,
Vladimir Tosic,
Steven J. Bleistein,
June M. Verner:
Integrating B-SCP and MAP to manage the evolution of strategic IT requirements.
Information & Software Technology 50(7-8): 815-831 (2008) |
| 51 | EE | Javier Pereira,
Narciso Cerpa,
June M. Verner,
Mario Rivas,
J. Drew Procaccino:
What do software practitioners really think about project success: A cross-cultural comparison.
Journal of Systems and Software 81(6): 897-907 (2008) |
| 50 | EE | Mahmood Niazi,
Karl Cox,
June M. Verner:
A measurement framework for assessing the maturity of requirements engineering process.
Software Quality Journal 16(2): 213-235 (2008) |
| 2007 |
|---|
| 49 | EE | Abdul Babar,
Karl Cox,
Vladimir Tosic,
Steven J. Bleistein,
June M. Verner:
Identifying Domain Context for the Intentional Modelling Technique MAP.
DEXA Workshops 2007: 835-839 |
| 48 | EE | Narciso Cerpa,
Javier Pereira,
June M. Verner:
A Practitioner Experiment in Understanding Software Process Improvement Using Systems Modular Analysis.
EuroSPI 2007: 82-93 |
| 47 | EE | Barry W. Boehm,
Sunita Chulani,
June M. Verner,
Bernard Wong:
Fifth Workshop on Software Quality.
ICSE Companion 2007: 131-132 |
| 46 | EE | Abdul Babar,
Karl Cox,
Steven J. Bleistein,
June M. Verner:
Towards evolution of strategic IT requirements.
SAC 2007: 1220-1227 |
| 45 | EE | June M. Verner,
William M. Evanco,
Narciso Cerpa:
State of the practice: An exploratory analysis of schedule estimation and software project success prediction.
Information & Software Technology 49(2): 181-193 (2007) |
| 44 | EE | Karl Cox,
Steven J. Bleistein,
June M. Verner,
Alan M. Davis:
REBNITA'05 - 1st International Workshop on Requirements Engineering for Business Need and IT Alignment.
Journal of Systems and Software 80(3): 283-284 (2007) |
| 43 | EE | Muhammad Ali Babar,
June M. Verner,
Phong Thanh Nguyen:
Establishing and maintaining trust in software outsourcing relationships: An empirical investigation.
Journal of Systems and Software 80(9): 1438-1449 (2007) |
| 2006 |
|---|
| 42 | EE | Sunita Chulani,
Barry W. Boehm,
June M. Verner,
Bernard Wong:
Workshop description of 4th workshop on software quality (WOSQ).
ICSE 2006: 1019-1020 |
| 41 | EE | Phong Thanh Nguyen,
Muhammad Ali Babar,
June M. Verner:
Critical factors in establishing and maintaining trust in software outsourcing relationships.
ICSE 2006: 624-627 |
| 40 | EE | June M. Verner,
Karl Cox,
Steven J. Bleistein:
Predicting good requirements for in-house development projects.
ISESE 2006: 154-163 |
| 39 | | Bee Bee Chua,
June M. Verner,
Darren Dalcher:
A Framework for Predicting Person-Effort on Requirements Changes.
SoMeT 2006: 439-451 |
| 38 | EE | J. Drew Procaccino,
June M. Verner,
Steven J. Lorenzet:
Defining and contributing to software development success.
Commun. ACM 49(8): 79-83 (2006) |
| 37 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner,
Keith Phalp:
B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process.
Information & Software Technology 48(9): 846-868 (2006) |
| 36 | EE | J. Drew Procaccino,
June M. Verner:
Software project managers and project success: An exploratory study.
Journal of Systems and Software 79(11): 1541-1551 (2006) |
| 35 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner:
Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams.
Journal of Systems and Software 79(3): 362-378 (2006) |
| 34 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner,
Keith Phalp:
Requirements engineering for e-business advantage.
Requir. Eng. 11(1): 4-16 (2006) |
| 2005 |
|---|
| 33 | EE | June M. Verner,
Narciso Cerpa:
Australian Software Development: What Software Project Management Practices Lead to Success?
Australian Software Engineering Conference 2005: 70-77 |
| 32 | EE | Bernard Wong,
June M. Verner,
Sunita Chulani,
Barry W. Boehm:
Third workshop on software quality.
ICSE 2005: 688-689 |
| 31 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner:
Strategic alignment in requirements analysis for organizational IT: an integrated approach.
SAC 2005: 1300-1307 |
| 30 | | Bee Bee Chua,
June M. Verner:
IT Practitioner's Perspective on Australian Risk Management Practices and Tools for Software Development Projects: A Pilot Study.
SoMeT 2005: 111-125 |
| 29 | EE | June M. Verner,
William M. Evanco:
In-House Software Development: What Project Management Practices Lead to Success?
IEEE Software 22(1): 86-93 (2005) |
| 28 | EE | Karl Cox,
Keith Phalp,
Steven J. Bleistein,
June M. Verner:
Deriving requirements from process models via the problem frames approach.
Information & Software Technology 47(5): 319-337 (2005) |
| 27 | EE | J. Drew Procaccino,
June M. Verner,
Katherine M. Shelfer,
David Gefen:
What do software practitioners really think about project success: an exploratory study.
Journal of Systems and Software 78(2): 194-203 (2005) |
| 26 | EE | Katherine W. McCain,
June M. Verner,
Gregory W. Hislop,
William M. Evanco,
Vera J. Cole:
The use of bibliometric and knowledge elicitation techniques to map a knowledge domain: Software Engineering in the 1990s.
Scientometrics 65(1): 131-144 (2005) |
| 2004 |
|---|
| 25 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner:
Requirements Engineering for e-Business Systems: Integrating Jackson Problem Diagrams with Goal Modeling and BPM.
APSEC 2004: 410-417 |
| 24 | EE | Ming Huo,
June M. Verner,
Liming Zhu,
Muhammad Ali Babar:
Software Quality and Agile Method.
COMPSAC 2004: 520-525 |
| 23 | EE | Steven J. Bleistein,
Karl Cox,
June M. Verner:
Modeling Business Strategy in E-Business Systems Requirements Engineering.
ER (Workshops) 2004: 617-628 |
| 22 | | Rosina Weber,
William M. Evanco,
Michael Waller,
June M. Verner:
Identifying Critical Factors in Case-Based Prediction.
FLAIRS Conference 2004 |
| 21 | EE | Bernard Wong,
Sunita Chulani,
June M. Verner,
Barry W. Boehm:
Second Workshop on Software Quality.
ICSE 2004: 780-782 |
| 2003 |
|---|
| 20 | EE | William M. Evanco,
June M. Verner:
Some Architectural Features of Ada Systems Affecting Defects.
Ada-Europe 2003: 232-245 |
| 19 | EE | William M. Evanco,
June M. Verner:
Some Optimal Object-Based Architectural Features for Corrective Maintenance.
CSMR 2003: 281-280 |
| 18 | EE | Rosina Weber,
Michael Waller,
June M. Verner,
William M. Evanco:
Predicting Software Development Project Outcomes.
ICCBR 2003: 595-609 |
| 2002 |
|---|
| 17 | | Katherine M. Shelfer,
June M. Verner:
Using Competitive Intelligence to Develop an Automated Visa Approval System.
I3E 2002: 31-45 |
| 16 | | J. Drew Procaccino,
June M. Verner,
Scott P. Overmyer,
Marvin E. Darter:
Case study: factors for early prediction of software development success.
Information & Software Technology 44(1): 53-62 (2002) |
| 2001 |
|---|
| 15 | EE | June M. Verner,
Brian Henderson-Sellers:
A Pilot Study in Effort Estimation for the Generalization of Object-Oriented Components for Reuse.
Australian Software Engineering Conference 2001: 190-202 |
| 14 | EE | June M. Verner,
William M. Evanco,
Katherine W. McCain,
Gregory W. Hislop,
Vera J. Cole:
The determinants of visibility of software engineering researchers.
Journal of Systems and Software 59(1): 99-106 (2001) |
| 1999 |
|---|
| 13 | EE | June M. Verner,
Scott P. Overmyer,
Katherine W. McCain:
In the 25 years since The Mythical Man-Month what have we learned about project management?
Information & Software Technology 41(14): 1021-1026 (1999) |
| 1997 |
|---|
| 12 | EE | June M. Verner,
Narciso Cerpa:
The Effect of Department Size on Developer Attitudes to Prototyping.
ICSE 1997: 445-455 |
| 11 | | June M. Verner,
Narciso Cerpa:
Prototyping: Does Your View of its Advantages Depend on Your Job?
Journal of Systems and Software 36(1): 3-16 (1997) |
| 1996 |
|---|
| 10 | EE | Narciso Cerpa,
June M. Verner:
Prototyping: some new results.
Information & Software Technology 38(12): 743-755 (1996) |
| 9 | | Y. R. Pant,
Brian Henderson-Sellers,
June M. Verner:
Generalization of Object-Oriented Components for Reuse: Measurements of Effort and Size Change.
JOOP 9(2): 19-31, 41 (1996) |
| 1994 |
|---|
| 8 | | Y. R. Pant,
June M. Verner,
Brian Henderson-Sellers:
S/C: A Software Size/Complexity Measure.
Software Quality and Productivity 1994: 320-327 |
| 1993 |
|---|
| 7 | | P. V. Parkin,
June M. Verner,
Narciso Cerpa:
End-User Computing: A Study of Three Management Models.
Human, Organizational, and Social Dimensions of Information Systems Development 1993: 353-373 |
| 6 | | June M. Verner,
Elizabeth G. Todd:
Experiences with the Organisation and Assessment of Group Software Development Projects.
Software Engineering Education 1993: 309-315 |
| 1992 |
|---|
| 5 | | Graham Tate,
June M. Verner,
D. Ross Jeffery:
CASE: A Testbed for Modeling Measurement and Management.
Commun. ACM 35(4): 65-72 (1992) |
| 4 | EE | June M. Verner,
Graham Tate:
A Software Size Model.
IEEE Trans. Software Eng. 18(4): 265-278 (1992) |
| 1991 |
|---|
| 3 | | June M. Verner,
D. Ross Jeffery:
Software Metrics for the Management of CASE-Based Development.
Managing Information Technology's Organisational Impact 1991: 241-253 |
| 1989 |
|---|
| 2 | | June M. Verner,
Graham Tate,
B. Jackson,
R. G. Hayward:
Technology Dependence in Function Point Analysis: A Case Study and Critical Review.
ICSE 1989: 375-382 |
| 1987 |
|---|
| 1 | EE | June M. Verner,
Graham Tate:
A model for software sizing.
Journal of Systems and Software 7(2): 173-177 (1987) |
