Sie sind auf Seite 1von 85

System Analysis and Design: Sample Question

1. Draw a decision table for the following decision procedure for travelling to a place X: If the place you are travelling to is within 150km, take your car; if the place is between 150km and 600km, take a train if the travel is for a holiday, and a plane otherwise; for travel over 600km take a plane.

Example DFDs

Lower levels of Data Flow Diagrams


Process 8 in Figure 10 is chosen to be investigated in more detail. A level 2 DFD is constructed of this process in Figure 11.

Process boundary

Figure 11 A Level 2 DFD corresponding to Process 8 from the level 1 DFD in Figure 10

An example context diagram

A systems analyst collects the following information about a project she is working on for an auction house. To assist her, draw context and level 0 data flow diagrams . The auction house has selling customers, who want to put up an item for sale, and buying customers, who buy an item at an auction. Selling customers ask the auction house to sell an item on their behalf. The auction house decides whether to accept the request and maintains a record for all accepted requests. Buying customers register with the auction house and participate in auctions. Auctions are conducted by giving buying customers information about an item, then taking bids. The auction determines a buying customer for each item put up for sale. The sale is completed when the buying customer pays for the item. The auction house sends a portion of the sale income to the selling customer who put up the item for sale in the first place. Of course, the auction house keeps track of all auctions (which are conducted every few weeks) and all sales at each auction.

Consider the following (abstract) DFD. Find out all the (syntax) errors. Justify your answer.

We wish to draw the DFD for a distance education university. The enrolment process works as follows: Students send in an application form containing their personal details, and their desired course. The university checks that the course is available and that the student has necessary academic qualifications. If the course is available the student is enrolled in the course, and the university confirms the enrolment by sending a confirmation letter to the student. If the course is unavailable the student is sent a rejection letter.

1. Find out the suitable external entity (ies). (1) 2.Find out and describe the suitable DFD context level input(s) and output(s). (1) 3. Find out the Level 0 DFD data store (s) (1) Reconsider the scenario described in the previous question. Draw the level 0 DFD related to the above described scenario. A banking system is managing banking accounts for customers. Customers may be provided with saving accounts and/or cheque accounts. A customer requests details on his/her saving and/or cheque account(s) from a bank. First the system should check the identity of the customer, then the appropriate cheque/saving account information is retrieved and provided to the customer. 1. Draw the context DFD diagram related to the above scenario. Identify the external entities and the external inputs outputs We wish to draw the DFD level 0 of the above system: a. b. c. 2. Identify and describe briefly the required processes. Identify and describe briefly the required data stores Identify and describe briefly the required data flows Draw the resulting DFD level 0.

3. A department of a company has a supervisor and at least one employee. Employees must be assigned to at least one, but possibly more departments. At least one employee is assigned to a project, but an employee may be on vacation and not assigned to any projects. The important data fields are the names of the departments, the projects, the supervisors and the employees, as well as the supervisor and employee number and a unique project number. 4. 1. Draw the ER diagram related to the scenario described above. 5. 2. Select one many to many association from the drawn ER diagram and. transform this association and its attached entities into a set of relations

An airline reservation system offers the capability to print a report that displays the list of daily flights that connect two pre-defined airports. The displayed flight information are: week day, departure airport, arrival airport, flight number, departure time, arrival time, airplane type and the number of seats. Airport names: alphabetic string (maximum 20 characters) Flight numbers: alphanumeric string (first two characters are alphabetic ones, the following four characters are digit ones)- Example: RJ1234 Airplane type: alphanumeric string (first character is alphabetic one, the following three characters are digit ones)- Example: A320

Number of seats: Integer with 3 digits Week day: one digit (from 1 to 7) - Example: 1 for Monday. Time: HH:MM ( HH: 00 to 23; MM: 00 to 59). Suggest and design a layout for this report.

1. Bellow is a data flow diagram

P1

A,B,C

B, X

P3

B,Y
P2

D,E

E,Y

The logic of the processes P1, P2 and P3 are respectively as follows: Process P1: if A>B then B=A End if else Y=-1 end if Are there any miracle or black hole on the above DFD? Give your reason please. 2. Please state the advantages and disadvantages of using the internet as a application platform. 3.
ERD---Relational database Schema

Process P2: if D=E+100 then Y=1000

Process P3: Y=B*E

Customer
Name Address Phone AccountNumber

Order
OrderDate Tax GrandTotal

OrderItem
Price Quantity

InventoryItem
ItemName QuantityOnHand AverageCost

Draw ERD A library has many books and many readers. One reader can borrow many books, one book can be borrowed by many readers at different time. If a book is lent to a reader, the lending date and return date must also be recorded. Attributes about book and reader are given below: Book: book number, book name, author, price, publishing date, status; Reader: card number, reader name, gender, address, phone number;

Please draw an entity relationship diagram about book and reader, if necessary, add associative entity to represent the relationship between book and reader

Create event table and draw DFD(or from event table to DFD)

You are asked to develop a library management information system, the system contains only the following information: Book information including book number, book name, author, price, publishing date; Reader information including library card number, reader name, gender, address, phone number; Book lending and returning information including lending date and return date. Please answer the following questions based on the previous information and your reasonable assumptions: Create an event table listing the main events that the system must respond, include event name, trigger, source, activity, response, and destination for each event. Draw a context diagram and event-partitioned diagram(diagram0) for this system.

DFD---Structure chart

The following is an event-partitioned data flow diagram for library management, using transaction analysis technique to develop a structure chart for it.
1 Reader info Reader Register 2 Reader Deregister 3 Book info book register 4 Book number book deregister Book info Book lending info 4 Return book 4 Book Query Book query request Book information Reader info 4 Lend book Library card number book number book number

Library card number

1.

Draw Decision table/decision tree/structured English The rules of deciding the postage of a postal parcel is described as follows: if the parcel is to be sent by express, then the basic charge will be 6$/kg, otherwise the basic charge will be 4$/kg. If the distance is over 200km, then each kg will be charged for one more dollar. If the parcels weight is over 10kg, then another 0.5 dollar will be charged for each kg that exceeds 10 kg. Suppose a parcels weight is W kilograms, please draw a decision table to show the calculation of the postage for this parcel.

The InfoStar Corporation develops PC database software products that are sold for both the domestic and international market. Customers receiving the products are sent a set of additional fonts if they return (by mail) a warranty registration card that is included with the software and documentation. The following tasks are performed to process warranty registration cards. This process is a batch process. It is a child of process 5, ADD CUSTOMER REGISTRATION. Inspect the Warranty Registration Card received from the customer to ensure that the information is complete and accurate. Incomplete cards are placed in a reject box. Data entry operators key the Warranty Registration Card, thus creating a Warranty Registration File. A different data entry operator verifies the keyed data by reentering the Warranty Registration Card information. The data entry terminal compares the data previously keyed with the entry made by the second operator. Discrepancies are displayed. The Warranty Registration File is input to a batch edit program. Each record is checked for accuracy. Errors are printed on a Warranty Validation Report, and valid records are placed on a valid Warranty Registration File. The Valid Warranty Registration File is used as input, along with the Custom er Master File, into the Customer Warranty Update Program. Records are added or updated, depending on whether the customer exists on the Customer Master File. The Valid Warranty Registration File is used to print a series of mailing labels for sending ( by mail) the font software to the customer. 1) Identify the tasks/subtasks that should be part of the logical and physical diagrams. You may need to add tasks/subtasks. 2) Design a logical DFD for the process described above (processing Warranty Registration Cards) 3) Design a physical DFD for the DFD proposed in question (2). 4) Partition the physical data flow diagram in question (3), grouping processes as you deem appropriate. Explain why you partitioned the diagram in this manner.
Which of the following Information systems are aimed at improving the routine business activities on which all organizations depend? (a) Management Information systems (b) Decision support systems (c) Transaction processing systems (d)

Management support systems (e) Transaction Information systems. 2. Which of the following strategies are adopted if information requirements are not welldefined? (a) Rapid application development method (b) Structured analysis development method (c) Systems development life cycle method (d) Prototyping method (e) Spiral method. 3. Structured Programming involves: (a) functional modularization (b) localization of errors (c) decentralized programming (d) stress on analysis (e) stress on requirements gathering. 4. Which of the following is not a fact-finding technique? (a) Third party enquiry (b) Interview (c) Questionnaire (d) Record reviews (e) Observation. 5. Which of the following notation is not a part of data-flow diagram?

6.

Which of the following questions are useful in evaluating data flow diagrams? (a) Are there any unnamed components in the data flow diagram? (b) Are there any processes that do not receive input? (c) Are there any data stores that are input but never referenced?

(d) Both (a) and (b) above (e) All (a), (b) and (c) above. 7. In system design and development field what does spaghetti code mean? (a) programs written in unstructured languages. (b) well structured and well documented code. (c) program code that has many GOTO statements. (d) Both (a) and (c) above (e) Both (b) and (c) above. 8. Which of the following statements is false with respect to a Data Dictionary? (a) It is a repository of the elements in a system. (b) data dictionary and data store both are same (c) It manages detail (d) It communicates the common meanings for system elements and activities. (e) It documents system features. 9. Match the following and select the correct options given under

i) physical design A) Documentation ii) interview B) Type of output iii) Input design C) defines design specifications that are to be coded iv) Installation procedure D) a data gathering technique v) report E) Identification and design of

interfaces to enter data

(a) i-D, ii A, iii-B, iv C, v- E (b) i-C, ii D, iii-E, iv A, v- B (c) i-A, ii D, iii-B, iv C, v- E (d) i-D, ii A, iii-E, iv B, v- C (e) i-B, ii A, iii-D, iv C, v- E. 10. Cost-Benefit Analysis is performed during (a) Analysis phase (b) Design phase (c) Feasibility study phase (d) Implementation phase (e) Maintenance phase.

