Tuesday, July 21, 2009

State of Computer Science Reseach


Last 2005, Mr. Wm. A. Wulf, president of the National Academy of Engineering, and the AT&T Professor of Engineering and Applied Science in the Department of Computer Science at University of Virginia was invited in the House of Science to deliver some points about the current state of Computer science research.

There he delivered four points of interest, the first of which is he took it out from the Science the Endless Frontier, the report that established our system of federal funding of basic research, Vannever Bush advocated a system in which the government funds research, but the research to be done is selected on its merit by the researchers themselves. He said that such a system would pay dividends to the nation in national security, prosperity, and health. It is hard to think of a better “poster child” for the truth of this assertion than Computer Science. Consider the abbreviated list:

• National Security: smart bombs, GPS, unprecedented “information awareness” for the war-fighter, unmanned robotic vehicles for surveillance, enormously enhanced training through use of virtual reality, etc
• Prosperity: a 3% national productivity growth fueled by information technology, dozens of multi-billion dollar per year industries (see Figure 1), internet-enabled business models, a 40-fold reduction in the cost of telephony, a global wireless phone system, etc.
• Health: Medical imagery (CAT scans, etc), cochlear implants, bio-sensors, smart prosthetics, smart defibrillating pacemakers, etc.

All of these were made possible by the federal investment in long-term, basic computing research. Like Mr.Wulf, I believe that it is a mistake to think of such funding as an “expense” and it must be regarded as an investment that demonstrably has had a huge return! Technology such as that listed above is the return on the investments made a decade or more ago. Investments made today in research will have equally large returns for our children and grandchildren; conversely, it is our children and grandchildren that will pay if we do not make them now.

Second, computing and computer science is in the unusual position of being both a challenging intellectual discipline in itself, and providing an infrastructure for other fields of science, engineering, and commerce. While the benefits to society listed above can be directly attributed to computer science, there are also many more benefits that have resulted from the use of computing in everything from cosmology, to weather prediction, and to health care. Across this broad spectrum, computer science has enabled a better quality of life for us all. This simply reinforces the notion that funds expended on computing research are demonstrably investment, not expense. They are, in fact, an investment with an enormous multiplier because advances in computing and information technology have immediate, direct and tangible benefits on virtually all human activities.

Thirdly, the idea that basic research begets applied research begets development begets benefits to society is both wrong and counter-productive when applied to public policy decisions. Instead, there is a marvelously rich and productive interplay between basic scientific discovery and application, between universities and industry, between societal need and technology. The bottom line, however, is that if federally-funded, university-based basic research weren’t “in the loop”, these enormously beneficial technologies would not exist. Basic research may not be the original source for all the benefits we enjoy from technology, but it is a vital and irreplaceable component of the rich system that produces them.

Lastly, computer science research is for and about the people. If computing research has a large multiplier because of its broad application, then the people capable of doing that research are yet another multiplier on top of that! Disinvestment in university-based research is a disinvestment in the production of the next generation of people, with far greater negative impact than simply the loss of the research.

In these points raised by Mr. Wulf we can see that at those times the funding for computer science research was being talked over by the government, specifically the US government. As a summary, the government is still arguing whether continued funding for such researches would be beneficial for both government and people. And as Mr. Wulf pointed out, with the proper research support and funding to universities and colleges across the country or even across the globe is beneficial to all, maybe not today but certainly for tomorrow.

Mr. Wulf also stressed the importance of cybersecurity. At that time, PITAC strongly identified the need for a better funded and stable program of long term basic research. The dominant model of cybersecurity, namely a perimeter defense, is flawed and incremental patches to it will never result in the level of security we need for today’s systems, much less the increased dependence we should expect for future ones. This is an excellent example where boldness and courage are needed, and hence where the perception of excessively low proposal success rates can have severe consequences. He emphasized that the future of researches is greatly affected by the resources available, in the mean point, funding is a great issue. New ideas are needed, just as in cybersecurity research, but instead of temerity, conservatism was imposed. Decline in the success rates of proposals indeed has a significant negative impact, however, we must have the courage to explore things and open for discoveries and innovations. One of the highlights of his words is that the thought of research funding is not merely an expense but instead it is an investment.

But on my research today, the government funding to computer science research now leads to the new trend of studying Green Computing. Go to IT related company webpages, search in the Internet or simply read IT magazines and you can see that the trend is going “green. Computers were and are still aiding people for more comfortable life but we can’t deny the fact that at some point the environment is compromised with these advances. Today, consumers are looking for products with good quality but eco friendly and energy efficient which lead to more research about this topic. Computer science researches are going for greener data centers, monitors, hardware and even researches for green softwares. Also, researches for creating products that might lessen the negative effects of computer radiation is also on going. Computers release electromagnetic field radiation.

This EMF is actually a type of radiation. It isn’t the same type as uranium or plutonium; rather, it is a non-ionizing radiation. This means that the emitted radiation is not strong enough to remove electrons, or ionize the atoms. Instead, it just excites the electrons. It already sounds a little Different devices emit different types and amounts of this EMF radiation. But then past and ongoing researches are trying to prove that these is still harmful since it can also premature cell division. The cells actually divide before the DNA is correctly established, which may possibly lead to mutation or can also bring cancer especially for those who have been in contact with computers in a long time (referring to years).

