I.

Introduction
In our previous discussions, the question, Can we come up with an information system without going through systems analysis phase was raised. And by now, we already know that yes we can indeed develop an information system without going through systems analysis but, we cannot be guaranteed that all the systems component parts have been considered. Systems analysis phase provides complete understanding of the business or system which will be an input to the development of an information system. This will enable the systems analysts to identify the exact problem and suggest probable solution to the users. Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.

II. Game Pass the characters

To energize the class a game was initiated. The objective of the game is to have each groups last receiver of the given alphanumeric character to write it on the board. The first group to write the given characters correctly on the board wins. The problem there is how will each member communicate the given characters to the person in front without speaking. The receiver of the characters cannot face the communicator. The class was divided into two groups wherein each group was asked to fall in line facing the facilitator. It is understood that the 1st character is an alphabet while the last 3 characters are numeric. The groups were given 3 minutes to discuss their technique on how they will communicate the given characters. In this game we have seen that each group had different techniques on how they communicate the characters but were both able to deliver the required output which is to write the given characters on the board. However, on the second round, group two applied the technique used by group one upon seeing that it is more effective. Likewise in systems analysis there are many approaches in solving a problem, some techniques may be used in combination with another to achieve a better result. The choice of what technique or approach to use also depends on what will work best on a given problem.

III. Lecture
A. Systems Analysis
Systems Analysis is defined as problem solving technique that decomposes a system into its component parts for the purpose of studying how well those component parts work and interact to accomplish its purpose. Context of Systems Analysis is a study of a system as a prerequisite to systems design. It is driven by the business concerns of SYSTEM OWNERS and SYSTEM USERS. It addresses the knowledge, process, and communications building blocks from system owners and system users perspectives Systems analysis is driven by the business concerns of system owners and system users. Hence, it addresses the KNOWLEDGE, PROCESS, and COMMUNICATIONS building blocks from system owners and system users perspectives. The documentation and deliverables produced by systems analysis tasks are typically stored in a repository. A repository may be created for a single project or shared by all projects and systems.

Repository is a location (or set of locations) where systems analysts, systems

designers, and system builders keep all of the documentation associated with one or more systems or projects. A repository is implemented as some combination of the following: A network directory of word processing, spreadsheet, and other computer generated files that contain project correspondence, reports, and data. Case tools dictionaries or encyclopedias Printed documentation An Intranet website

B. Systems Analyst
The systems analyst serves as the facilitator of a systems analysis. The systems analyst systematically assesses how the business function by examining the inputting and processing of data and the outputting of information with the intent of improving organizational processes.

C. Systems Analysis Approaches

There are many approaches to systems analysis. The most popular of which have been grouped into two.

1.

Model-Driven Analysis Approach

A problem-solving approach that emphasizes the drawing of pictorial system models to document and validate both existing and/or proposed systems. Ultimately, the system model becomes the blueprint for designing and constructing an improved system.

Examples of Models Used

Flowcharts See appendix A for a sample flowchart Structure or hierarchy charts Organization charts

See appendix B for an example of an organizational chart

Automated Tools Used

Visio Professional See appendix C for a screenshot of Visio Professional General purpose graphic software System Architect See appendix D for a screenshot of System Architect Visible Analyst Rational ROSE

Case tools offer the advantage of consistency and completeness analysis

a) Structured Analysis
Structured analysis is a model-driven, process-centered technique used to either analyze an existing system, define business requirements for a new system, or both. The models are pictures that illustrate the systems component pieces: processes and their associated inputs, outputs and files. It is still one of the most widely practiced approaches. The emphasis on this technique is on the process building blocks in the information system framework. Data Flow Diagrams Data Flow Diagram is a series of process models that depict the existing and/or proposed processes in a system along with their inputs, outputs, and files. The models show the flow of data between and through processes and show the places where data is stored. Process models serves as blueprints for business processes to be implemented and software to be purchased or constructed Simple Process Model/DFD

Business Process Redesign Through business process redesign, organizations seek to study the fundamental business processes to increase throughput and efficiency and reduce waste and costs.

a) Information Engineering and Data Modeling

Information Engineering and Data Modeling is a model-driven and datacentered, but process-sensitive, technique for planning, analyzing, and designing information systems. IE models are pictures that illustrate and synchronize the systems data and processes. IE focuses on the structure of data in a system and it emphasizes the study and requirements analysis of knowledge (or data) requirements before those of the process and communications requirements. This is based on the belief that knowledge and data are corporate resources and should be planned and managed. Entity Relationship Diagrams Entity relationship diagrams are data models in IE. IEs contribution was to define an approach for integrating and synchronizing data and process models. Systems analysts draw entity relationship diagrams to model the systems raw data before they draw the data flow diagrams that illustrate how that data will be captured, stored, used and maintained.

