|18:00||Get picked up by bbdb://Martin.Patacsil|
1. sony pcg-u1 battery life: 2 hours --- tech : 11:11
2. finite state automata : 11:16
3. Ryan Kristoffer Tan joins blogging community --- blog : 11:31
4. personal information : 11:34
5. strange search queries : 12:03
6. puzzles at IBM : 12:19
7. i-manila connection works fine : 12:26
8. student home directories : 14:19
9. compaq tablet tc1000 --- tech : 14:20
10. curriculum review meeting : 17:38
Issues / Plans - New Chair: Didith - Research Program goal: create more structure in our research proposal: form "research groups"
hard to actually come up with a formal research group, unlike in the US where research groups are composed of several faculty and students and they actually get grants and funding. We don't necessarily have that, but we can at least form research groups. Take a look at the LCS website. You can see that they have general topics, and then under these are particular groups. If you go to their group website, you'll see that typically the group website is divided into people, publications and projects. Directory. Different projects. It's kind of a loosely formed group, and maybe that's something we can do for now. My idea is basically, I want to be able to - well - organize our webpage and say in Ateneo we have these research groups, and list the faculty, students, theses and ongoing projects. This can be a loosely organized group. It doesn't have to be a focused group. For example, you can list all the multimedia stuff together. At least a semblance of structure. Eventually, when you have these groups, then people can talk to each other. They know what different people are working on. We're hoping that more people will be encouraged.
example: MIT's LCS - many different research groups - each group's website usually follows the format - faculty, students, projects, publications - faculty do not necessarily have to be working directly with each other - need to push students and faculty to publish - research directory?
Proposed groups - MIS and Software Engineering - paolo, john paul, bong, roland, eugene, mm, beth, ariel, sandra - Multimedia, E-Learning and Human Factors: - bea, nestor, bong, jal, didith, albert, david, luis, reena, paolo - Networks and Distributed Systems - pierre, jal, luis, gino, william, marco - Wireless, Mobile and Pervasive Computing - luis, pierre, didith, doc mana, nestor, eugene, sacha, marco - Open Source - sacha, doc mana, gino, william, marco - Computational Science and Grid Computing - john paul, luis, jon - Theory of Computation - bong, jon, john paul, beth, doc mana - Others? Now that we have the groups, maybe someone in that group can take care of collecting projects and fixing the web page
- Curriculum Review
Goals - update our curriculum - identify 'must-haves' for our curriculum - integrate into current subjects - create new subjects / recreate subjects if necessary - make sure we satisfy ACM and CHED minimum requirements - be innovative and daring!
(note: ACM publishes a curriculum for liberal arts colleges, too)
(note: we actually went beyond the ACM curriculum before when we introduced Java.)
(note: ACM 2001 - look at page 17 to 21, list of body of knowledge. Page 20, 21 - example of how you can do a curriculum. Different approaches.)
(note: wants spreadsheet form of this)
They also have recommended syllabi. Note that we don't have the textbooks yet.
- New things in ACM Curriculum 2001 - objects-first is now a "standard" option - "net-centric computing" is now a major core topic group something for us to look into because we're already doing a bit of that. We start them out with network programming already. We should also integrate net-centric thinking into all the other subjects. Doesn't just mean the CS154 course, where you talk about setting up networks, but writing programs that run on top of the network. Maybe even multimedia could benefit. - curriculum document actually gives sample syllabi for different classes and different styles - IS curriculum Previously it was just CS. Haven't looked at this one yet.
New Topics I think We _Should_ Integrate - web-centric computing - web front-end programming - web services - enterprise computing you probably have to deal with enterprise systems, and I don't know what you need in order to be able to do that. We should think about that. - distributed systems (incl. WAN systems and clustered systems) beyond what we teach in CS21B and think about that. I don't know if we need to add another class where they do distributed computing. Required class perhaps for enterprise computing? - database-backed web-based systems (incl. JDBC, .NET, etc) - B2B, B2C - Data mining, data warehousing, etc. Mentioned in MIS101. All Doc Luis's batchmates are doing Oracle data warehousing. Something to look into. - (note: this may also be relevant for e-learning) I think e-learning is still a specific thing for now. Knowledge management. Didith: Our interests are dovetailing because they mix strong capabilities in certain areas. We should work again on the core CS competencies and reinforce them. So many of our efforts have focused on our interests and bahala na yung core subjects. I think it's a good idea to go back to our core subjects. I don't quite know how to deal with the research subjects. If it's just to fill the 3 units, why don't you get something else? Unless you see yourself as practicing, it's not going to be relevant to you. They seem to cater to a very specific crowd, and I don't know. It needs to be rethought. Luis: Maybe we can think about generalizing what you learn... Instead of e-learning, think of knowledge management. Need to rethink for the undergrads. While it's nice that the classes are filled, you can see that they're only taking it for the credits... Luis: ACM, number of hours per topic. You dedicate one or two lectures on this topic and put it in some class. We might be able to put e-learning as a required topic in some other class. Didith: Even the multimedia... fine, we have the intro to multimedia class. Some people are looking for something more advanced. Computation. They want to get into compression and rendering algorithms. (Mention of Eric Vidal). There seems to be interest in more advanced multimedia topics. Niches? Development of simulations. Simulations are not necessarily for learning. It can be offered as an elective. Discussed under CAI, but lip service. Simulation can be a subject in itself. For example, scientific. Fr. Nebres. Thrust toward computational science. - mis buzzwords - crm, scm, cmm advanced topics elective in MIS - open source - including methodologies and tools such as CVS, etc. CS161, CS23 - maybe some things on methodology - wireless? to what extent do we integrate it into our curriculum? - quality assurance suggested by Ariel - any others?
doesn't have to be a separate subject. Could just be a quick lecture.
Bong: One person should do an industry scan. Luis: We need to involve alumni. Self-survey. We haven't been involving alumni directly into our curriculum reviews for the past few times. I think maybe one person or a small group of people can be in charge of doing the industry scan, and everyone else is welcome to contribute. Point person for that. We'll assign tasks later.
Didith: Suggestion. Consult with our mentors and advisors from the different schools so that we can get their perspective. Didith will do it. Pierre also, from his position.
Some ideas - CS21B design patterns RMI and/or servlets J2ME? - CS122 JDBC discuss clustering introduce data mining, data warehousing, etc. Feedback: we should discuss performance and ways to improve it, like clustering and stuff. Ariel: Nagging problem. Time constraint. This sem we weren't able to discuss JDBC because of time constraints. Nagging problem, explored in the last curriculum review. Solution proposed, two semesters? JPV: clarifying curriculum review direction. need a process for making key decisions. Luis: Topics *:* course - CS161? suggestion for CS, CS161+CS23 -> CS162a&b Luis: Was talking to William. Kind of a mess this year. I think we should split the MIS and the CS again. Ariel: Ayoko na! - CS112: Programming Languages* XML, Perl, LaTeX, Python, make your own language, etc. LISP! New course. Structure of programming languages. Intent: Compiler theory. Part of automata. JPV: Sequencing is important. Problem of irreconcilable groups. Luis: Try to map out what we have right now by the hour. Doc Luis flunked the programming part of the MIT diagnostic thing because it was in Scheme. - CS123 Design patterns Web services Enterprise systems - These are just a few random ideas
The Plan - everyone please browse through ACM curricula in order to be "inspired" - divide into groups - review existing subjects - include alumni - suggest change - iterate - have 1 or 2 "big meetings" where everyone can see the emerging "big picture"
DocMana: Maybe not the CS students, but maybe the MIS students might be interested in learning Visual Basic. I think we should have a pool of Visual Basic programmers we can draw from.
Luis: I would rather do a .NET thing.
DocMana: Isn't .NET that Microsoft thing?
Everyone: So is VB.
Luis: We need to reconsider the math requirements. The ACM team, that was one of their weak points. Our sophomores are flunking their math. Luis: Can we do a calculus for computer scientists? Mike: They do that in ECCE. There's a math for engineers. They're teaching it Doc Mana: We can teach calculus like Math 20. Luis: Abstract algebra? Statistics is also very useful. Doc Mana: The kind of calculus they teach in the BM program. Doc V: Points. Very controversial. Turf issue. You don't want it to evolve into everyone teaching their own math. Second, core curriculum constraints with math. Some discussions. Core curriculum for science programs? It's not fully within our control. Output should be these are the type of things we think we need. Doc Mana: Think they will require Ma101? Doc V: Think students are a problem. Doc Mana: Why should it be a problem now, when it wasn't with you and Didith? Doc V: Has been a problem ever since. Usual concern - top 10% of those who applied in math. They may not be enough for the Math department. Doc Luis: Big group failing Ma22. Doc V: Lower target group. We have a whopping 7 out of 70 confirmees with two weeks to go.
Bong: Optional fourth hour. Pierre: Tutorials. Optional. Doc V: Tools course. Virginia Tech. 1 unit. Luis: Sa MIT, ganoon din. Luis: Warning about regular basis and peer pressure. Didith: Seminars. DocV: Keep hour free. Luis: CS hour. Luis: Monday, 4:30 - 6? Parallel sessions? Eugene: Org-assisted? Use activity hour? Luis: In fact, it should be org-assisted. Bong: We give the structure, they implement it. DocV: We can sustain it. Maybe we'll even give allowances. We can make that evolve. Increase our student assistant fund. Luis: Parallel sessions. Bong: CompSAT and MISA.
Luis: Course outlines and hours per topic. Suggest changes. Don't try to solve it yet. We need to be able to get feedback from the alumni. Very crucial. Need to know what's out there. Generate a wishlist of what you want to add. Everyone needs to see what the demand is. Ideally, I would like to raise the bar on our students as well. Try to push them. Reviewing our subjects...
JPV: Milestones and deliverables so that it's a little clearer. Schedules also.
Luis: Are the electives really worth that much time? Luis: Existing syllabus and wishlist. JPV: Wishlist of topics and hours.
Before BM1 Per subject: (Including Math, Physics and Electives) Review existing syllabi course outline and hours per topic wishlist / recommendations wish list of topics (with hours) Rough recommendations fit wish list within current course or put in a new course or existing course survey alumni (when possible) Notes includes looking at ACM 2001, CHED and "Hot Topics" look at requirements and recommendations Where does ACM 2001 put them? Industry scan Generate wish list Deliverable by 1 week before Big Meeting #1
Big Meeting #1 When? Last weekend of April (26-27) Where? Hotel in Manila? What do we do? Present deliverables Inclde outside faculty and alumni Output Rough curricula - coarse grouping of topics CS, MIS, Grad Clustering of electives Suggest minors? Agenda for BM #2 In charge of organizing: Didith - Ortigas Center
New: Albert, Edwin, Jon, Sacha, Stanley (part-time)
(Note: Marivi is leaving on April 1st to study. Grace will replace her. Has been working for the Registrar's office for 2 years.)
math: possibly calculus for computer scientists, abstract algebra, linear algebra and stuff...
Tasks and Grouping
|- CS112||Doc Mana|
After Big Meeting #1, the issue would be fitting in the actual courses already? Making the detailed outline of the courses. Farm out syllabi to generate Output: new syllabi per course (in Loyola Schools format) Includes plan for exams/lab/projects/assignments and grading scheme.
Big Meeting #2: When? Last Saturday of May (31) Where? Ateneo What do we do? Present Deliverables Output Validated curriculum Todo list
Need to propose items for the agenda.
I'd love to hear about any questions, comments, suggestions or links that you might have. Your comments will not be posted on this website immediately, but will be e-mailed to me first. You can use this form to get in touch with me, or e-mail me at firstname.lastname@example.org .