TOPIC 1 • Clerical and service workers
A Framework for Systems Analysis and Design • Technical and professional staff
A system is a group of interrelated components that function together
to achieve a desired result.
An information system (IS) is an arrangement of people, data,
processes, and information technology that interact to collect,
process, store, and provide as output the information needed to
support an organization.
Information technology is a contemporary term that describes the
combination of computer technology (hardware and software) with
telecommunications technology (data, image, and voice networks).
Types of Information Systems
• A transaction processing system (TPS) is an information
system that captures and processes data about business
transactions.
• A management information system (MIS) is an
information system that provides for management-oriented
reporting based on transaction processing and operations of
the organization.
• A decision support system (DSS) is an information system
that either helps to identify decision making opportunities
or provides information to help make decisions.
• An expert system is an information system that captures
the expertise of workers and then simulates that expertise to
the benefit of non-experts.
• A communications and collaboration system is an
information system that enables more effective
communications between workers, partners, customers, and
suppliers to enhance their ability to collaborate.
• An office automation system is an information system that
supports the wide range of business office activities that
provide for improved workflow between workers.
Stakeholders: Players in the Systems Game
• A stakeholder is any person who has an interest in an
existing or proposed information system. Stakeholders can
be technical or nontechnical workers. They may also
include both internal and external workers.
• Information workers are those workers whose jobs
involve the creation, collection, processing, distribution,
and use of information.
• Knowledge workers are a subset of information workers
whose responsibilities are based on a specialized body of
knowledge.
System Owners
 an information system’s sponsor and executive advocate,
usually responsible for funding the project of developing,
operating, and maintaining the information system.
System Users
 a “customer” who will use or is affected by an information
system on a regular basis – capturing, validating, entering,
responding to, storing, and exchanging data and
information.
Internal System Users
• Supervisors, middle managers, and executive managers
External System Users
• Customers
• Suppliers
• Partners
• Employees
• Remote users - users who are not physically
located on the premises but who still requires
access to information systems.
• Mobile users - users whose location is constantly
changing but who requires access to information
systems from any location.
System Designers and System Builders
System designer – a technical specialist who translates system users’
business requirements and constraints into technical solution. She or
he designs the computer databases, inputs, outputs, screens, networks,
and software that will meet the system users’ requirements.
System builders – a technical specialist who constructs information
systems and components based on the design specifications generated
by the system designers.
Systems Analysts
Systems analyst – a specialist who studies the problems and needs of
an organization to determine how people, data, processes, and
information technology can best accomplish improvements for the
business.
• A programmer/analyst (or
analyst/programmer) includes the
responsibilities of both the computer programmer
and the systems analyst.
• A business analyst focuses on only the non-
technical aspects of systems analysis and design.
The Systems Analyst as a Problem-Solver
• By "Problems" that need solving, we mean:
• Problems, either real or anticipated, that require
corrective action.
• Opportunities to improve a situation despite the
absence of complaints.
• Directives to change a situation regardless of
whether anyone has complained about the current
situation.
Skills Needed by the Systems Analyst
• Working knowledge of information technology
• Computer programming experience and expertise
• General business knowledge
• General problem-solving skills
• Good interpersonal communication skills
 • Good interpersonal relations skills
