1. INFO 2000 Course Review Course Review Exam paper format

2. INFO 2000 Course Review Week 1: Chapter 1. Players in the system games For information systems, the stakeholders can be classified as: –System owners –System users –Systems analysts –System designers –System builders –IT vendors and consultants A stakeholder is any person who has an interest in an existing or new information system. Stakeholders can be technical or nontechnical workers.

3. Classes of Information Systems Transaction processing systems Management information systems Decision support systems Expert systems Office automation systems Week 1: Chapter 1. Players in the system games and classes of information systems

4. INFO 2000 Course Review Week 2: Chapter 3. Information System Development. F ramework for the A pplication of S ystems T echniques A system development methodology is a very formal and precise system development process that defines a set of activities, methods, best practices, deliverables, and automated tools that system developers and project managers are to use to develop and maintain information systems and software.

5. FAST System Development Phases Is this project worth? Scope, preliminary reg., constraints, participants, budget and schedule Technical Operational Economic Schedule Assisting users & Fixing bugs

6. Process of System Development A system development process is a set of activities, methods, best practices, deliverables, and automated tools that stakeholders use to develop and maintain information systems and software. An activity is any work which has a beginning and an end, and requires the use of company resources including people, time and money. Conducting a interview Designing a report Selecting a software A method provides a prescription for how to perform a collection of activities

7. INFO 2000 Course Review Week 3-4: Chapter 8. Process Modeling Process modeling is a technique for organizing and documenting the structure and flow of data through a system’s processes, and/or the logic, policies, and procedures to be implemented by a system’s processes. A data flow diagram (DFD) is a tool (and type of process model) that depicts the flow of data through a system and the work or processing performed by that system. DFDs have become a popular tool for business process redesign.

8. A simple process for making lunch

9. Data Flow Diagram Symbols Four basic symbols Process Data flow Data store External entity/agent

10. Data Flow Diagram Symbols  Process symbol Symbol is a rectangle with rounded corners Documented with process descriptions Receives input data and produces output Pay a bill OR Process No.

11. Data Flow Diagram Symbols  Data flow symbol Symbol is a line with an arrowhead showing direction A path for data to move from one part of the system to another Represents one or more data items At least one data flow must enter and exit each process Deposit

12. Data Flow Diagram Symbols  Data store symbol Symbol is a rectangle open on the right side Data store is also called a data repository Represents data that is retained for later processing Must be connected to a process with a data flow Must have at least one outgoing and incoming data flow

13. Data Flow Diagram Symbols  External entity/agent Symbol is a square, usually shaded Represents a person, organization, or other system that provides data or receives output from the system

14. Simple Data Flow Diagram

15. Illegal Data Flows CustomerEmployee CustomerEmployee Cancel the order

16. Illegal Data Flows Customer Cancel the order

17. Illegal Data Flows Customer Cancel the order

18. Illegal Data Flows Cancel the order

19. Levels of Data Flow Diagram

20. The context data flow diagram The first DFD in every business process is the Context data flow diagram. Top-level view that shows the systems’ boundaries and scope Represent the results of fact-finding One process symbol, numbered 0 (zero) is drawn in the center Each context diagram must fit on one page Process name in the context diagram should be the name of the information system

21. Rules for creating context data flow diagram Start by placing a single process symbol in the center of the page. The symbol represents the entire information system, and you identify it as process 0 Then place the external agents around the perimeter of the page and use data flows to connect the entities to the central process Do not show any data stores in a context diagram because data stores are internal to the system Place the external agents around the central process and label them Create labeled input and output data flows between the external agents and the central system

22. The context data flow diagram

23. Diagram 0 A context diagram provides the most general view of an information system Diagram 0 zoom in on the context diagram and shows major processes, data flows and data stores. Each process in diagram 0 has a reference number. Diagram 0 also represents the external agents and data flows that appear in the context diagram

24. Diagram 0

25. INFO 2000 Course Review Week 4-6: Chapter 7. Data Modeling An entity is something about which we want to store data. Examples: Student, University, Book, house etc An attribute is a descriptive property or characteristic of an entity. Examples: Student name, student address, student GPA. A relationship is a natural business association that exists between one or more entities. Relationships are important to identify and describe because they are the logical link between business functions. They can be interpreted in both directions between multiple entities. Example: Surgeon Operation

26. Why ERD To facilitate database design. To facilitate communication between the database designer and the end user. To enable the database designer to display the overall database view of the enterprise. Operation (Operation Number, Operation code, Surgeon Number*) Surgeon (Surgeon Number, Surgeon Specialty) The format of the above tables does not encourage a quick appreciation of the main concepts and rules. For example, each operation can be performed by only one surgeon is not immediately apparent. Surgeon Operation

27. Data Modeling Concepts: Cardinality Notations Cardinality Interpretation Minimum Instances Maximum Instances Graphic Notation Exactly one11 Zero or one01 One or more1Many Zero, one or more 0Many More than oneGreater than 1

28. Data Modeling Concepts: Relationships Draw the following relationships: Each department must have one head Each head must have one department Each employee can be awarded zero, one or more qualifications Each qualification can be awarded to zero, one or more employees Department Head One to one Employee Qualification Many to Many

