Systems, Roles, and Development

Methodologies

1
Lecturer: Kanar R. Tariq
Sulaimani Polytechnic University
@2023
 Introduction
 Information Technology (IT)
◼ Combination of hardware and software products and
services that companies and individuals use to
manage, access, communicate, and share
information
 The Future
◼ Three issues that will shape the future
 Changes in world
 Changes in technology
 Changes in client demand

2
 The Impact of Information
Technology
 Systems Analysis and Design
◼ Systems Analysis and Design
 Step-by-step process for developing high-quality information
systems
 Systems Development
◼ Business information systems are developed by
people who are technically qualified, business-
oriented, and highly motivated
 Must be good communicators with strong analytical and
critical thinking skills

3
 System and Information
• A system is a set of related components that
produces specific results
• A Mission-critical system is one that is vital to a
company’s operations
• Data consists of basic facts that are the system’s
raw material
• Information is data that has been transformed into
output that is valuable to users
• Information systems have five key components:
hardware, software, data, processes, and people
4
 Information System Components
 Hardware
◼ Is the physical layer of
the information system
◼ Moore’s Law
 Software
◼ System software
◼ Application software
◼ Enterprise applications
◼ Horizontal system
◼ Vertical system
◼ Legacy systems 5
 Information System Components
 Data
◼ Tables store data
◼ Linked tables work
together to supply
data

6
Information System Components
 Processes
◼ Describe the tasks and
business functions that
users, managers, and
IT staff members
perform to achieve
specific results
 People
◼ Stakeholders
◼ Users, or end users

7
 Understanding The Business
 Business Process Modeling
 Business Profile

 Business Models

8
 Impact of the Internet
E-Commerce or I-Commerce
◼ B2C (Business-to-Consumer)
◼ B2B (Business-to-Business)
◼ Mobile Commerce (M-Commerce)
◼ Local Commerce
◼ Social Commerce

9
 Type of The System
◼ Transaction Processing Systems (TPS)
◼ Office Automation Systems (OAS)
◼ Knowledge Work Systems (KWS)
◼ Management Information Systems (MIS)
◼ Decision Support Systems (DSS)
◼ Expert Systems (ES)
◼ Executive Support Systems (ESS)
◼ Group Decision Support Systems (GDSS)
◼ Computer-Supported Collaborative Work Systems
(CSCWS)
1-10
 Strategic
Level

Higher
Level

Knowledge
Level

Operational
Level

A systems analyst may be involved with any or

all of these systems at each organization level. 1-11
 Need for Systems Analysis and Design
 Installing a system without proper planning leads
to great user dissatisfaction and frequently
causes the system to fall into disuse.
 Lends structure to the analysis and design of
information systems
 A series of processes systematically undertaken
to improve a business through the use of
computerized information systems

1-12
 Systems Analyst
 Plan,develop, and maintain information
systems
 The analyst must be able to work with
people of all descriptions and be
experienced in working with computers.
 Three primary roles:
◼ Consultant
◼ Supporting expert
◼ Agent of change
1-13
 Qualities of the Systems Analyst
 Problem solver
 Communicator
 Strong personal and professional ethics
 Self-disciplined and self-motivated

1-14
 Systems Development Life Cycle (SDLC)
 The systems development life cycle is a phased
approach to solving business problems.
 Developed through the use of a specific cycle of
analyst and user activities
 Each phase has unique user activities.

1-15
The Seven Phases of the Systems Development Life
Cycle

1-16
Some Researchers Estimate that the Amount of Time Spent on Systems
Maintenance May Be as Much as 60 Percent of the Total Time Spent1-17
on Systems Projects
 The Impact of Maintenance
 Maintenance is performed for two reasons:
◼ Removing software errors
◼ Enhancing existing software
 Over time the cost of continued
maintenance will be greater than that of
creating an entirely new system. At that
point it becomes more feasible to perform a
new systems study.

1-18
1-19
 Four Agile Resources
 Resources are adjusted to ensure
successful project completion.
◼ Time
◼ Cost
◼ Quality
◼ Scope

1-20
 Five Stages of Agile Development
 Exploration
 Planning

 Iterations to the first release

 Productionizing

 Maintenance

1-21
Agile Approach
1-22
 Object-Oriented (O-O) Systems Analysis
and Design
 Alternate approach to the structured approach of the
SDLC that is intended to facilitate the development
of systems that change rapidly in response to
dynamic business environments
 Analysis is performed on a small part of the system
followed by design and implementation.
 The cycle repeats with analysis, design, and
implementation of the next part and this repeats until
the project is complete.
 Examines the objects of a system
1-23
Unified Modeling Language
(UML) Phases

1-24
 Choosing a Method
 Choose either:
◼ SDLC
◼ Agile

◼ Object-oriented methodologies

1-25
 When to Use SDLC
 Systems have been developed and documented
using SLDC.
 It is important to document each step.
 Upper level management feels more
comfortable or safe using SDLC.
 There are adequate resources and time to
complete the full SDLC.

1-26
 When to Use Agile
 There is a project champion of agile methods in the
organization.
 Applications need to be developed quickly in response to
a dynamic environment.
 A rescue takes place (the system failed and there is no
time to figure out what went wrong).
 The customer is satisfied with incremental
improvements.
 Executives and analysts agree with the principles of
agile methodologies.

1-27
 When to Use Object-Oriented
 The problems modeled lend themselves to
classes.
 An organization supports the UML learning.
 Systems can be added gradually, one
subsystem at a time.
 Reuse of previously written software is a
possibility.
 It is acceptable to tackle the difficult problems
first.
1-28
 Incorporating Human-Computer Interaction
(HCI) Considerations
 The demand for analysts who are
capable of incorporating HCI into the
systems development process keeps
increasing, as companies begin to realize
that the quality of systems and the quality
of work life can be improved by taking a
human-centered approach at the outset
of a project.

1-29
 Using Case Tools
 CASE tools are productivity tools for
systems analysts that have been created
explicitly to improve their routine work
through the use of automated support.
 Reasons for using CASE tools
◼ Increasing analyst productivity

◼ Improving analyst-user communication

◼ Integrating life cycle activities

1-30
 Case Tool Classifications
 Upper CASE tools perform analysis
and design.
 Lower CASE tools generate programs

from CASE design.

1-31
 Upper CASE Tools
 Create and modify the system design.
 Help in modeling organizational
requirements and defining system
boundaries.

1-32
 Lower CASE Tools
 Lower CASE tools generate computer
source code from the CASE design.
 Source code is usually generated in several
languages.
 Decreases maintenance time
 Generates error-free code

1-33