• Flexibility and adaptability
• Character and ethics
Other Stakeholders
External Service Provider (ESP) – a systems analyst, system
designer, or system builder who sells his or her expertise and
experience to other businesses to help those businesses purchase,
develop, or integrate their information systems solutions; may be
affiliated with a consulting or services organization.
Project Manager – an experienced professional who accepts
responsibility for planning, monitoring, and controlling projects with
respect to schedule, budget, deliverables, customer satisfaction,
technical standards, and system quality.
Business Drivers for Today’s Information Systems
• Globalization of the Economy
• Electronic Commerce and Business
• Security and Privacy
• Collaboration and Partnership
• Knowledge Asset Management
• Continuous Improvement and Total Quality Management
• Business Process Redesign
Globalization of the Economy
Global Economy brings.
• New and expanded international markets.
• New international competitors
Impact on information systems
• Require support of multiple languages, currency
exchange rates, business cultures
• Require consolidation of international data
• Demand for players who can communicate, orally
and in writing, with management and users that
speak different languages.
Electronic Commerce and Business
E-Commerce – the buying and selling of goods and services by
using the Internet.
E-Business – the use of the Internet to conduct and support day-to-
day business activities.
Types of e-commerce and e-business
• Marketing of corporate image, products, and
services
• Business-to-consumer (B2C)
• Business-to-business (B2B)
Impact on information systems
• Most new information systems are being
designed for an Internet (or intranet) architecture.
• Since the only client-side software is a web
browser, the choice of client operating system is
becoming less important.
Security and Privacy
Security
• How will the business continue in the event of a
security breach, terrorist attack, or disaster?
• How can the business protect its digital assets
from outside threats?
Privacy
• Consumer demands for privacy in e-commerce
transactions
• Government requirements
Impact on information systems
• Need to incorporate stringent security and
privacy controls.
Collaboration and Partnership
Organizations seek to break down the walls that separate
organizational departments and functions.
Organizations collaborate with outside business partners and even
competitors.
Impact on information systems
• Need to provide secure, external access.
• Need to pass data between different information
systems.
Knowledge Asset Management
Data – raw facts about people, places, events, and things that are of
importance in an organization.
Information – data that has been processed or reorganized into a
more meaningful form for someone.
Knowledge – data and information that is further refined based on
the facts, truths, beliefs, judgments, experiences, and expertise of the
recipient.
Knowledge Asset Management
• Recognizes that data, information, and
knowledge are critical business resources.
• Asks: “How can the organization manage and
share knowledge for competitive advantage?”
• Strives to integrate the data and information that
can create and preserve knowledge.
Continuous Improvement and Total Quality Management
Business Processes – Tasks that respond to business events (e.g., an
order). Business processes are the work, procedures, and rules
required to complete the business tasks, independent of any
information technology used to automate or support them.
Continuous process improvement (CPI) – The continuous • Objects are reusable.
monitoring of business processes to effect small but measurable
improvements in cost reduction and value added. • Objects are extensible.

Total quality management (TQM) – a comprehensive approach to • Object-oriented programming languages include
facilitating quality improvements and management within a business. C++, Java, Smalltalk, and .NET

Business Process Redesign
Business process redesign (BPR) is the study, analysis, and redesign
of fundamental business processes to reduce costs and/or improve
value added to the business.
• More substantial changes and improvements than
CPI
Object-oriented analysis and design – a collection of tools and
techniques for systems development that will utilize object
technologies to construct a system and its software.
Agile development – a system development strategy in which system
developers are given the flexibility to select from a variety of tools
and techniques to best accomplish the tasks at hand.

• Usually complemented by CPI

Collaborative Technologies
Technology Drivers for Today’s Information Systems
Collaborate technologies are those that enhance interpersonal
• Networks and the Internet communications and teamwork.

• Mobile and Wireless Technologies • E-mail

• Object Technologies • Instant messaging

• Collaborative Technologies • Groupware

• Enterprise Applications • Workflow.

Networks and the Internet Enterprise Applications

Networks include mainframe time-sharing systems, network servers, • Virtually all organizations require a core set of enterprise
and a variety of desktop, laptop, and handheld client computers. applications.

The most pervasive networking technologies are based on the • Financial mgmt., human resources, sales, etc.
Internet.
• Frequently purchased.
• XHTML and XML
• Frequently need to have custom elements added.
• Scripting languages
• Systems Integration - the process of building a
• Web-specific programming languages unified information system out of diverse
components of purchases software, custom-built
• Intranets software, hardware, and networking.
• Extranets Enterprise Applications – ERP
• Portals Enterprise Resource Planning (ERP) – a software application that
fully integrates information systems that span most or all of the basic,
• Web services
core business functions.
Mobile and Wireless Technologies
An ERP solution is built around a common database shared by
Some mobile and wireless technologies common business functions.

• PDAs Representative ERP vendors:

• Smart phones • SSA

• Bluetooth • Oracle/Peoplesoft

• Wireless networking • SAP AG

Impact on information systems Enterprise Applications – SCM

• Wireless connectivity must be Supply Chain Management (SCM) – a software application that
assumed. optimizes business processes for raw material procurement through
finished product distribution by directly integrating the logistical
• Limitations of mobile devices information systems of organizations with those of their suppliers and
and screen sizes must be accommodated. distributors.

Object Technologies Representative SCM vendors:

Object technology – a software technology that defines a system in • i2 Technologies

terms of objects that consolidate data and behavior (into objects).
• Manugistics
 • SAP System analysis – the study of a business problem domain to