29. Data Modeling Concepts: Identification A key is an attribute, or a group of attributes, that assumes a unique value for each entity instance. A primary key is a field whose values identify one and only one record in a file. A foreign key is a pointer to a record in a different file (A foreign key is an attribute or combination of attributes that is the primary key of another entity)

30. Database concepts (Primary and foreign keys)

31. Department number Department name 101Computer 102Math 103Physics 104Chemistry 101Engineering Department Program of study code Title of program Type of degree Department number 901ScienceMaster101 902MathMaster102 903ITMaster101 904ISMaster101 PhysicsMaster115 Curriculum

32. INFO 2000 Course Review Week 7: OO Analysis Concepts of OO Analysis and Design. UML diagrams. Use Case Modeling Class Diagrams Sequence Diagrams State Transition Diagrams Activity Diagrams

33. INFO 2000 Course Review Week 8-9: Chapter 6. Requirements discovery Requirement: Create a means to transport a single individual from home to place of work. I T Interpretation User Interpretation

34. INFO 2000 Course Review Phase in Which FoundCost Ratio Requirements1 Design3-6 Coding10 Development Testing15-40 Acceptance Testing30-70 Operation40-1000

35. INFO 2000 Course Review Questionnaires. Research and site visits. Observation of the work environment. Interviews. Prototyping. Joint requirements planning (JRP). Use case modeling and documenting

36. INFO 2000 Course Review Week 10: Chapter 10. Feasibility Analysis Operational feasibility is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system/project. Technical feasibility is a measure of the practicality of a specific technical solution and the availability of technical resources and expertise. Schedule feasibility is a measure of how reasonable the project timetable is? Economic feasibility is a measure of the cost- effectiveness of a project or solution.

37. INFO 2000 Course Review Week 11 Chapters 10, 12, 13, 14, 15 Systems Design Input design Output design Interface design

38. Types of outputs Internal outputs External outputs Turnaround outputs

39. Internal Outputs Internal outputs are intended for the internal system owners and system users within an organization. –Detailed reports present information with little or no filtering. –Summary reports categorize information for managers who do not want to wade through details. Increasingly presented in graphical formats using charts. –Exception reports filter detailed information before presenting it.

40. Detailed Report

41. Summary Report

42. Exception Report

43. External Outputs External outputs leave an organization.They are intended for customers, suppliers, partners, or regulatory agencies. Examples: Account statements, invoices, course schedule, Airline tickets, boarding passes, telephone bills and purchase orders.

44. External Document

45. Turnaround Outputs Turnaround documents are external outputs that eventually re-enter the system as inputs. Most “bills” and invoices include a stub to be returned by the customer with payment.

46. Turnaround Outputs

47. Bad Flow in a Form

48. Good Flow in a Form

49. INFO 2000 Course Review Week 12: Chapter 4. Project Management and Software Quality Assurance A project is a sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by specific time, within budget, and according to specification. Project management is the process of scoping, planning, staffing, organizing, directing, and controlling the development of an acceptable system at a minimum cost within a specified time frame.

50. Project Management Tools & Techniques A PERT chart is a graphical network model that depicts a project’s tasks and the relationships between those tasks. A Gantt chart is a simple horizontal bar chart that depicts project tasks against a calendar. Each bar represents a named project task. The tasks are listed vertically in the left-hand column. The horizontal axis is a calendar timeline.

51. PERT Chart 5-3-20015-12-2001 5-3-20015-11-2001 Preliminary Investigation 5-12-20016-12-2001 5-12-20016-14-2001 Problem Analysis 5-28-20017-15-2001 5-30-20017-18-2001 Requirements Analysis 6-13-20017-30-2001 6-13-20018-3-2001 Decision Analysis 9-10-200112-14-2001 TBD Implementation 7-19-200111-13-2001 7-20-2001In Progress Construction 7-3-20019-25-2001 7-5-200110-9-2001 Design 5-3-2001N/A 5-3-2001N/A Project Initiation Scheduled Start Scheduled Finish Actual Start Actual Finish Task intertask dependency Legend Scheduled Start Scheduled Finish Actual Start Actual Finish Task

52. Gantt Chart Incomplete Task Complete Task Legend ID 1 2 3 4 5 6 7 Preliminary investigation Problem analysis Requirements analysis Decision analysis Design Construction Implementation MayJunJulAugSepOctNovDec 2001 Task Name Today

53. Software Quality Assurance Understand the terms Quality, Software Quality, Software Quality Assurance, Understand the need for quality assurance of software products Capability Maturity Model (CMM)

54. Format of the paper Total time – 2 hours + 10 minutes reading time Total Questions - Eight Questions Combination of theoretical and practical questions Easy for those students who regularly attended their lectures and tutorials. Very difficult for those students who were not regular in their lectures and tutorials.

55. INFO 2000 Paper Format Two Questions from Process Modeling (Chapter 8) One Question about diagram zero and other general question about dataflow diagrams

56. INFO 2000 Paper Format One Question about Use Case Modeling and description Identify actors and use case Create a use case diagram Complete use case description document

57. INFO 2000 Paper Format Two Questions about Entity Relationship diagram

58. INFO 2000 Paper Format One Question about feasibility analysis (Chapter 9)

59. INFO 2000 Paper Format Two Questions from chapter reviews, lecture notes, text book: Briefly describe ….. What is the different between ….. What is …. Identify and briefly describe…….

60. INFO 2000 Paper Format GOOD LUCK