In past, computer science research tends to focus more on using and improving technology. Making it more flexible for implementation of different purposes, beneficial in different areas such as security, defense, healthcare or medicine, and education but nowadays it leans more on ways to make it more eco friendly but not comprising the quality and services it was built to do.

These are the Technical Topics in which Computer Science Researches are now focused:

<1.>
2. Commerce
3. Electronic Teaching
4. Information Retrieval, Databases, and Data Mining
5. Machine Learning
6. Networking, Distributed Systems, and Security
7. Robotics, Computer Vision, and Graphics
8. Software Systems and Architecture
9. Green Computing

Published Research Papers


THE SOCIAL STRUCTURE OF FREE AND OPEN SOURCE SOFTWARE DEVELOPMENT
Kevin Crowston and James Howison
School of Information Studies, Syracuse University
{crowston,jhowison}@syr.edu


Summary

What do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects?

These are the questions this paper responds to. Questioning the assumption of distinctiveness is important because practitioner-advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production.

To address these questions, this study examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. It was found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users.

And therefore, it was suggested that it is wrong to assume that FLOSS projects are distinguished by a particular social structure merely because they are FLOSS. Our findings suggest that FLOSS projects might have to work hard to achieve the expected development advantages which have been assumed to flow from “going open.” In addition, the variation in communications structure across projects means that communications centralization is useful for comparisons between FLOSS teams. The social structure of Free and Open Source software development 2 found that larger FLOSS teams tend to have more decentralized communication patterns, a finding that suggests interesting avenues for further research examining, for example, the relationship between communications structure and code modularity.

Evaluation

The topic being raised is really interesting (since I can relate to it better than the other researches I found). At its conclusion it really did prove the points raised but the downside for me in this study is its methodology. Though indeed the results are gathered with evidence or supporting data this paper mostly is done by researching topics directly and indirectly related to it. The methodology only consists of gathering data and queueing them up and no other strategies were done (as I see it). As Kate quoted it, "The paper was more of a historical type of research rather than a technical research because they did not perform any experimentation and relied majorly on their literature."

With regards to the format, there were only two major parts: related literature and conclusion. The other parts of a “standard” paper were indeed missing and thus it can e understood that the conclusion and recommendation was drawn from the literature review.

However, I think this research still is effective since it provided sufficient data/ literature to support the study.


----------------------------------------------------
OPEN SOURCE SOFTWARE: THE USE OF OPEN SOURCE GIS STANDARD AND ITS IMPACT ON ORGANIZATION
by: Mahmoud Refaat Nasr


Summary

This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI’s ArcIMS, Intergraph’s GeoMedia WebMap, and MapInfo’s MapXtreme. The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.


Evaluation

All I can say is that this is a very good research paper. Maybe its because I'm still inexperienced in judging the research work but I can't find I fault or major ones anyway in this paper. Upon reading this paper, you can see how detailed the framework is, how in depth the research has gone and the structure of the paper is complete and done nicely. Researching histories and related topics were complete with regards to the points the researcher raised in his objectives and also survey done in terms of testing the hypothesis of the study was also shown and detailed in the paper.

Though the survey done was fine as a suggestion, it would be better if he added observation and interview of organizations who were already using open source GIS standards as to support his survey findings. Format wise its done throughly and
But overall, its a pretty much detailed and good research paper.


-------------------------------------------
COORDINATION OF FREE/LIBRE OPEN SOURCE SOFTWARE DEVELOPMENT
Kevin Crowston, Kangning Wei, Qing Li,
U. Yeliz Eseryel, and James Howison


Summary

The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, they used the coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. The researchers examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. The researchers found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, it found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, The researchers found that “self-assignment” was the most common mechanism across three FLOSS projects.

This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.

Evaluation

Honestly, reading these research papers was easy but understanding them is a hard so most of the time I just skim through a whole section and judge it by its format and methodology. As I have observed, the drawbacks of the paper is just like the first paper I commented on. Though indeed the results are gathered with evidence or supporting data this paper mostly is done by researching topics directly and indirectly related to it. The methodology only consists of gathering data and queueing them up and no other strategies were done (as I see it). As Kate quoted it, "The paper was more of a historical type of research rather than a technical research because they did not perform any experimentation and relied majorly on their literature."

With regards to the format, there were only two major parts: related literature and conclusion. The other parts of a “standard” paper were indeed missing and thus it can e understood that the conclusion and recommendation was drawn from the literature review.

As a suggestion, using other data collection techniques to combine with the data or literature collected would be better.

Monday, July 6, 2009

Comddap Davao 2009



"Where the highest mountain in the land rises over the vast rich plains of Davao, where the king of Philippine birds soar over his domain, the giant of all Philippine I.T. shows once more unfolds its latest event. It’s COMDDAP Davao 2009 – the biggest I.T. expo held regularly in the South."