Answers

1.

Answer : (c)

Reason: Transactions produce loads of data everyday and Transaction processing systems aim at improving the routine business activities. 2. Answer : (d)

Reason: Prototyping is adopted if information requirements are not well-defined. 3. Answer : (a)

Reason: structured programming means splitting the overall task into well-defined subtasks. 4. Answer : (a)

Reason: Third party enquiry is not a technique to capture the requirements of the user. 5. Answer : (e)

Reason: The parallelogram is not used in drawing DFDs. 6. Answer : (e)

Reason: All the given questions are useful in evaluating the DFDs.

7.

Answer : (d)

Reason: extensive use of GOTO leads to spaghetti code. 8. Answer : (b)

Reason: data dictionary is for storing data about data where as data store is where actual data is stored . 9. Answer : (b)

Reason: After matching the both sides the correct option is (b). 10. Answer : (c)

Reason: During the Feasibility study the financial feasibility is also measured

System Analysis and Design / Tools for Systems Analysts Multiple Choice Questions
5.1.1 In a DFD external entities are represented by a (a) rectangle (b) ellipse (c) diamond shaped box (d) circle 5.1.2 A data flow can (a) only emanate from an external entity (b) only terminate in an external entity (c) may emanate and terminate in an external entity (d) may either emanate or terminate in an external entity but not both 5.1.3 A rectangle in a DFD represents (a) a process (b) a data store (c) an external entity (d) an input unit 5.1.4 External Entities may be a (a) source of input data only

(b) source of input data or destination of results (c) destination of results only (d) repository of data 5.1.5 By an external entity we mean a (a) unit outside the system being designed which can be controlled by an analyst (b) unit outside the system whose behavior is independent of the system being designed (c) a unit external to the system being designed (d) a unit which is not part of a DFD 5.1.6 A data store in a DFD represents (a) a sequential file (b) a disk store (c) a repository of data (d) a random access memory 5.1.7 A data flow can (a) only enter a data store (b) only leave a data store (c) enter or leave a data store (d) either enter or leave a data store but not both 5.1.8 A data cannot flow between a store and (i) a store (ii) a process (iii) an external entity (a) i and iii (b) i and ii (c) ii and iii (d) ii 5.1.9 Data cannot flow between two data stores because
V. Rajaraman/IISc. Bangalore M5/V1/July 04/1

1. a relationship between two things of the same type, such as one person being married to another person compound attribute unary (recursive) relationship*** n-ary relationship ternary relationship binary relationship 2. a group of computers of the same type that have the same operating environment and share resources computer network multicomputer architecture distributed computing target processing environment clustered architecture*** 3. a process with a data input that is never used to produce a data output black hole*** structured English miracle balancing 4. a computer that requests services from other computers on the network wide area network (WAN) middleware data layer client computer*** router server computer local area network (LAN) 5. software products used to help develop analysis and design specifications and completed system components tools*** techniques

6. the phase of the SDLC in which the system and programs are designed support phase design phase*** problem domain waterfall method implementation phase analysis phase help desk application planning phase 7. a system development methodology that focuses on strategic planning, data modeling, and automated tools, thought to be more rigorous and complete than the structured approach object-oriented approach structured approach information engineering*** 8. an occurrence that tells the system that an even has occurred, either the arrival of data needing processing or of a point in time response source activity trigger*** destination 9. the present value of dollar benefits and costs for an investment such as a new system tangible benefits net present valuee (NPV)*** return of investment (ROI) payback period / breakeven point cost/benefit analysis intangible benefits business benefits

10. the area of the user's business for which a system is being developed help desk application planning phase implementation phase problem domain*** analysis phase waterfall method support phase design phase 11. a system requirement that describes a function or process that the system must support transaction query functional requirement*** stakeholders system requirements technical requirement 12. writing statements in a programming language to define what each type of object does, including the messages the objects send to each other object-oriented programming (OOP)*** class diagram top-down programming 13. the assumption that events should be included during analysis only if the system would be required to respond under perfect conditions event table perfect technology assumption*** system controls 14. a role played by a user of the system use case scenario lifeline

actor*** implementation classes 15. defining all of the types of objects that do the work in the system and showing how the objects interact to complete tasks data flow diagram (DFD) entity-relationship diagram (ERD) object-oriented design object structured analysis object-oriented analysis*** 16. a texttual description of a data flow's content and internal structure decision tree process decomposition diagram data flow definition*** decision table structured English 17. classes in a class diagram needed for physical implementaiton, such as user-interface classes implementation classes*** actor scenario lifeline use case 18. a database that stores information about the system in a CASE tool, including models, descriptions, and references that link the various models together physical model spiral model sociotechnical systems repository*** rapid application development (RAD) logical model

19. a computer system that enables multiple people to participate with comments at the same time, each on his or her own computer group support system*** structured walkthrough mock-up joint application design prototype 20. organizing and directing of other people to achieve a planned result within a predetermined schedule and budget client user oversight committee project management*** milestone 21. any modeling technique that breaks the system into a hierarchical set of increasingly more detailed models data store process levels of abstraction*** external agent data flow 22. any model that shows what the system is required to do without committing to any one technology spiral model physical model rapid application development (RAD) logical model*** repository sociotechnical systems 23. support systems that allow a user to explore tha impact of available options or decisions executive information systems (EIS)

communication support systems transaction processing systems (TPS) decision support systems (DSS)*** management information systems (MIS) 24. the layer on a client-server configuration that contains the database wide area network (WAN) client computer middleware server computer router data layer*** local area network (LAN) 25. an external agent or actor that supplies data to the system trigger response source*** activity destination 26. one phase of the SDLC whose objective is to understand the user's needs and develop requirements planning phase support phase analysis phase*** waterfall method implementation phase problem domain help desk application design phase

27. the type or classification to which all similar objects belong cardinality / multiplicity identifier / key attribute relationship encapsulation methods data entities class*** 28. software that is already built and can be purchased as a package facilities management packaged software*** benchmark turnkey system enterprise resource planing request for proposal (RFP) 29. a phase that occurs after the system is installed analysis phase waterfall method design phase support phase*** implementation phase problem domain planning phase help desk application 30. a computer network where the distances are local, such as within the same building local area network (LAN)*** wide area network (WAN) router

server computer client computer data layer middleware 31. an intranet that has been extended outside of the organizaation to facilitate the flow of information Intranet virtual organization Internet extranet*** World Wide Web (WWW) 32. an arrow on a DFD that represents the movement of data among processes, data store, and external agents process data flow*** levels of abstraction data store external agent 33. an undesirable condition that occurs when too much information is presented to a reader at one time minimization of interfaces rule of 7 2 DFD fragment information overload*** context diagram event-partitioned system model (diagram 0) 34. a DFD that represents the system response to one event within a single process symbol rule of 7 2 information overload minimization of interfaces event-partitioned system model (diagram 0)

DFD fragment*** context diagram 35. a thing in the computer system that can respond to messages object-oriented analysis data flow diagram (DFD) structured analysis entity-relationship diagram (ERD) object*** 36. a loosely coupled group of people and resources that work together as though they were an organization World Wide Web (WWW) virtual organization*** Intranet extranet Internet 37. an event that occurs outside the system, usually initiated by an external agent or actor external event*** state event event temporal event 38. a particular sequence of activities within a use case; a use case may have several different scenarios implementation classes scenario*** use case actor lifeline 39. narrative memos, reports, or lists that describe some aspect of a system descriptive model***

diagrams and schematic representations of some aspect of a system mathematical model 40. a place where data is held pending future access by one or more processes data flow external agent levels of abstraction process data store*** 41. information systems that capture and record information about the transactions that affect the organization management information systems (MIS) communication support systems decision support systems (DSS) transaction processing systems (TPS)*** executive information systems (EIS) 42. the flow of control through a processing activity as it moves among people, organizations, computer programs, and specific processing steps activity-data matrix location diagram workflow*** activity-location matrix 43. benefits that accrue to the organization but that cannot be measured quantitatively or estimated accurately return of investment (ROI) cost/benefit analysis business benefits intangible benefits*** payback period / breakeven point tangible benefits net present valuee (NPV)

44. a symbol on a DFD that represents an algorithm or procedure by which data inputs are transformed into data outputs levels of abstraction data flow external agent data store process*** 45. the benefits that accrue to the organization; often measured in money cost/benefit analysis return of investment (ROI) payback period / breakeven point net present valuee (NPV) business benefits*** 46. a model that represents the hierarchical relationship among processes at different levels of abstraction decision table process decomposition diagram*** decision tree structured English data flow definition 47. all the people who have an interest in the success of a new system query system requirements technical requirement transaction functional requirement stakeholders*** 48. a program or program module that has one beginning and one ending, and each step in the program execution consists of sequence, selection, or repetition constructs structured analysis structured design

top-down programming structure chart structured program*** 49. the person or group who funds the project client*** project management oversight committee user milestone 50. a bar chart which represents the tasks and activities of the project schedule Gantt chart*** PERT/CPM 51. heirarchies that structure or rank classes from the more general superclass to the more specialized subclasses; sometimes called inheritance hierarchies associative entity aggregation generalization/specialization hierarchies*** inheritance 52. a relationship between three different types of things binary relationship compound attribute unary (recursive) relationship ternary relationship*** n-ary relationship 53. a system requirement that describes an operating environment or performance objective transaction query functional requirement system requirements

