How does barmaid see?
MUHAMMAD AZEEM QURESHI
Contact Centers : Workforce Management and Quality Optimization Specialist
The main content of this article goes to the book on "SYSTEM ANALYST AND DESIGN" by KENNETH E. KENDALL and JULIE E. KENDALL.
System Analyst and Design:
Information Systems are developed for different purposes, depending on the needs of the business. Transaction processing systems (TPS) function at the operational level of the organization. Office Automation System (OAS) and Knowledge work system (KWS) support work at the knowledge level. Higher level systems include decision support systems (DSS) and management information system (MIS). Expert Systems apply the expertise of decision makes to solve specific, structured problems. On the strategic level of management we find executive support system (ESS). Group decision support systems (GDSS) aid group-level decision making of semi structured or unstructured way.
The title of this article, "How does barmaid see?" is the linguistic inspiration, understanding and comprehension taken from the Sanskrit language word "sAkSAtkAra" (means Interview in English), dialectally deciphered as per the default language brim up in my mind like English and Urdu, and when I recite and read this word "sAkSAtkAra" so it sounds like "SAQI KAISA TAAK RAHA" and I did jot the title, "How does barmaid see?"
"INTERVIEW" is the very powerful word of the world's most powerful language "ENGLISH".
If you want to study and understand the true meaning of the world's most powerful English word "INTERVIEW" then research and translate it into all languages of the world and recite/read it in the Roman English alphabet, trust me it will give you complete comprehension and understanding as per the default languages already brim up in your mind as my mind has ENGLISH and URDU.
For example, we say "INTERVIEW" in Sanskrit by following words:?
sAkSAtkAra, samAsyA, anyonyadarzana
The below link will lead you to enjoy researching the extremely high-level taste of WINE has filled with the perceptivity of intellectuals and intelligibility. (How to say?"INTERVIEW"?in Different Languages)
If you look at the above cover image, the title "TECH TALK" also gives a sound of Urdu words "THEEK THAAK" means "Alright, okay, ok, fine, good, all right, satisfactory, agreeable."
Interview Case Study | CPU STAFF MEMBER.
Respondent: Dorothy (Dot) Matricks, Manager, Micro Computer Systems
Interviewer: Anna Liszt
Location: Dorothy's Office
Anna: (Extending her hand as she enters Dorothy's office) Hello, Dorothy, its good to see you once again. I think we last saw each other when they had the reception for the new president.
Dot: (Rising from her shakes hand with from Anna) Please, call me Dot. And I remember that reception, too. It was fun. Please have a seat (She indicates a chair besides her desk) when I call Pat to put a hold on my phone calls. I didn't know at the time we would be working together. But (She continues with the Laugh). It seems sooner or later computer people find each other. I have heard through the grapevine that your group is contemplating helping us out of our quagmire here.
Anna: I am not sure it's "quagmire" but the administration has requested that the systems and programming group help you to manage your micros with the system of your own.
Dot: (Sits back with the chair with a chuckie) I could not be more delighted. That means my efforts to get some help or should I say my unabashed pleading, has not fallen on deaf eras. Tell me more.
Anna: I thought I would keep this first interview short, about an half an hour to forty five minutes (glancing at her watch). My overall objective is to find out about micro usage on campus currently, from your perspective. Later we can get into the system you use to manage the micros and its strengths and weaknesses.
Dot: It is easy enough to give an overview, since it's something I often communicate to people. Let me begin with a little history so you can understand where I am coming from. We started getting involved with micro in the early eighties. We though we were very high-tech to be buying them as fast as they were produced.
Anna: Yes, not many schools or even businesses had a plan for implementing micro computer systems.
Dot: Don't be misled by the haze of history. We purchased some micros early, mostly for the accounting areas. But we did not have a plan, except that we reacted to demand. The beginning was slow, but once hardware and software become available we grew explosively. Once a marketing professor saw what accounting was doing, he or she would say, "What's new for me? We don't to deal with the mainframe unless we have to." And so grew and grew.
We now have about 820 micros with three or four pieces of equipment attached to each one. Do you believe there is a total of more than 4,000 tagged items in our inventory? By the end of next fall, 200 more macros will be added. You have probably noticed that we have a mix of brands. IBM is used primarily in the business courses, and Apple Macs are used in the art department. Science areas like to use both IBM and Apple, it seems. Many of our computers are IBM compatibles.
Anna: (Nodding as she absorbs Dot's response) That's a lot for anyone to manage. But you seem to be up-ti-date on what you have in inventory. What systems are you using now to keep track of it all?
Dot: I have been here since the beginning and I honestly belive we have done better than most, but still the database system we use is indequate. Again, my analysis is that just like we outgrew our Apple IIs we have outgrown our management system. But we reluctant to fiddle with too much.
Anna: Why?
Dot: Well. I guess it's because something is better than nothing, even if something is antiquated. We try to resourceful. It all started in the mid-eighties. I, and the few other people who were assigned to the micros (on a part time basis, back then), began to realize that something had to be done to prevent chaos. People were asking on things and we could lay our brands on them. If they had ever been serviced, and so on. We sensed disaster in making. From our old mainframe experience, we started trying to organize what we have in logical way. We all agreed to get a system running with the little off-the-shelf database package (which was not user-friendly, may I be the first to point out), We had very much a family atmosphere at that time.
Anna: What function did the package perform?
Dot: It was very basic information, which is what we desperately needed at that time. It sounds simple now, but we took some time and we were thrilled to have inventory information, including the type of equipment, the manufacturer, room number where equipment was located, serial number, and equipment purchase date. Even that took extensive updating.
领英推荐
Anna: Is it the same system you run today?
Dot: Yes and no. Same Software, but we have been through three updates.
Anna: What other improvements were made?
Dot: After using the system for a couple of years, we know what we wanted. We added fields to capture the memory size on each micro and graphics boards were installed in the machines.
Anna: And is this the same system you are using now?
Dot: Yes. Yes it is. We can print a number of reports and summary information. But do not get the wrong impression. The system as it stands is clearly inadequate. You won't get much argument on that point from anyone you interview. But we did what we could with what we had at that time. In fact, there are still a few of the original group here. I will admit that it's been interesting to watch the micro grow. It makes me feel like I had a hand in helping develop a very important area.
Anna: What do you see as the strengths of the current system?
Dot: Since I was in it from the start. I find it fairly easy to use. And it's flexible enough to produce a variety of reports. It's brought us quite far and it does provide the elementary information required to manage the micros.
Anna: Earlier you alluded to some limitations of the system. What are the specific weaknesses you were speaking about?
Dot: (Reflecting before she speaks) In a way, they are not weaknesses of the system per se, but changes in the types of micros we are seeing that they system was not far-sighted enough to accommodate. For instance, the number of internal boards and disk drives has increased markedly. A few machines have modems, some have different graphic boards. EGA and VGA, and many have hard drives, but some macros micros just have two floppy drives. These drives also vary. Some use 5 1/4 inch disks and others use 3 1/2. We have no information on file regarding the components, and we ask many question each week, such as where can I find a machine with VGA graphics and a mouse?".
Another problem is that we do not have a concise report of which peripherals are connected to the machines, so we do not have a handle on what type of keyboard, printer, mouse or external drive until each micro uses. Memory is also a mixed bag. Some machines have 640K, some have 1 meg and some have other memory installed. You can imagine what it is like to try and fight the right memory installed. you can imagine what it is like to try and find the right memory to run a particular software package, Sometimes we run the software and run into problems.
Anna: How do you track what software is installed on which machine?
Dot: Well, unfortunately, we don't have a good grasp of that. We started to track it, but as I mentioned, the whole micro area is growing so fast. We spend so much time putting out brush fires that we are losing the battle to keep track of the information we have.
Anna: Are there similar problems with maintaining the equipment?
Dot: You are getting the idea, now. We fix whatever we can as soon as possible. Some of the machines are shipped out on warranty. We don't even dream of preventive maintenance, even though we are agreed that is is important.
Anna: Really, I am interested in what you are dreaming abut for the new system. What would you like it to accomplish?
Dot: That's easy for me to summarize. All of the weaknesses. I have outlined should be addresses. I would like to have a dossier about each machine - Its internal components, the peripherals attached to it. I would also like like to have good cost and repair information maintained. As changes occur, we need to keep the file up to date.
Anna: Anything specifically related to software?
Dot: Software cross referencing is the must.
Anna: One of the items I picked up on during our conversation today has been your dissatisfaction with the capability of the old system to keep pace with micros' growth. How would any future plans affect the system we develop?
Dot: Certainly we will be adding significant numbers of machines every year. The requests for machines far exceed the budget for several years. We expect that new technology will be adding new components, such as optical disks, that must be added to the system. Also, the use of laptop and notebook micros that actually leave the premises with users will probably grow. Perhaps they will be chucked out by individuals for teaching remote classes, research, curriculum development, and like.
Anna: (Glancing at her notes) We have covered quite a bit, I think I am beginning to understand what the old system does and does not do. What you would like to see in the new system, and what you project for growth in the coming years. Is there anything else that you think is important for me to know that I have not asked?
Dot: It's an oversight of mine, but i should mention that we also have micros on our satellite campuses in outlining areas. Those machines and all they entail need to be included in our system plans.
Anna: I know there are several people who can help with this project. Is there anyone in particular you would recommend that I talk to?
Dot: There are several people that you want to seek out. They will be very useful to us. Mike Crowe is our maintenance expert. He's been here almost as long as I have. You will enjoy him very much. Its counterpart in software is cherware. She is easy to talk with. Don't forget to touch base with Paige Prynter. She's in charge of financial information about the micros. She'll have what you need in that area. And Hy perteks runs information Center for us. Certainly, you will want to see him before you are done.
Anna: Yes. In fact, they are already on my schedule. We must be thinking alike. As I summarize our interview for the systems team. I may have some follow-up questions for you.
Dot: I am delighted to be part of this. Call me anytime.
Anna: (Standing up and extending her hand to Dot). Thanks very much for your time. The information you provided gave me a solid start. I will be back in touch.
Dot: (Shaking hands and standing) Let me know how I can help. My door is always open.
Thanks,
With Love and Sincerity,
Contact Center Workforce Management and Quality Optimization Specialist