[TOS] TOS in the SWEBOK and with various scholarly societies?
hislopg at drexel.edu
Thu Sep 3 15:38:48 UTC 2009
A bunch of comments:
a) if you want to provide examples that will be useful to instructors, you might want to organize them around the SE 2004 curriculum recommendation rather than SWEBOK. People working on BSSE programs will look at both sources, but SE 2004 is more easily mapped to a degree. SE 2004 is available on the ACM curriculum recommendations page http://www.acm.org/education/curricula-recommendations.
b) You could also consider organizing around a graduate level SE curriculum recommendation that is currently under construction. See http://asysti.org/issechome.aspx There is a discussion underway for this to become a sponsored curriculum recommendation by the ACM and IEEE/CS (along with INCOSE). (All things considered I'd vote for using the undergrad model though.)
c) The notion of creating a TOS curriculum recommendation and having ACM adopt it may not be the way to go. Under the current policy (which you cite at http://www.acm.org/education/education/curric_vols/curr_proposals ) the notion has been that a "curriculum recommendation" maps to a degree program. More narrowly focused recommendations have not been put in any of these recognition categories. (As it happens, I'm coordinating an effort to re-write this policy and coordinate it between ACM and IEEE-CS, but I'm not hearing any interest in changing this aspect of what gets recognized.)
d) I like the idea of a repository of examples and the notion of organizing the examples using a curriculum recommendation or SWEBOK. There are several options that could be used to make such a repository available (and visible). One option would be to use SWENET (www.swenet.org), a collection of SE teaching materials that I happen to curate. I'd be happy to help people put examples there (it's already set up using the SE 2004 organization of topics). It would also be possible to create a collection of examples under the TOS umbrella. Either way (SWENET or TOS), I'd suggest making the collection visible through the Ensemble project (http://www.computingportal.org). Ensemble is project under the NSF NSDL program (was "National Science Digital Library" now "National STEM Education Distributed Learning") that is constructing a portal to provide access to instructional materials for all branches of computing education. I'm involved in Ensemble too, so I'd be happy to facilitate making a collection part of Ensemble, which would increase visibility.
From: tos-bounces at teachingopensource.org [mailto:tos-bounces at teachingopensource.org] On Behalf Of Mel Chua
Sent: Wednesday, September 02, 2009 1:16 AM
Subject: [TOS] TOS in the SWEBOK and with various scholarly societies?
While reading through some "CS Curriculum Standards!" papers from Harish
and Sankarshan tonight
www.asysti.org/Data/Sites/1/iSSEcImages/CSEET_Paper_final.pdf) I found
out that the SWEBOK's going to get a 2010 refresh.
http://www2.computer.org/portal/web/swebok/volunteering --> "Become a
Reviewer: This October, the 2010 SWEBOK will be open for public review.
Sign up now to be on the e-mail list for notification."
They're breaking it into chapters, you have to pick a chapter to review,
and I signed up for "process," leaving this note:
"What I'm most interested in is how open source fits into the 2010
SWEBOK. An idea: what if we built a repository of examples of each item
in the SWEBOK so that readers can see examples of each point in action,
and the tie to software engineering practice is clear?"
Now, I realize that SWEBOK is also controversial. Cem Kaner has a
critique here: http://www.satisfice.com/kaner/?p=7 and the ACM pulled
out (the SWEBOK is an IEEE thing) because the ACM didn't think there
should be a software engineering certification (yet), but IEEE went
ahead and did it anyway
(http://www2.computer.org/portal/web/certification). ACM's rationale:
http://www.cs.washington.edu/homes/notkin/bok_assessment.pdf And SWEBOK
isn't meant as a "here's what you should learn in undergrad" list; it
excludes non-computing things that are important for software engineers
to learn (say, documentation) and includes things beyond the scope of an
undergraduate program (for instance, management). This is my
understanding, at least; please holler if I've gotten something wrong.
So perhaps making that offer / building that repository of examples for
http://www.acm.org/education/curricula-recommendations and/or other
recommendations from other places, or as a neutral upstream for these
kinds of projects, would be more appropriate. In general, I am thinking
of this as one way to engage TOS with scholarly societies. For instance,
what would it take for the ACM to sponsor a curriculum recommendation
with TOS on open source development?
Question: So as to not create More Work To Do, is there anything we are
Doing Anyway that could fit nicely into this with very, very little
extra effort? Is this a potential point of leverage?
tos mailing list
tos at teachingopensource.org
More information about the tos