Scribd
Upload
151 views

Tutorial01 (Answers)

This document discusses key terms related to systems analysis and design. It provides definitions for terms like systems development life cycle (SDLC), joint application design (JAD), prototyping, logical design, physical design, outsourcing, and more. It also includes sample questions about choosing development methodologies, the importance of following methodologies, SDLC phase diagrams, and expected products from each SDLC phase.

Uploaded by

vignesvaran
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
151 views

Tutorial01 (Answers)

This document discusses key terms related to systems analysis and design. It provides definitions for terms like systems development life cycle (SDLC), joint application design (JAD), prototyping, logical design, physical design, outsourcing, and more. It also includes sample questions about choosing development methodologies, the importance of following methodologies, SDLC phase diagrams, and expected products from each SDLC phase.

Uploaded by

vignesvaran
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Faculty of Computing and Informatics

TIS2211 / TSE2251 Systems Analysis and Design


Tutorial 1
1. Match each of the key terms above with the definition that best fits it:
Analysis

Data

Design

Application
software
Application
Service Provider
(ASP)
Logical design

Reuse

Outsourcing

Process-oriented
approach
System
Development Life
Cycle (SDLC)
Database

Processing logic

Prototyping

Object-oriented
Analysis and
Design (OOAD)
Stakeholder

System
development
methodology
Information

System analyst

Physical design

Rational Unified
Process (RUP)

Enterprise
Resource
Planning (ERP)
System

Managed Service
Provider (MSP)

Joint Application
Design (JAD)
Request for
Proposal (RFP)

Rapid Application
Development
(RAD)
Information
System analysis
and design
Maintenance

Application
independence
Data-oriented
approach

Implementation

Joint

a. Systems development methodologies and techniques based on objects rather than data or
processes.
Object-oriented Analysis and Design (OOAD)
b. The third phase of the SDLC in which the description of the recommended solution is
converted into logical and then physical system specifications.
Design
c. The complex organization process whereby computer-based information systems are
developed and maintained.

Page 1

Information System analysis and design

d. Computer software designed to support organizational functions and processes.


Application software
e. The organizational role most responsible for the analysis and design of information
systems.
System analyst
f. The use of previously written software resources, especially objects and components, in
new application.
Reuse
g. 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.
Joint Application Design (JAD)
h. 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
i. 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
j. 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
k. The practice of turning over responsibility of some to all of an organizations information
systems applications and operations to an outside firm.
Outsourcing

Page 2

l. The second phase of the SDLC in which the current system is studied and alternative
replacement systems are proposed.
Analysis
m. The fourth phase of the SDLC in which the information system is coded, tested, installed
and supported in the organization.
Implementation
n. 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
o. A standard process followed in an organization to conduct all the steps necessary to
analyze, design, implement, and maintain information systems.
System development methodology
p. Organizations that host and run computer applications for other companies, typically on a
per-use or license basic.
Application Service Provider (ASP)
q. The traditional methodology used to develop, maintain, and replace information systems.
System Development Life Cycle (SDLC)
r. Systems development methodology created to radically decrease the time needed to
design and implement information systems. This methodology relies on extensive user
involvement, Joint Application Design sessions, prototyping, integrated CASE tools and
code generators.
Rapid Application Development (RAD)
s. 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 system, or someone who has
authority over the parts of the organization affected by the system.
Stakeholder
t. An object-oriented systems development methodology. This methodology establishes
four phases of development, each of which is organized into a number of separate
iterations, inception, elaboration, construction and transition.

Page 3

Rational Unified Process (RUP)

u. An organization that remotely provides customized computer applications and networkbased services for other companies for a monthly or per-use fee.
Managed Service Provider (MSP)
v. A document provided to vendors to ask them to propose hardware and system software
that will meet the requirements of your new system.
Request for Proposal (RFP)
w. A system that integrates individual traditional business functions into a series of modules
so that a single transaction occurs seamlessly within a single information system rather
than several separate systems.
Enterprise Resource Planning (ERP) System
2. In the section on choosing off-the-shelf software, eight criteria are proposed for evaluating
alternative packages. Suppose the choice was between alternative custom software
developers rather than pre-written packages. What criteria would be appropriate to select and
compare among competing bidders for custom development of an application? Define each
of these criteria.

3. 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?

Page 4

4. Fill in the blank in the following diagrams:

Planning

Analysis

Maintenance

Implementati
on

Design

Page 5

Design

Implementati
on

Analysis

Maintenance
Planning

Develop
Prototype

Convert to
Operational
System

Implement and
Use Prototype

Revise and
Enhance
Prototype

5. Based on the diagram below, what is the expected product for each phase in the SDLC?

Page 6

Feasibility Study

System Requirements

System Specifications

Working System

Enhancement

Case Study (Optional)


Students are encouraged to discuss the case study below on their own.
Situation: You are the IT manager at Low-Voltage Components, a medium-sized firm that makes
and sells specialized electrical cables to companies that manufacture electronic test
equipment. Low-Voltages largest customer, TX Industries, recently installed a
computerized purchasing system and wants Low-Voltage to connect to the new
system to receive purchase orders and production schedule forecasts. Low-Voltage
currently has the following information systems: finance, accounts receivable, and
accounts payable.
1. Should Low-Voltage develop an order entry system to connect with TX Industries
purchasing system? Why or why not?
2. What factors will affect the complexity of Low-Voltages new order entry system?
Modification
Cost
Time Constraint
System Boundaries (Security)
Page 7

3. What term describes the proposed computer-to-computer relationship between Low-Voltage


and TX Industries?
Electronic Data Interchange (EDI)
4. Is Low-Voltages proposed new system an operational system? Why or why not?
Yes, because it is dealing to the day-to-day operational data.

Page 8

You might also like