• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 JonKernPA commented Permalink

I find the vision lacking in coherence. In 25 words or less, can you describe the purpose of SEMAT? <div>&nbsp;</div> I also think that it might be helpful to look at the economics of software and the history of engineering discipline. <div>&nbsp;</div> If we could better expose the costs of software and the resulting "product" in ways that others can understand, I am confident the free market will choose the winners and the losers better than any august body of software experts. <div>&nbsp;</div> Tying the "universal elements" or "kernel" via a set of metrics will work if those metrics express the same sort of value (e.g., money) that the funding people care about. <div>&nbsp;</div> If SEMAT results help make it easy for folks to know if they are getting the right bang for their software development buck, that would be a worthwhile outcome. Unlike many other "services," software remains elusive for stakeholders to know if their team is 10 times less effective than they could be. It is also hard to measure if they are producing the right thing -- no too much, and not too little. And what about it's ability to grow over time? When should we consider growing it or starting anew given improved business understanding, maybe new tools, new processes, new teams? <div>&nbsp;</div> In software, there is rarely one right process or solution path. Therefore, I posit that the best thing we can do for the industry is better expose the costs/benefits and let the chips fall where they may.

2 ScottAmbler commented Permalink

How about this for a potential purpose: <br /> "To define and evolve a proven foundation which provides a contextual and empirical basis for software engineering practitioners and researchers."

Add a Comment Add a Comment