Assignment #1 MIS2

Think about yourself worthy to be called as IT professional, how do you see yourself 10 years from now, what are your strategies to get there?

Worthy IT Professional? Am I belong to this group? how can i become an worthy IT professional? can i be a worthy IT professional? this are the question coming from my mind when i heard a word worthy IT professional. this question challenge me to face the consequences and trials coming to my life as an IT student because i want to become an worthy IT professional.In this world there is a lot of an IT professional claiming themselves as an worthy IT professional.. I don't know what kind of skills or characteristics does the worthy IT professional have. As an IT student I'm looking forward that may be in the future i will become a worthy IT professional if i will graduate in my course BSIT with the proper discipline and attitude.Sooner if i'm already working in a big company i can properly manage myself and my carrier as an worthy IT professional. I Think you will be called as an worthy IT Professional if you have a good manner, discipline and responsible to every job that you have. Honesty i think, is also one of the reason on how to become an worthy IT professional. I know that i will become a worthy IT professional if i will strive hard to reached this.

I see my self 10 years from now as a developer of the integrated system of all automated and manual system that the Philippine government offer. Just one website and you can access everything that you want to surf regarding the national and local government services. So that our country will be known as one of the country who implemented this kind of integrated system. the question is how can i do this? it is possible for to achieve my dream? do i have a capacity to handle this kind of project?

My strategic plan to achieve this dream is to finish my study, proper training and discipline to my self, to become an a system analyst, a good programmer, and a lot of experienced.:

how to finish my study?

Of course I must be responsible for the every task, to do this perseverance is the characteristics that i need.

proper training and discipline

Some guidelines to consider are:

* Thoroughly investigate the situation which includes obtaining the employee's explanation or response prior to administering discipline.
* Document the process and results of your investigation.
* It is acceptable to repeat a step if you feel that it will correct the problem. This may be the case if some time has passed since it was last necessary to address the issue and the situation has only recently reappeared. Or perhaps, the employee misunderstood or you feel there is value in doing it again in a clearer fashion. If repeating the step works, the situation has been resolved without escalating it unnecessarily. However, be aware that an employee may be led to believe that nothing worse will happen if you continually repeat a step. If repeating a step does not resolve the problem, you can then move on to a higher step.
* The goal is to modify the unacceptable behavior or improve the performance. The goal is not to punish the employee but to more strongly alert the employee of the need to correct the problem.
* There is no rigid set of steps nor is there an inflexible rule that all steps must be followed before terminating an employee. The circumstances of each case and your judgment as to the least severe action that is necessary to correct the situation will help determine which step to use.
* Early, less stringent, measures are skipped for serious offenses such as theft, fighting, drug or alcohol use or sale. All steps are typically used for attendance or general work performance problems.
* While usually unnecessary, it is acceptable to have a witness or note taker present when meeting with the employee during the progressive discipline process. Your witness/note taker should never be a peer of the employee. university policy permits the employee to have a witness if he or she wishes.
* Human Resources is available for consultation at any step of the process, but it is especially important at the steps of suspension and termination.

To Become an a System Analyst

The development of a computer-based information system often comprises the use of a systems analyst. When a computer-based information system is developed, systems analysis (according to the Waterfall model) would constitute the following steps:

* The development of a feasibility study, involving determining whether a project is economically, socially, technologically and organisationally feasible.
* Conducting fact-finding measures, designed to ascertain the requirements of the system's end-users. These typically span interviews, questionnaires, or visual observations of work on the existing system.
* Gauging how the end-users would operate the system (in terms of general experience in using computer hardware/software), what the system would be used for etc.

A Good Programmer

Here are the following steps to improve my skills in programming:

1. Gather complete requirements.
Take the time to write down what the end product needs to achieve. Clarity of thought at this stage will save a lot of time down the line.
2. Write an implementation plan (or model).

* For something small and self-contained, this might just be a basic flowchart or an equation.
* For larger projects, it helps to break it into modules and consider what job each module must do, how data gets passed between modules, and within each module how it will function.
* Although it is fun to dive straight into code, it is equally tedious to spend hours debugging. By taking the time to design the structure on paper, you will drastically reduce your debugging time (and you may also spot more efficient ways of doing things even before you write the first line of code).

3. Add Comments to your code.
Whenever you feel your code needs some explanation, drop some comments in. Each function should be preceded by 1-2 lines describing the arguments and what it returns. (Comments should tell you why more often than what. Remember to update the comments when you update your code!)
4. Use naming conventions for variables.
It will help you keep track of what type the variable is and also what it's purpose is. Although this means more typing than x = a + b * c, it will make your code easier to debug and maintain. One popular convention is Hungarian notation where the variable name is prefixed with its type. e.g. for integer variables, intRowCounter; strings: strUserName. It doesn't matter what your naming convention is, but be sure that it is consistent and that your variable names are descriptive. (See Warnings below)
5. Organize your code.
Use visual structure to indicate code struture. i.e. indent a code block that sits within a conditional (if,else,...) or a loop (for,while,...) Also try putting spaces between a variable name and an operator such as addition, subtraction, multiplication, division, and even the equal sign (myVariable = 2 + 2). As well as making the code more visually elegant, it makes it much easier to see the program flow at a glance. (See tips on indentation below)
6. Test.
Start by testing it with inputs that you would typically expect. Then try inputs that are possible but less common. This will flush out any hidden bugs. There is an art to testing and you will gradually build up your skills with practice.
Write your tests to always include the following:

* Extremes: zero and max for positive values, empty string, null for every parameter.
* Meaningless values, Jibberish. Even if you don't think someone with half a brain might input that, test your software against it.
* Wrong values. Zero in a parameter that will be used in a division, negative when positive is expected or a square root will be calculated. Something that is not a number when the input type is a string, and it will be parsed for numeric value.

7. Practice. Practice. Practice.
8. Be prepared for change.
In a realistic working environment, requirements change. However, the clearer you are at the start about the requirements and the clearer your implementation plan, the less likely those changes will be down to misunderstanding or "Ah, I hadn't thought of that" scenarios.

* You can take an active role in improving clarity of thinking by presenting your requirements document or your implementation plans before coding to ensure that what you are planning to create is actually what's been asked for.
* Structure the project as a series of milestones with a demo for each block. Approach the programming one milestone at a time - the less you need to think about at any moment, the more likely you will think clearly.

9. Start simple and work towards complexity.
When programming something complex, it helps to get the simpler building blocks in place and working properly first.
For example, let's say you want to create an evolving shape on screen that follows the mouse and where the degree of shape change depends on mouse speed.

* Start by displaying a square and get it to follow the mouse, i.e. solve movement tracking on its own.
* Then make the size of the square relate to mouse speed, i.e. solve speed-to-evolution tracking on its own.
* Finally create the actual shapes you want to work with and put the three components together.
* This approach naturally lends itself to modular code writing, where each component is in its own self-contained block. This is very useful for code reuse (e.g. you want to just use the mouse tracking in a new project), and makes for easier debugging and maintenance.

Through all of this i can say that i can reached my ambition for the next 10 years. hoping that there's no barrier in the middle of this plan..

http://www.wikihow.com/Improve-your-Skills-as-a-Programmer
http://www.indiana.edu/~uhrs/training/ca/progressive.html
http://en.wikipedia.org/wiki/Systems_analysis