If I would my relate my objectives in life to a SDLC (System Development Life Cycle), I would choose it to weigh more on the adaptive side and weigh lesser on the predictive side. Why? Its simple. In the real world there are many factors that could affect your objectives in life and also your SDLC. There are this factors that are not in the plans and that budge into your life. Citing an example is a "failed subject", we did not plan to have one. Right?. In fact we never thought we would have one. We set our goal on our diploma not thinking of the events that could occur in between the day you set foot on this university and the day of our graduation rites. In short if we compare it to a SDLC, we have to adopt on the situation that comes day by day. Therefore for me it is better to be on the adoptive side that the predictive side because we should be honest to ourselves that we cannot predict everything.
Moving on. Lets say that my objective is to graduate. I am just referring to my medium term objective here because my long term objective is to be successful in life. We are not aware of the phases that we came through but we the truth is we already finished a phase such as planning. Therefore my own model of a SDLC is planning-learning-building-trial-implementation.
Planning
If we assume that our objective is to attain a diploma, planning is the part on where should we attain it and what kind of diploma should we attain. We planned to take exams on several schools and consider several courses. If you are like me, I planned to take exam only and only in USeP and enlist myself as a Bachelor of Science in Computer Science student. That is what I planned. A plan must be final and certain because coming back at this phase only means you have to start all over again and you dont want that to happen. We may not be aware but we have already finished this phase because we are here now as what we have planned.
Learning
This is the phase where we learn and gather information to attain our goal. We do this subject by subject. This is the phase where we absorb knowledge in the field of IT. So ask we can see, we are still in the learning phase.
Building
What I am trying to emphasize in the word building is building of one self as a future IT professional . After the learning phase it is up to an individual on how he builds himself as an IT proffesional. He can choose whether to discard some of his learnings ang take what he thinks can be useful for him.
Trial
This is the phase where we put ourselves in trials such as quizzes, exam and projects. This is where we test if what we build ourselves on is enough. This is also the most crucial part because in this phase we see if we should go back to building, learning or much worse back to planning. If we pass this trial therefore we go back again to learning but this time with another subject and so the cycle continious until we have nothing to try anymore so we proceed to the implementation phase.
Implementaion
This is the phase where we are suppose to be holding our hard earned diplomas and join the real world of IT. This is the phase where we take a step into a larger objective. This is the phase where we attained our goal.
Where is adoptive there? What is adoptive there is we should break a large picture into smaller pieces. We should be able to adopt in those smaller pieces before jumping into another piece. We should also learn to adopt if we have absorbed a failing grade. We should be able to adopt whatever comes. For example you have a certain problem that you have not predicted, it is more advantages if you could learn to adopt with that problem.
Time and Date
Monday, December 22, 2008
Assignment 1
Humble to say our chosen system is simple but if we think of the time left for our group to accomplish a part of that system, I think it is justifiable. We also considered our limitations and our skills in coding and analysis. I honestly think that if given a short time and with my skills as a Computer Science student, I could not accomplish the given task. It's right to say that our team is just playing it safe but thinking of our skills and knowledge, I think it is only fair. I know my team as well as I should know them. Some of the members of the team are my group mates every time we have a project to be done therefore I know their weaknesses and their strengths. As a group we aimed for a system that is attainable to us and a system that we could handle as a group.
What our professor said is right. I don't have anything against what he said. It was a call for a realization. We should realize to build a system that is worth credits, credits not only from our professor but credits from other schools or organizations. I am willing to take that challenge but I should not risk the fate of my team for my pride. I would like to share some systems that I think worth given credits. I was introduced to this systems during my participation on Y4IT Congress held at UP Diliman. One is a GIS or a Geographical Information System. It is a system that shows a certain location and its status. It can also be seen in layers, groups and status. So where can this system be used. First of all its a kind of map, a very detailed map. Second it could be used as a simulation for disasters or anything you like to simulate. Lets say you want to simulate the location with an earthquake, you could see the result of that earthquake and the damage it could deal. So developing this kind of system could save lives because you would know if that location if safe to reside on. The speaker (also the developer of that system) said that developing a GIS needs time, knowledge in geology, and great grasp of computations. In fact, he said that it still unfinished and outdated due to the changes in technology. I forgot the exact name of the second system i want to introduce but generally it is a data keeping system for a hospital (a big one). So what is the challenge about this? The speaker, a young and techie female doctor, said that only 4 such system had been developed here in the Philippines and not one of them had been implemented. So we may ask why? There was no problem with the software she said. The problem is with the users. They are hesitant to try the new system (especially the old doctors). Therefore not one had been implemented and is fully running because the doctors still opt to use the traditional paper and pen. This post is becoming out of the subject and too long so if you have questions maybe I can share my knowledge.
So thinking that i knew about this system, maybe you are thinking, why did we still choose to develop a system that is common and simple. It is a group decision and I honestly think that such system (the ones i talked about earlier) needs time to develop. One semester is insufficient and even a year is insufficient. We also based it on our capacity to develop a project. First we proposed to our former teacher that we would develop a system for a barangay day care center. A simple enrollment and data keeping system integrated into one. It was not approved because we have to admit that would a barangay really spend time and money (considering it is a real life situation) to ask us to build a system for them. After that, our former professor asked us to develop a system for the Human Resource Office of our university instead. We gladly agreed to develop a system for the said office and that is how we came up with our proposal.
What our professor said is right. I don't have anything against what he said. It was a call for a realization. We should realize to build a system that is worth credits, credits not only from our professor but credits from other schools or organizations. I am willing to take that challenge but I should not risk the fate of my team for my pride. I would like to share some systems that I think worth given credits. I was introduced to this systems during my participation on Y4IT Congress held at UP Diliman. One is a GIS or a Geographical Information System. It is a system that shows a certain location and its status. It can also be seen in layers, groups and status. So where can this system be used. First of all its a kind of map, a very detailed map. Second it could be used as a simulation for disasters or anything you like to simulate. Lets say you want to simulate the location with an earthquake, you could see the result of that earthquake and the damage it could deal. So developing this kind of system could save lives because you would know if that location if safe to reside on. The speaker (also the developer of that system) said that developing a GIS needs time, knowledge in geology, and great grasp of computations. In fact, he said that it still unfinished and outdated due to the changes in technology. I forgot the exact name of the second system i want to introduce but generally it is a data keeping system for a hospital (a big one). So what is the challenge about this? The speaker, a young and techie female doctor, said that only 4 such system had been developed here in the Philippines and not one of them had been implemented. So we may ask why? There was no problem with the software she said. The problem is with the users. They are hesitant to try the new system (especially the old doctors). Therefore not one had been implemented and is fully running because the doctors still opt to use the traditional paper and pen. This post is becoming out of the subject and too long so if you have questions maybe I can share my knowledge.
So thinking that i knew about this system, maybe you are thinking, why did we still choose to develop a system that is common and simple. It is a group decision and I honestly think that such system (the ones i talked about earlier) needs time to develop. One semester is insufficient and even a year is insufficient. We also based it on our capacity to develop a project. First we proposed to our former teacher that we would develop a system for a barangay day care center. A simple enrollment and data keeping system integrated into one. It was not approved because we have to admit that would a barangay really spend time and money (considering it is a real life situation) to ask us to build a system for them. After that, our former professor asked us to develop a system for the Human Resource Office of our university instead. We gladly agreed to develop a system for the said office and that is how we came up with our proposal.
Saturday, December 20, 2008
My First Reflection
This is my first time to post on a blog so bear with me guys (including girls).
I am expecting our reporting to be slow but I was wrong because as I had observed we were all reporting in a fast phase. It was good in a way that we must cover 7 Chapters in just 2 days but I think the topics were not properly absorbed by the audience. Although if we think about it, all those topics were already discussed to us since we were freshmen therefore all those reports are just a review of what we have learned in the previous semesters. I am expecting what we have learned from the reports would be used on our project. Speaking of what is useful, on my personal opinion I think the first report and the fourth report are essential. I think the topics under the first report and also the fourth should be given importance because the topics discussed there serves as a foundation for a system analyst. Along the report of Object - oriented approach and Traditional approach, a question is raised if what is best used as a tool for system analysis and design. Object oriented approach is easier compared to the traditional approach. The objects are there and all we need to do is implement them. I was taken back of what our professor said that we must not rely on objects. We must also learn how to manipulate this objects thus bringing us back into the traditional approach. As what i have learned after the two reports of chapter 6 and 7, I can now answer the question stated earlier. In reality, object oriented approach is much easier to adopt because of its simplicity but i would rather have a knowledge or expertise in both approach. I would like to add that every one of us has his choice on what tools, approaches and techniques to use but what is really important is the foundation of his learning as a system analyst. It was also a good idea to finish the reports in two days because we can have more time in our consultation (which i think is more important than the reports). So a general overview of the reports is it is good. Thank you for reading this.
I am expecting our reporting to be slow but I was wrong because as I had observed we were all reporting in a fast phase. It was good in a way that we must cover 7 Chapters in just 2 days but I think the topics were not properly absorbed by the audience. Although if we think about it, all those topics were already discussed to us since we were freshmen therefore all those reports are just a review of what we have learned in the previous semesters. I am expecting what we have learned from the reports would be used on our project. Speaking of what is useful, on my personal opinion I think the first report and the fourth report are essential. I think the topics under the first report and also the fourth should be given importance because the topics discussed there serves as a foundation for a system analyst. Along the report of Object - oriented approach and Traditional approach, a question is raised if what is best used as a tool for system analysis and design. Object oriented approach is easier compared to the traditional approach. The objects are there and all we need to do is implement them. I was taken back of what our professor said that we must not rely on objects. We must also learn how to manipulate this objects thus bringing us back into the traditional approach. As what i have learned after the two reports of chapter 6 and 7, I can now answer the question stated earlier. In reality, object oriented approach is much easier to adopt because of its simplicity but i would rather have a knowledge or expertise in both approach. I would like to add that every one of us has his choice on what tools, approaches and techniques to use but what is really important is the foundation of his learning as a system analyst. It was also a good idea to finish the reports in two days because we can have more time in our consultation (which i think is more important than the reports). So a general overview of the reports is it is good. Thank you for reading this.
Friday, December 19, 2008
Subscribe to:
Posts (Atom)
