MIS Quarterly - Special issue on IS curricula and pedagogy
Understanding the role of documents in a hierarchical flow of work
GROUP '97 Proceedings of the international ACM SIGGROUP conference on Supporting group work: the integration challenge
Requisite IS management knowledge and skills construct: a survey
ACM SIGCPR Computer Personnel
Coporate IT skill needs: a case study of BigCo.
ACM SIGCPR Computer Personnel
The Rational Unified Process: an introduction
The Rational Unified Process: an introduction
A new method to evaluate software artifacts against predefined profiles
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Software Engineering Explained
Software Engineering Explained
The evolution of artifacts in cooperative work: constructing meaning through activity
GROUP '03 Proceedings of the 2003 international ACM SIGGROUP conference on Supporting group work
A framework to elicit the skills needed for software development
Proceedings of the 2005 ACM SIGMIS CPR conference on Computer personnel research
Systems architect and systems analyst: are these comparable roles?
Proceedings of the 2006 ACM SIGMIS CPR conference on computer personnel research: Forty four years of computer personnel research: achievements, challenges & the future
An artifact-centric method for creating software job descriptions
Proceedings of the 2008 ACM SIGMIS CPR conference on Computer personnel doctoral consortium and research
On identifying the skills needed for software architects
Proceedings of the first international workshop on Leadership and management in software architecture
| Hi-index | 0.00 |
While the specific knowledge, skills and abilities needed to develop software can be determined, it is much more difficult to decide what skill set is required for any given software development role. This paper suggests that progress may be made if, instead of trying to relate knowledge, skills or abilities to individual roles, efforts are made to understand what knowledge, skills and abilities are required to create and use the artifacts associated with software development. To this end, a framework incorporating two relationships is presented: The first relates software development artifacts to organizational functions, while the second relates knowledge, skills and abilities to different phases of an artifact's lifecycle. This framework leads to a new taxonomy of skills.