Saturday, December 03, 2005

Software Engineering class

Im teaching software engineering class this semester. Of course its the usual project based class, but this time i decided to follow three different software process models for my three groups.

One group will be doing the classic Waterfall model, but I made it so that they would be releasing a prototype during the semester before the final deployment. Another group would be using the spiral development pattern, with three prototype releases during the semester. Finally, the last group will be using extreme programming with prototypes every two weeks.

Since they are using different software process models, the groups will be having different documentation submissions. I still havent worked out the details yet, but before the christmas break, the waterfall group and the spiral group will be submitting a formal requirements document while the XP group will be submitting user stories with acceptance tests included.

At the end of the semester, I'll have all the groups together to discuss their experiences with the different process models.

Gosh though, one of the things i lack as a teacher is how software is developed in the "real world." It would be great if i could give a glimpse of what happens outside in my classes.


At 11:13 PM, Blogger Roy said...

I think it's an awesome idea. Sana mapost mo how well the three different models compare.

As for real world experience, what I can tell you is that in practice, the waterfall development model rarely works out the way it's described in theory. In the real world, there's always a lot of haggling and clarifications and such with users, so more often than not the waterfall stages will overlap.

At 1:43 PM, Blogger Corsarius said...

hi sir! si Phillip Kimpo Jr po ito, student ninyo sa CS12 in UPD and fellow Pisay alumni (sana naaalala nyo pa po ako) ;)

congrats po sa Level UP!! :D

At 9:17 PM, Blogger Dominique said...

Hi, Mario. As usual, I think there is a delicate balance that you have to strike. University is where students should be taught "to be" and not just "to do." So teaching the pure principles, at least the thinking behind it, also has its place. The real world is just too convoluted.

That said, maybe you can invite some IT project managers to give a talk to your class one time.

At 9:18 PM, Blogger chocolate said...

a lesson we knew but didn't learn in class was that specs change. customers are fickle.

how about during the middle of the semester, the "customer" proposes some big spec changes? Then they would have to negogiate with the customer which features to drop, etc to accomodate these changes with the remaining time.

(or is this too realistic?)

At 12:18 PM, Blogger mac.n.tux said...

mario, please try to use the JEDI Software Engineering materials so we can get feedback from you, one of the trainers. :D Thanks.


Post a Comment

<< Home