a good systems analyst

The question was based on my learning from chapter 1, identify and discuss some characteristics that a good Systems Analyst must have. So for me to start, I will discuss first all the necessary information that you need to know about chapter 1 which is the world of the information systems analyst. So to start, first I will give you all the definitions and etc. so what is a Systems Analyst? A systems analyst is a business professional who uses analysis and design techniques to solve business problems using information technology. So a systems analyst is just basically person that handles all the necessary analysis and design in an organization. System analysis is the process of understanding and specifying in detail what the information system should accomplish. So as a systems analyst, they are the one who do the analysis so basically they need to understand and specify what the organizations information system should accomplish. And in design, as a systems analyst they should also be able to do systems design. Systems design is the process of specifying in detail how the many components of the information system should be physically implemented. So in short, a system analyst also needs to design the information system of an organization to specify in detail the physical aspect of the desired information system. Now let’s go to the characteristics that a good systems analyst have. I have searched some inputs over the web and this is all the inputs I have gathered. The system analyst must be able to communicate in writing and orally. The analyst must easily get along with people. The analyst must be a good listener and be able to react to what people say. The analyst must be knowledgeable of technology. The analyst is not expected to know the intricacies of programming, but a decent general knowledge of concepts and terms is essential. The analyst must be knowledgeable of business. The analyst is not expected to be an expert in business but a decent understanding of the client's world is required. Other sources are as follows, one should be familiar with designing concepts that is appropriate for the particular development environment. This means one who is good at designing commercial buildings isn't necessarily a good person to design residential housing. Although a lot of concepts overlap, one who is good at designing mainframe system isn't necessarily a good candidate for web projects. One should have the skills to use the tools to facilitate his/her work such as design software tools. If someone is struggling to use a hammer s/he is worrying about putting a nail in straight not about building a good structure. One should have the industry/business knowledge or the capacity to acquire them. System implementation is a lot like a bunch of blind people trying to figure out what an elephant looks like. Each person has his/her own field expertise. However, the more knowledge one person has would make the process easier and create better results. Good communication skills without saying are very important. So these are basically all the characteristics that a good system analyst have. So let’s go deeper to that.

A business problem solver – systems analysis and design is, first and foremost, a practical field grounded in time-tested and rapidly evolving knowledge and techniques. Analysts must certainly know about computers and computer programs. They should possess the special skills and develop expertise in programming. But they must also bring to the job a fundamental curiosity to explore how things are done and the determination to make them work better. Developing information systems is not just about writing programs. Information systems are developed to solve problems for organization, and a systems analyst is often thought of as a problem solver rather than a programmer. How does an analyst solve problems? System analysis and design focuses on understanding the business problem and outlining the approach to be taken to solve it. Now I will discuss to you or show you the systems analyst approach in problem solving. Obviously, part of the solution is a new information system, but that is just part of the story.

· First is research and understand the problem
· Then, verify that the benefits of solving the problem outweigh the costs
· After, define the requirements for solving the problem
· Next, develop a set of possible solutions (alternatives)
· Then, decide which solutions is best and make a recommendation
· Next, define the details of the chosen solutions
· After, implement the solution
· And lastly, monitor to make sure that you obtain the desired results

The analyst must first understand the problem and learn everything possible about it – who is involved, what business processes come into play, and what other systems would be affected by solving the problem. Then the analyst needs to confirm for the management that the benefits of solving the problem outweigh the costs. If solving the problem is feasible, the analyst defines in detail what is required to solve it – what specific objectives must be satisfied, what data need to be stored and used, what processing must be done to the data, and what outputs must be produced. What needs to be done must be defined first. After detailed requirements are defined, the analyst develops a set of possible solutions. Each possible solution (an alternative) needs to be thought through carefully. Usually, an information system alternative is defined as a set of choices about physical components that make up an information system. Many different alternatives must be considered, and the challenge is to select the best – that is, the solution with the fewest risks and more benefits. Alternatives for solving the problem must be cost-effective, but they also must be consistent with the corporate strategic plan. Does the alternative contribute to the basic goals and objectives of the organization? Will it integrate seamlessly with other planned systems? Does it use technology that fits the strategic direction that the management defined? Will end users be receptive to it? Analyst must consider many factors and make tough decisions. After the systems analyst has determined, in consultation with the management, which alternative is to recommend and the management has approved the recommendation, the design details must be worked out. Here the analyst is concerned with creating a blueprint (design specifications) for how the new system will work. Systems design specifications cover databases, user interfaces, networks, operating procedures, conversion plans, and of course, program modules. After the design specifications are complete, the actual construction of the system can begin, including the programming and testing. An information system can cost a lot of money to build and install so detailed plans must be drawn up. It is not unusual for dozens of programmers to work on programs to get a system up and running and those programmers need to know exactly what the system is to accomplish. So this is a characteristic that a good systems analyst must have.

Systems that solve business problems – so let me define first what is a system, a system is a collection of interrelated components that function together to achieve some outcome. An information system is a collection of interrelated components that collect, process, store, and provide as output the information needed to accomplish a business task. What are the interrelated components of an information system? A subsystem is a system that is part of another system, so subsystems might be one way to think about the components of a system. Every system, in turn, is part of a larger system, called a supersystem. Another way is to list the parts that interact. Examples of this include hardware, software, inputs, outputs, data, people, and procedures. This view is also very useful to the analyst. Every system has a boundary between it and its environment. Any inputs or outputs must cross the system boundary. Defining these inputs and outputs are important part of systems analysis and design. In an information system, people are also key components, and these people do some of the system’s work. Another boundary that is important to a systems analyst is the automated boundary which is a part of the system, where work is done by computers. And now I will discuss the types of information systems that a systems analyst must know which the following is:

· Transaction processing system (TPS)
· Management information systems (MIS)
· Decision support and knowledge-based systems (DSS/KBS)
· Enterprise applications
· Communication support systems
· And office support systems

Required skills of the systems analyst - first is the analytical skills, so what is an analytical skill? Analytical skill is the ability to see things as systems, identify, analyze, and solve problems in an optimal way for a specific organization. So from what is stated above, the ability to see things as a system, the ability to identify, the ability to analyze, and the ability to solve problems are the main concerns of a system analyst in the analytical aspect of a systems analyst. So a system analyst must develop these types of skills. As we all know that we can have all these skills but a system analyst must really develop in order to be more effective in designing any modeling process. So, enough for the analytical skill and lets go to the next one which is the technical skills.

The second one is the technical skills, so what is a technical skill? Technical skill is the ability to understand how computers, data networks, databases, operating systems, etc. work together, as well as their potentials and limitations. So from what is stated above, the ability to understand how computers, data networks, databases, operating systems, and etc. work together is the main concerns of a system analyst in the technical aspect of a system analyst. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. I think for me this very important that a system analyst must really develop in order to be more effective.

