Tutorial 1 Solution

1. Match each of the key terms above with the definition that best fits it: (Analysis, Application independence, Application software, Data, Database, Data flow, Data-oriented approach, Design, Implementation, Information, Information system analysis and design, Application Service Provider (ASP), Joint Application Design (JAD), Logical design, Maintenance, Reuse, Outsourcing, Object-oriented analysis and design (OOAD), Physical design, Process-oriented approach, Processing logic, Planning, Prototyping, Stakeholder, System analyst, System development life cycle (SDLC), System development methodology) Systems development methodologies and techniques based on objects rather than data or processes (Object-oriented analysis and design)
b.

a.

The first phase of the SDLC in which an organizations total information system needs are identified ,analyzed, prioritized and arranged . (Planning ) The third phase of the SDLC in which the description of the recommended solution is converted into logical and then physical system specifications (design) The complex organization process whereby computer-based information systems are developed and maintained (information system analysis and design) Computer software designed to support organizational functions and processes (application software) The organizational role most responsible for the analysis and design of information systems (system analyst) The use of previously written software resources, especially objects and components, in new application. (reuse) A structured process in which users, managers and analysts work together for several days in a series of intensive meetings to specify or review system requirements (JAD)

c.

d.

e.

f.

g.

h.

i.

An iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between an analyst and users (prototyping) The part of the design phase of the SDLC in which all functional features of the system chosen for development in analysis are described independent of any computer platform (logical design) The part of the design phase of the SDLC in which the logical specifications of the system from logical design are transformed into technology-specific details from which all programming and system constructions can be accomplished (physical design) The practice of turning over responsibility of some to all of an organizations information systems applications and operations to an outside firm. (outsourcing) The second phase of the SDLC in which the current system is studied and alternative replacement systems are proposed (analysis) The fourth phase of the SDLC in which the information system is coded, tested, installed and supported in the organization (implementation) The final phase of the SDLC in which an information system is systematically repaired and improved; or changes made to s system to fix or enhance its functionality (maintenance) A standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems (system development methodology) Organizations that host and run computer applications for other companies, typically on a per-use or license basic (application service provider) The traditional methodology used to develop, maintain, and replace information systems (SDLC) A person who has an interest in an existing or new information system. Someone who is involved in the development of a system, in the use of a

j.

k.

l.

m.

n.

o.

p.

q.

r.

s.

system, or someone who has authority over the parts of the organization affected by the system (stakeholder) 2. Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be quick and easy?

Methodologies, techniques, and tools help ensure the quality and appropriateness of the system being built. Following a systems methodology, applying techniques, and using appropriate tools provides structure to the systems development process, since they have been tested and perfected by others. The quick and easy approach to building systems may be easier, cheaper, and quicker in the short run, but it almost always results in a poorly developed system, meaning that the system will be less than optimal and require extra work to maintain. In the long run, a poorly developed system requires more time and money to make right. Following an engineering-type approach ensures that systems analysis and design is rigorous, structured, and systematic. 3. How might prototyping be used as part of the SDLC? Prototyping is useful for requirements determination, helping to clarify and communicate user requirements. Also, a prototype can serve as the basis for the final system. As an example, imagine that an analyst is developing a computerized inventory-tracking system. This inventory-tracking system provides a sales representative with real-time access to inventory levels. The analyst asks the sales representative what kinds of inventory information he needs, including when and where he needs to access this information. Using a graphical, object-oriented development tool, such as Microsoft Visual Basic, the analyst quickly builds several sample interface displays. The sales representative reviews these displays and provides the analyst with feedback. Based on this feedback, the analyst modifies the

displays and, again, solicits feedback from the sales representative. Given Visual Basics ease of use, the analyst can build the sample interfaces onthe-fly with the sales representative present. The sample interfaces can be used to build the actual system, either in Visual Basic or in some other development environment