Designing Job Descriptions for Software Development

  • Jack Downey


This chapter presents an approach to creating job descriptions for roles within software development project teams. An artifact-centric skill framework has been created, which suggests a way that companies can create meaningful job descriptions based on the artifacts persons work on and the people they cooperates with. This chapter will describe the framework, before presenting real-world example job descriptions and their equivalent artifact-centric variants.


Project Manager Project Plan Engineering Requirement Work Breakdown Structure Window Form 


  1. Belbin, R. M. (2000). Beyond the Team. Oxford, Elsevier Butterworth-Heinemann.Google Scholar
  2. Casteleyn, M. (1996).Job Descriptions for the Information Profession. London, Aslib, The Association for Information Management.Google Scholar
  3. Cluts, M. M. (2003). The Evolution of Artifacts in Cooperative Work: Constructing Meaning Through Activity. ACM SIGGROUP 2003, Florida, USA, ACM Press 144–152.Google Scholar
  4. DeMarco, T. and T. Lister (1999). Peopleware: Productive Projects and Teams, Dorset HouseGoogle Scholar
  5. Downey, J. (2005). A Framework to Elicit the Skills Needed for Software Development. 2005 ACM SIGMIS CPR Conference, Atlanta, Georgia, ACM Press 14–16 April, 2005 122–127.CrossRefGoogle Scholar
  6. Downey, J. (2006). Systems Architect and Systems Analyst: Are These Comparable Roles? 2006 ACM SIGMIS CPR Conference, Claremont, California, ACM Press 13–15 April, 2006 213–220.Google Scholar
  7. Downey, J. and N. Power (2007). An Artifact-centric Framework for Software Development Skills. ACM SIGMIS CPR, St. Louis, Missouri, ACM Press 19–20 April, 2007 186–195.CrossRefGoogle Scholar
  8. Enterprise Strategy Group (2004). Ahead of the Curve: Ireland's Place in the Global Economy. Dublin, Forfas.Google Scholar
  9. Fernandez-Araoz, C. (1999). "Hiring without Firing." Harvard Business Review 77(4): 109–120.Google Scholar
  10. Ford, G. and N. E. Gibbs (1996). A Mature Profession of Software Engineering, Carnegie Mellon University: 1–94.Google Scholar
  11. Forfas (2003). Responding to Ireland's Skills Needs, The Fourth Report of the Expert Group on Future Skills Needs. Dublin, Forfas: 24–33, 86–94.Google Scholar
  12. Hackman, J. R. and G. R. Oldham (1980). Work Redesign. Reading Massachusetts, Adison-Wesley.Google Scholar
  13. Irish Computer Society (2006). Irish Computer Society Website. 28 June 2006:
  14. Litecky, C. R., K. P. Arnett and B. Prabhakar (2004). "The Paradox of Soft Skills versus Technical Skills in IS Hiring." Journal of Computer Information Systems 45(1): 69–76.Google Scholar
  15. Mambrey, P. and M. Robinson (1997). Understanding the Role of Documents in a Hierarchical Flow of Work. ACM SIGGROUP 1997, Phoenix, Arizona, ACM Press 119–127.Google Scholar
  16. McConnell, S. (1993). Code Complete. Redmond, Washington, Microsoft Press.Google Scholar
  17. Morisio, M., I. Stamelos and A. Tsoukias (2002). A New Method to Evaluate Software Artifacts Against Predefined Profiles. ACM SIGSSEKE, Ischia, Italy, ACM Press 811–818.Google Scholar
  18. Office for National Statistics (2000).Standard Occupational Classification—Volume 2. London, The Publishing House.Google Scholar
  19. SFIA Foundation (2006). Skills Framework for an Information Age. 28 June 2006:
  20. Shapero, A. (1985). Managing Professional People: Understanding Creative Performance. New York, The Free Press.Google Scholar
  21. Shaw, M. (2000). Software Engineering Education: A Roadmap. 22nd International Conference on Software Engineering, Limerick, Ireland, ACM Press 373–380.Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2009

Authors and Affiliations

  • Jack Downey

There are no affiliations available

Personalised recommendations