Analytical and Problem Solving Skills

22678 Views
9 Likes
0 Comments

In its simplest form, a Feasibility Study represents a definition of a problem or opportunity to be studied, an analysis of the current mode of operation, a definition of requirements, an evaluation of alternatives, and an agreed upon course of action. As such, the activities for preparing a Feasibility Study are generic in nature and can be applied to any type of project, be it for systems and software development making an acquisition, or any other project.

Author: Tim Bryce

9781 Views
1 Likes
0 Comments

Good question! What do you think?

This is an important question which is ultimately at the heart of a lot of the problems in systems and software development. There is one camp that believes development to be an art form requiring free-spirited creative types of people, and another camp believing it to be a science requiring people that are more disciplined and organized.

The difference between an art and a science is subtle but significant. An art form is based on the intuitiveness of the person performing the work, something that is difficult, if not impossible, to pass on to another human being. For example, apprentices serving under an artist may try for years to emulate the master, but may never attain his level of skill and creativity. In contrast, a science is based on a governing body of concepts and principles and, as such, can be easily taught to others.

Author: Tim Bryce

24032 Views
4 Likes
0 Comments

I always find it amusing when I tell a young person in this industry that I worked with punch cards and plastic templates years ago. Its kind of the same dumbfounded look I get from my kids when I tell them we used to watch black and white television with three channels, no remote control, and station signoffs at midnight. It has been my observation that our younger workers do not have a sense of history; this is particularly apparent in the systems world. If they do not have an appreciation of whence we came, I doubt they will have an appreciation of where we should be going. Consequently, I have assembled the following chronology of events in the hopes this will provide some insight as to how the systems industry has evolved to its current state.

I'm sure I could turn this into a lengthy dissertation but, instead, I will try to be brief and to the point. Further, the following will have little concern for academic developments but rather how systems have been implemented in practice in the corporate world.

Author: Tim Bryce

6229 Views
0 Likes
0 Comments
Just how important is it to fully develop your project’s requirements? After all, nailing down your requirements usually takes only 8% to 15% of your overall project effort. Truth be told, it’s not really something you’ll want to spend your resources and energy on—unless, that is, you care at all about the quality of your pr...
11046 Views
3 Likes
2 Comments
Author: Derrick Brown and Jan Kusiak This extract from IRM’s training material looks at how systematic, creative thinking techniques can be used to design practical solutions to business problems. The first step in developing a solution is to identify and define the problem - see the IRM paper Problem Analysis Techniques. Using the problem definit...
8139 Views
3 Likes
0 Comments
This extract from IRM's training material looks at how a structured approach to defining and analysing problems can be used as the basis for designing better solutions. Part 1 of this paper looks at problem definition. Part 2 introduces the reader to analytical techniques for determining the root cause of a problem. Future papers in this series wil...
Page 4 of 4First   Previous   1  2  3  [4]  Next   Last   




Latest Articles






Copyright 2006-2019 by Modern Analyst Media LLC