Last July 2, 2009 we attended the Comddap Davao 2009. This is a product exhibit of the Computer Manufacturers, Distributors and Dealers Association of the Philippines.

Admittedly, it is geeky. LOL. But fun and informative at the same time. My friends and I signed up for the seminar to be given in the afternoon but fortunately we arrived there a little earlier and that's why we had a little time on our hands to make rounds on the exhibit area.

As I remember it, companies such as AOC, NEXUS, HEWLETT PACKARD PHILS. CORP., Canon, Dell, EPSON, MSI-ECS PHILIPPINES. INC., WORDTEXT SYSTEMS, INC., SMART, Gigabyte, Envision and other IT related companies where there to show their products on separate booths and stalls.

I was trying to get an idea for my research topic by looking at the products and I have seen a lot of Green IT related products such as a green computing based motherboards (from Gigabyte), laptops (mostly by Dell) and LCD monitors by AoC.

Later in the afternoon we joined in the seminar held by Mr. Celmer Santos of Jupiter System Inc, Nexus group. He introduced us to Jupiter Systems and focused more their Dealer Management System. If you want to outsource software developments especially those which focus more on car dealership and management you can visit to their site: http://www.jupitersystems.com.ph/

Jupiter Systems has a lot of services such as procurement, manufacturing, order management and dealership management system. And the one the Mr. Santos focused more on his talk is their dealership management system. A lot of well known companies such as Volvo, Mazda, Honda, Ford, Mercedes Benz, Toyota and other big car brands purchased their services. The general features of their dealership management systems are the following:
• Monitor Sales Executive Activities,
• Sales lead monitoring from initial inquiry to actual close
• Sales quotation processing
• support sales of new and used vehicles
• vehicle reservation and deposit collection
• vehicle inventory
• customer incident and resolution recording
• interface to manufacturer systems
• reports and queries
• highly graphical technician assignment and loading window
• customer appointment
• repair order and estimates
• customer/vehicle service history
• technician time in and time-out
• parts requisitioning and picking
• control parts and consumables cost

After Mr. Santos, Mr, Leonard Zapa from HP Invent took thestage and introduced us to HP's new product: thin client. It was a really informative topic and a very handy product. By the first three slides he already convinced me to buy the product (but I can't since I don't have dough haha). Thin clients are small and protable CPU like device but with lower memory since it doesn't have a hard drive. It has an IDE flash with a memory of 1-2GB which may seem as a disadvantage but it actually is very beneficial especially to task based users.

Thin clients are computing devices that function as an access device on a network. These solid-state devices connect over a network to a server where the bulk of the processing takes place. Thin clients have no hard drive, allowing for more secure storage of data and applications on the server. Thin clients offer the highest data security, lower total cost of ownership, increased energy efficiency, easier manageability and high reliability with a small chance of downtime to occur in the system or even none at all.

With no hard drive, fan or other moving parts, thin clients have a much longer lifespan than standard computers and use significantly less power. Lower maintenance costs are another benefit as software application updates, virus scanning and patches can be executed on the server. Thin clients offer significant savings in power usage over traditional desktops. This is realized not only in energy costs but reduced air-conditioning costs in some cases. With their long lifecycle thin clients allow companies to achieve energy savings targets and reduce the need for replacement equipment. Deployment costs are also reduced as thin clients can be remotely configured and do not need to be set up individually. Break-fix simply requires replacing the thin client.

In a Thin Client environment you can upgrade users quickly and inexpensively by updating application software hosted on servers, not clients. Not only do you have a more controlled and secure environment, but technical support costs are greatly reduced. These are long-lasting products with no moving parts, to not only reduce noise levels, but also lower maintenance costs. There’s even optional wireless connectivity support on select models.

Total Cost of Ownership*
• 80% less maintenance per year
• 25% capital cost savings
• 34% less in maintenance
• 23% less to operate
• 25% productivity increase

Other advantages of thin clients are:
• Control software, applications and files centrally
• Save up to 80% on maintenance costs
• Deploy out-the-box in under 10 minutes
• Support your legacy mainframe
• Effortlessly manage enterprise IT
• Use fewer support personnel
• Manage remotely with simple problem diagnosis
• Reduce hardware theft

The talk with Mr. Zapa was really fun and all of us were listening closely so that e could answer the questions he will give at the end of his speech. I was called to answer and the question was relatively simple but bad enough it’s not my lucky day and I just blurted out an answer with fully reading all the choices. Maybe and with the highest probability I answered wrong because of excitement. Going back to that experience my head just churns because I should have won a t-shirt from HP and a 2 gigabyte USB if I answered it correctly. What a shame. I became really interested in the product so I will feature it in my upcoming posts.

Going back to the COMDDAP, it was a very geeky but entertaining and time worthy event. It felt like being a small kid again locked up in a room full of candies and toys.


Photo credits to Ms.Kate Mariel Dizon


Motherboard from Gigabyte

LCD Monitors from AOC

Me advertising AOC *tehee*


From left to right (cham2x, dolor, angel,kate, Me (looking sleepy) and Karren)