Data Data is raw material & unorganized facts that need to be processed Information When data are processed,

organized, structured or presented in a given context so as to make them useful, they are called Information. System A set of detailed methods, procedures, and routines established or formulated to carry out a specific activity, perform a duty, or solve a problem. System is a software system which has components as its structure and observable Inter-process communications as its behavior. Analysis A systematic examination and evaluation of data or information, its component parts to uncover their interrelationships. by breaking it into

Analysis is an examination of data and facts to uncover and understand cause-effect relationships, thus providing basis for problem solving and decision making. System Analyst Systematically assesses how business functions by examining the inputting and processing of data and the output of the information with the extent of improving organizational process System Analyst Profession Standards of Practice Ethics Career path

Qualities of a system Analyst Problem Solver Communicator Self discipline, creative and innovative System Analyst Skills Analytical Able to understand the function, and problem "Creative problem solving abilities." Technical Managerial Manage projects, and resources

Strong organizational skills. ...the ability to handle multiple responsibilities and to adapt quickly to shifting priorities. Demonstrate leadership and professionalism." Interpersonal Help work with end users as well as with others "Excellent written and verbal communication skills."

Primary Role of a System Analyst Consultant A consultant hired specifically to address information system issues within a business. A consultant must be a problem Solver. Supporting Expert A supporting expert draws on professional expertise concerning computer hardware and software and their uses in the business. It is not managing the project merely serving a resources for those who are in need of the assistance. Agent of Change A person, who serves as catalyst for change, develops a plan for change and works with other in facilitating that change. Some qualifications of a System Analyst Ability to draw Flowchart Able to view system in many different perspectives Skill to interview users Application knowledge Computer skills to understand

What is Design? Design is the creative process of transforming the problem into a solution. Conceptual Design Tells the client exactly what the system will do. It describe the system in language that the client can understand. The conceptual design describes each of these system aspects by answering questions such as the following: Where will the data come from? What will happen to the data into the system? What will the system look like to the user? What choices will be offered to the users? What is the timing of the events? What will the reports and the system look like? Technical design describe the following

Hardware configuration Software needs Communication interfaces Input and output of the system The Network architecture and anything else that translate the customers problem into solution.

A good conceptual design should have the following characteristics It is written in customers/clients language It contains no technical jargons It describes the function of the system It is independent of implementation It is linked to the requirements document Five ways to create designs Modular decomposition Data-oriented Decomposition Event oriented decomposition Outside-in design Object oriented design

1. Modular Decomposition This construction is based on assigning functions to components. The designer begins with a high level description of the function that will be implemented and builds lower level explanations of how each will be organized and related to the other components. 2. Data-oriented Decomposition This design approach maps the systems external data structure into elements within the system. Provide detail on what data elements will be involved and how they related to one another. 3. Event-oriented Decomposition This is based on events that the system handles and includes states and state transition. 4. Object-oriented Design The design identifies classes of objects and their interrelationships 5. Outside-in Design This black box approach is based upon user inputs to the system. That is, the high level descriptions list all possible inputs a user can make. Lower level descriptions address what the system does with each input. Including what outputs are produced. Design Evaluation and validation Mathematical Validation Measuring design quality

Comparing design o One specification many design o Comparison table Design reviews o Preliminary design review Examines conceptual design with customer and users o Critical design review Presents technical design to developers o Program design review Programmers get feedback on their design before implementation

Preliminary design review participants The client who helped define the system requirement The analyst who helped define the system requirement The prospective users of the system The designer Moderator Secretary Other interested system developer who are not involved in this project Critical design review participants Analyst who helped define the system requirement System designer A moderator Secretary Program designer for this project Program design review Analyst who produced the system requirement System designer Program designer System tester Analyst who will be writing system documentation Developers Moderator Secretary Other interested system developer who are not involved in this project Questions for any design review Is it the solution to the problem? Is it modular, well-structured and easy to understand? Can we improve the structure and understandability? Is it portable to other platform? Is it reusable? Is it easy to modify or expand? Does it support ease of testing?

Does it maximize performance, where appropriate? Does it reuse components from other projects where appropriate? Are the algorithms appropriate or they can be improved? If this system is to have a phased development, are the phases interfaced sufficient so that there is an easy transition from one phase to the next? Is it well-documented including design choices and rationale? Does it cross-reference the components and data with the requirements? Does it use appropriate techniques for handling faults preventing failures?

Documenting the design Design rationale Menus and other display-screen formats Human interfaces, function keys, touch screen descriptions, keyboard layout, use of the mouse or joystick. Report formats Input: where data come from, how they are formatted on what media they are stored Output: where data are sent, how they are formatted on what media they are stored General functional characteristics Performance constraints Archival procedures Fault-handling approach