Information systems researchers determine successful software programming aids

Mar 18, 2014
Professor Radha Mahapatra and Associate Professor Sridhar Nerur, both in the Information Systems and Operations Management Department of the College of Business, recently published "Distributed Cognition in Software Design: An Experimental Investigation of the Role of Design Patterns and Collaboration" in the prestigious MIS Quarterly. Credit: UT Arlington

The success of having software programmers work in pairs greatly depends on the ability level of those individual programmers, two UT Arlington College of Business professors have written in a recently released paper.

The paper also concluded that using design patterns can greatly improve the quality of software programs and the productivity of programmers.

Professor Radha Mahapatra and Associate Professor Sridhar Nerur, both in the Information Systems and Operations Management Department of the College of Business, recently published "Distributed Cognition in Software Design: An Experimental Investigation of the Role of Design Patterns and Collaboration" in the prestigious MIS Quarterly.

MIS Quarterly is the premier academic journal in the discipline.

Rachel Croson, UT Arlington College of Business dean, said that MIS Quarterly is an elite publication, which speaks to the quality and importance of this work.

"This research draws from insights and techniques in organizational behavior and applies them to programming," Croson said. "Their results suggest how firms could greatly speed up software programming without sacrificing quality."

In recent times, paired development has gained considerable traction among software developers. However, Mahapatra and Nerur conclusions on using paired development were mixed.

"We concluded that programmers working in pairs helps the software design process many times," Mahapatra said. "However, for the very top echelon of programmers, working alone yields the best results."

Mahapatra and Nerur co-authored the paper with George Mangalaraj, a UT Arlington doctoral graduate and currently an associate professor of Information Systems at Western Illinois University, and Ken Price, a professor emeritus in the UT Arlington College of Business Management Department.

The other major conclusion of the paper was that relying on the use of design patterns improves positive outcomes in software design. Design patterns help software developers create superior quality software at less time.

"Software design is a very labor and knowledge intensive endeavor. About two out of three new projects are deemed unsuccessful, according to an industry report," Nerur said. "What we've demonstrated through a controlled experiment is that relying on design patterns can help programmers be more successful."

The researchers said many companies are constantly seeking ways to improve productivity and quality. They said companies who can save a small percentage of time and personnel expense in avoiding bad code early in the process could yield big results down the road.

Explore further: Marketing study shows ethnically diverse workforce may improve customer experience

add to favorites email to friend print save as pdf

Related Stories

Recommended for you

Facebook sues law firms, claims fraud

9 hours ago

Facebook is suing several law firms that represented a man who claimed he owned half of the social network and was entitled to billions of dollars from the company and its CEO Mark Zuckerberg.

IBM 3Q disappoints as it sheds 'empty calories'

9 hours ago

IBM disappointed investors Monday, reporting weak revenue growth again and a big charge to shed its costly chipmaking division as the tech giant tries to steer its business toward cloud computing and social-mobile ...

User comments : 1

Adjust slider to filter visible comments by rank

Display comments: newest first

antialias_physorg
not rated yet Mar 18, 2014
"We concluded that programmers working in pairs helps the software design process many times," Mahapatra said. "However, for the very top echelon of programmers, working alone yields the best results."

Interesting. That mirrors my experience very well. Also the conclusion about using design patterns - though I have found that if you overdo it in a group there is a point where it can again become a hindrance.
Refactoring to take into account all chosen design patterns tends to lengthen at some point if not every one is equally familiar with all patterns. Also some patterns aren't entirely distinct from others, so it tends to come down to decisions of style and personal preference - which can lead to frission in a team if the patterns are too strictly enforced.