ISE – why!!!
Today, I joined to the next subject of this semester: Information System Engineering (ISE) and here is some points after nearly 3 hours class.
First of all, the name ISE, especially E (engineering), I was thinking of what is a very heavy subject (a lot of theory and techniques and so hard to start with it). Luckily, my teacher today made it become quite easier to come up.
Information system engineering mainly refers to the Information System. It means the differences between data and information. This is the first thing you should know when start studying this subject.
In the system, data is normally considered as the raw information, just the dummy thing – hasn’t been processed and also is the system’s input. Then, data will be processed and became information after that. Information has meaning itself, in some ways.
The next thing is the Information System Development cycle (ISD cycle) with some key words: PADIS. This stands for: Planning – Analyzing – Developing – Implementing – Supporting. This is the general cycle and I think it would be covered in some next classes.
Here has one question: what is this subject used for? uhmmm!!! It can be said that ISE is used in how to build a system from the start but mainly covers in methods and techniques. I looked through the text book and they (methods and techniques) are represented in almost chapters. After coming up with those method, techniques, blah blah blah, series of ISE will be posted.
So, releasing a new product (new system), what is the most concerning thing? It’s the quality. What is the good products? How many criterias needed to be marked? They are:
- Product must fit with the requirements
- Products must be on-time (in releasing)
- Products also must be within budget
If your products meet 3 above, it can be considered as a good product. That’s it!!!
However, it’s very hard to reach to both of 3. And many many reports have showed that there are many many projects FALL, FALl, FAll, Fall, fall… WHY???
This was the most interesting part in our class today. All can be put in 2 categories: Human factors and organization factors. I’m not really interesting in business, so I cannot cover the organization factors too much and I need your help (if you could). The Human factors, ^_^ I take a summary after reading slides, listening to my teacher… and all are pointed to the communication problems such as:
- Fall because of misunderstanding requirements
- Fall because of cannot working by group
- Fall because of having many IT’s professional (from developing, planning, managing, …). This is the most funny thing I’ve heard. They’re thinking of PRO themselves that make the project falls.