recommend improvements and specify the business requirements and
• SCT priorities for the solution.
Enterprise Applications – CRM System design – the specification or construction of a technical,
computer-based solution for the business requirements identified in a
Customer Relationship Management (CRM) – a software
system analysis.
application that provides customers with access to a business’s
processes from initial inquiry through postsale service and support. System implementation – the construction, installation, testing, and
delivery of a system into production.
Representative CRM vendors:
Project and Process Management
• SAP
Project management – the activity of defining, planning, directing,
• BroadVision
monitoring, and controlling a project to develop an acceptable system
• E.piphany within the allotted time and budget.

• Kana Process management – the ongoing activity that defines, improves,

and coordinates the use of an organization’s chosen methodology (the
• Amdocs “process”) and standards for all system development projects.

• Oracle/Peoplesoft Topic 2

• Siebel Information System Building Blocks

Enterprise Applications – EAI Front- and Back-Office

Information Systems
Enterprise Application Integration (EAI) – the process and
technologies used to link applications to support the flow of data and • Front-office information systems support business
information between those applications. functions that extend out to the organization’s customers (or
constituents).
Middleware – software (usually purchased) used to translate and
route data between different applications. • Marketing

Representative EAI vendors: • Sales

• BEA Systems • Customer management

• IBM (MQSeries) • Back-office information systems support internal business

operations of an organization, as well as reach out to
• Mercator Software suppliers (of materials, equipment, supplies, and services).
• TIBCO Software • Human resources
System Development Process • Financial management
System development process – a set of activities, methods, best • Manufacturing
practices, deliverables, and automated tools that stakeholders use to
develop and maintain information systems and software. • Inventory control.

A general problem-solving approach Information Systems Architecture

1. Identify the problem. Information systems architecture - a unifying framework into

2. Analyze and understand the problem.
3. Identify solution requirements or expectations.
4. Identify alternative solutions and choose the
“best” course of action.
5. Design the chosen solution.
6. Implement the chosen solution.
7. Evaluate the results. If the problem is not solved,
return to step 1 or 2 as appropriate.
System Development Process Overview
System initiation – the initial planning for a project to define initial
business scope, goals, schedule, and budget.
which various stakeholders with different perspectives can organize
and view the fundamental building blocks of information systems.
High-Level Goals of System Owners and System Users
• Improve business knowledge.
• Improve business processes and services.
• Improve business communication and people collaboration.
Technology Perspectives of System Designers & System Builders
• Database technologies that support business accumulation
and use of business knowledge
• Software technologies that automate and support business
processes and services
• Interface technologies that support business communication
and collaboration
 Focuses for Information Systems
• Knowledge — the raw material used to create useful
information.
• Process — the activities (including management) that carry
out the mission of the business.
• Communication — how the system interfaces with its
users and other information systems.
Views of KNOWLEDGE
• System owners’ view
• Interested not in raw data but in information that
adds new business knowledge and helps
managers make decisions.
• Business entities and business rules.
• System users’ view
• View data as something recorded on forms,
stored in file cabinets, recorded in books and
spreadsheets, or stored on computer.
• Focus on business issues as they pertain to data.
• Data requirement – a representation of users’
data in terms of entities, attributes, relationships,
and rules independent of data technology.
• System designers’ view
• Data structures, database schemas, fields,
indexes, and constraints of database management
system (DBMS).
• System builders’ view
• SQL
• DBMS or other data technologies
Views of PROCESS
• System owners’ view
• Concerned with high-level processes called
business functions.
• Business function – a group of related processes
that support the business. Functions can be
decomposed into other subfunctions and
eventually into processes that do specific tasks.
• A cross-functional information system – a
system that supports relevant business processes
from several business functions without regard to
traditional organizational boundaries such as
divisions, departments, centers, and offices.
• System users’ view
• Concerned with work that must be performed to
provide the appropriate responses to business
events.
• Business processes – activities that respond to
business events.
• Process requirements – a user’s expectation of
the processing requirements for a business
process and its information systems.
• Policy – a set of rules that govern a business
process.
• Procedure – a step-by-step set of instructions
and logic for accomplishing a business process.
• Workflow – the flow of transactions through
business processes to ensure appropriate checks
and approvals are implemented.
• System designers’ view
• Concerned with which processes to automate and
how to automate them.
• Constrained by limitations of application
development technologies being used.
• Software specifications – the technical design of
business processes to be automated or supported
by computer programs to be written by system
builders.
• System builders’ view
• Concerned with programming logic that
implements automated processes.
• Application program – a language-based,
machine-readable representation of what a
software process is supposed to do, or how a
software process is supposed to accomplish its
task.
• Prototyping – a technique for quickly building a
functioning, but incomplete model of the
information system using rapid application
development tools.
Views of COMMUNICATION
• System owners’ view
• Who (which business units, employees,
customers, and partners) must interact with the
system?
• Where are these business units, employees,
customers, and partners located?
• What other information systems will the system
have to interface with?
• System users’ view
• Concerned with the information system’s inputs
and outputs.
• System designers’ view
• Concerned with the technical design of both the
user and the system-to-system communication
interfaces.
• Interface specifications – technical designs that
document how system users are to interact with a
system and how a system interacts with other
systems.
• User dialogue – a specification of how the user
moves from window to window or page to page,
interacting with the application programs to
perform useful work.
 • System builders’ view
