Showing posts with label Programming Language. Show all posts
Showing posts with label Programming Language. Show all posts

Friday, January 16, 2009

Much More Web Pages in the World

It is my first article featured with image. This image inspired by Coding Horror, taken from Pearls Before Swin. Just laugh a while...

Pearls Before Swine

Actually Atwood, Coding Horror writer use this image to say about saying clever and being clever. But I interested in "They are all on the web". Then one question flying around my brain. How many web pages in the world?
    When I ask Answer.com how many sites in the world, they answer about 70,392,567 websites indexed by Yahoo. And in July 25th 2008, Google process links on the web to find new content hit a milestone, 1 trillion unique URL's on the web at once. What a big number, isn't it. With those number of sites, so more web pages exist in this world. There are 250,000 new pages a day. One datum again, Wikipedia, the open source project with 'open source' article that born in January 2001, has 2,683,000+ articles, just in English.
Hmm...

Friday, December 19, 2008

Informatics Level

My friend ever asks me, which one that he should improve his skill, programming or networking. Suddenly I say, "Both of them are low level fields in informatics area."

Whoa, where did I get that answer?
Exactly I do not know where it came from, it just rise in my brain and I just speak it up without more thinking. But I have some arguments for that. I can say that we can divide some informatics fields into their level based on the nearby relation, to machine (computer) or to people (user and another stakeholders).

If we refer to ACM, they already defined 5 sub disciplines of computing and its level based on which they teach, Hardware Architecture, System Infrastructure, Software Methods, Application Technology or Organization/Information System. Those sub disciplines are:
  1. Computer Engineering
  2. Computer Science
  3. Software Engineering
  4. Information System
  5. Information Technology

But in my college, Informatics Study Program (in the old structure) has 7 fields that represented by 7 Laboratories of Expertise. If I try to classify them into their level, there are the results:
  1. Low Level Fields
  2. In this level, we study basic this information age knowledge, from how to write code in a good/right manner, how the code works, what inside this 'black box' (CPU) and things that flowing inside this wire and this air. It consists of:
      • Fundamental Programming
      • Computer Science
      • Distributed System

  1. Mid Level Fields
  2. In here, we study the higher level of computer science applications. And most of these applications need high peripherals specification in order to work properly. If in Low Level, we study how to make a good program in each code line, in Mid Level we must consider to make a good program in a whole system. This level includes:
      • Software Engineering
      • Database System
      • Graphic & Artificial Intelligent

  1. High Level Fields
  2. In this level, we discuss about informatics in business purpose. Even more we don't feel the existence of computer science here. After 6 fields in previous level, there is remain 1 field that has been separated from my study program. But I still say it as an informatics field because we still study information knowledge here. The field is:
      • Information System


However it is not always like that. I can say for example, there is a high level applicative computer science section, but most of computer science section is low level section. So, because I learn programming course that supported by Programming Laboratory and networking course that supported by Distributed System Laboratory, I say programming and networking are low level fields in informatics, isn't it.

Saturday, October 25, 2008

Analysis Diagram vs Design Diagram

What is the difference between the diagram in Analysis Phase with the diagram in the Design Phase?
In Software Engineering, essentially Analysis closer to the Requirement and Design closer to Implementation.
Thus, the consequences:
  • When do the analysis, first, do not think too various possibility, just spill to the analysis of all the requirement, especially when we make Class Analysis. Then when we design, refine them, which classes that need to be combined or separated, which the Boundary/Entity Class that need Controller Class.
  • The other clear difference is the message in the Sequence Diagram in Analysis Phase still form the clause, but in the Diagram Phase is a message function/attribute that represents the language (web using underscore, which Java with Camel)
So, to refine this Class Analysis Diagram, all of team member should gather again to collect their class and stare with that big Complete Class Analysis to make any change and adaptation each other.

Well, it seems only.OK
--
don't forget them!