- WHO MAKES THE BEST SYSTEMS ANALYSTS?
Describes the attributes of Systems Analysts, both good and bad. - IS SYSTEMS DEVELOPMENT AN ART OR A SCIENCE?
Good question; what do you think? - ESTIMATING BY PERCENTAGES
Discusses the fallacy of project estimating by percentages of phase development. - STANDARD SYSTEM STRUCTURE
Proposes a standard model of Information Systems for use in design and development. - IMPLEMENTING A METHODOLOGY
The use of organized methodologies for the development of systems and software have been around for 35 years. Today, there are dozens, if not hundreds, of methodologies available for use. Regardless of what methodology you elect to use, there are some serious implementation considerations to ponder and it would be foolish not to look before you leap into one. - WHAT PRICE QUALITY?
f we lived in a perfect world, systems and software would be developed rapidly and inexpensively, they would effectively satisfy business needs, and would be easy to maintain and modify. There is only one problem with this scenario: it is a fantasy. - The Dichotomy of Systems Development Management
In order to be a Systems Development Manager, you have to be a lot of things: front man, educator, mentor, sage, politician, etc. Oh yea, something else, you also have to be a hypocrite. - MANAGING VIRTUAL PROJECT TEAMS
These are interesting times for managing systems development projects. In the old days (as late as the 1980's), whenever a development project was initiated, it was necessary to form a project team at a centralized geographical location in order to expedite communications between project members. But now we live in an age of electronic communications that provides greater flexibility in terms of allowing workers to work just about anywhere. - BOXES AND LINES
Until such time as we can master the Vulcan "mind meld," whereby we can transfer knowledge telepathically, there will always be a need for documentation. Its an inherent part of the design process and the principal deliverable produced by engineers and architects. Don't deny it, accept it. - The Ratio of Analysts to Programmers
Whether you call them Systems Analysts, Business Analysts, Systems Engineers, or Enterprise Architects, it is very encouraging to see this vital function being reintroduced to companies. As far as I am concerned, it was inevitable.
|