Technical skills needed by systems analysts include but are not limited to:

1. Computers (PCs, mini, mainframes, etc.)
2. Computer networks (LAN, WAN, VPNs, administration, security, etc.)
3. Operating systems (UNIX, Mac/OS, Windows).
4. Data Exchange Protocols (ftp, http, etc.)
5. Programming languages (C++, Java, XML, etc.)
6. Software applications (Office, project managements, etc.)
7. Information systems (databases, MISs, decision support systems)
8. System development tools and environments (such as report generators, office automation tools, etc.)

The third one is the management skills, so let me define what a management skill is all about. So what is a management skill? Management skill includes organization’s recourse management, project management (people and money), risk management, and change management. So to elaborate more it is just management skills help systems analysts manage projects, resources, risk, and change. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. They should be able to manage all the things that are needed to be manage in an organization such as resources, be able to properly disseminate all workforce in a project and properly manage it, be able to know the risk that are involve, and be able to anticipate changes in the environment.

Managerial skills needed by systems analysts include but are not limited to:
1. Resource management - effectively managing the project’s resources, including time, equipment, hardware, software, people, money, etc.,
2. Project management - determining the tasks and resources needed for a project and how they are related to each other,
3. Risk management - identifying and minimizing risks,
4. Change management - managing the system’s (organization's) transition from one state to another

The last skill that a system analyst must develop is the communication skill. So let me define what communication skill is all about. So what is communication skill? Communication skill includes effective interpersonal communication (written, verbal, visual, electronic, face-to-face conversations, presentations in front of groups), listening, and group facilitation skills. To elaborate, communication skills are very important to develop in order for the system analyst and clients understand each other. Having good communication with client’s makes things go smoothly and properly. Poor communication leads to mismanagement and even resulting to project failures, and etc.

Communication skills needed by systems analysts include:

1. Clear and effective interpersonal communication, whether written, verbal, or visual, from writing reports to face–to–face conversations, to presentations in front of groups;
2. Listening (accepting opinions and ideas from other project team members),
3. Group facilitation or formal technical reviews (FTR) skills:

· setting an agenda,
· leading discussions,
· involving all parties in the discussion,
· summarizing ideas,
· keeping discussions on the agenda, etc.

The analyst’s role in strategic planning – we have described a systems analyst as someone who solves specific business problems by developing or maintaining information systems. The analyst might also be involved with senior managers on strategic management problems – that is, problems involving the future of the organization and plans and processes to ensure its survival and growth. Therefore, the analyst might be asked to participate in a study that carefully examines existing business processes and procedures and then to propose information system solutions that can have a radical impact. Many tools and techniques of analysis and design are used to analyze business processes, redesign them, and the provide computer support to make them work. So basically, the role of a systems analyst in creating a strategic plan is very crucial, so systems analyst must really have the skills in creating a strategic plan.

The analyst as a system developer – we have discussed many roles that a systems analyst can play in an organization, however the main job of an analyst is working on a specific information systems development project. As a preview of what system development involves the systems analyst, systems analysis tasks, systems design tasks, and implementation and support. So these are the requirements that a system development involves.

So to summarize basically to be called a good systems analyst, one must be a problem solver, business problems using information systems technology. Problem solving means looking into the problem in great details, understanding everything and generating several alternatives for solving problem, and then picking up the best solution. And also to be a good systems analyst, you must have the skills needed to be more effective in solving problems such as technical, analytical, managerial, and interpersonal skills. Integrity and ethics behavior are crucial to the success of the analyst. And lastly, become involved in strategic planning.


References:
http://books.google.com.ph
http://answers.yahoo.com/question/index?qid=20080725042042AA2MqMh
http://answers.yahoo.com/question/index?qid=20070731092009AAjzWqQ

my IS plan for the university

The question was if I were invited by the university president to prepare an Information Systems plan for the university, discuss what the steps are in order to expedite the implementation of the Information Systems Plan. So in order for me to be able to come up with the IS plan I need some resources for it. Especially, the focus of creating the Information Systems plan is to expedite it. So to start, let me give you some definitions and overview of what is an Information Systems Plan.

Just to review I will just state some of the content of the Information Systems Plan of the university which was create in the year 2007. The university planned a 15-year Strategic Plan for the betterment of the said organization. The 15-year Strategic Plan of the University of Southeastern Philippines specifically aims to provide the University with a roadmap to reposition itself toward becoming more competitive and responsive to the needs of its stakeholders. Essentially, this would mean USEP achieving academic excellence in the future and the leader in research, development and extension in Southern Philippines and the rest of the country. The Strategic Plan covers the period 2007 to 2021. It consists of five parts containing the long-term directions and medium-term strategies for the University. The long-term directions which are found in Part I, include the vision, mission and goals of the University. This was formulated through a consultation conducted with the faculty, non-teaching personnel and students and take into consideration the existing challenges and potentials of the University. The medium-term strategies which are found in Part II of the plan, take into account the major final outputs of the university on instruction, extension, research and development, and production and how the same may be strategically improved to respond to the growing demands of the University and its stakeholders. The strategies to build up instruction, extension, and research and development give enough consideration to the desire of the university for program accreditation. The plan, as discussed in Part III, likewise, outlines university-wide strategies and defines specific strategies for each campus. Strategies for each campus of the University allow for the distinctive demands of the localities where it is located to be factored in. This is without disregard to the overall direction of the University in the medium-term. The plan implementation and communication are discussed in Part IV. It specifically contains the procedure for the implementation of the plan as well as the manner of communicating the plan to the university constituency and external stakeholders. The Institutional mechanisms for monitoring and evaluation of plan implementation are discussed in Part V. It contains the following elements: scope and focus; monitoring and evaluation process; accountabilities and responsibilities, deliverables and costs and timing. So basically, this was the Information Systems Plan of the university in order to expedite the implementation of the Information Systems Plan. It has five parts which is composed of the first one is Development Direction, the second part which is the Competitive Benchmark Analysis, the third part is the Strategic Actions, the fourth is the Plan Implementation and Communication, and lastly is the Monitoring and Evaluation.

The first part is composed of the ff:

· Introduction
· Vision
· Mission
· Goals

The second part is composed of the ff:

· Competitive Advantage of the University
· Current development Trends
· Challenges and Priorities

The third part is composed of the ff:

· Academic Programs, Curriculum and Instruction
· Research, Development, and Extension
· Administration and Institution
· Physical Plant and Facilities
· Human Resource Development
· Financial Resources
· Student Services
· Library Services

The fourth part is composed of the ff:

· Implementing Mechanisms
· Communicating Mechanisms

The fifth part is composed of the ff:

· Scope and Focus
· Strategies
· M & E Deliverables

So basically, this is all what’s inside the Information Systems Plan of the university. So enough of that I will now proceed to my own Information Systems Plan for the university in order for it to expedite the implementation of the Information Systems Plan. So first is I will discuss the steps in creating my Information Systems Plan. These are the following steps in creating my Information Systems Plan.

1. Gather Base Information
2. Create the mission model
3. Develop a high-level data model
4. Create the resource life cycles (RLC) and their nodes
5. Allocate precedence vectors among RLC nodes
6. Allocate existing information systems and databases to the RLC nodes
7. Allocate standard work break down structures (WBS) to each RLC node
8. Load resources into each WBS node
9. Schedule the RLC nodes through a project management package.
10. Produce and review of the ISP
11. Execute and adjust the ISP through time

Step 1: Gather Base Information

Interviewing the Client
Why interview the client? Good question. Well, who's the person that's going to build the database, and knows exactly what information is needed in order for you to gather all the necessary data?
You of course!
Sure, in the big, wide (and well-paid) corporate world, there mightn't be much chance of you, the fabled geek in the cupboard, actually meeting the client. But not everyone's in the corporate world are they? So perhaps your chances of interviewing the client will be higher. Make sure you're prepared for the meeting -- and by that, I mean prepared for the fact that the client won't understand much of what you do. Unfortunately for us, the majority of clients have a tendency of thinking visually: forms, Web pages and other user interfaces. As a general rule, the client won't really care how the data is structured or how it interacts with their system. Because changing visuals can usually be done easily and quickly, the client may often think this ease applies to every kind of change. So be ready to explain to them the importance of the schema in the overall development process, and the difficulty they'll experience in making changes down the track. Now, how do I get the right information out of a client? Well, I generally approach interviews with the following points in mind:

Interview Rule Number 1: Be nice to the client and don't make it seem like you're smarter than they are. The word is "interview", not "interrogate". The client doesn't have your technical expertise, but they have the information you need. It's your job to get to the data. So the best way to approach the interview is tactfully, and to avoid frustrating your client, overwhelming them, or making them feel like an idiot.

Interview Rule Number 2: Enter with an agenda and ask the right questions. Enter the interview with an agenda, making sure that you're going to cover the important areas, but always retain an open mind. The best opening question might be "What do you want from this project?" Asking this question first will give the client/interviewee the chance to tell you what they want from the project in a way that makes them feel comfortable. It also shows that you're attentive to their needs. Try to find out their initial ideas about the job, and how they'd like to achieve their goals. This should hopefully give you a clear idea of what they want. Be prepared to listen, and take notes -- lots of them.

Interview Rule Number 3: Talk to everyone who's involved with the project. Have you ever been in a situation where you're going to the movies with a group of friends, and one person decides what you're going to see? It's annoying, right? Well, this can also happen in the data collection process. If you only use the ideas voiced by the first (or loudest, or boldest) person you talk to, then you may not get the information you need to build a suitable database.

Interview Rule Number 4: Make sure you understand what the client wants. Making sure you know exactly what the client wants is important. If you don't, you may leave the interview with completely the wrong idea of their expectations. Make sure you thoroughly understand what they tell you. If in doubt, ask for clarification. And reiterate the important points with the client in your own words, to make sure you've grasped what they're talking about.

Interview Rule Number 5: Record what the client is looking for and any important data they provide. If understanding what the client wants is critical, recording this information is a necessity. Write down all the important points covered by the client. You might even go so far as to record or even video the interview, for a complete and more in-depth set of notes.

Interview Questions

As I mentioned above, it's imperative that you ask the right questions of your client. To me, identifying the right questions was one of the hardest things to do. So here are the questions I always ask -- make sure the client answers these fully, and be sure to include relevant questions tailored to your specific project as well:

Who will generally use the data?
In answering this question, the client might inform you of other people that you may need to discuss the project with. It will also tell you whether the database is to be used in-house or publicly.

How will the data be used?
Is your data simply to be used on the company intranet? Or will the same data need to be available in a different format on the public Website as well? Obviously the options will depend on the job -- make sure you ask!

Where is your data now?
Never in my work experience has a client handed me one database or one source that contained all the data. As you seek out data from the client, it will be handed to you in all kinds or formats! Spreadsheets, mainframe data, desktop databases, paper brochures and filling cabinets are just a few.

How much is the data worth?
It's important that the client knows the value of their data. Just because it's available doesn't automatically mean that it should be used. The client should always be informed of the value estimate for all the data available. This means that the client is able to make decisions that may save funds, and make your life easier!

What rules do you want to apply to the data?
Rules can be important for maintaining data integrity. Your client may want contact information in the database to include an email address, a valid street address or the contact's name, so that the information can be split into separate categories. This is something you must find out in advance, so that you can build the system to your client's requirements.

Rules

Like just about everything else, most businesses use rules to govern their data. Ever filled in a form that said it needed your email address? Or wanted your phone number broken into three? These are data rules, and they govern how the data should be formatted, what type of data it should be, etc. If the client says they want a first name, middle name and a last name for their contact database, then we consider this a rule. Rules are designed to maintain data integrity, and trust me, if you make them up instead of developing them in lone with the client's needs, you're asking for trouble!

Getting Rules
Ask your client what rules they have for their data and they generally look at you with a confused expression. It's never that easy! You're going to have to search for the rules yourself. Here are a couple of places I'd look:

1. Request for Quote or Request for Proposal
These two documents can be a goldmine for data -- they're generally used as a basis for determining the price of the project in, so they're usually packed with data
2. Old Systems
Having access to an older database system can be both a blessing and a curse. The information you gather from the old database can give you a good idea about what kind of data you can expect to find. However, unless the job simply involves tweaking this old system, then only use it as a reference point. It's often easy to think that simply editing the existing database and accommodating new code will finish the job. In a very small number of cases, this may be true, but usually it isn't.
3. Reports, Spreadsheets, Forms and Filing Cabinets
Just about every company can lay claim to asking customers to fill in forms, having tons of data in spreadsheets, and stacks of information in filing cabinets. It's guaranteed that the data will be scattered all over the place - but if it's needed to meet the project's objectives, then you must find it.

Finishing Up
Collecting data so you can develop an accurate schema and, eventually, a successful database that achieves your client's goals and meets their needs is no mean feat. It's an intense and often difficult task. But now you know how to interview the client and look for data rules -- often the toughest steps in the process. Good luck, and could the schema be with you!

Step 2: Create the mission model

Missions and mission descriptions are represented through hierarchically composed text. They are natural and are devoid of the effects from organizational structure stylistic effects. Missions from enterprises from the same “line of business” are very similar. In contrast, their function models may be quite different because of effects imposed by management styles and organizational structures. Simply stated, mission descriptions are goal and objective oriented and are best seen as characterizations of the idealized end-results, without any regard for “who and how.” It is important to distinguish between missions and functions. At first, missions and functions look very much alike. However they are not. The following table illustrates their key differences.

Missions are descriptions of the characteristics of the end result. Missions are noun-based sentences.
Functions are descriptions of how to accomplish an end result. Functions are verb-based sentences.

Missions are a-political. They are devoid of “who and how.” There should only be ONE mission description for a mission.
Function hierarchies are commonly tainted by organizations and styles. There can be any number of equivalent versions of a given function.

Databases and Business Information Systems are based on missions.
“Human” activities and organizations are based on business functions.
When you “Business Process Re-engineering (BPR)” functions you still have the same business.
When you “BPR” mission you have a different business.

Mission descriptions are strategic and long range.
Functions are tactical to operational, and medium to short range, and are organizationally sensitive
Building an information systems plan on the basis of functions is a 100% guarantee of failure.

Step 3: Build the High Level Data Model

The high level data model is created in two steps: building database domains, and creating database objects. It is critical to state that the objective of this step is the high-level data model. The goal is
NOT to create a low level or fully attributed data model. The reasons that only a high-level data model is needed are straight forward:

· No database projects are being accomplished; hence no detailed data modeling is required!
· The goal of the ISP is to identify and resource allocate projects including database projects and for that goal, entity identification, naming and brief definitions is all that is required for estimating.

The message is simple: any money or resources expended in developing a detailed data model is wasted.

Step 3.1 Create Database Domains

Database domains are created from the “bottom” leaves of the mission description texts. There are two cases to consider. First, if the mission description’s bottom leaves are very detailed, they can be considered as having being transformed into database domains. That is they will consist of lists of nouns within simple sentences. The other case is that the mission descriptions have been defined to only a few levels, and the lists of nouns that would result from the development of database domains have yet to be uncovered. The example on the next page presents the database domain for accounts payable.
Whenever a database domain describes complex sets of data, multiple levels of the database domain description may be required. These sub domains are expressed as additional paragraphs. A review of these paragraphs clearly shows that the text is “noun-intensive.” The “who and how” is clearly missing. That is the way it should be. If the “who and how” were contained in the database domains then they would not be independent of either process or organization. A series of diagramming techniques created especially for data and the relationships among data is called entity-relationship (ER) diagramming. Within one style of this technique, the entities are drawn as rectangles and the relationships are drawn as diamonds. The name of the relationship is inside the diamond. Another style of ER modeling is to just have named lines between the entities. In this methodology, since the domain of the diagram is data, it is called the database domain diagram.

Step 3.2 Define Database Objects

In today's parlance, a lucid policy-procedure pair is called a business object. When the policy- procedure pair are completely defined within the language constructs of ANSI/SQL and is stored, retrieved, and maintained in an ANSI/SQL database through a sequence of well-defined states, the business object is a database object. The goal of database object analysis is to enable the definition of both the data structure and the data structure transformations that:

Installs a new database object in the database
Transforms a database object from one coherent state to another
Removes a database object from the database
Database objects are found by researching business policies and procedures. Database objects are however much more than just collections of policy-homogeneous entities. In fact database objects consist of four main parts:

Data Structure: the set of data structures that map onto the different value sets for real world database objects such as an auto accident, vehicle and emergency medicine incident.

Process: the set of database object processes that enforce the integrity of data structure fields, references between database objects and actions among contained data structure segments, the proper computer-based rules governing data structure segment insertion, modification, and deletion. An example is the proper and complete storage of an auto accident.

Information System: the set of specifications that control, sequence, and iterate the execution of various database object processes that cause changes in database object states to achieve specific value-based states in conformance to the requirements of business policies. An example is the reception and database posting of data from business information system activities (screens, data edits, storage, interim reports, etc.) that accomplish entry of the auto accident information.

State: The value states of a database object that represent the after-state of the successful accomplishment of one or more recognizable business events. Examples of business events are auto accident initiation, involved vehicle entry, involved person entry, and auto accident DUI (driving under the influence of alcohol/drugs) involvement. Database object state changes are initiated through named business events that are contained in business functions. The business function, auto accident investigation includes the business event, auto-accident- incident initiation, which in turn causes the incident initiation database object information system to execute, which in turn causes several database object processes to cause the auto accident incident to be materialized in the database.
A database object is specified to the SQL DBMS through the SQL definition language (DDL).
All four components of a database object operate within the “firewall” of the DBMS. This ensures that database objects are protected from improper access or manipulation by 3GLs, or 4GLs. A DBMS that only defines, instantiates, and manipulates two dimensional data structures. The database objects are mapped in a many-to-many fashion within the metabase to missions. This provides the ability to know which databases support which missions and vice versa.

Step 4: Create Resources and the Resource Life Cycles (RLC)

As a short review, missions are the idealized characterizations of end results of the visionary state of the operating enterprise. Database objects, founded squarely on missions are the high- level declarations of the data required to reflect the achievement of the mission’s vision.
Resources and their life cycles are the names, descriptions, and life cycles of the critical assets of the enterprise, which when exercised achieve one or more aspects of the missions. Each life cycle is composed of RLC nodes. A mission might be human resource management, where in, the best and most cost effective staff is determined, acquired and managed. A database object squarely based on human resources would be employee. Within the database object, employee, are all the data structures,

Step 4.1
Determine the Resources
The enterprise’s product and/or service resources are defined; they may be either concrete or
Abstract. Ron Ross provides two guidelines to assist in resource identification:

· Define the product or service that constitutes the enterprise’s resources from the customer perspective.
· Define the resource as it is managed between the enterprise and its customers.
· The resource must be monitored and forecasted. By the time the resource is required, it is too late to be produced.
· The resource must be optimized. The resource is of such a cost that an unlimited supply is not possible.
· The resource must be controlled and allocated. The resource is desirable and necessary, and must be shared among functions of the enterprise.
· The resource must be tracked. Each stage of the resource is important to the enterprise, including its demise.

Step 4.2 Determine the Resource Life Cycles
The second step is to determine a life cycle for each resource. Each node in the life cycle represents a major state change in the resource. The state change is accomplished by business information systems and is reflected through the enterprise’s database objects (conformed into databases). The three figures below, developed in support of an enterprise database project for a state-wide court information system, shows the resource life cycles for Document, Case, and for Court’s Personnel.

Step 5: Allocate Precedence Vectors among RLC Nodes

After the resources and life cycles are complete, precedence vectors are established. There are actually two types of presidencies: Within the value chain and between resources. Presidencies within the value chain are established during the life cycle analysis. These are the lines that connect one node to the next. Precedence between resources is created when a resource life cycle state, that is, a specific life cycle node, cannot be effective or correctly done unless the preceding resource life cycle state has been established or completed. A precedence arrow, renamed precedence vector, is drawn from the enabling resource life cycle state to the enabled resource life cycle state. The most difficult problem in establishing the precedence is the mind set of the analyst. The life cycle is not viewed in operational order, but in enablement order: that is, what resource life cycle state must exist before the next resource life cycle state is able to occur. This is a difficult mind set to acquire, as there is a natural tendency to view the life cycle in operational order. The test of precedence becomes: what enables what and what is it enabled by what? For example, project establishment precedes the award of a contract. This does not seem natural, since a project would not operationally begin until after a contract is awarded. However, there must be an established infrastructure to create the project and to perform the work prior to the contract award. A workforce must be in place to perform work along with the ability to assign work to the employee on the contract, and the ability to bill the customer. Therefore, the project enables the contract.

Step 6: Allocate Business Information Systems and Databases to the RLC Nodes

Once the resource life cycle network has been created, it is stored into the metabase. Once there, its lattice can be employed to attach the databases and business information systems. Databases and their business information systems exist within a data architecture framework. The five distinct classes of databases are:

· Original data capture (ODC)
· Transaction data staging area (TDSA)
· Subject area databases (SDB)
· Data warehouses (wholesale and retail (a.k.a. data marts))
· Reference data

Step 6.1 Allocate Existing (As-is) Databases or Files to Resource Life Cycle Nodes

Within the class of existing databases or files, there are three prototypical examples:

· A file for every distinct process or purpose
· A single database for all reasons
· Multi-data architecture database classes

Step 6.2 Allocate Existing (As-Is) Business Information System to Resource Life Cycle Node

Within the class of existing business information systems, there are three prototypical examples:

· Monolithic mainframe with manual subsystems for workflow
· LAN-based, workflow and client/server systems architecture
· Commercial Off-the-shelf software (COTS)

Step 6.3 Allocate Future (To-Be) Databases to Resource Life Cycle Node
Within the class of existing databases or files, there are three prototypical examples:

· A file for every distinct process or purpose transformed to a single database for all reasons
· A single database for all reasons transformed to multiple databases fitting within the five database architecture classes
· A file for every distinct process or purpose transformed to multiple databases fitting within the five database architecture classes

Step 6.4 Allocate Future (To-Be) Business Information System to Resource Life Cycle Node

Any of these alternatives could be enhanced by either Internet or Intranet access. This type of access, if the proper software development environment is employed, is a paradigm shift only if the system is batch. If the system is intended to be on-line through terminals, PCs, or is client/server, the Internet or Intranet should only be a presentation layer shift. In any case, the high level metadata for the three components that comprise the future business information system must be collected and stored in the metabase. The first set of metadata should already be in the metabase as a consequence of Step 5.2. In addition, all future business information systems should be cast in terms of future databases.

Step 6.5 Configure ISP Projects

Configuring ISP projects consists of determining the full set of requirements and then selecting the first cut preferred alternative for carrying out the transformation from the “as-is” environment to the “to-be” environment. The considerations that must be reviewed and addressed are distinct for databases and for business information systems. The figures on the next two pages provide the three prototypical alternatives for each and then the assessment areas that must be addressed.
The final outcome is a full understanding of the proposed future project. This full understanding is then employed in the next step, Allocating Standard Work Breakdown Structures to Each Database and Business Information System Project. Thereafter, each proposed project is input to a project management system and scheduled.

Step 7: Allocate Standard Work Break down Structures (WBS) to Each Business Information Systems and Database Project

The key reason for having a well engineered check list for identifying the types of work involved in either a database or business information system project is the ability to then used canned work breakdown structures (WBS). When these WBSs are coupled with experience-honed metrics that are embedded in a project management system that “self-learns” from on-going projects, accurate, reliable and repeatable project plans result. The figure below presents a very high level view of how project management and the projects associated with RLC nodes are interrelated. There are five distinct classes of projects are:

· Administration and management
· Specification
· Implementation
· Operation and maintenance
· Multiple category

Step 8: Load Resources into Each Project

Once the WBS is selected, the WBS list and associated deliverables and metrics are automatically brought into the project. When the quantities for each deliverable type are computed, then the overall gross hours estimate for the project is created.
The gross hours estimate is then finalized (either upwards or downwards) by the selection of work environment factors (e.g., nobody even knows who the users are (that’s a bad work environment factor)), and also by the specific persons assigned who have varying levels of capabilities in certain experience levels (e.g., someone is assigned to create the data model who doesn’t yet even know the meaning of the term, “ER diagram”). That’s a bad staffing factor.
The value in having highly engineered work environment and staffing experience factors that adjust the gross hours is that project managers can then relay back to management the exact reasons why a project will cost more or less than another project of even the same construct and size.

Step 9: Schedule through a Project Management Package

Project management systems like Microsoft Project, Welcom’s Open Plan Professional, or
Primavera’s P3e all require PERT (activity network charts) to effectively schedule an entire RLC network of RLC node assigned projects. When WBSs are brought into a project management system, they are treated as self- contained subprojects within the overall set of RLC node network of projects. The figure below shows a RLC network. The resource life cycles are depicted from their first to last node in a top- down fashion. The precedence vectors are shows from one node of a RLC to another node of a different RLC. Multiple precedence vectors do not exist between resource life cycles. When this
RLC network is turned on its side, as shown on the next page, it resembles a PERT chart. The chart naturally contains parallel sets of nodes that intersect. From this diagram it is easy to see that the network of RLC nodes can be traditionally scheduled.

Step 10: Produce and Review the ISP
When the resource loaded network of projects is scheduled through a project management system, normal results are produced. That is, the enterprise is faced with the requirement for:


· Infinite resources
· Infinite time
· Infinite computer capacity and speed, and
· Zero time allocated by “management” to accomplish all the work

Step 11: Execute and Adjust the ISP through Time

Enterprises, once they evolve beyond their first round of information systems, find themselves transformed from a project and package mentality to a release mentality. The diagram on the next page illustrates this new continuous flow environment. It is characterized by:

· Multiple, concurrent, but differently scheduled projects against the same subject area database or warehouse database
· Single-database projects that affect multiple subject area and data warehouse databases
· Projects that develop completely new capabilities, that can assess required changes to existing capabilities, and that can accommodate a variety of systems generation alternatives (COTS, package, and custom programming)

The continuous flow environment contains four major sets of activities. The user/client is represented at the top in the small rectangular box. Each of the ellipses represents an activity list to accomplish a specific need. The four basic needs are essentially:

· Need Identification
· Need Assessment
· Design
· Deployment

So basically, these are the steps that I would suggest to the university president in order for the implementation of IS plan in the university will expedite. The important thing is gather data, analyze the data, and solve the problem with all the data gathered.


References:
Google.com
http://articles.sitepoint.com/article/gathering-data-made/2

System Analyst

The question was “Interview a Systems Analyst and ask what skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process?” so what are the skills and characteristics must a systems analyst develop in order to be more effective in any design modeling process? So before I give my comment to that I would give you some introductions or a short overview of what is a system analyst and what are those things that a system analyst do. So first I will give you the definition of a system analyst.

Systems analysts solve computer problems and apply computer technology to meet the individual needs of an organization. They help an organization to realize the maximum benefit from its investment in equipment, personnel, and business processes. Systems analysts may plan and develop new computer systems or devise ways to apply existing systems' resources to additional operations. They may design new systems, including both hardware and software, or add a new software application to harness more of the computer's power. Most systems analysts work with specific types of systems—for example, business, accounting, or financial systems, or scientific and engineering systems—that vary with the kind of organization. Some systems analysts also are known as systems developers or systems architects. For systems analyst, programmer-analyst, and database administrator positions, many employers seek applicants who have a bachelor's degree in computer science, information science, or management information systems (MIS). MIS programs usually are part of the business school or college and differ considerably from computer science programs, emphasizing business and management-oriented course work and business computing courses. The level of education and type of training that employers require depend on their needs. One factor affecting these needs is changes in technology. Employers often scramble to find workers capable of implementing “hot” new technologies. Those workers with formal education or experience in information security, for example, are in demand because of the growing need for their skills and services. As technology becomes more sophisticated and complex, employers demand a higher level of skill and expertise from their employees. Individuals with an advanced degree in computer science or computer engineering or with an MBA with a concentration in information systems should enjoy highly favorable employment prospects. College graduates with a bachelor's degree in computer science, computer engineering, information science, or MIS also should enjoy favorable prospects for employment, particularly if they have supplemented their formal education with practical experience. Because employers continue to seek computer specialists who can combine strong technical skills with good interpersonal and business skills, graduates with non-computer-science degrees, but who have had courses in computer programming, systems analysis, and other information technology areas, also should continue to find jobs in these computer fields. In fact, individuals with the right experience and training can work in these computer occupations regardless of their college major or level of formal education. So enough for the introduction let’s go to the definition.

A System Analyst is responsible for researching, planning, coordinating and recommending software and system choices to meet an organization's business requirements. The systems analyst plays a vital role in the systems development process. A successful systems analyst must acquire four skills: analytical, technical, managerial, and interpersonal. Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms. Management skills help systems analysts manage projects, resources, risk, and change. Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals. This was the definition that a Wikipedia.org gave to me as I researched it on the web. But for me, I think the definition of a system analyst is planning, analyzing, coordinating and recommending software and systems to the top management in order to meet the organization’s business goals.

So enough for the definition and functions of a system analyst, let’s go to the question of what skills that are needed for a systems analyst to develop in order to be more effective in designing any modeling process? And try to answer what are those skills that are needed to develop. There are four skills that a system analyst must develop in order to be more effective in designing any modeling process. These are the analytical skills, technical skills, management skills, and the communication skills. So, let us define each of them in order to explain why a system analyst must develop these types of skills.

First is the analytical skills, so what is an analytical skill? Analytical skill is the ability to see things as systems, identify, analyze, and solve problems in an optimal way for a specific organization. So from what is stated above, the ability to see things as a system, the ability to identify, the ability to analyze, and the ability to solve problems are the main concerns of a system analyst in the analytical aspect of a systems analyst. So a system analyst must develop these types of skills. As we all know that we can have all these skills but a system analyst must really develop in order to be more effective in designing any modeling process. So, enough for the analytical skill and lets go to the next one which is the technical skills.

The second one is the technical skills, so what is a technical skill? Technical skill is the ability to understand how computers, data networks, databases, operating systems, etc. work together, as well as their potentials and limitations. So from what is stated above, the ability to understand how computers, data networks, databases, operating systems, and etc. work together is the main concerns of a system analyst in the technical aspect of a system analyst. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. I think for me this very important that a system analyst must really develop in order to be more effective.

Technical skills needed by systems analysts include but are not limited to:
1. Computers (PCs, mini, mainframes, etc.)
2. Computer networks (LAN, WAN, VPNs, administration, security, etc.)
3. Operating systems (UNIX, Mac/OS, Windows)
4. Data Exchange Protocols (ftp, http, etc.)
5. Programming languages (C++, Java, XML, etc.)
6. Software applications (Office, project managements, etc.)
7. Information systems (databases, MISs, decision support systems)
8. System development tools and environments (such as report generators, office automation tools, etc.)

The third one is the management skills, so let me define what a management skill is all about. So what is a management skill? Management skill includes organization’s recourse management, project management (people and money), risk management, and change management. So to elaborate more it is just management skills help systems analysts manage projects, resources, risk, and change. So a system analyst must develop these types of skills in order to be more effective in designing any modeling process. They should be able to manage all the things that are needed to be manage in an organization such as resources, be able to properly disseminate all workforce in a project and properly manage it, be able to know the risk that are involve, and able to anticipate changes in the environment.

Managerial skills needed by systems analysts include but are not limited to:
1. Resource management - effectively managing the project’s resources, including time, equipment, hardware, software, people, money, etc.,
2. Project management - determining the tasks and resources needed for a project and how they are related to each other,
3. Risk management - identifying and minimizing risks,
4. Change management - managing the system’s (organization's) transition from one state to another

The last skill that a system analyst must develop is the communication skill. So let me define what communication skill is all about. So what is communication skill? Communication skill includes effective interpersonal communication (written, verbal, visual, electronic, face-to-face conversations, presentations in front of groups), listening, and group facilitation skills. To elaborate, communication skills are very important to develop in order for the system analyst and clients understand each other. Having good communication with client’s makes things go smoothly and properly. Poor communication leads to mismanagement and even resulting to a project failures, and etc.

Communication skills needed by systems analysts include:
1. Clear and effective interpersonal communication, whether written, verbal, or visual, from writing reports to face–to–face conversations, to presentations in front of groups;
2. Listening (accepting opinions and ideas from other project team members),
3. Group facilitation or formal technical reviews (FTR) skills:
· setting an agenda,
· leading discussions,
· involving all parties in the discussion,
· summarizing ideas,
· keeping discussions on the agenda, etc.

So these are the skills that a system analyst must develop in order to be more effective in designing any modeling process. A system analyst must develop the four skills that I listed in order to be more effective. All the four skills that I stated must be developed so that the goals on an organization can be attained. Because in an organization information is very crucial, so in order for the system analyst attain the goals of an organization and in order for the organization to prosper a system analyst must develop the analytical skill, technical skill, management skill, and the communication skill.

Skills

1. Understanding written sentences and paragraphs in work related documents.
2. Writing computer programs for various purposes.
3. Determining causes of operating errors and deciding what to do about it.
4. Analyzing needs and product requirements to create a design.
5. Communicating effectively in writing as appropriate for the needs of the audience.
6. Conducting tests and inspections of products, services, or processes to evaluate quality or performance.
7. Giving full attention to what other people are saying, taking time to understand the points being made, asking questions as appropriate, and not interrupting at inappropriate times.
8. Using logic and reasoning to identify the strengths and weaknesses of alternative solutions, conclusions or approaches to problems.
9. Talking to others to convey information effectively.
10. Identifying complex problems and reviewing related information to develop and evaluate options and implement solutions.

Knowledge

1. Circuit boards, processors, chips, electronic equipment, and computer hardware and software, including applications and programming.
2. Structure and content of the English language including the meaning and spelling of words, rules of composition, and grammar.
3. Principles and methods for curriculum and training design, teaching and instruction for individuals and groups, and the measurement of training effects.
4. Arithmetic, algebra, geometry, calculus, statistics, and their applications.
5. Principles and processes for providing customer and personal services. This includes customer needs assessment, meeting quality standards for services, and evaluation of customer satisfaction.

Abilities

1. Read and understand information and ideas presented in writing.
2. Communicate information and ideas in writing so others will understand.
3. Choose the right mathematical methods or formulas to solve a problem.
4. Listen to and understand information and ideas presented through spoken words and sentences.
5. Apply general rules to specific problems to produce answers that make sense.
6. See details at close range (within a few feet of the observer).
7. Communicate information and ideas in speaking so others will understand.
8. Come up with a number of ideas about a topic (the number of ideas is important, not their quality, correctness, or creativity).
9. Tell when something is wrong or is likely to go wrong. It does not involve solving the problem, only recognizing there is a problem.
10. Combine pieces of information to form general rules or conclusions (includes finding a relationship among seemingly unrelated events).

Tasks

1. Analyze information processing or computation needs and plan and design computer systems, using techniques such as structured analysis, data modeling and information engineering.
2. Assess the usefulness of pre-developed application packages and adapt them to a user environment.
3. Confer with clients regarding the nature of the information processing or computation needs a computer program is to address.
4. Define the goals of the system and devise flow charts and diagrams describing logical operational steps of programs.
5. Determine computer software or hardware needed to set up or alter system.
6. Develop, document and revise system design procedures, test procedures, and quality standards.
7. Expand or modify system to serve new purposes or improve work flow.
8. Interview or survey workers, observe job performance and/or perform the job in order to determine what information is processed and how it is processed.
9. Provide staff and users with assistance solving computer related problems, such as malfunctions and program problems.
10. Recommend new equipment or software packages.

In relation to what I have interviewed, he is a systems analyst of the Davao Light and Power Company. I won’t tell you the name for security purposes. He told us that based on what he had experienced as a system analyst, he stated that what a system analyst really need to develop in order to be more effective is communication, technical skills, how to model data, how to model processes, and administrative work. For communication, he stated that you must know hot to point something to the clients. You should know all the systems in an organization, develop and program systems, knows business functions and processes. So basically, these were the words that he stated during our interview regarding what are the skills and characteristics that a system analyst must develop.

Appendixes:



References:
Wikipedia.org
Google.com
http://jobs.virginia.gov/careerguides/computersystemsanalyst.htm

Assignment 1

What will I be 10 years from now?

Just thinking about it is hard, and thinking about it in the future is very stressful. But if you think of it thoroughly it’s your future at stake. Would you be having a very bright future or your life would be the same as what it is right now? There is one thing that I’m sure 10 years from now that I will be a graduate of my own University which is the University of Southeastern Philippines with a degree of Bachelor of Science in Information Technology. After making sure that I am already a college graduate, maybe 10 years from now I would have my own family. Maybe I have my own children to rise. Or maybe I would be very successful 10 years from now; we don’t know what will our future up ahead. We can’t tell what will our future will be but one thing for sure I think we can do something about it.

10 years from now, I want to be a successful and what they call “worthy” IT professional. I would be the boss for myself. Or a boss of my own company, IT company. These are only some of my dreams in life to be the boss for myself or a boss of an IT company. Talking about dreams, I will share some of my childhood experiences. To start, when I was a boy I really dream about someday I would be rich. That was really the first dream I wanted in my life to be very rich. But that was a dream so everyone can dream to be rich. As years goes by and I am getting older and having thoughts of my own from one dream it became dreams because my dreams multiplied or shall we say “added” from wanting to be rich and to become the computer master. That was the next dream I want to be when I grow up. I really don’t know why I thought of a thing in my mind that I want to be the master of computers. Maybe I thought of that because of the many influence by that time, such as temptations such as computer gaming. This was the time when online gaming was on the rise. Everyday I spend much time playing online games. After class I play online games or sometimes because of temptations I cut class just to play online games. By that time I also heard of the word IT or Information Technology. That word stuck in my mind as I finish my high school days. I thought that the course Information Technology is some related to computer gaming or just having knowledge about how to use a computer. By that time my mind had made a decision and the decision is to take up IT or Information Technology when I reach college. So these were initially why I wanted to take up IT or Information Technology. It was initially the reason why I took up Information Technology. But these things changed when I reach the college level. It was all shock from what I expected when I was in my high school days. I came unprepared to take up college with the course of Information Technology because of the initial thought about the word Information Technology. After able to adjust about the life on an Information Technology student and what is really the main description or shall we say the main role of Information Technology in reality. I soon realized that this is really what I want to become, to become an IT professional someday not just IT professional but a worthy IT professional. So in order to attain my goal of becoming a successful yet worthy IT professional these are the things that is needed to be done.

To graduate

In order to become a successful and worthy IT professional I really need to graduate to the course that I took up which is Bachelor of Science in Information Technology. We all know that we don’t need to graduate in order for us to be successful but I think from the word being “worthy” having a diploma is giving you a proof of being a “worthy” professional because it gives you a plus in all aspects and giving a proof that you have done all the required things in the Information Technology field. So it’s really a plus on your part if you can graduate from a course, not just IT but all other degrees. But what are the required things that you need to do in order to graduate? These are the things that you mind to list in your mind. First, is you need to study, study hard, and study well. You don’t need just study and you also don’t need just to study hard but you need all these aspects in order to have a good foundation. Just studying doesn’t count as worthy but you all need those aspects. Next is being a positive thinker. You study hard but you lack of motivations still you cant bare a good fruit from it so when you study you also need to be a positive thinker. It gives you a boost emotionally that you need when you are loosing hope in studying. So you need to be study but partner it with being a positive thinker. After securing it, the next thing you should do is what will be your forte or priorities?

Priorities

What will you are focusing at when you graduate and go to the real world? These are some things that you could be when you graduate in Information Technology.

· IT Consultant
· Software Engineer
· Programmer
· System Analysts
· Database Administrator
· Web Developer

These are some forte that you can choose from in setting up priorities. But I’m not saying that you only focus on one forte but what I really mean is that you identify your own strength. Are you good at programming, or are you a good web developer, and etc., these are just some way of identifying your strengths. So after identifying it, you can also identify where are your weaknesses are so by that you could work on your weakness in order to make it as a strength. So what I really mean is being flexible in all aspects. That can be considering a “worthy” IT professional. But all of these won’t work if you have a bad personality. If you don’t know how to collaborate with others even your good at something still you can’t be called worthy because you lack in Good Moral and Right Conduct. Having a good personality in this field is also important in being a worthy IT professional.

So I would explain more about them one by one from IT consultant until Web Developer.

IT Consultant - An IT consultant works in partnership with clients, advising them how to use information technology in order to meet their business objectives or overcome problems. Consultants work to improve the structure and efficiency and of an organization's IT systems. IT consultants may be involved in a variety of activities, including marketing, project management, client relationship management and systems development. They may also be responsible for user training and feedback. In many companies, these tasks will be carried out by an IT project team. IT consultants are increasingly involved in sales and business development, as well as technical duties.

Software Engineer - A software engineer is a person who applies the principles of software engineering to the design, development, testing, and evaluation of the software and systems that make computers or anything containing software, such as chips, work. Typically these are some of the work activities of a software engineer:

· researching, designing and writing new software programs;
· testing new programs and fault finding;
· developing existing programs by analyzing and identifying areas for modification;
· ‘bolting together’ existing software products and getting incompatible platforms to work together;
· investigating new technologies;
· creating technical specifications and test plans;
· working with computer coding languages;
· writing operational documentation with technical authors;
· maintaining systems by monitoring and correcting software defects;
· working closely with other staff, such as project managers, graphic artists, systems analysts, and sales and marketing professionals;
· consulting clients/colleagues concerning the maintenance and performance of software systems and asking questions to obtain information, clarify details and implement information;
· constantly updating technical knowledge and skills by attending in-house and/or external courses, reading manuals and accessing new applications;
· Problem-solving and thinking laterally as part of a team, or individually, to meet the needs of the project.

Programmer - A programmer is someone who writes computer software. The term computer programmer can refer to a specialist in one area of computer programming or to a generalist who writes code for many kinds of software. One who practices or professes a formal approach to programming may also be known as a programmer analyst. A programmer's primary computer language (Lisp, Java, Delphi, C++, etc.) is often prefixed to the above titles, and those who work in a web environment often prefix their titles with web. The term programmer can be used to refer to a software developer, software engineer, computer scientist, or software analyst. However, members of these professions typically possess other software engineering skills, beyond programming; for this reason, the term programmer is sometimes considered an insulting or derogatory oversimplification of these other professions. This has sparked much debate amongst developers, analysts, computer scientists, programmers, and outsiders who continue to be puzzled at the subtle differences in these occupations.

System Analysts - A systems analyst is responsible for researching, planning, coordinating and recommending software and system choices to meet an organization's business requirements. The systems analyst plays a vital role in the systems development process. A successful systems analyst must acquire four skills: analytical, technical, managerial, and interpersonal. Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms. Management skills help systems analysts manage projects, resources, risk, and change. Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals.
Because they must write user requests into technical specifications, the systems analysts are the liaisons between vendors and the IT professionals of the organization they represent. They may be responsible for developing cost analysis, design considerations, and implementation time-lines. They may also be responsible for feasibility studies of a computer system before making recommendations to senior management.

A systems analyst performs the following tasks:
· Interact with the customers to know their requirements
· Interact with designers to convey the possible interface of the software
· Interact/guide the coders/developers to keep track of system development
· Perform system testing with sample/live data with the help of testers
· Implement the new system
· Prepare High quality Documentation

Database Administrator - A database administrator (DBA) is a person responsible for the design, implementation, maintenance and repair of an organization's database. They are also known by the titles Database Coordinator or Database Programmer, and are closely related to the Database Analyst, Database Modeler, Programmer Analyst, and Systems Manager. The role includes the development and design of database strategies, monitoring and improving database performance and capacity, and planning for future expansion requirements. They may also plan, co-ordinate and implement security measures to safeguard the database. Employing organizations may require that a database administrator have a certification or degree for database systems (for example, the Microsoft Certified Database Administrator). The duties of a database administrator vary depending on job description, corporate and Information Technology (IT) policies and the technical features and capabilities of the DBMS being administered. They include disaster recovery (backups and testing of backups), performance analysis and tuning, data dictionary maintenance, and database design.

Web Developer - A web developer is a software developer or software engineer who is specifically engaged in the development of World Wide Web applications, or distributed network applications that are run over the HTTP protocol from a web server to a web browser. Web developers can be found working in all types of organizations, including large corporations and governments, small and medium sized companies, or alone as freelancers. Some web developers work for one organization as a permanent full-time employee, while others may work as independent consultants, or as contractors for an employment agency. Modern web applications often contain three or more tiers, and depending on the size of the team a developer works on, he or she may specialize in one or more of these tiers - or may take a more interdisciplinary role. For example, in a two person team, one developer may focus on the technologies sent to the client such as HTML, JavaScript, CSS, and on the server-side frameworks (such as Perl, Python, Ruby, PHP, Java, .NET) used to deliver content and scripts to the client. Meanwhile the other developer might focus on the interaction between server-side frameworks, the web server, and a database system. Further, depending on the size of their organization, the aforementioned developers might work closely with a web designer, web producer, project manager, software architect, or database administrator - or they may be responsible for such tasks as web design, project management, and database administration themselves.

So these are some description or definition of different forte that you can work in becoming a worthy IT professional. By focusing first on one forte and after mastering at it focus on your weaknesses. And that doesn’t end there you need to read and try to learn new technologies that are available in the market. Because we all know that the world is changing fast and it will become faster in the future so adapt to it and try to fit in so that you won’t be left behind in the ever fast changing environment.

So after attaining all of it the next thing to do is work hard in order to reach your goal. Seek help from the Lord and guidance. If you want to be rich be good at what you’re doing and save money.

So 10 years from now I would become a successful and worthy enough to be called “worthy” IT professional. I’m not sure what will be my future but my focus is to finish my schooling after that we will see.