• Concerned with the construction, installation,
testing and implementation of user and system-
to-system interface solutions.
• Middleware – utility software that allows
application software and systems software that
utilize differing technologies to interoperate.
Network Technologies and the IS Building Blocks
Clean-layering approach allows anyone building block to be
replaced with another while having little or no impact on the other
building blocks.
Topic 3
Information Systems Development
Process of System Development
System development process – a set of activities, methods, best
practices, deliverables, and automated tools that stakeholders (topic
1) use to develop and continuously improve information systems and
software.
Life Cycle versus Methodology
• System life cycle – the factoring of the lifetime of an
information system into two stages, (1) systems
development and (2) systems operation and maintenance.
• System development methodology – a formalized
approach to the systems development process; a
standardized development process that defines (as in CMM
Level 3) a set of activities, methods, best practices,
deliverables, and automated tools that system developers
and project managers are to use to develop and
continuously improve information systems and software.
Principles of System Development
• Get the system users involved.
• Use a problem-solving approach.
• Establish phases and activities.
• Document through development.
• Establish standards.
• Manage the process and projects.
• Justify systems as capital investments.
• Don’t be afraid to cancel or revise scope.
• Divide and conquer.
• Design systems for growth and change.
Use a Problem-Solving Approach
Classical Problem-solving approach
1. Study and understand the problem, its context,
and its impact.
2. Define the requirements that must be meet by any
solution.
3. Identify candidate solutions that fulfill the
requirements and select the “best” solution.
4. Design and/or implement the chosen solution.
5. Observe and evaluate the solution’s impact and
refine the solution accordingly.
Manage the Process and Projects
Process management – an ongoing activity that documents,
manages, oversees the use of, and improves an organization’s chosen
methodology (the “process”) for system development. Process
management is concerned with phases, activities, deliverables, and
quality standards should be consistently applied to all projects.
Project management is the process of scoping, planning, staffing,
organizing, directing, and controlling a project to develop an
information system at a minimum cost, within a specified time frame,
and with acceptable quality.
Justify Information Systems as Capital Investments
Cost-effectiveness – The result obtained by striking a balance
between the lifetime costs of developing, maintaining, and operating
an information system and the benefits derived from that system.
Cost-effectiveness is measured by a cost-benefit analysis.
Strategic information systems plan – a formal strategic plan (3-5
years) for building and improving an information technology
infrastructure and the information system applications that use that
infrastructure.
Strategic enterprise plan – a formal strategic plan (3-5 years) for an
entire business that defines its mission, vision, goals, strategies,
benchmarks, and measures of progress and achievement. Usually, the
strategic enterprise plan is complemented by strategic business unit
plans that define how each business unit will contribute to the
enterprise plan. The information systems plan is one of those unit-
level plans.
Don’t Be Afraid to Cancel or Revise Scope
Creeping commitment – a strategy in which feasibility and risks are
continuously reevaluated throughout a project. Project budgets and
deadlines are adjusted accordingly.
Risk management – the process of identifying, evaluating, and
controlling what might go wrong in a project before it becomes a
threat to the successful completion of the project or implementation
of the information system. Risk management is drive by risk analysis
or assessment.
Where Do Systems Development Projects Come From?
• Problem – an undesirable situation that prevents the
organization from fully achieving its purpose, goals, and/or
objectives.
• Opportunity – a chance to improve the organization even
in the absence of an identified problem.
• Directive - a new requirement that is imposed by
management, government, or some external influence.
• Planned Projects
• An information systems strategy plan has
examined the business as a whole to identify
those system development projects that will
return the greatest strategic (long-term) value to
the business.
 • A business process redesign has thoroughly