technical requirement*** stakeholders 54. strategies for completing specific system development activities techniques*** tools 55. the initial phase of the SDLC whose objective is to scope and plan the project design phase planning phase*** waterfall method application analysis phase help desk problem domain support phase implementation phase 56. a division of the SDLC in which similar activities are performed systems development life cycle phase*** project 57. a concept that allows subclasses to share characteristics of their superclasses aggregation associative entity inheritance*** generalization/specialization hierarchies 58. computer-aided system engineering tool designed to help systems analyst complete development tasks model CASE tool*** technique system development methodology

59. a single use or function performed by the system for those who use the system implementation classes actor use case*** scenario lifeline 60. the time period at which the dollar benefits offset the dollar costs tangible benefits business benefits cost/benefit analysis intangible benefits return of investment (ROI) net present valuee (NPV) payback period / breakeven point*** 61. the approach to distributing a system across several computers and locations distributed computing*** target processing environment clustered architecture computer network multicomputer architecture 62. the part of the client-server configuration that contains the user interface and other components to access the system three-layer architecture n-layer architecture / n-tiered architecture data layer business logic layer view layer*** 63. a relationship between n (any number) different types of things unary (recursive) relationship binary relationship

ternary relationship n-ary relationship*** compound attribute 64. the person of group who wil use the new system client project management oversight committee milestone user*** 65. a diagram showing the life of an object in states and transitions statechart diagram*** message use case diagram sequence diagram collaboration diagram interaction diagram 66. a collection of resources such as files and programs that can be accessed over the Internet useing standard protocols virtual organization extranet Internet Intranet World Wide Web (WWW)*** 67. a system that is part of a larger system system analysis system design information system system analyst system subsystem***

68. a process with a data output that is created out of nothing black hole structured English miracle*** balancing 69. the plan defining the technology and applications the information systems function needs to provide to support the organization's strategic plan information systems strategic plan*** strategic planning business process reengineering 70. graphical model descriptive model diagrams and schematic representations of some aspect of a system*** mathematical model 71. a group of dissimilar computers that are linked together target processing environment computer network distributed computing multicomputer architecture*** clustered architecture 72. a diagram showing the objects that collaborate together to carry out a use case collaboration diagram*** interaction diagram message sequence diagram use case diagram statechart diagram 73. a client-server architecture that contains the three layers of view layer, business logic layer, and data layer data layer

n-layer architecture / n-tiered architecture three-layer architecture*** business logic layer view layer 74. an attribute that uniquely identifies a thing relationship attribute cardinality / multiplicity encapsulation class methods identifier / key*** data entities 75. a description of the integrated information systems needed by the organization to carry out its business functions technology architecture plan enterprise resource planning (ERP) applications architecture*** 76. a process in which an organization commits to using an integrated set of software packages for key information systems technology architecture plan enterprise resource planning (ERP)*** applications architecture 77. an output, produced by the system, that goes to a destination source trigger destination response*** activity

78. an example of a final product that is for viewing only, not executable prototype group support system mock-up*** joint application design structured walkthrough 79. support systems that allow employees to communicate with each other and with customers and suppliers executive information systems (EIS) decision support systems (DSS) communication support systems*** office support systems transaction processing systems (TPS) management information systems (MIS) 80. the separation between the automated part of a system and the manual part of a system functional decomposition automation boundary*** supersystem system boundary 81. the behaviors all objects of the class are capable of attribute identifier / key cardinality / multiplicity methods*** relationship encapsulation data entities class 82. a method of systems development that consists of planning, analysis, design, implementation, and support phases phase

project systems development life cycle*** 83. a principle of model design that seeks simplicity by minimizing the number of interfaces or connections among model components rule of 7 2 minimization of interfaces*** context diagram DFD fragment event-partitioned system model (diagram 0) information overload 84. a naturally occurring association among specific things, such as an order is placed by a customer and an employee works in a department encapsulation class cardinality data entities relationship*** attribute multiplicity methods identifier / key 85. information systems that take information captured by transaction-processing systems and product reports that management needs for planning and control communication support systems executive information systems (EIS) decision support systems (DSS) management information systems (MIS)*** transaction processing systems (TPS) 86. the definition of specifications for functions to be provided by a system technical requirement

functional requirement system requirements*** 87. a DFD that models system requirements using a single process for each event in a system or subsystem minimization of interfaces information overload context diagram DFD fragment event-partitioned system model (diagram 0)*** rule of 7 2 88. the configuration of computer equipment, operating systems, and networks for the new system distributed computing target processing environment*** multicomputer architecture clustered architecture computer network 89. a larger system that contains other systems functional decomposition automation boundary supersystem*** system boundary 90. the process of specifying in detail how the many component parts of the information system should be physically implemented system analyst system design*** system analysis system information system subsystem

91. the part of a client-server configuration that contains the programs that implement the program logic of the application data layer three-layer architecture view layer n-layer architecture / n-tiered architecture business logic layer*** 92. a table that lists events in rows and key pieces of information about each event in columns event table*** system controls perfect technology assumption trigger 93. an attribute that contains a collection of related attributes unary (recursive) relationship n-ary relationship ternary relationship compound attribute*** binary relationship 94. information systems that provide information for executives to use in strategic planning management information systems (MIS) decision support systems (DSS) executive information systems (EIS)*** transaction processing systems (TPS) communication support systems 95. an occurrence at a specific time and place, that can be described and is worth remembering external event temporal event event*** state event

96. a technique that seeks to alter the nature of the work done in a business function with that objective of radically improving performance strategic planning information systems strategic plan business process reengineering*** 97. a technique to define requirements or design a system in a single session by having all necessary people participate together group support system structured walkthrough mock-up joint application design*** prototype 98. comprehensive guidelines to follow for completing every activity in the system development life cycle, including specific models, tools, and techniques CASE tool system development methodology*** model technique tool 99. an evaluation of a system against some standard packaged software facilities management turnkey system request for proposal (RFP) benchmark*** enterprise resource planing 100. dividing a system into components based on subsystems that in turn are further divided into subsystems automation boundary system boundary

functional decomposition*** supersystem 101. covering or protecting each object so that it contains values for attributes and methods for operating on those attributes, making the object a self-contained (and protected) unit cardinality / multiplicity attribute relationship class identifier / key methods encapsulation*** data entities 102. a complete system solution, including software and hardware, that can be turned over facilities management packaged software request for proposal (RFP) enterprise resource planing benchmark turnkey system*** 103. dividing more complex programs into a hierarchy of program modules structured program structured analysis structure chart structured design top-down programming*** 104. a relationship between an object and its parts aggregation*** associative entity inheritance generalization/specialization hierarchies

105. a diagram showing the sequence of messages between objects during a use case statechart diagram interaction diagram use case diagram message collaboration diagram sequence diagram*** 106. a table that describes the relationship between processes and the locations in which they are performed activity-data matrix activity-location matrix*** workflow location diagram 107. a variation of the system development life cycle that aims to speed up radically the development process using a variety of techniques rapid application development (RAD)*** logical model sociotechnical systems repository spiral model physical model 108. The process of understanding and specifying in detail what the informaiton system should do system analysis*** system analyst subsystem system design information system system

109. behavior that the system performs when an event occurs destination source response activity*** trigger 110. a process which executives try to answer questions about the company such as where they are now, where they want to be, and what they have to do to get there information systems strategic plan strategic planning*** business process reengineering 111. a review of the findings from your investigation and of the models built based on those findings mock-up group support system structured walkthrough*** prototype joint application design 112. a DFD that summarizes all processing activity within the system in a single process symbol information overload event-partitioned system model (diagram 0) minimization of interfaces DFD fragment rule of 7 2 context diagram*** 113. a method of scheduling a project based on individual tasks or activities Gantt chart PERT/CPM*** 114. a description of the hardware, software, and communications networks required to implement planned information systems enterprise resource planning (ERP)

technology architecture plan*** applications architecture 115. a series of formulas that describe technical aspects of a system descriptive model mathematical model*** diagrams and schematic representations of some aspect of a system 116. the availability of support staff to help the users with any technical or processing problem associated with an information system design phase application analysis phase support phase problem domain waterfall method help desk*** planning phase implementation phase 117. the communication between objects within a use case interaction diagram sequence diagram statechart diagram collaboration diagram use case diagram message*** 118. the number of associations that occur between specific things, such as a customer places many orders and an employee works in one department encapsulation cardinality / multiplicity*** identifier / key attribute

relationship methods data entities class 119. any model that shows how the system will actually be implemented physical model*** spiral model logical model sociotechnical systems rapid application development (RAD) repository 120. a private network that is accessible to a limited number of users, but which uses the same TCP/IP protocol as the Internet extranet virtual organization Internet Intranet*** World Wide Web (WWW) 121. benefits that can be measured or estimated in terms of dollars and that accrue to the organization return of investment (ROI) tangible benefits*** payback period / breakeven point net present valuee (NPV) cost/benefit analysis intangible benefits business benefits 122. information systems that include both social and technical subsystems designed to work well together repository rapid application development (RAD)

physical model logical model spiral model sociotechnical systems*** 123. support systems that help employees create and share documents, including reports, proposals, and memos management information systems (MIS) executive information systems (EIS) communication support systems transaction processing systems (TPS) decision support systems (DSS) office support systems*** 124. one piece of specific information about a thing data entities encapsulation class identifier / key cardinality / multiplicity attribute*** methods relationship 125. a global collection of networks that use the same networking protocol - TCP/IP Intranet Internet*** extranet virtual organization World Wide Web (WWW) 126. a table that describes stored data entities, the locations from which they are accessed, and the nature of the accesses activity-data matrix***

