Home » Archives » March 2009

System Analysis and Design I Update

Monday, March 23rd, 2009

In the recent updates of our SAD proposal, I have reflected that my knowledge and skills is not yet enough, most especially in experience. I am grateful for our professor for guiding us accordingly in creating our major paper. From my experiences with our consultations, I have learned many things, especially when producing a good major paper. And as we struggle with finishing our major paper, I am gradually motivated to implement and make our integrated systems development proposal successful.

 Currently, I was forcefully assigned as the President for the class of our SAD I. Unfortunately, the burden of making our system implementable by SAD II falls on me. Now, I am trying to see if I am determined enough to lead the class to our system’s implementation. 

Posted by matterscantmatter at 2:19 PM | permalink | comments[22]

SDLC for Real Life

Tuesday, March 10th, 2009
In following the SDLC model, various factors are must be determined first before proceeding to  theconceived SDLC model for real life. In the real life, factors are weighed not by codes and calculations. Incalculable variables are present such as opportunities, chances, risks, and other possibilities so no SDLC can be conceived accurately by reviewing and measuring the requirements for the real life. Instead, an outlook is developed and plans are only used as guides so not to get lost but most certainly plans is always being manipulated and changed to fit the circumstance happening at the present moment. No best options are always present.


In my life, I had set my objectives/ goals as a general direction or outcome, meaning I do not have any clear image of what I want in my life as of the present. Most suited for this circumstance is the adaptive approach where I will surpass any obstacles that may prove as hindrance to my goals. Although I mentioned taking the adaptive approach, it can not be avoided anticipating some things for the future. Thus it will more adaptive than predictive, a combined approach.


To set things clearly, my own SDLC follows:

  • Retrospection or more like information gathering. My personality projects a nature that I work on things that I currently know and sure of thus making sure that the most desirable outcome will be conceived. I believe that when you act based on facts, nothing can ruin your plan, of course with every possible things added as the factor.
  • Planning. Based on the fact or information gathered, I then will set my sight on an exact goal then plan on what steps and actions are necessary to achieve that goal. My planning consists of the main course of action, a plan B and a fallback plan. Based on my personality, i do not risk on things that would not conceive any good results or plans when a failure will occur. It is most beneficial that even when you fail, you have achieved much and the outcome of the failure will weigh closer to the outcome of the success.
  • Executing the plan. The plan will only be most useful when you are using or following it. In my case, I am usually not strict in implementing my plans but I just make it sure that the projected outcome will still be derived.
  • Success? No more like progress. In my case, I do not usually plan for a clear objective but for a goal that can never be reached so that I will continually be trying to reach that goal, never ending my progress for I believe that improvement and progress should be stopped when success is derived but only stopping when you can not go any further despite all things.


The statement in the last step is innate to my nature since I can not see a true and exact success for I also believe that a success is only accomplishing one part of it, not all of it. I also believe that maintaining is bad since it does not project any progress but a stalemate. It is better if you fail than stop for it is ensured that progress is sustained and improvement is inevitable. Thus, success will become apparent.
Posted by matterscantmatter at 10:34 AM | permalink | comments[1]

Information System Planning Initiative

Friday, March 6th, 2009
In our subject course “Management Information System II”, we were asked to do a task asking us what initiatives each of us will do in the case our university president asks us to an Information System Plan for the university. Most of us answered by discussing the steps undertaken when developing an ISP, which can be gathered in the internet and other reference materials. I did not bother to conduct a thorough gathering of information regarding in the development of an ISP in an academic organization since I wanted to discuss my initiatives and perception upon the development of an ISP for our university. Needless to mention, there are numerous ways or processes that can be followed to develop a good ISP plan but in the end, it must be made from accurate information and implemented effectively first before an ISP becomes any good for the university. I took this chance to discuss my concerns as a student of the university and what I wanted to focus or aim the ISP for is the problems found inside the university campus. I believed that if any organization wishes to develop and improve by implementing ISP must address its weaknesses and conflicts found inside the organization. An organization that have achieved high is bound to fall if its foundation or the organization structure itself is weak and unstable. I believed that an organization is successful when the organization itself is stable and built upon an unbreakable foundation from which the organization will thrust itself towards great achievements. In contrast to our university, I wanted to develop an ISP addressing these concerns and having a goal of creating a stable and strong university. From that then the university can improve and compete with other universities.
Posted by matterscantmatter at 1:08 PM | permalink | Add comment

System Analysis of USEP Enrollment System

Thursday, March 5th, 2009

We have been tasked to do an analysis regarding of our university’s enrollment system and from that, we are to make a Data Flow Diagram, Use Case Diagram and Activity Diagram. The diagram are as follows:

                                     Data Flow Diagram

  


                                                                   Use Case Diagram   

                                                                      Activity Diagram

 

 

These diagrams are developed from our university’s current enrollment system. From just looking at the diagrams, it can be said that the enrollment system is not yet fully organized and systemized for optimal service performance. Based from what we have learned upon this task, we have understood that our current enrollment system is not very capable of giving good service or output. From this case, we were encouraged to develop better system with good database management and activity flow.

Posted by matterscantmatter at 2:43 PM | permalink | comments[5]