Simple Data Model (ERD)

Both information engineering and structured analysis attempt to synchronize data and process models. The two approaches differ only in which model is drawn first. Information engineering draws the data models first, while structured analysis draws the process models first.

b) Object-Oriented Analysis
Object-Oriented Analysis is a model-driven technique that integrates data and process concerns into constructs called objects. OOA is the encapsulation of the data (called properties) that describes a discrete person, object, place, event, or thing, with all the processes (called methods) that are allowed to use or update the data and properties. The only way to access access or update the objects data is to use the objects predefined process. OOA models are pictures that illustrate the systems objects from various perspectives such as structure and behavior, and interactions of the objects. Object technologies have emerged to eliminate the artificial separation of concerns about data and processes. Object represents a real person, place, event or transaction that is significant to the information system Attributes characteristics that describes an object Methods tasks or functions that an object performs

A Simple Object Model Some programming languages based on object technology Visual Basic, C++, Powerbuilder, Object Pascal, Smalltalk and Java Unified Modeling Languages (UML) OOA has become so popular that a modeling standard has evolved around it. UML defines several different types of diagrams that collectively model an information system or application in terms of objects.

Simple Object Model (UML)

2. Accelerated Systems Analysis Approach

Accelerated systems analysis approach emphasizes the construction of prototypes to more rapidly identify business and user requirements for a new system. Accelerated analysis approaches place much emphasis on the communications building blocks in the information system framework by constructing sample forms and reports. Prototype -a small-scale, incomplete, but working sample of a desired system.

a) Discovery Prototyping
Discovery prototyping is a technique used to identify the users business requirements by having them react to a quick-and-dirty implementation of those requirements. Systems analysts use a simple development tool like Microsoft Access to rapidly create a simple database, user input forms, and sample reports to solicit user responses as to whether the database, forms, and reports truly represent the business requirements. Prototypes cater to the Ill know what I want when I see it way of thinking that is characteristic of many users and managers. However, in discovery prototyping, users are discouraged from becoming preoccupied with the final look and feel of the system prototypes. Users can be misled to believe that the completed system can be built rapidly using prototyping tools. Using prototyping cannot completely replace model-driven design. Some amount of more formal design is still needed for prototyping.

b) Rapid Architected Analysis

Rapid architected analysis is an accelerated analysis approach that attempts to derive system models from existing systems or discovery prototypes.

Reverse engineering Reverse-engineering makes rapid architecture analysis possible through the use of automated tools such as CASE and programming languages. It is the use of technology that reads the program code for an existing database, application program, and/or user interface and automatically generates the equivalent system model. Reverse engineering can be applied to legacy information systems Prototypes

IV.Synthesis
Systems Development undergoes Systems Analysis to study the system and its component parts before proceeding to Systems Design. This step ensures that the problem is identified correctly before a solution will be made. An advantage of systems analysis is that it gives the systems analyst a clear picture of the business process, in the same way that the systems owners and systems users are given a chance to review their system and an opportunity to have their process redesigned to increase throughput and efficiency and reduce wastes and costs. Having mentioned this, it is important to note that systems analysis may be applied even if the goal is not to develop an information system. There are various approaches to solving a problem as there are various approaches to systems analysis. These approaches use tools and models to capture the business process. Some of the models are DFD, ERD and prototypes. The models enable the system owner and system users to visualize their business processes and its components and ultimately eliminate or reduce bureaucracy. The output of systems analysis which are the documentation and deliverables are used as an input to systems design which provides the specification of a new and improved system. Systems Analysis equips the systems designer to concentrate on the logical design of the system.

V. Appendices
Appendix A - Flowchart sample (Medical Dental System Clearance)

Appendix B Organizational Chart sample

Appendix C Visio Professional screenshot

Appendix D System Architect screenshot

VI.

References

Whitten, Bentley and Dittman, 2004, Systems Analysis and Design Methods, 6th Edition, McGraw-Hill Irwin Shelly, Cashman and Rosenblatt, 2001, Systems Analysis and Design, Course Technology, Cambridge, Massachusetts http://www.codebydesign.com/SystemArchitect/ http://intranet.dlsu.edu.ph/directory/offices