Dorothy llagas

ICMT 2-5

Systems analysis is the study of sets of interacting entities, including computer systems analysis. This field is closely related to requirements analysis or operations research. It is also "an explicit formal inquiry carried out to help someone (referred to as the decision maker) identify a better course of action and make a better decision than he might otherwise have made. The development of a computer-based information system includes a systems analysis phase which produces or enhances the data model which itself is a precursor to creating or enhancing a database (see Christopher J. Date "An Introduction to Database Systems"). There are a number of different approaches to system analysis. When a computer-based information system is developed, systems analysis (according to the Waterfall model) would constitute the following steps: System analyst A systems analyst researches problems, plans solutions, recommends software and systems, at least at the functional level, and coordinates development to meet business or other requirements. Although they may be familiar with a variety of programming languages, operating systems, and computer hardware platforms, they do not normally involve themselves in the actual hardware or software development. Because they often write user requests into technical specifications, the systems analysts are the liaisons betweenvendors and information technology professionals.[1] They may be responsible for developing cost analysis, design considerations, staff impact amelioration, and implementation time-lines. A systems analyst may: Identify, understand and plan for organizational and human impacts of planned systems, and ensure that new technical requirements are properly integrated with existing processes and skill sets. Plan a system flow from the ground up. Interact with internal users and customers to learn and document requirements that are then used to produce business requirements documents. Write technical requirements from a critical phase. Interact with designers to understand software limitations. Help programmers during system development, ex: provide use cases, flowcharts or even database design. Perform system testing. Deploy the completed system. Document requirements or contribute to user manuals. Whenever a development process is conducted, the system analyst is responsible for designing components and providing that information to the developer

Scope Definition Problem analysis Requirements analysis Logical design Decision analysis Types of Information Systems and Systems Development

Transaction Processing Systems (TPS) Automate handling of data about business activities (transactions) Management Information Systems (MIS) Converts raw data from transaction processing system into meaningful form Decision Support Systems (DSS) Designed to help decision makers Provides interactive environment for decision making Types of Information Systems and Systems Development Expert Systems (ES) Replicates decision-making process Knowledge representation describes the way an expert would approach the problem Use cases are a widely used systems analysis modeling tool for identifying and expressing the functional requirements of a system. Each use case is a business scenario or event for which the system must provide a defined response. Use cases evolved out of object-oriented analysis; however, their use as a modeling tool has become common in many other methodologies for system analysis and design. Office automation Office automation refers to the varied computer machinery and software used to digitally create, collect, store, manipulate, and relay office information needed for accomplishing basic tasks. Raw data storage, electronic transfer, and the management of electronic business information comprise the basic activities of an office automation system.[1] Office automation helps in optimizing or automating existing office procedures. The backbone of office automation is a LAN, which allows users to transmit data, mail and even voice across the network. All office functions, including dictation, typing, filing, copying, fax, Telex, microfilm and records management, telephone and telephone switchboard operations, fall into this category. As office methods evolved to take full advantage of new technologies, there was a corresponding increase in innovations tailor-made to optimize office processes.[2] Office automation was a popular term in the 1970s and 1980s as the desktop computer exploded onto the scene. Advantages are: Office automation can get many tasks accomplished faster. It eliminates the need for a large staff. Less storage is required to store data. Multiple people can update data simultaneously in the event of changes in schedule