location diagram activity-location matrix workflow 127. a data entity that represents a many-to-many relationship between two other data entities generalization/specialization hierarchies associative entity*** inheritance aggregation 128. clients and management who review and direct the project, like a board of trustees for a company client milestone oversight committee*** user project management 129. questions that have a simple definitive answer close-ended questions*** open-ended questions 130. a client-server architecture that contains n layers business logic layer n-layer architecture / n-tiered architecture*** view layer three-layer architecture data layer 131. a graphical model showing the hierarchy of program modules produced in a structured design structured program structure chart*** top-down programming

structured analysis structured design 132. life cycle moel with heavy iteration that breaks each project into smaller pieces, each with a different type of "risk" physical model spiral model*** logical model sociotechnical systems rapid application development (RAD) repository 133. a method of writing process specifications that combines structured programming techniques with narrative English balancing miracle black hole structured English*** 134. a planned undertaking that has a beginning and an end, and which produces a predetermined result or product phase project*** 135. a graphical model of the data needed by a system including things about which information is stored and the relationships among them, produced in structured analysis and information engineering object-oriented analysis object entity-relationship diagram (ERD)*** structured analysis data flow diagram (DFD) 136. either a collaboration diagram or a sequence diagram that shows the interactions between objects statechart diagram

use case diagram collaboration diagram interaction diagram*** message sequence diagram 137. a request for information from a system or from a database stakeholders transaction system requirements technical requirement query*** functional requirement 138. a formal document, containing details on the system requirements, sent to vendors to request that they bid on supplying hardware, software, and/or support services facilities management request for proposal (RFP)*** benchmark turnkey system packaged software enterprise resource planing 139. a piece of equipment that is used to direct information within the network server computer router*** local area network (LAN) wide area network (WAN) data layer client computer middleware 140. a measure of the percentage gain received from an investment such as a new system business benefits

return of investment (ROI)*** cost/benefit analysis net present valuee (NPV) payback period / breakeven point intangible benefits tangible benefits 141. a single occurrence of a piece of work or an activity done in an organization system requirements functional requirement stakeholders query technical requirement transaction*** 142. a collection of interrelated components that function together to achieve some outcome system design system analysis system analyst subsystem information system system*** 143. the rule of model design that limits the number of model components or connections among components to no more than nine DFD fragment information overload context diagram event-partitioned system model (diagram 0) minimization of interfaces rule of 7 2*** 144. a turnkey system that includes all operational functions of an organization benchmark

packaged software request for proposal (RFP) turnkey system enterprise resource planing*** facilities management 145. a tabular list of all the functions to be included within a system scoping table*** 146. a method of executing an SDLC where one phase leads (falls) to the next phase help desk support phase design phase waterfall method*** application analysis phase planning phase implementation phase problem domain 147. the outsourcing of all data processing and information technology to an outside vendor benchmark facilities management*** packaged software request for proposal (RFP) turnkey system enterprise resource planing 148. an event that occurs as a result of reaching a point in time event temporal event*** state event external event

149. the analysis to compare costs and benefits to see whether the investment in the development of a new system will be more beneficial than costly cost/benefit analysis*** business benefits intangible benefits tangible benefits return of investment (ROI) net present valuee (NPV) payback period / breakeven point 150. a representation of some important aspect of the real world CASE tool model*** technique system development methodology 151. defining all of the types of objects necessary to communicate with people and devices in the system and refining the definition of each type of object so it can be implemented with a specific language or environment object object-oriented analysis structured analysis object-oriented design*** data flow diagram (DFD) entity-relationship diagram (ERD) 152. a business professional who uses analysis and design techniques to solve business problems using information technology system subsystem information system system analysis system design system analyst***

153. relationships between two different types of things, such as customer and an order compound attribute ternary relationship unary (recursive) relationship binary relationship*** n-ary relationship 154. an event that occurs when something happens inside the system that triggers the need for processing state event*** temporal event event external event 155. a tabular representation of processing logic containing decision variables, decision variable values, and actions or formulas decision tree structured English data flow definition decision table*** process decomposition diagram 156. checks or safety procedures put in place to protect the integrity of the system system controls*** perfect technology assumption event table 157. a person or organization, outside the boundary of a system, that provides data inputs or accepts data outputs data store external agent*** process levels of abstraction data flow

158. the separation between a system and its environment that inputs and outputs must cross automation boundary supersystem system boundary*** functional decomposition 159. the phase of the SDLC in which the new system is programmed and installed help desk support phase design phase waterfall method application problem domain planning phase analysis phase implementation phase*** 160. a diagram to show the vsrious user roles and how those roles use the system collaboration diagram statechart diagram message interaction diagram sequence diagram use case diagram*** 161. the things the system needs to store information about in the traditional approach to information systems methods encapsulation class identifier / key attribute cardinality / multiplicity

data entities*** relationship 162. a collection of interrelated components that collect, process, store, and provide as output the information needed to complete business tasks system analysis information system*** system design system system analyst subsystem 163. a computer that provides services to other computers on the network router data layer local area network (LAN) wide area network (WAN) server computer*** client computer middleware 164. a collection of guidelines that help the analyst complete a system development activity or task CASE tool technique*** system development methodology model 165. the portion of the new information system that satisfies the user's needs in the problem domain planning phase problem domain waterfall method implementation phase analysis phase

help desk application*** support phase design phase 166. a graphical model showing the inputs, processes, storage, and outputs of a system produced in structured analysis data flow diagram (DFD)*** structured analysis entity-relationship diagram (ERD) object object-oriented analysis 167. a graphical model that shows all of the classes of objects in the system in the object-oriented approach object-oriented programming (OOP) class diagram*** top-down programming 168. questions that require discussion and do not necessarily have a simple short answer open-ended questions*** close-ended questions 169. a preliminary working model of a larger system structured walkthrough joint application design prototype*** mock-up group support system 170. a set of transmission lines, equipment, and communication protocols to permit sharing of information and resources distributed computing target processing environment multicomputer architecture

clustered architecture computer network*** 171. a technique that helps the developer define what the system needs to do (the processing requirements), what data the system needs to store and use (data requirements), what inputs and outputs are needed, and how the functions work together overall to accomplish tasks object-oriented analysis structured analysis*** object data flow diagram (DFD) entity-relationship diagram (ERD) 172. an event in the project schedule to denote the completion of a predetermined portion project management user client oversight committee milestone*** 173. a technique providing guidelines for deciding what the set of programs should be, what each program should accomplish, and how the programs should be organized into a hierarchy structured analysis structure chart structured design*** structured program top-down programming 174. a diagram or map that identifies all of the processing locaitons of a system activity-data matrix workflow location diagram*** activity-location matrix 175. computer software that implements communication protocols on the network and helps different systems communicate data layer

server computer router wide area network (WAN) local area network (LAN) client computer middleware*** 176. equivalence of data content between data flows entering and leaving a process and data flows entering and leaving a process decomposition DFD black hole miracle balancing*** structured English 177. a computer network across large distances such as a city, state, or nation local area network (LAN) middleware client computer server computer router data layer wide area network (WAN)*** 178. an approach to systems development that views an information system as a colleciton of interacting objects that work together to accomplish tasks information engineering structured approach object-oriented approach*** 179. a graphical description of process logic that uses lines organized like branches of tree data flow definition structured English decision table

decision tree*** process decomposition diagram 180. an external agent or actor that receives data from the system trigger response activity source destination*** 181. system development using structured programming, structured analysis, and structured design techniques information engineering structured approach*** object-oriented approach
What category of information system determines the sale of an item and a withdrawal from an ATM? (a) Management Information System (b) Executive Information System (c) Decision Support System (d) Communication Support System (e) Transaction Processing System. 32. Which of the following is not true regarding the waterfall method? (a) Fairly rigid approach (b) Can easily go back to previous phases (c) Good for traditional type of projects (d) Not as good for many of the new types of interactive and highly complex applications (e) This approach is less used now. 33. Which feasibility determines the availability of team and support staff?

(a) Economic Feasibility (b) Cultural Feasibility (c) Technological Feasibility (d) Schedule feasibility (e) Resource Feasibility. 34. Which among the following is an intangible benefit? (a) Maintaining constant staff (b) Decreasing operating expenses (c) Survival (d) Reducing error rates (e) Ensuring quicker processing and turnabout. 35. Which chart is represented by vertical bars? (a) PERT (b) ROI (c) GANTT (d) NPV (e) CPM. 36. Which of the model is used for system components? (a) PERT chart (b) Gantt chart (c) Organizational hierarchy chart (d) CPM (e) DFD. 37. Which is not used in context level diagram? (a) Source (b) Destination (c) Data flow (d) Data Store (e) Process.

38.

Which of correct?

the following statement(s)

is/are

I. Program modules should be loosly coupled. II. Program modules should be highly cohesive. III. Program modules should be highly coupled. (a) Only (I) above (b) Only (II) above (c) Only (III) above (d) Both (I) and (II) above (e) Both (I) and (III) above. 39. Which of the following is not a resource for setting JAD sessions? (a) Overhead projector (b) Black or white board (c) Flip chart (d) Adequate work space (e) All of the above. 40. What will help the system analyst to work with users to determine system usage? (a) Use case (b) Actor (c) Class (d) Component (e) Package.

Answers

31.

Answer : (e)

Reason: TPS capture and record information about the transactions that affect the organization like the sale of an item, a withdrawal from ATM etc. 32. Answer : (b)

Reason: Cant easily go back to previous phases as each phase would get signed off. 33. Answer : (e)

