QMIS331: Information System Analysis and Design (ISAD)

1. QMIS331:InformationSystem Analysis and Design (ISAD) By Dr. Aboul Ella Hassanien

2. Lecture Meeting and Location • Lecture Meeting: • Saturday • Monday • Wednesday • 8.00 8.50 • Location: Room # 311 • Office Hours: • Sat & Monday 9.00 -10.00

3. Required Text Book Modern System Analysis & Design, 4th Jefferey A. Hoffer, Joey F. George and Joseph. S. Valacich, Prentice-Hall, 2005

4. Course Objective • To provide you with new ways of looking at information in the world in order to solve business problems • To introduce you to concepts and methods of SAD • To describe the systems development life cycle (SDLC) • To teach you effective methods for gathering essential information during system analysis • To teach you effective methods for designing systems to solve problems effectively using technology

5. Chapter-1: The Systems Development Environment • Basic concepts of IS • System analysis and design definition • SAD: Discuss modern approach • Discuss Organizational Roles • System analyst • Information system types • SDLC :The System Development Life Cycle Using CASEtools (Computer Aided Software Engineering)

6. Systems Theory • What is a System? • Systems and Subsystems • Business organization as a Socio-technical system • Information Systems (IS) as a system

7. What is a System? • A collection of parts that work together to achieve a goal/task • Examples • Solar system • Digestive systems • Public transport system • Central heating system • Computer system • Information system • A set of objects and relationships among the objects viewed as a whole and designed to achieve a purpose

8. INPUT PROCESS OUTPUT FEEDBACK System Elements

9. Systems Can Be Composed of Subsystems System Elemental Part C Subsys A Subsys B SubsysB-1 Subsys A-1 Subsys A-2 SubsysB-2 Subsys A-3 Elemental part B1

10. What is subsystem? • A subsystem is simply a system within a system. • Automobile is a system composed of subsystems: • Engine system • Body system • Frame system • Each of these subsystem is composed of sub-sub --systems. • Engine system: carburetor system, generator system, fuel system, and so son

11. Bad Systems • Fail to meet requirements • Poor performance • Poor reliability • Lack of usability • Example difficulties: • Not to schedule • Not to budget • Runaway = 100% over budget or schedule • Some problems are simply “wicked” problems

12. Reasons for Failure • Complexity • Shifting requirements • Bad estimation • Bad management • New technology • Must tackle complexity by, for example: • Structure partitioning of problem • Organized interaction of parts • Ensure you achieve the task • Systems are subject to the need for continuing change

13. Important System Concepts • Decomposition • The process of breaking down a system into smaller components • Allows the systems analyst to: • Break a system into small, manageable subsystems • Focus on one area at a time • Concentrate on component pertinent to one group of users • Build different components at independent times 1.14

14. Important System Concepts • Modularity • Process of dividing a system into modules of a relatively uniform size • Modules simplify system design • Coupling • Subsystems that are dependent upon each other are coupled • Cohesion • Extent to which a subsystem performs a single function 1.14

15. Computer-based Information Systems (CBIS) vs Manual Systems • CBIS • Information system that rely on computer hardware and software for processing and disseminating information • Manual systems • Use paper + pencil technology

16. CBIS Components • A Computer-based Information System = Hardware + Software + People + Procedures + Information

17. Data and Information • Data are raw facts about the organization and its business transactions. Most data items have little meaning and use by themselves. • Alternative definition: • Data are a collection of items such as words, numbers, images, and sounds that are not organized and have little meaning individually • Data are raw facts about people, objects, and events in an organization • information: Data that is organized

18. Data flow and processing logic • Data flow: • Data in motion, moving from one place in a system to another • Processing logic: • The steps by which data are transformed or moved and a description of the events that trigger these steps

19. Processing logic example Events: H-W = 0 Event-action: If H-W > 40 then Pay = 40 *Pay-rate + (H-W – 40 ) *(1.5 *Pay-rate) Else Pay = Pay-rate *H-W End if -- H-W …. Worked Hours

20. Databases • A shared collection of logically related data designed to meet the information needs of multiple users in organization. • Database – Files – Records -- Fields

21. Levels of data managements

22. Payroll system Tax data Personal data Traditional vs database approach • Traditional approach Project Management System Personal data Project data Redundant data

23. Payroll system Tax data Personal data Traditional vs database approach • Database approach Project Management System Project data

24. Approach to system development • There are three strategies of IS development • Process-oriented approach • Data-oriented approach • Object-oriented approach

25. Process-oriented approach • An strategy to IS development that focuses on how and when data are moved through and changed by an IS • Data-oriented approach • An strategy to IS development that focuses on the ideal organization of data rather than where and how data are used. • Object-oriented approach • A system development methodologies and techniques base on objects rather than data or process

26. Application independence • The separation of data and the definition of data from the applications that the use these data

27. Example Process Oriented Approach Rent books system Rent house system Link Book data Personal data Personal data House data Is missing Rent books system Data oriented Rent house system Application independence House data Book data Personal data

28. Executive IS dept Dbase Admin. Director Operations Director Telecomm Director IS Devolp Manager IS dept Manger Programming Manager Voice Comm Manager Data Comm Your Role and Other Organizational responsibilities in systems development

29. What is an Information Systems? • Interrelated components working together to • Collect • Process • Store • Disseminate information To support decision making, coordination, control, analysis and visualization in an organization

