A competent computer professional needs to understand three different things
Introduction
Computerized systems appear in all kinds of organizations. This class is
about the best way to develop software solutions inside any organization. Unfortunately
(Principle 1): One Size Does Not Fit All.
You must learn enough skills and knowledge so you can fit them to the kind of organization and the kind of work that is needed. You must also learn to look at the organization your are working for and figure out what computers and software are best for it. You need to learn how to find out how the organization works, and how your work can best improve the way it works. Even if your initial job does not let you make these choices, promotion will depend on learning to this "Systems Analysis and Design" well.
This part of the course reviews the many kinds of organization and provides a kind of map of the possibilities.
You will find that in many real cases there are two distinct organizations involved: the client or customer system and the development system. You need to understand both because the kind of organization that is good at producing software is not the kind of organization that is good at producing and selling lead pencils. In a large enterprise you will have to learn how the part that develops software works, how the organization invests in new hardware, and how the rest of the organization operates. Then you have a chance of making changes that make you rich and famous -- or at least -- an unsackable employee.
If you are creating a new organization then you will need to know the different types of organizations so as to pick the best way for it to work. For example: a small enterprise is
often very loose and relies on face-to-face communication. But a big enterprise will
rely on paperwork and rules. So you need to find a way to move from your initial
small company to a larger one.
Stories about analyzing organizations
If they had analyzed the existing system better the electronic system might
be more useful than it's manual predecessor.
From Dr. Dobbs -- The Election Night Enigma and Other Stories
Halloween Horror Stories --
[ 184415199 ]
Stories of the top 10 Disasters from ZDNet.co.uk
Simple mistakes that "seemed OK at the time" can lead to expensive
results. Please look at these and see how they happened.
[ 0,1000000169,39290976-39001115c,00.htm ]
Story -- the case of the standing soldier
At the start of the second world war(circa 1940) in England the army discovered
that whenever an piece of artillery (big gun) was fired the manual instructed one
soldier to stand still behind and to the side of the gun. The soldier
didn't have anything to do. He just had to stand there.
Before they could be sure that they could change the procedure and so reduce the manpower involved they had to find out why the soldier had to stand there. So they worked their way through earlier manuals. In the 1914-18 version they found out what the soldier was supposed to do: hold the officer's horse!
Moral: Analyze the activities to find redundant ones.
Story -- Letter from Australia
A letter "Outsourcing Consequences", Letter IEEE Computer Magazine V39n8(Sep 2006)pp5+7 by Walter Hill
[ MC.2006.317 ]
argues that "legacy" systems contain large amounts of useful information
that needs to be preserved -- complex business rules, tested data
structures, etc. etc.
This meta-data (data about the data) should be analyzed and organized for future use.
. . . . . . . . . ( end of section Stories about analyzing organizations) <<Contents | End>>
Describe the kinds of Enterprise that we might be working in
I keep a website for the projects done by students at CSUSB: BA, BS, and MS. They were presented in the CSCI Department Seminar [ seminar/ ] series. Here some of the abstracts from a few presentations --
Web-based book exchange for CSUSB
This site has many features. It has a password authenticated administrator login feature that enables easy to edit and save member profiles, easy to download word documents, awards and scholarships component, archives component, on-line member nomination capability for faculty, details of the events held by the honor society, executive committee information and access to bulletin board.
The application is built on a MYSQL database for data storage and uses Java 2 Enterprise Edition (J2EE) technologies. Java Server Pages (JSP) (version 2.0) technology is used to implement the graphical user interface (GUI) and Servlets (version 2.4) handle the controller layer of the core functionalities. The Apache Tomcat application server (version 5.0) is used to host the website. These tools used to implement the Project are Open Source software tools which are free of cost and easy to download and install.
The goal of the internship was to redesign Public Works website. This presentation discusses some of the steps taken to redesign the website including the development of a database that displays employment opportunities and the development of online forms for making requests. The website and the online forms were created using HTML, VB, CSS,java_script, Adobe Photoshop CS, and Macromedia Dreamweaver MX 2006. This presentation also discusses the development of the website using ASP technology to interface an MS Access database.
The new website will incorporate all needed information for all six airports. This will include technical and weather information for the airports, services for each airport, administration contacts, and any current events that may be occurring at the airports. The website will be more user friendly and more interactive.
County Superintendent of Schools
Building and implementing a Network Diagnostic Tool server can solve this problem. The NDT is designed to quickly and easily identify a specific set of conditions that are known to impact network performance. An NDT server can determine: duplex mismatch conditions on Ethernet/FastEthernet links, incorrectly set TCP buffers in the user's computer, or problems with the local network infrastructure. Lastly, the test results may be easily emailed to the appropriate administrator to assist in the problem resolution phase. Implementing this server will allow the department to continuously monitor the computers on the network and diagnose the problems easily.
Flow Diagram of Manufacturing
Plotting the flow of materials is an excellent way to get an idea
of what a business is about. Money flows come next.
Information/data flows tend to run parallel material and money flow either
in the same direction or the opposite direction. They can electronic,
paper, speech, post it notes, memos, gestures, phone calls, email, ....
Here is a rough diagram
of how the parts are connected in a typical manufacturing
company.
The 6 business functions in the non-service sector
In a typical (larger) non-service sector enterprise
you will find the business organized not just by level but also by function.
You need to know the 6 classic functions:
You are likely to be working in IT but supporting the needs of the other five functions. So the next step is to look inside a typical IT department.
Structure of a typical IT Department circa 2006
In medium to large enterprises there will be a special
IT department that is in charge of the data and computers.
Here is a list of the parts in a typical IT department:
In a small enterprise you find that you have to fulfill all the above roles. In a large enterprise a team of people are dedicated to the above areas.
Job Titles in IT
You will find many specialist jobs within an IT department.
Here is list of typical titles, top-down.
Can you have people that do analysis and programming
Yes. In a small enterprise you will find yourself doing both programming and analysis.
In fact, if you are a people person who
can handle the technical details and debugging then this is the best organization.
What training must employees need to work in security
I don't have a quick list. You definitely need training in the tools of the trade.
You need to know the kinds of holes that have opened up in the past and have
knowledge to keep up with the upcoming problems.
You also need to know the underlying theory -- in particular network protocols,
cryptography, etc. etc.
Charles Handy (Op. Cit.) also distinguishes three kinds of work that
are needed in an enterprise:
| Flow | Face to Face | Paper | Electronic |
|---|---|---|---|
| one-to-one | Interviews, Informal | memo, letter | Phone, EMail, IM, SMS,... |
| one-to-many | Lectures/talks | memo, letter | mailing list, blog, ... |
| many-to-many | Meetings | - | Wikis,Google Docs, ... |
When you set up a meeting follow these guidelines (distilled from
half-a-dozen books on management):
When you attend meetings
. . . . . . . . . ( end of section Organization) <<Contents | End>>
Questions
. . . . . . . . . ( end of section Questions) <<Contents | End>>
Review Questions
. . . . . . . . . ( end of section Review Questions) <<Contents | End>>
. . . . . . . . . ( end of section Organizational Context of Systems Work) <<Contents | End>>
Also see
[ glossary.html ]
for more special abbreviations and phrases.
End