Reason: Resource feasibility determines availability of team, computer resources, and support staff. 34. Answer : (c)

Reason: Maintaining Constant staff, decreasing operating expenses, reducing error rates and ensuring quicker processing and turnabout fall into the category of tangible costs which can be measured in terms of money whereas survival cant me measured. 35. Answer : (c)

Reason: PERT/CPM is represented by rectangles whereas ROI and NPV are Return on investment and net present value. 36. Answer : (e) Reason: Models to manage the development process are: PERT / CPM chart Gantt chart Organizational hierarchy chart Whereas DFD model is used for system components. 37. Answer : (d) Reason: In context level diagram data store is not used. 38. Answer : (e) Reason: Program modules should be loosly coupled and highly cohesive. 39. Answer : (e)

Reason: Usually JAD sessions are conducted in special rooms, Off-site location may be good, but need access (phone etc.) to executives and technical staff not present. Resources required are Overhead projector, Black or white board, Flip chart, adequate work space. 40. Answer : (a) Reason: System analyst uses use case to work with users to determine system usage. Which of the following Information systems are aimed at improving the routine business activities on which all organizations depend? (a) Management Information systems (b) Decision support systems (c) Transaction processing systems (d) Management support systems

(e) Transaction Information systems. 2. Which of the following strategies are adopted if information requirements are not well-defined? (a) Rapid application development method (b) Structured analysis development method (c) Systems development life cycle method (d) Prototyping method (e) Spiral method. 3. Structured Programming involves: (a) functional modularization (b) localization of errors (c) decentralized programming (d) stress on analysis (e) stress on requirements gathering. 4. Which of the following is not a fact-finding technique? (a) Third party enquiry (b) Interview (c) Questionnaire (d) Record reviews (e) Observation. 5. Which of the following notation is not a part of data-flow diagram?

6.

Which of the following questions are useful in evaluating data flow diagrams? (a) Are there any unnamed components in the data flow diagram? (b) Are there any processes that do not receive input? (c) Are there any data stores that are input but never referenced? (d) Both (a) and (b) above (e) All (a), (b) and (c) above.

7.

In system design and development field what does spaghetti code mean? (a) programs written in unstructured languages.

(b) well structured and well documented code. (c) program code that has many GOTO statements. (d) Both (a) and (c) above (e) Both (b) and (c) above. 8. Which of the following statements is false with respect to a Data Dictionary? (a) It is a repository of the elements in a system. (b) data dictionary and data store both are same (c) It manages detail (d) It communicates the common meanings for system elements and activities. (e) It documents system features. 9. Match the following and select the correct options given under

i) physical design A) Documentation ii) interview B) Type of output iii) Input design C) defines design specifications that are to be coded iv) Installation procedure D) a data gathering technique v) report E) Identification and design of interfaces to enter data

(a) i-D, ii A, iii-B, iv C, v- E (b) i-C, ii D, iii-E, iv A, v- B (c) i-A, ii D, iii-B, iv C, v- E (d) i-D, ii A, iii-E, iv B, v- C (e) i-B, ii A, iii-D, iv C, v- E. 10. Cost-Benefit Analysis is performed during (a) Analysis phase (b) Design phase (c)

Feasibility study phase (d) Implementation phase (e) Maintenance phase.

Answers

1.

Answer : (c)

Reason: Transactions produce loads of data everyday and Transaction processing systems aim at improving the routine business activities. 2. Answer : (d)

Reason: Prototyping is adopted if information requirements are not well-defined. 3. Answer : (a)

Reason: structured programming means splitting the overall task into well-defined subtasks. 4. Answer : (a)

Reason: Third party enquiry is not a technique to capture the requirements of the user. 5. Answer : (e)

Reason: The parallelogram is not used in drawing DFDs. 6. Answer : (e)

Reason: All the given questions are useful in evaluating the DFDs. 7. Answer : (d)

Reason: extensive use of GOTO leads to spaghetti code. 8. Answer : (b)

Reason: data dictionary is for storing data about data where as data store is where actual data is stored . 9. Answer : (b)

Reason: After matching the both sides the correct option is (b). 10. Answer : (c)

Reason: During the Feasibility study the financial feasibility is also measured

Part I: True/False (remove the incorrect answer, 50%, 0.5% for each question) 1-20 : Chapter 1, 21-40: Chapter 2, 41-60: Chapter 3, 61-80: Chapter 4, 81-100: Chapter 5.

T 1. Traditionally, a company either developed its own information systems, called inhouse applications, or purchased systems called software packages from outside vendors. F 2. A mission-critical system is one that is unimportant to a companys operations. F 3. In an information system, data is information that has been transformed into output that is valuable to users. F 4. In an information system, information consists of basic facts that are the systems raw material. F 5. System software consists of programs that support day-to-day business functions and provide users with the information they require. F 6. Application software manages hardware components, which can include a single workstation or a global network with many thousands of clients. F 7. A horizontal system is designed to meet the unique requirements of a specific business or industry, such as a Web-based retailer, a medical practice, or a video chain. F 8. A vertical system is a system, such as an inventory or payroll application, that can be adapted for use in many different companies. F 9. The success or failure of an information system usually is unrelated to whether users are satisfied with the systems output and operations. T 10. A business process describes a specific set of transactions, events, tasks, and results. F 11. Product-oriented companies primarily offer information or services or sell goods produced by others. F 12. Service-oriented companies manufacture and sell products such as computers, routers, or microchips. F 13. Although the business-to-business (B2B) sector is more familiar to retail customers, the volume of business-to-consumer (B2C) transactions is many times greater. T 14. IBM claims that its WebSphere strategy is best for Web-based application development, while Microsoft counters with a broad vision called .NET that redefines that companys approach to Web-based application development. T 15. In many large companies, applications called enterprise resource planning (ERP) systems provide cost-effective support for users and managers throughout the company. F 16. TP systems are inefficient because they process a set of transaction related commands individually rather than as a group. T 17. New business support systems that produced valuable information, in addition to performing manual tasks, were called management information systems (MIS) because managers were the primary users. T 18. The decision support capability of a business support system can help users make decisions; for example, a truck fleet dispatcher can run a series of what-if scenarios to determine the impact of increased shipments or bad weather. F 19. In a knowledge management system, a knowledge base consists of logical rules that identify data patterns and relationships. F 20. A knowledge management system uses inference rules, which consist of a large database that allows users to find information by entering keywords or questions in normal English phrases. F 21. A strong business case suggests that a company should pursue other options, above

the alternative, because it would be in the firms best interest to do so. T 22. Strategic planning looks beyond day-to-day activities and focuses on a horizon that is 3, 5, or even 10 years in the future. F 23. A companys mission statement is unrelated to its major goals, shorter-term objectives, and day-to-day business operations. F 24. Management leadership and information technology are unconnected, and no significant changes have occurred in either area. T 25. Today, systems development is much more team-oriented than in the past. T 26. A systems request might propose enhancements for an existing system, the correction of problems, or the development of an entirely new information system. F 27. Systems requests seldom are aimed at improving service to customers or users within a company. T 28. Performance limitations result when a system that was designed for a specific hardware configuration becomes obsolete when new hardware is introduced. T 29. A system must have effective controls to ensure that data is secure and accurate. F 30. Hardware-based security controls include passwords, various levels of user access, and coding data. F 31. Data entry controls should be excessive without being effective. T 32. Internal and external factors affect every business decision that a company makes, and IT systems are no exception. F 33. A strategic plan that stresses technology tends to create an unfavorable climate for IT projects that extends throughout an organization. T 34. As users rely more heavily on information systems to perform their jobs, they are likely to request even more IT services and support. T 35. Errors or problems in existing systems can trigger requests for systems projects. T 36. The purpose of a JIT (just-in-time) system is to provide the right product in the right place at the right time. F 37. Information systems that interact with customers usually receive low priority. T 38. Competition drives many information systems decisions. F 39. Economic activity has little influence on corporate information management. T 40. With Microsoft Project, a project manager can use a map to define project tasks, list activities and participants, plan the sequence of work, estimate project milestone dates, and track all costs. T 41. Each activity within the systems analysis phase has an end product and one or more milestones. F 42. Greater user involvement in the system development process usually results in poorer communication, slower development times, and less satisfied users. F 43. Because it is linked to a specific development methodology, systems developers use JAD whenever group input and interaction is not desired. F 44. While RAD typically focuses only on fact-finding and requirements determination, JAD provides a fast-track approach to a full spectrum of system development tasks, including planning, design, construction, and implementation. T 45. IT professionals recognize that successful systems must be user-oriented, and users need to be involved, formally or informally, at every stage of systems development. F 46. Because of the limited range of input and interaction among participants, few companies believe that a JAD group produces the best definition of a new system.