30. WHAT IS A COMPUTER BASEDINFORMATION SYSTEM? A SYSTEM THAT USES COMPUTERS TO PROVIDE THE NEEDED INFORMATION What is an Information System? A SYSTEM THAT PROVIDES THE INFORMATION NEEDED TO ACCOMPLISH THE ORGANIZATION’S TASKS

31. Information System Types • Transaction Processing Systems (TPS) • Management Information Systems (MIS) • Decision Support Systems (DSS) • Expert System and Artificial Intelligence (ES &AI)

32. Transaction Processing Systems (TPS) • TPS are computerized information systems that were developed to process large amounts of data for routine business transaction. • Automate the handling of data about business activities and transactions, which can be thought of a simple discrete events in the life of an organization. • Data about each transaction are captured, • Transactions are verified and accepted/rejected, • Validation transactions are stored for later aggregation. • Report may be produced to provide summarization of the transactions, and • Transaction may be moved from process to process in order to handle all aspects of the business activities.

33. Management Information Systems (MIS) • Information system at the management level of an organization that serves the functions of planning, controlling, and decision making by providing routine summary and exception reports. • It takes the relatively raw data available through a TPS and converts them into a meaningful aggregated form that mangers need to conduct their responsibilities. • Developing an MIS calls for a good understanding of what kind of information managers require and how managers use information in their jobs.

34. Decision Support systems(DSS) • Information system at the management level of an organization that combines data and sophisticated analytical models or data analysis tools to support semi-structured and unstructured decision making. • DSS are designed to help organizational decision make decision. • A DSS is composed of a: • Database ( may be extracted from a TPS/MIS) • Graphical/mathematical models for business process • User interface that provides a way to communicate with DSS

35. Expert System and Artificial Intelligence (ES & AI) • Knowledge representation describes the way an expert would approach the problem. It attempts to codify and manipulate knowledge rather than information, (for example if .. Then rule) • User communication with an ES via an interactive dialogue. • The ES asks questions ( that an expert would ask) and the end user supplies the answers. • The answers are then used to determine which rules apply and the ES provides a recommendation based on the rule. • Knowledge Engineers perform knowledge acquisition; they are similar with system analyst but are trained to use different techniques.

36. Information Systems Applications

37. System development for different IS types • 1- TIS • IS characteristic: • High volume, data capture focus • System development methods: • Process-oriented • Concern with capturing, validating, and storing data with moving data between each required step

38. System development for different IS types • 2- MIS • IS characteristic: • Draws on diverse yet predictable data resources to aggregate and sumamrize data • System development methods: • Data-oriented • Concern with understanding relationship between data so data can be accessed and summarize in a variety ways

39. System development for different IS types • 3- DSS • IS characteristic: • Provide guidance in identifying problem, finding and evaluating alternative solutions and selecting or comparing alternatives; potentially involves groups of decision making • System development methods: • Data- and decision logic orientation • Design of user dialogue; group communication may be key an access to unpredictable data may be necessary

40. System development for different IS types • 4-ES • IS characteristic: • Provide expert advice by asking users a sequence of questions dependent on prior answers that lead to a conclusion or recommendation • System development methods: • A specialized decision logic orientation in which knowledge is elicited from experts and described by rule or other form

41. Stakeholders: Players in the Systems Game • A stakeholder is any person who has an interest in an existing or new information system. Stakeholders can be technical or nontechnical workers.

42. Stakeholders Classification • For information systems, the stakeholders can be classified as: • IS manger • Systems analysts in systems development • Programmers in systems development • End user in systems development • Supporting End user development • Business managers in systems development • Other IS mangers/Technicians in system development

43. IS Manger in Systems Development • The manager of an IS department may have a direct role in the systems development process if the organization is small or I that is the manger’s style • IS mangers are more involved in allocating resources to and overseeing approved system development projects rather than in the actual project development process. • There are several IS mangers in any medium to large IS department. • The manger of an entire IS department may have the title Chief Information Officer and may report to the president or chairman of the firm. • Each division of the IS department will also have a manger • Director of IS development, IS operation manger, IS programmer director, etc.

44. Systems Analysts • Systems analysts are the key individuals in the systems development process. • A systems analyst studies the problems and needs of an organization to determine how people, data, processes, communications, and information technology can best accomplish improvements for the business. • The organizational role most responsible for the analysis and design of information systems.

45. Skills of a Successful Systems Analyst • Analytical skills • Understanding of organizations. • Problem solving skills • System thinking • Ability to see organizations and information systems as systems • Technical skills • Understanding of potential and limitations of technology. 1.45

46. Skills of a successful systems analyst • Managerial skills • Ability to manage projects, resources, risk and change • Interpersonal skills • Effective written and oral communication skills • Help you work with end user as well as other system analysts and programmers 1.46

47. The analyst is responsible • for: • The efficient capture of data from its business source, • The flow of that data to the computer, • The processing and storage of that data by the computer, and • The flow of useful and timely information back to the business and its people.

48. Variations on the Systems Analysts Title • A business analyst is a systems analyst that specializes in business problem analysis and technology-independent requirements analysis. • A programmer/analyst includes the responsibilities of both the computer programmer and the systems analyst. • Others • Systems consultant • Systems engineer • Information engineer

49. The Systems Analyst as a Facilitator

50. Skills Required by Systems Analysts • Working knowledge of information technology • Computer programming experience and expertise • General business knowledge • Problem-solving skills • Interpersonal communication skills • Interpersonal relations skills • Flexibility and adaptability • Character and ethics • Systems analysis and design skills