analyzed a series of business processes to
eliminate redundancy and bureaucracy and to
improve efficiency and value added. Not it is
time to redesign the supporting information
system for those redesigned business processes.
• Unplanned projects
• Triggered by a specific problem, opportunity, or
directive that occurs in the course of doing
business.
• Steering committee – an administrative body of
system owners and information technology
executives that prioritizes and approves candidate
system development projects.
• Backlog – a repository of project proposals that
cannot be funded or staffed because they are a
lower priority than those that have been approved
for system development.
The PIECES Problem-Solving Framework
P the need to improve performance
I the need to improve information (and
data)
E the need to improve economics, control
costs, or increase profits
C the need to improve control or security
E the need to improve efficiency of people
and processes
S the need to improve service to customers,
suppliers, partners, employees, etc.
Scope Definition Phase
Problem statement – a statement and categorization of problems,
opportunities, and directives; may also include constraints and an
initial vision for the solution. Synonyms include preliminary study
and feasibility assessment.
Constraint – any factor, limitation, or restraint that may limit a
solution or the problem-solving process.
Scope creep – a common phenomenon wherein the requirements and
expectations of a project increase, often without regard to the impact
on budget and schedule.
Statement of work – a contract with management and the user
community to develop or enhance an information system; defines
vision, scope, constraints, high-level user requirements, schedule, and
budget. Synonyms include project charter, project plan, and service-
level agreement.
Requirements Analysis Phase
• What capabilities should the new system provide for its
users?
• What data must be captured and stored?
• What performance level is expected?
• What are the priorities of the various requirements?
Logical Design Phase
Logical design – the translation of business user requirements into a
system model that depicts only the business requirements and not any
possible technical design or implementation of those requirements.
Common synonyms include conceptual design and essential design.
System model – a picture of a system that represents reality or a
desired reality. System models facilitate improved communication
between system users, system analysts, system designers, and system
builders.
Analysis paralysis – a satirical term coined to describe a common
project condition in which excessive system modeling dramatically
slows progress toward implementation of the intended system
solution.
Decision Analysis Phase
• Candidate solutions evaluated in terms of:
• Technical feasibility – Is the solution technically
practical? Does our staff have the technical
expertise to design and build this solution?
• Operational feasibility – Will the solution fulfill
the users’ requirements? To what degree? How
will the solution change the users’ work
environment? How do users feel about such a
solution?
• Economic feasibility – Is the solution cost-
effective?
• Schedule feasibility – Can the solution be
designed and implemented within an acceptable
time?
• Risk feasibility – What is the probability of a
successful implementation using the technology
and approach?
Physical Design & Integration Phase
Physical design – the translation of business user
requirements into a system model that depicts a technical
implementation of the users’ business requirements. Common
synonyms include technical design or implementation model.
Two extreme philosophies of physical design
• Design by specification – physical system models and
detailed specification are produced as a series of written (or
computer-generated) blueprints for construction.
• Design by prototyping – Incomplete but functioning
applications or subsystems (called prototypes) are
constructed and refined based on feedback from users and
other designers.
Construction and Testing Phase
• Construct and test system components
• Software
• Purchased
• Custom-built
• Databases
• User and System Interfaces
• Hardware
 • Networks