T 47. RAD relies heavily on prototyping and user involvement. F 48. Compared with traditional methods, the entire RAD process is expanded and, as a result, the new system is built, delivered, and placed in operation much later. F 49. The main objective of all RAD approaches is to extend development time and expense by excluding users from every phase of systems development. T 50. A risk of RAD is that a system might work well in the short term, but the corporate and long-term objectives for the system might not be met. T 51. System analysts use modeling and fact-finding interactively first they build factfinding results into models, then they study the models to determine whether additional fact-finding is needed. F 52. Creating an FDD is different from drawing an organization chart systems analysts start at the bottom and work their way up. T 53. UML provides various graphical tools and techniques, such as case diagrams and sequence diagrams. T 54. Because use cases depict a system through the eyes of a user, common business language can be used to describe the transactions. F 55. In a sequence diagram, the interaction proceeds from left to right along horizontal arrows, while a vertical timeline represents messages from one object to another. T 56. System requirements serve as benchmarks to measure the overall acceptability of a finished system. T 57. System requirements fall into five general categories: outputs, inputs, processes, performance, and controls. F 58. Because it will have a shorter useful life, a scalable system offers a poorer return on the initial investment. T 59. In determining total cost of ownership (TCO), one problem is that cost estimates tend to understate costs such as user support and downtime productivity losses. F 60. Although software cannot help to gather and analyze facts, many programs actually perform fact-finding for a systems analyst. F 61. The deliverable, or end product, of data and process modeling is a physical model of the current system. F 62. A logical model describes how a system will be constructed. F 63. A physical model shows what the system must do, regardless of how it will be implemented. T 64. A data flow diagram (DFD) shows how the system transforms input data into useful information. F 65. A set of DFDs provides a logical model that shows how the system works, not what the system does. T 66. In a DFD, processes contain the business logic, also called business rules, that transform the data and produce the required results. F 67. Using Gane and Sarson symbols, a DFD represents processes as circles. T 68. A data flow in a DFD represents one or more data items. F 69. A DFD shows the structure and detailed contents of a data flow. F 70. In a DFD, a process symbol can have only one outgoing data flow. T 71. In a DFD, a data flow must have a process symbol on at least one end. T 72. Spontaneous generation, black holes, and gray holes are logically impossible in a DFD because a process must act on input, shown by an incoming data flow, and

produce output, represented by an outgoing data flow. T 73. A DFD does not show the detailed contents of a data store the specific structure and data elements are defined in the data dictionary. F 74. Two data stores can be connected by a data flow without an intervening process. F 75. A DFD does not show the external entities that provide data to the system or receive output from the system. F 76. Systems analysts call an entity that supplies data to the system a sink, and an entity that receives data from the system a source. F 77. Data flows are shown in a context diagram because data stores are external to the system. T 78. What makes one system more complex than another is the number of components, the number of levels, and the degree of interaction among its processes, entities, data stores, and data flows. T 79. The process name in a context diagram should be the name of the information system. F 80. A context diagram provides the most detailed view of an information system and contains multiple process symbols. T 81. The Software and Information Industry Association (SIIA) believes that the acquisition of software as a service rather than a product will have a major impact on the software industry. T 82. Typically, customers purchase licenses that give them the right to use the software under the terms of the license agreement. T 83. Building an application in a Web-based environment might involve different risks and benefits, compared to a traditional environment. T 84. Two Web-based development environments are IBMs WebSphere and Microsofts .NET. T 85. In a traditional systems development environment, security issues usually are less complex than with Web-based systems, because the system operates on a private telecommunications network, rather than the Internet. F 86. Internet-based development treats the Web as just a communications channel, rather than as a platform. T 87. An IBS (Internet business service) solution is attractive to customers because it offers online data center support, mainframe computing power for mission-critical functions, and universal access via the Internet. F 88. An ASP provides a license to use the software, and nothing more. T 89. Another term for IBS is managed hosting, because the operation is managed by the outside firm, or host. T 90. Mission-critical IT systems should be outsourced only if the result is a costattractive, reliable, business solution that fits the companys long-term business strategy. F 91. A major advantage of outsourcing is that it eliminates employee concerns about job security. T 92. A company considering outsourcing must realize that the solution can be only as good as the outsourcing firm that provides the service. F 93. Mergers and acquisitions typically have no impact on clients and customers of large, financially healthy firms.

