- HEC application approved!! This was quick...thank God...now I can get started on the interviews in Jan when offices reopen.
- Need to start on THE PROPOSAL
- Heard from HEC ppl...minor changes recommended. Made all suggested changes and emailed revised documents back. Will have to wait till uni re-opens for the response.
- NZSCRSC'08: Went through 4 draft versions with Stuart and James, finally submitted it on 21st Dec (deadline)
- Getting travel plans sorted - this is NOT EASY !
- Need to submit 6 monthly report - filled and passed on to supervisors
- StuArt reviewed initial draft of NZSCRSC paper...working on suggested changes and finishing remaining sections. Its running over 4 pages...will need to cut it down later.
- Got some good leads from the BarCamp...few companies interested to help with research - thank God! Might conduct pilot study here in NZ...incorporate initial results into proposal and give seminar in March.
- Attended BarCamp Agile - writing up a report on it
- NZCSRSC'08 Paper Deadline extended to 21st Dec...Yaaay!!
- Bar Camp Agile Friday, 7th Dec 8:30-5pm: Prepared information sheet
- Preparing paper to submit for NZCSRSC (New Zealand Computer Science Research Student Conference)
- Need to apply for travel grant
- Planning to start on Proposal writing sometime soon...
- Waiting on HEC application
- Submitted HEC application. May take from 3 to 6 weeks.
- Attended SIENZ conference in Auckland 26-27th November. It was very cool to hear about the various different projects people are working on and some new software eng courses that have been introduced in universities across NZ.
- New and interesting courses that were presented include our very own SWEN102: Introduction to Software Modelling and ENGR101, and a 300 level SE course at Lincoln Uni etc
- Projects I found particularly interesting were PeerWise from the University of Auckland(application which allows question banks to be created and maintained by students of a course)
- 'Website Inaccessibility' by Ben Bradshaw and StuArt and 'An Open Source approach to developing for development' were particularly good in terms of relating software to social issues.
- Preparing for my HEC application
- Agile Project Management or APM. Sounds cool
- Seems like its gonna be XP for me - might sneak in AOP in the code if I get a chance
- Emailed Angela...got some really good pointers...thanks!
- (early Oct) This is leaving me more tense than the first time around - trying to decide on a topic that is both interesting and doable
- Never thought this would happen to me...but looks like I might need to revise my topic (apparently this is more common than I thought)
- Not enough stuff available on AOP or design
- Nearly zilch available on AOP + XP (besides a solitary paper named 'XP + AOP = Better Software?')
- Met with James after a long break
- Time for some serious introspection
- printed the final version of the survey and labeled the submission box.
- StuArt to distribute them to the participants - Hope to get enough response
- made a survey for the Agile week participants. Aimed at getting useful information about XP project experience.
- got John Hine's approval for the survey
- working on designing a small prototype, a stand-alone tool for XP project management (will focus on a few elements only for now). The idea is to use AOP to separate the cross-cutting concerns at the design phase...and possibly use AOP in development as well.
- read more case studies and the italy paper about tracking and managing XP projects in the IDE.
- found few tools which focus on XP planning game and project management. Thankfully most are Open source and hence free.
- I thought I was done with my share of the flu...but not really...this is the real thing
- The case studies on XP are good examples (found from Springer) In particular one case study titled 'Adapting Extreme Programming to Research, Development, and Production Environments' by Gil Broza was useful. It highlighted the various practices of XP which the company (Affinium Pharmaceuticals) found useful and others which they struggled to define/apply.
- Another interesting article was "Demystifying Extreme Programming: "XP distilled" revisited, Part 1" by Roy Miller. This one attempts to clarify and summarize what XP is and what it isn't. First he displays statistics to show the alarming rate of project failures. Then he points out the various reasons behind these dismal stats. He then offers the use of Agile methods as one solution. He then goes on to explain the 19 XP practices (original 12 plus few.) The focus of the article is on creating 'one team' which uses common practices (programmers, customers, and management.) The new practices introduced include Open workspace, Iterations ("write code, let people use it, and let their feedback steer the project"), and Retrospectives (looking back and reflecting on actions to avoid repeating failures.)
- Issued some books from the library on XP (practices, hands-on approach)
- Stuart found the Springer link...its pretty good actually...there are loads of useful and relevant articles on XP.
- This diary thing can get out of hand if forgotten to update regularly...now I have to r'ber what I was upto...other than struggling with the nasty flu sweeping across my family...hmm...
- Looking at tools that support the software development process ('process tools')
- Exploring the role of aspects in agile technologies like XP or AUP (Agile Unified Process). There are two different approaches.
- Approach A: Treat each work-flow as an aspect (in AUP) or try to model XP using aspects and development tools that use aspects.
- Approach B: Use aspects (AO design, programming, tools) to manage XP. Example: Weave in aspects as spike code. Might start playing with this one first.
- Looking at Project Management Tools
- Use of agile technologies in project management - didn't find much material relating to this.
- exploring cross cutting concerns in project management that can give way to aspects
- Reviewing the Unified Process, the Rational Unified Process (RUP), and the Agile Unified Process. Reference: Wikipedia
- Exploring the use of aspects to manage workflows in the Agile Unified Process. The 7 Workflows are Model, Implement, Test, Deployment, Configuration Management, Project Management, and Environment.
- Use of aspects in project management tools.
- System development and process configuration tools using aspects.
- Setting up an SVN (SubVersion) repository and creating projects with SVN. Some good sources of reference on the topic can be found here: SubVersion and COMP205 page
- Using the eclipse plugin for SubVersion called subclipse (works similar to CVS on eclipse)
- Checking out the IEEE and Springer for interesting articles (through the vuw library link)
- And ofcourse, creating and maintaining a diary or progress report here on elvis.
I officially started on my PhD thesis in Feb 2006. Read several relevant articles (literature review) on the subject. Found many articles on both AOP and XP but very few that combined the two together. The bulk of the AOP articles seem to be focused on the requirements gathering and designing phases. Others talked about developing new tools for AOP. I went on my maternity leave in August 2006 and have now returned to my thesis (2007).