Installation and Delivery Phase
• Deliver the system into operation (production)
• Deliver User training
• Deliver completed documentation
• Convert existing data
System Operation & Maintenance
System support – the ongoing technical support for users of a
system, as well as the maintenance required to deal with any errors,
omissions, or new requirements that may arise.
Sequential versus Iterative Development
Waterfall development approach an approach to systems analysis
and design that completes each phase one after another and only once
.
Iterative development approach an approach to systems analysis
and design that completes the entire information system in successive
iterations. Each iterations does some analysis, some design, and some
construction. Synonyms include incremental and spiral.
Model-Driven Development Strategy
• Model-driven development – a system development
strategy that emphasizes the drawing of system models to
help visualize and analyze problems, define business
requirements, and design information systems.
• Process modeling – a process-centered technique
popularized by the structured analysis and design
methodology that used models of business
process requirements to derive effective software
designs for a system.
• Data modeling – a data-centered technique used
to model business data requirements and design
database systems that fulfill those requirements.
• Object modeling – a technique that attempts to
merge the data and process concerns into singular
constructs called objects. Object models are
diagrams that document a system in terms of its
objects and their interactions.
Logical vs. Physical Models
Logical model - a pictorial representation that depicts what a system
is or does.
Physical model - a technical pictorial representation that depicts
what a system is or does and how the system is implemented.
Automated Tools and Technology
• Computer-aided systems engineering (CASE)
• Application development environments (ADEs)
• Process and project managers.
Application Development Environments
Application development environments (ADEs) – an integrated
software development tool that provides all the facilities necessary to
develop new application software with maximum speed and quality.
A common synonym is integrated development environment (IDE)
• ADE facilities may include:
• Programming languages or interpreters
• Interface construction tools
• Middleware
• Testing tools
• Version control tools
• Help authoring tools.
• Repository links
Topic 4
System Analysis
What is Systems Analysis?
Systems analysis – a problem-solving technique that decomposes a
system into its component pieces for the purpose of studying how
well those component parts work and interact to accomplish their
purpose.
Systems design – a complementary problem-solving technique (to
systems analysis) that reassembles a system’s component pieces back
into a complete system—hopefully, an improved system. This may
involves adding, deleting, and changing pieces relative to the original
system.
Information systems analysis – those development phases in an
information systems development project the primarily focus on the
business problem and requirements, independent of any technology
that can or will be used to implement a solution to that problem.
Repository
Repository – a location (or set of locations) where systems analysts,
systems designers, and system builders keep all of the documentation
associated with one or more systems or projects.
Accelerated Systems Analysis
Accelerated systems analysis approaches emphasize the
construction of prototypes to more rapidly identify business and user
requirements for a new system.
prototype – a small-scale, incomplete, but working sample of a
desired system.
 Accelerated systems analysis approaches • Discovery
Prototyping
 Rapid Architected Analysis
Discovery Prototyping
Discovery prototyping – a technique used to identify the users’
business requirements by having them react to a quick-and-dirty
implementation of those requirements.
Rapid Architected Analysis
Rapid architected analysis – an approach that attempts to derive
system models (as described earlier in this section) from existing
systems or discovery prototypes.
 Reverse engineering – the use of technology that reads the
program code for an existing database, application
program, and/or user interface and automatically generates
the equivalent system model.
Requirements Discovery
Requirements discovery – the process, used by systems analysts of
identifying or extracting system problems and solution requirements
from the user community.
Agile Methods
Agile method – integration of various approaches of systems analysis
and design for applications as deemed appropriate to problem being
solved and the system being developed.
 Technical feasibility – Is the solution technically practical?
Does our staff have the technical expertise to design and
build this solution?
 Operational feasibility – Will the solution fulfill the users’
requirements? To what degree? How will the solution
change the users’ work environment? How do users feel
about such a solution?
 Economic feasibility – Is the solution cost-effective?
 Schedule feasibility – Can the solution be designed and
implemented within an acceptable time period?

Systems Analysis Phases

Scope Definition Phase

 Is the project worth looking at?

Problem Analysis Phase

 Is a new system worth building?

Requirements Analysis Phase

 What do users need and want from the new system?

Logical Design Phase

 What must the new system do?

Decision Analysis Phase

 What is the best solution?

Key Terms of the Problem Analysis Phase

Cause-and-effect analysis – a technique in which problems are

studied to determine their causes and effects.

Context Diagram – a pictorial model that shows how the system

interacts with the world around it and specifies the system inputs and
outputs in general terms.

Objective – a measure of success. It is something that you expect to

achieve, if given sufficient resources.

Constraint – something that will limit your flexibility in defining a

solution to your objectives. Essentially, constraints cannot be
changed.

Key Terms of Requirements Analysis Phase

Functional requirement – a description of activities and services a

system must provide.

 inputs, outputs, processes, stored data

Nonfunctional requirement – a description of other features,

characteristics, and constraints that define a satisfactory system.

 Performance, ease of learning and use, budgets, deadlines,

documentation, security, internal auditing controls

Use case – a business scenario or event for which the system must
provide a defined response. Use cases evolved out of objectoriented
analysis; however, their use has become common in many other
methodologies for systems analysis and design.

Timeboxing – a technique that delivers information systems

functionality and requirements through versioning.

Key Terms of Decision Analysis Phase