F 94. According to Gartner, a leading IT research and consulting firm, by 2005, three in 10 IT jobs at U.S. IT companies and four in 20 at non-IT companies will move offshore. T 95. The main reason for offshore outsourcing is the same as domestic outsourcing: lower bottom-line costs. F 96. A software package that can be used by many different types of organizations is called a vertical application. F 97. A software package developed to handle information requirements for a specific type of business is called a horizontal application. T 98. By designing a system in-house, companies can develop and train an IT staff that understands the organizations business functions and information support needs. F 99. Compared to software developed in-house, a software package almost always is more expensive, particularly in terms of initial investment. T 100. Many firms feel that in-house IT resources and capabilities provide a competitive advantage because an in-house team can respond quickly when business problems or opportunities arise. Part II: Short Answer (answer each question completely, 50%, 1% for each question) 1-10 : Chapter 1, 11-20: Chapter 2, 21-30: Chapter 3, 31-40: Chapter 4, 41-50: Chapter 5. 1. _Information technology_ refers to the combination of hardware and software products and services that companies use to manage, access, communicate, and share information. 2. _Systems analysis and design_ is a step-by-step process for developing highquality information systems. 3. A(n) _information system_ combines information technology, people, and data to support business requirements. 4. An IT department team includes _system analysts_ who plan, develop, and maintain information systems. 5. A(n) _system_ is a set of related components that produces specific results, such as routing Internet traffic, manufacturing microchips, and controlling complex events like a NASA launch. 6. Traditional companies sometimes are called _brick-and-mortar_ companies because they conduct business from physical locations. (Chapter 1, #16) 7. Internet-based commerce is called _e-commerce_ and includes two main sectors: B2C (business-to-consumer) and B2B (business-to-business). 8. Most B2B transactions rely on _electronic data interchange_, which refers to computer-to-computer transfer of data between companies, usually over private telecommunications networks. 9. _Enterprise computing_ refers to information systems that support company-wide operations and data management requirements. 10. _Groupware_ programs run on a company intranet and enable users to share data, collaborate on projects, and work in teams. 11. The term _business case_ refers to the reasons, or justification, for a systems development proposal. 12. _Strategic planning_ is the process of identifying long-term organizational goals, strategies, and resources.

13. During strategic planning, top managers ask a series of questions that is called a(n) _SWOT analysis_ because it examines a companys strengths, weaknesses, opportunities, and threats. 14. A(n) _mission statement_ describes a company for its stakeholders and briefly states the companys overall purpose, products, services, and values. 15. _Stakeholders_ include anyone affected by a companys operations, such as customers, employees, suppliers, stockholders, and members of the community. 16. After composing a mission statement, a company identifies a set of _goals_ that will accomplish the mission. 17. To achieve its goals, a company develops a list of shorter-term _objectives_, which translate into day-to-day business operations. 18. _Critical success factors_ are vital objectives that must be achieved for an enterprise to fulfill its mission. 19. _Critical business issues_ are the key problems, opportunities, and constraints that affect and shape a firms decisions. 20. At some point in the systems development process, a(n) _case for action_ is presented, which is a summary of the project request and a specific recommendation. 21. One of the main activities in the systems analysis phase is _requirements modeling_, which involves fact-finding to describe the current system and identify requirements for the new system. 22. The deliverable, or end product of the systems analysis phase is a(n) _systems requirements document_, which is an overall design for the new system. 23. _Analytical skills_ enable a systems analyst to identify a problem, evaluate the key elements, and develop a useful solution. 24. A common technique that allows users to participate in various development tasks is called _joint application development_, which is a team-oriented technique for fact-finding and requirements modeling. 25. In addition to joint applications development, another popular user-oriented method is _rapid application development_, which resembles a condensed version of the entire SDLC with users involved every step of the way. 26. The _unified modeling language_ is a widely used method of visualizing and documenting software systems design. (Chapter 3, #11) 27. A(n) _use case diagram_ is a UML technique that visually represents the interaction between users and an information system. 28. In a use case diagram, the user becomes a(n) _actor_, with a specific role that describes how he or she interacts with a system. 29. A(n) _sequence diagram_ is a UML technique that shows the timing of transactions between objects as they occur. 30. A(n) _system requirement_ is a characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users. 31. Analysts use _ data and process _ modeling techniques to show how a system transforms data into useful information. 32. A(n) _data flow diagram_ uses various symbols to show how the system transforms input data into useful information. 33. In addition to the Gane and Sarson symbol set, another popular symbol set is the

_Yourdon_ symbol set. 34. In a typical company, _processes_ might include calculating sales trends, filing online insurance claims, ordering inventory from a suppliers system, or verifying e-mail addresses for Web customers. 35. Another term for business logic is business _rules_. 36. To show the detail inside a black box, create DFD _diagram 0_, which zooms in on the context diagram and shows major processes, data flows, and data stores. (Chapter 4, #16) 37. A(n) _diverging data flow_ is a data flow in which the same data travels to two or more different locations. 38. When a set of DFDs is created for a system, a(n) _functional primitive_ is a process that consists of a single function that is not exploded further. 39. _Leveling_ is the process of drawing a series of increasingly detailed diagrams, until all functional primitives are identified. 40. _Balancing_ maintains consistency among DFDs by ensuring that input and output data flows align properly. 41. The _Software and Information Industry Association_ is an industry group that focuses on the digital economy. 42. As Internet-based systems become more popular, developers will focus on _webbased application development_, where the Web becomes an integral part of the application, rather than just a communication channel. 43. Web-based software usually requires additional layers, called _middleware_, to communicate with existing software and legacy systems. 44. _Outsourcing_ is the transfer of information systems development, operation, or maintenance to an outside firm that provides these services, for a fee, on a temporary or long-term basis. 45. A firm that offers outsourcing solutions is called a(n) _service provider_. 46. A(n) _application service provider_ is a firm that delivers a software application, or access to an application, by charging a usage or subscription fee. 47. Some firms offer _Internet business services__, which provide powerful Webbased support for transactions such as order processing, billing, and customer relationship management. 48. A(n) _usage model or transaction model_ is an outsourcing fee model that charges a variable fee based on the volume of transactions or operations performed by the application. 49. The choice between developing versus purchasing software often is called a(n) _make-or-buy or build-or-buy_ decision. 50. The software that a companys IT department makes, builds, and develops is called _in-house software_.

Define System and explain its characteristics. Ans.: A System means an organised relationship among functioning units or components. It is an orderly grouping of interdependent components linked together according to a plan to achieve a specific objective. The elements of the system are as under :

(1) Outputs and Inputs : A major objective of a system is to produce an output that has value to its user. Whatever the nature of the output, it must be in line with the expectations of the intended user. Inputs are the elements that enter the system for processing and output is the outcome of the processing. (2) Processors : The processor is the element of the system that involves the actual transformation of input into output. It is the operational component of a system. Processors modify the input totally or partially. (3) Control : The control element guides the system. It is the decision-making subsystem that controls the pattern of activities governing input, processing and output. (4) Feedback : Control in a dynamic system is achieved by feedback. Feedback measures output against a standard in some form that includes communication and control. Feedback may be positive or negative, routine or informational. (5) Environment : It is the source of external elements that impinge on the system. It determines how a system must function. (6) Boundaries and Interfaces : A system should be defined by its boundaries- the limits that identify its components, processes and interrelationships when it interfaces with another system. The characteristics of a system are as under : (1) Organisation : It implies structure and order. It is the arrangement of components that helps to achieve objectives. (2) Interaction : It refers to the manner in which each component functions with other component of the system. In an organisation, for example, purchasing must interact with production, advertising with sales, etc. (3) Interdependence : It means that parts of the organisation or computer system depend on one another. They are coordinated and linked together according to a plan. One subsystem depends on the input of another subsystem for proper functioning. (4) Integration : It refers to the completeness of systems. It is concerned with how a system is tied together. It is more than sharing a physical part or location. It means that parts of a system work together within the system even though each part performs a unique function. (5) Central Objective : Objectives may be real or stated. Although a stated objective may be the real objective, it is not uncommon for an organisation to state one objective and operate to achieve another.

What is the role of a Systems Analyst? Ans.: System Analysts bridges the gap that always exists between those who need computer-based business solutions. They understand both business and computing. They study business problems and opportunities and then transform business and information requirements into specifications for information systems that will be implemented by various technical specialists including

computer programmers. System Analysts initiate change within an organization. Every new system changes the business. System Analyst is basically a problem solver. An analyst must possess various skills to effectively carry out the job. Specifically, they may be divided, into two categories: Interpersonal and technical skills. Both are required for system development. Interpersonal skills deal with, relationships and the interface .of the analyst with people in business. They are useful in establishing trusts resolving conflict, and communicating information. Technical skills, on the other hand, focus an procedures and techniques for operations analysis, systems analysis, and computer science The interpersonal skills relevant to systems work include the following : Communication Understanding Foresightedness and Vision Adaptability and Flexibility Skills Teaching Selling Patience and Rationality Management Skills Leadership Quality Training and Documentation Capability Technical skills include : CreativityProblem solvingProject managementDynamic interfaceQuestioning attitude and inquiring mindKnowledgeExplain the Waterfall Model. Sometimes called the classic life cycle or the linear sequential model, the waterfall model is a systematic, sequential approach to software development in which development is seen as flowing downwards ( like a waterfall ) that begins at the system level and progresses through analysis, design, coding, testing and support. To follow the waterfall model, one proceeds from one phase to the next in a sequential manner. For example, one first completes "requirements specification". When the requirements are fully completed, one proceeds to design. The software is designed (on paper) and this design should be a plan for implementing the requirements given. When the design is fully completed, an implementation of that design, i.e. coding of the design is made by programmers. After the implementation phases are complete, the software product is tested and debugged; any faults introduced in earlier phases are removed here. Then the software product is installed, and later maintained to add any new functions that the user needs and remove bugs. Thus in a waterfall

model, we can move to the next step only when the previous step is completed and removed of all errors. There is no jumping back and forth or overlap between the steps in a waterfall model. The model consists of six distinct stages, namely : (1) In the Information Modelling phase (a) Work begins by gathering information related to the existing system. This will consists of all items consisting of hardware, people, databases etc. (2) In the requirements analysis phase (a) The problem is specified along with the desired objectives (goals). (b) The constraints are identified. (c) All information about the functions, behaviour, and performance are documented and checked by the customers. (3) In the design phase, all inputs, computations and outputs of the system should be converted into a software model so that it can be coded by programmers. The hardware requirements are also determined at this stage along with a picture of the overall system architecture. (4) In the code generation phase, the design has to be translated into a machinereadable form using any of the programming languages available that is suitable for the project Explain Information Gathering Process for System Development. OR Explain Fact Finding Method of System Analysis Ans.: Fact finding means learning as much as possible about the present system. The tools used in information gathering or fact finding are (1) Review of Written Documents : In all organizations documents such as forms, records, reports, manuals, etc are available. These help in determining how the present system runs. The process of fact finding includes collection of all possible documents and evaluating them. Unfortunately, most manuals are not up to date and may not be readable. The analyst needs to find out how the forms are filled out, what changes need to be made and how easy they are to read. (2) On-Site Observation : The purpose of on-site observation is to get as close as possible to the real system being studied. It is the process of recognizing and noting people, objects and occurrences to obtain information. As an observer the analyst must follow a set of rules. He/she must listen than talk and not give advice or pass a moral judgment, must not argue or show friendliness towards others. The following questions can serve as a guide for on-site observations: _ What kind of system is it? What does it do? _ Who runs the system? Who are the important people in it? _ What is the history of the system? (3) Interviews : An interview is a face to face interpersonal situation in which a person called the interviewer asks a person being interviewed, questions

designed to gather information about a problem. The analyst or interviewer can schedule interviews with key personnel of the organization. The analyst also needs to conduct detailed interviews with all the people who will actually use the system. This will provide all the details the analyst needs and also remove any fear from the users that the computers will replace the. Interviews help gather vital facts about the existing problems, such as lack of quality control or security, etc. Interviewing needs a friendly atmosphere so that the interviewer can ask questions properly, obtain reliable and correct answers and record the answers accurately and completely. (4) Questionnaires : A questionnaire is a tool that has questions to which individuals respond. A questionnaire has the following advantages: _ It is economical and requires less skill than an interview. _ It can be used to gather data from large number of people simultaneously _ It is a uniform method in which all question asked are the same to all people The users are happy as they know that the answers they give are confidential _ User get time to think about the questions and so can give more accurate results than in an interview What is Feasibility? Describe the different types of Feasibility Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called feasibility study. A feasibility study is carried out to select the best system that meets performance requirements. When conducting feasibility study, an analyst can consider 7 types of feasibility: Technical Feasibility : It is concerned with specifying the equipment and the computer system that will satisfy and support the proposed user requirements. Here we need to consider the configuration of the system which tells the analyst how many work stations are required, how the units are interconnected so that they can operate and communicate smoothly. Operation Feasibility : It is related to human organizational aspects. The points to be considered here are what changes will be brought with the system?, what new skills will be required?, do the existing staff members have these skills and can they be trained? Economic Feasibility : It is the most frequently used technique for evaluating a proposed system. It is also called Cost/Benefit Analysis. It is used to determine the benefits and savings that are expected from the proposed system and compare them with the costs. If benefits are more than the cost, the proposed system is given an OK. Social Feasibility : It is a determination of whether the proposed system

will be acceptable to the people or not. It finds out the probability of the project being accepted by the group of people who are directly affected by the changed system. Management Feasibility : It is a determination of whether the proposed system is acceptable to the management of the organization. The project may be rejected, if the management does not accept the proposed system. Legal Feasibility : It is a determination of whether the proposed project is under legal obligation of known Acts, Statutes, etc. Explain Data Modeling and ER diagram with example. Ans.: Data Modeling : It gives answers to questions regarding the data that is to be used in the application. We come to know the data objects, where they are stored, what is the relationship between objects, etc. Data modeling uses an Entity Relationship diagram to solve these questions. An Entity Relationship diagram will focus on all data that are entered, stored, transformed and produced within an application. The data model consists of three interrelated information data objects, attributes that describe the data objects and relationships that connect data objects to one another. Data Objects : A data object is something that has a number of different properties or attributes and that can be understood by software. For example a person or a car can be viewed as data objects. Data objects are related to one another. E.g. person can own car, where the relationship own denotes a connection between person and car. A data object reflects only data and not the operation that can be done on that data. Attributes : Attributes define the properties of a data object. They can be used to name an instance of the data object, describe the instance or make reference to another instance in another table (e.g. attribute Owner). One or more attributes that uniquely identifies one and only one instance of an entity is defined as an identifier or primary key. E.g. employee no is a primary key for an employee. Relationships : Data objects are connected to one another in different ways. Consider two data objects book and bookstore. A connection is established between book and bookstore because the two objects are related. Entity Relationship Diagrams : The object-relationship pair can be represented graphically using an ER diagram. An entity represents an object. Examples: a computer, an employee, a song, a mathematical theorem. Entities are represented as rectangles. A relationship captures how two or more entities are related to one another. Examples: an owns relationship between a company and a computer, a supervises relationship between an employee and a department, a performs relationship between an artist and a song. Relationships are represented as diamonds, connected by lines to each of the entities in the relationship. Entities and relationships can both have attributes. Examples: an employee entity might have an employee ID number attribute; the proved relationship may have a date attribute. Attributes are represented as ellipses connected to their entity by a line.

In context with an ER diagram explain Cardinality and Modality. Give example. Ans.: Cardinality : The elements of data modeling data objects, attributes and relationships provide information only about which objects are related to one another. But this information is not sufficient for software engineering purpose. Cardinality specifies how many instances or occurrences of object X are related to how many occurrences of object Y. Cardinality is usually expressed as one or many. Thus two objects can be related as (1) One-to-One (1:1) : An occurrence of object A can relate to one and only one occurrence of object B and an occurrence of B can relate to only one occurrence of A. (2) One-to-Many (1:N) : One occurrence of object A can relate to one or many occurrences of object B but an occurrence of B can relate to only one occurrence of A. E.g. mother can have many children, but a child can have only one mother. (3) Many-to-Many (M:N) : An occurrence of object A can relate to one or many occurrences of object B and an occurrence of B can relate to only one or many occurrences of A. E.g. an uncle can have many nieces and a niece

can have many uncles. Cardinality defines the maximum number of objects that can participate in a relationship. It does not tell whether or not a data object must participate in the relationship. Modality : If a particular relationship is optional or not needed then we say that the modality of that relationship is 0. The modality is 1 if an occurrence of the relationship is necessary. Example : Consider 2 data objects Patient and Doctor. The relationship between the two data objects is Treats. A doctor needs a patient to treat, so the modality is 1 while it is not necessary for a patient to be treated by a doctor (he can be treated with home remedies too). So here the modality is 0. When we need to specify cardinality we use the symbols One = a line or dash | Many = crows feet To specify modality we use the symbols One = a line or dash | Zero = a circle o The following ER diagram specifies cardinality and modality.

What is a Data Dictionary? Give an example. Ans.: A Data Dictionary (DD) is a structured repository of data about data. It is a set of accurate definitions of all DFD data elements and data structures. A data dictionary defines each term encountered during the analysis and design of a new system. Data dictionary is the place where we keep the details of the contents of data flows, data stores & processes. Without a data dictionary the development of large systems becomes difficult. The data dictionary is an effective solution to the problem of complicated nature. The main purpose of a data dictionary is to provide a source of reference in which the analyst, the user, the designer can look up & find out its content and any other relevant information. The main advantage of a DD is the documentation. It is a valuable reference to the organization which helps in communication between the analyst and the user. It is also important in building a database. The Data Dictionary notations are = is composed of + AND ( ) Optional value [ ] Either/Or

{} iteration ** comment @ identifier (key field) | separates alternative choices in the [] construct Examples of Data dictionary Name = Courtesy-Title + First-Name + (Middle-Name) + Last-Name Courtesy-Title = [ Mr. | Miss | Mrs. | Ms. | Dr. | Prof. ] First-Name = { Legal-Character } Last-Name = { Legal-Character } Legal-Character = [ A-Z | a-z |0-9| ' | - | | With examples explain what is a Data Flow Diagram Ans.: A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It describes the systems data and how the processes transform the data in a graphical manner. Data flow diagrams can be used to provide a clear representation of any business function. It starts with an overall picture of the business and continues by analyzing each of the functional areas of interest. It uses a top-down approach to show all the levels of the functions of the system. Initially a context diagram is drawn, which is a simple representation of the entire system under investigation. This is followed by a level 1 diagram; which provides an overview of the major functional areas of the business. The level 1 diagram identifies the major business processes at a high level and any of these processes can then be analyzed further - giving rise to a corresponding level 2 business process diagram. This process of more detailed analysis can then continue through level 3, 4 and so on.

The context diagram shown on this screen represents a book lending library. The library receives details of books, and orders books from one or more book suppliers. Books may be reserved and borrowed by members of the public, who are required to give a borrower number. The library will notify borrowers when a reserved book becomes available or when a borrowed book becomes overdue. In addition to supplying books, a book supplier will furnish details of specific books in response to library enquiries. After the context model is created the process is exploded to the next level to show the major processes in the system. Depending upon the complexity of the system each of these processes can also be exploded into their own process model. This continues until the goal of each process accomplishing a single function is reached. Because of this approach the context model is referred to as Level 0 (Zero) DFD, the next as Level 1 DFD, etc. Q.2 Briefly describe a Decision Tree with example. Ans.: Decision tree are graphical representation methods of representing a sequence of

logical decisions. It is mainly used when decisions need to be taken or for defining policies. A decision tree has as many branches as there are logical alternatives. It is easy to construct, easy to read and easy to update. A decision tree is used to identify the strategy most likely to reach a goal. It is also used as a means for calculating probabilities or making financial or number based decisions. A decision making tree is essentially a diagram that represents, in a specially organized way, the decisions, the main external or other events that introduce uncertainty, as well as possible outcomes of all those decisions and events. Q.3 How to draw a Decision Tree? Ans.: You start a decision tree with a decision that needs to be made. This decision is represented by a small square towards the left of a large piece of paper. From this box draw out lines towards the right for each possible solution, and write that solution along the line. At the end of each solution line, consider the results. If the result of taking that decision is uncertain, draw a small circle. If the result is another decision that needs to be made, draw another square. Squares represent decisions; circles represent uncertainty or random factors. Write the decision or factor to be considered above the square or circle. If you have completed the solution at the end of the line, just leave it blank. Starting from the new decision squares on your diagram, draw out lines representing the options that could be taken. From the circles, draw out lines representing possible outcomes. Again mark a brief note on the line saying what it means. Keep on doing this until you have drawn down as many of the possible outcomes and decisions as you can see leading on from your original decision. Example : Book return policy in library If a Faculty returns a book late, a fine of 5% of the book rate is charged. If a Student returns a book late by 3 days, fine is 10%, else 20% of book rate.

Each decision corresponds to a variable, relation or predicate whose possible values are listed among the condition alternatives. Each action is a procedure or operation to perform, and the entries specify whether (or in what order) the action is to be performed for the set of condition alternatives the entry corresponds to. Many decision tables include in their condition alternatives the don't care symbol, a hyphen. Using don't cares can simplify decision tables, especially when a given condition has little influence on the actions to be performed. In some cases, entire conditions thought to be important initially are found to be irrelevant when none of the conditions influence which actions are performed. The limited-entry decision table is the simplest to describe. The condition alternatives are simple boolean values, and the action entries are check-marks, representing which of the actions in a given column are to be performed. A technical support company writes a decision table to diagnose printer

problems based upon symptoms described to them over the phone from their clients.

Q.1 What is Structured English? Ans.: Structured English or pseudo code or program design language (PDL) uses the vocabulary of English and the syntax of a structured programming. Structured English looks like a modern programming language. The difference between structured English and a real programming language is in the use of narrative text which is placed within the structured English statements. Structured English cannot be compiled. It should have the following characteristics: o A fixed syntax of keywords used for structured constructs, data declaration o A free syntax of natural language that describes processing o Data declaration facilities that include simple(array) and complex(linked list or tree) data structures o Facility to declare subprograms and call them Decisions in Structured English are made through IF, THEN, ELSE, SO, etc. Q.2 What are Structure Charts? Describe.

Ans.: Structure Chart : A hierarchical diagram showing the relationships between the modules of a computer program. A module is the basic component of a structure chart and is used to identify a function. Modules are relatively simple and independent components. Higher-level modules are control modules that control the flow of execution. Lower level modules are worker bee modules and contain the program logic to actually perform the functions. The vertical lines connecting the modules indicate the calling structure from the high-level modules to the lower-level modules. The little arrows next to the lines show the data that is passed between modules and represent the inputs and outputs of each module. At the structure chart level, we are not concerned with what is happening inside the module yet. We only want to know that somehow it does the function indicated by its name using the input data and producing the output data. A program call is when one module invokes a lower-level module to perform a needed service or calculation. Program call: The transfer of control from a module to a subordinate module to perform a requested service. The arrows with the open circle, called data couples, represent data being passed into and out of the module. A data couple can be an individual data item (e.g., a flag or a customer account number) or a higher-level data structure (e.g., an array, record, or other data structure). The arrow with the darkened circle is a flag. A flag is purely internal information that is used between modules to indicate some result. Data couples: The individual data items that are passed between modules in a program call. A basic idea of structured programming is that each module only has to do a very specific function. The module at the very top of the tree is the boss module. Its functions will be to call the modules on the next tier, pass information to them, and receive information back. The function of each middlelevel module is to control the processing of the modules below it. Each has control logic and any error-handling logic that is not handled by the lower-level module. The modules at the extremities, or the leaves, contain the actual algorithms to carry out the functions of the program. Structure charts are developed to design a hierarchy of modules for a program. A structure chart is in the form of a tree with a root module and branches. A subtree is simply a branch that has been separated from the overall tree. When the subtree is placed back in the larger tree, the root of the subtree becomes just another branch in the overall tree.

What is a HIPO Chart? Explain. Ans.: HIPO charts show relationships between modules. It describes the data input and output from the processes and defines the data flow. It provides a structure by which the functions of a system can be understood. It also provides a visual description of input to be used and output to be produced for each level of the diagram. It makes the transformation from input to output data visible. There are two parts to a HIPO chart, a hierarchy chart and an IPO chart. The hierarchy chart is useful for showing hierarchy of procedures within a program. Hierarchy charts are also called structure charts, top-down charts, or VTOC (Visual Table of Contents) charts. All these names refer to planning diagrams that are similar to a company's organization chart. Hierarchy charts depict the organization of a program but omit the specific processing logic. They describe what each part, or module, of the program does and how the modules relate to each other. The IPO chart describes the system in terms of its inputs, outputs and the processes that are performed on the inputs to transform them into outputs. It provides the following : (a) The Input section that contains the data items used by the process steps. (b) The Output section that contains the data items created by the process steps. (c) Process section that contains numbered steps that describe the functions to be performed. Arrows connect them to the output steps and the input/output data items.

Das könnte Ihnen auch gefallen