Artificial Intelligence and Expert Systems There is a class of computer programs, known as expert systems, that aim to mimic human reasoning. The methods and techniques used to build these programs are the outcome of efforts in a field of computer science known as Artificial Intelligence (AI). Expert systems have been built to diagnose disease (Pathfinder is an expert system that assists surgical pathologists with the diagnosis of lymph-node diseases, aid in the design chemical syntheses (Example), prospect for mineral deposits (PROSPECTOR), translate natural languages, and solve complex mathematical problems(MACSYMA). Our purpose in writing this description of expert systems is to demystify these programs by revealing their surprisingly simple architecture, explaining a method by which they can be constructed inexpensively, and illustrating, using a simple example, the process by which they seem to reason.

1. Distinguishing Features In conventional computer programs, problem-solving knowledge is encoded in program logic and program-resident data structures. Expert systems differ from conventional programs both in the way problem knowledge is stored and used. An expert system is a computer program, with a set of rules encapsulating knowledge about a particular problem domain (i.e., medicine, chemistry, finance, flight, et cetera). These rules prescribe actions to take when certain conditions hold, and define the effect of the action on deductions or data. The expert system, seemingly, uses reasoning capabilities to reach conclusions or to perform analytical tasks. Expert systems that record the knowledge needed to solve a problem as a collection of rules stored in a knowledge-base are called rule-based systems. Grp decision support system An exciting new concept is emerging in the area of decision support. This involves the development of computer-based systems for use by groups of people who are jointly responsible for making decisions. Known as "Group Decision Support Systems" (GDSS) they can be useful to committees, review panels, executive board meetings, task forces, and groups of managers who work together on either a regular or one-time basis. The precise design of a GDSS will vary depending on the proximity of group members to one another and the duration of the decisionmaking session. This paper presents an overview of the GDSS concept and explores issues related to the design, implementation, and study of these systems. Roles of a system analyst SYSTEMS ANALYST AS CONSULTANT The systems analyst frequently acts as a systems consultant to humans and their businesses and, thus, may be hired specifically to address information systems issues within a business. Such hiring can be an advantage because outside consultants can bring with them a fresh perspective that other people in an organization do not possess. It also means that outside analysts are at a disadvantage because the true organizational culture can never be known to an outsider. As an outside consultant, you will rely heavily on the systematic methods discussed throughout this text to analyze and design appropriate information systems for users working in a particular

business. In addition, you will rely on information systems users to help you understand the organizational culture from others viewpoints. Information systems analysts and consultants conduct research, develop and implement information systems development plans, policies and procedures, and provide advice on a wide range of information systems issues. SYSTEMS ANALYST AS SUPPORTING EXPERT Another role that you may be required to play is that of supporting expert within a business for which you are regularly employed in some systems capacity. In this role the analyst draws on professional expertise concerning computer hardware and software and their uses in the business. This work is often not a full-blown systems project, but rather it entails a small modification or decision affecting a single department. As the support expert, you are not managing the project;you are merely serving as a resource for those who are. If you are a systems analyst employed by a manufacturing or service organization, many of your daily activities may be encompassed by this role. SYSTEMS ANALYST AS AGENT OF CHANGE The most comprehensive and responsible role that the systems analyst takes on is that of an agent of change, whether internal or external to the business. As an analyst, you are an agent of change whenever you perform any of the activities in the systems development life cycle (discussed in the next section) and are present and interacting with users and the business for an extended period (from two weeks to more than a year). An agent of change can be defined as a person who serves as a catalyst for change, develops a plan for change, and works with others in facilitating that change. Your presence in the business changes it. As a systems analyst, you must recognize this fact and use it as a starting point for your analysis. Hence, you must interact with users and management (if they are not one and the same) from the very beginning of your project. Without their help you cannot understand what they need to support their work in the organization, and real change cannot take place. If change (that is, improvements to the business that can be realized through information systems) seems warranted after analysis, the next step is to develop a plan for change along with the people who must enact the change. Once a consensus is reached on the change that is to be made, you must constantly interact with those who are changing. As a systems analyst acting as an agent of change, you advocate a particular avenue of change involving the use of information systems. You also teach users the process of change, because changes in the information system do not occur independently but cause changes in the rest of the organization as well. Qualities of a system analyst From the foregoing descriptions of the roles the systems analyst plays, it is easy to see that the successful systems analyst must possess a wide range of qualities. Many different kinds of people are systems analysts, so any description is destined to fall short in some way. There are some qualities, however, that most systems analysts seem to display. Above all, the analyst is a problem solver. He or she is a person who views the analysis of problems as a challenge and who enjoys devising workable solutions. When necessary, the analyst must be able to systematically tackle the situation at hand through skillful application of tools, techniques, and experience. The analyst must also be a communicator capable of relating meaningfully to other people over extended periods of time. Systems analysts need to be able to understand humans needs in interacting with technology, and they need enough computer experience to program, to understand the capabilities of computers, to glean information requirements from users, and to communicate what is needed to programmers.

They also need to possess strong personal and professional ethics to help them shape their client relationships. The systems analyst must be a self-disciplined, self-motivated individual who is able to manage and coordinate other people, as well as innumerable project resources. Systems analysis is a demanding career, but, in compensation, an ever changing and always challenging one. . Analytical Mind 2. Good Communication Skills 3. Good Organisation Skills 4. Self direction 5. Self discipline 6. Creative System development life cycle The system development life cycle (SDLC) is the traditional system development method that organizations use for large-scale IT Projects. The SDLC is a structured framework that consists of sequential processes by which information system are developed. 1. System Investigation 2. System Analysis 3. System Design 4. Programming and Testing 5. Implementation 6. Operation and Maintenance