WEEK 1 2024 – INTRODUCTION & SU1

CMPG213 Systems Analysis and Design I

Mrs LINDA REDELINGHUYS

[email protected]
 OUTLINE
1. Welcome
2. Language
3. Communication and classes (G1_111)
4. Module overview
5. Textbooks
6. Projects
a. Join project group on Site Info
b. Decide on project scenario, +- 4 nouns
c. Tutor Support
d. Projects
 OUTLINE continues
8. eFundi site
a. Gradebook
b. Assessment plan (40% Participation mark required to
obtain admission to write exam, Final Module mark will be
calculated as 50% Participation mark + 50% Exam mark)
c. Semester Work Plan
d. Study units
e. Assessments
I. Class Test 1, 29 February @ 7:30
II. Project Proposal, 26 February – 1 March, to
be submitted 24 hours PRIOR to proposal
9. Study Unit 1 (Chapter 1)
10. Questions
Lecturer: Mrs Linda Redelinghuys for CMPG213
Language
Communication and classes
• Communication weekly on
Monday mornings outlining the
week’s work
• All classes in G1_111
• Videos to watch PRIOR to classes
(see Semester Work Plan on
eFundi)
Module overview
• Up to now, only written (developed) single
programs as part of your degree in IT.
• During this year you will learn about methods
(methodologies) to develop systems consisting of
several programs and including aspects such as
architecture and databases.
• Waterfall, Agile and Hybrid methodologies
Module overview
• Senior Project Manager
• Project Manager
• Senior Project Leader
• Project Leader
• Senior Systems Analyst
• Systems Analyst
• Senior Developer
• Developer
Textbooks

A link to an electronic copy of this

textbook is available under the Resource
-> Textbook folder
Projects
• Join a project group on
eFundi Site Info page
• 5-6 members per group
• Stay behind after class to
join a project team
• Decide on project scenario,
+- 4 nouns
• Tutor Support is available,
contact detail on eFundi
 eFundi site
• No Gradebook
• Assessment plan (NOTE: 40%
Participation mark required to obtain
admission to write exam, Final Module
mark will be calculated as 50%
Participation mark + 50% Exam mark)
• Semester Work Plan
• Study units
Assessments
• Class Test 1, 29 February @ 7:30
• No late assignments, No 2nd
Opportunities without doctor’s
letter
• Plagiarism
• Project Proposal, 26 February – 1
March, to be submitted 24 hours
Questions??
 The value of
systems analysis
and design
Study Unit 1
Chapter 1
Objectives (Study
Guide):
• Describe seven types of information system applications; (p.16 - 22)
• Describe an information system and the role of the systems analyst; (p. 11 - 12)
• Describe what systems analysis and design is; (p. 32 -33)
• Explain how modern business and technologies influence systems development; (p.
22 - 30)
• Describe the role of each role player in the SDLC (Systems Development Life
Cycle); (p. 7 - 16)
• Explain what knowledge and skills are required to become a successful systems
analyst; and (p. 14 - 15)
• Approach the role of systems analyst with the ethically correct and responsible
attitude. (p. 15 - 16)
Objectives continue:
• distinguish between the waterfall and other iterative / incremental approaches to
system development;
• describe business and technology drivers influencing development; and
• describe a simple process for the development of IS.
SU1 The value of Systems
Analysis and Design
For this year, you need to know:
1.Stakeholders involved in Information systems
2.The role of the Systems Analyst
3.Distinguish between the waterfall and other
iterative / incremental approaches to system
development;
4.Business drivers for Information systems (only
summary slide)
5.Technology drivers for Information systems (only
summary slide)
6.A Simple Systems development process
A Framework for Systems Analysis
and Design
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).
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.
Stakeholders' Perspectives on an
Information System
System Owners
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
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
• Clerical and service workers
• Technical and professional staff
• 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
Classwork
• Problems and Exercises No 1 P 37

Assume you are a systems analyst who will be conducting a

requirements an analysis for an individually owned brick-and-mortar
retail store with a point-of-sale system. Identify who the typical
internal and external users might include.
Classwork Memo
• Problems and Exercises No 1 P 37

The internal users of the system might include the cashier, store
manager, store owner, salesperson, stock clerks, and the “back office”
accounting staff.
The external users of the system might include credit card
companies, the retail point of sale system vendor, federal and state
tax agencies, suppliers and customers.
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
Class Activity
The Ten Commandments of
Computer Ethics
1. Thou shalt not use a computer to harm other people.
2. Thou shalt not interfere with other people’s computer work.
3. Thou shalt not snoop around in other people’s computer files.
4. Thou shalt not use a computer to steal.
5. Thou shalt not use a computer to bear false witness.
6. Thou shalt not copy or use proprietary software for which you have not paid.
7. Thou shalt not use other people’s computer resources without authorization or proper
compensation.
8. Thou shalt not appropriate other people’s intellectual output.
9. Thou shalt think about the social consequences of the program you are writing or the
system you are designing.
10. Thou shalt always use a computer in ways that insure consideration and respect for
your fellow human

Source: Computer Ethics Institute

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.
Figure 1-8: Traditional
Waterfall SDLC
The SDLC Traditional Waterfall
Problems

• Once one phase ends another begins, going downhill

until complete
• Makes it difficult to go back
• Results in great expense to make changes
• Role of system users or customers narrowly defined
• Focused on deadlines
Agile Methodologies

Agile methodologies share three key principles:

1. A focus on adaptive rather than predictive
methodologies
2. A focus on people rather than roles
3. A focus on self-adaptive processes
Table 1-2: The Agile
Manifesto (1 of 3)
• The agile methodologies group argues that software development methodologies
adapted from engineering generally do not fit with real world software
development
• The Manifesto for Agile Software Development (Table 1-2)
• Seventeen anarchists agree
• We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

A manifesto is a published declaration of the intentions, motives, or

views of the issuer
Table 1-2: The Agile Manifesto
(2 of 3)
• That is, while we value the items on the right, we value the items on the left
more. We follow the following principles:
• The highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile
processes harness change for the customer’s competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple
of months, with a preference to the shorter timescale.
• Businesspeople and developers work together daily throughout the
project.
• Build projects around motivated individuals. Give them the environment
and support they need and trust them to get the job done.
• The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
• Working software is the primary measure of progress.
Table 1-2: The Agile
Manifesto (3 of 3)
• Continuous attention to technical excellence and good design
enhances agility.
• Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
• Simplicity—the art of maximizing the amount of work not done—
is essential.
• The best architectures, requirements, and designs emerge from
self-organizing teams.
• At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.

-- (www.AgileAlliance.org)
Agile Methodologies—Not for
Every Project

• Agile methodologies are not for everyone

• Fowler recommends an agile process if your
project involves
• unpredictable or dynamic requirements
• responsible and motivated developers
• customers who understand the process and
will get involved
Table 1-3: Five Critical Factors that
Distinguish Agile and Traditional
Approaches to System Development

Factor Agile Methods Traditional Methods

Size Well matched to small products and teams Methods evolved to handle large products and teams
Reliance on tacit knowledge limits scalability Hard to tailor down to small products

Criticality Untested on safety-critical products Methods evolved to handle highly critical products Hard
Potential difficulties with simple design and lack of to tailor down to products that are not critical.
documentation

Dynamism Simple design and continuous refactoring Detailed plans and Big Design Up Front, excellent for
are excellent for highly dynamic environments highly stable environment but a source of expensive
but a source of potentially expensive rework for rework for highly dynamic environments
highly stable environments

Personnel Requires continuous presence of a critical mass of Needs a critical mass of scarce experts during project
scarce experts definition but can work with fewer later in the project,
Risky to use non-agile people unless the environment is highly dynamic

Culture Thrives in a culture where people feel comfortable Thrives in a culture where people feel comfortable and
and empowered by having many degrees of empowered by having their roles defined by clear practices
freedom (thriving on chaos) and procedures (thriving on order)
eXtreme Programming (1 of 2)

• Short, incremental development cycles

• Focus on automated tests written by programmers
• Emphasis on two-person programming teams
• Customers to monitor the development process
• Relevant parts of eXtreme Programming that relate
to design specifications are
1. How planning, analysis, design, and construction
are all fused into a single phase of activity
2. Its unique way of capturing and presenting system
requirement and design specifications
eXtreme Programming
(2 of 2)

• Coding and testing are related parts of the same

process
• Advantages include
• Increased communications among developers
• Higher levels of productivity
• Higher quality code
• Reinforcement of other practices in eXtreme
Programming
• Include code-and-test discipline
Scrum (1 of 3)

• Originated in 1995 by Sutherland and Schwaber

• Most popular methodology for agile (58%)
• Scrum framework includes Scrum teams with
associated roles, events, artifacts, and rules
• Each team consists of three roles
• Product owner
• Development team
• Scrum master
Scrum (2 of 3)
• Scrum designed for speed and multiple
functional product releases
• Primary unit is the Sprint (runs two weeks to a
month)
• Starts with an eight-hour planning meeting
• What needs to be delivered by the end of
the sprint
• How will the team accomplish that work
• Daily Standup: A 15-minute meeting held to
evaluate progress made within the past 24
hours and what needs to be done
Scrum (3 of 3)

• At the end of the sprint, two additional meetings

• The Sprint Review: (4 hours) focusing on the product, what
has been accomplished, and what needs to be done
• The Sprint Retrospective: (3 hours) focusing on team
performance and how it can improve
• Three primary artifacts in the Scrum process
1. Product Backlog: Listing of potential requirements
2. Sprint Backlog: Listing of only items to be addressed in a
particular sprint
3. Increment: Represents the sum of all the Product Backlog
items completed during a sprint.
Agile in Practice
• Three primary factors critical for success
• Delivery strategy: Continuous delivery of working
software in short time scales
• Following agile software engineering practices
• Team capability: Agile principle of building
projects around motivated individuals
• Agile development offers managers and
programmers more choice in their efforts to produce
good systems that come in on time and under budget
Object-Oriented Analysis and
Design (OOAD)
• Based on objects rather than data or processes
• Combines data (called attributes) and processes (called
methods) into single entities call objects
• Object: A structure that encapsulates attributes and
methods that operate on those attributes
• Inheritance: Hierarchical arrangement of classes
enabling subclasses to inherit properties of superclasses
• Object Class: Logical grouping of objects that have the
same attributes and behaviors
 Relational Unified Process (R
UP)

• Relational Unified Process (RUP) is an object-oriented

systems development methodology
• Based on an iterative, incremental approach to systems
development
• RUPs four phases (each can be further divided)
• Inception - Communication and planning
• Elaboration - Planning and modeling
• Construction - Project is developed and completed
• Transition - Final project is released to public
Figure 1-9: Phases of OOAD-
Based Development
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

monitoring of business processes to effect small but measurable
improvements in cost reduction and value added.

Total quality management (TQM) – a comprehensive approach

to facilitating quality improvements and management within a
business.
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
• Usually complemented by CPI
Technology Drivers for Today’s
Information Systems
• Networks and the Internet
• Mobile and Wireless Technologies
• Object Technologies
• Collaborative Technologies
• Enterprise Applications
Networks and the Internet
Networks include mainframe time-sharing systems, network
servers, and a variety of desktop, laptop, and handheld
client computers.

The most used networking technologies are based on the

Internet.
• XHTML and XML
• Scripting languages
• Web-specific programming languages
• Intranets
• Extranets
• Portals
• Web services
Mobile and Wireless Technologies
Some mobile and wireless technologies
• PDAs
• Smart phones
• Bluetooth
• Wireless networking

Impact on information systems

• Wireless connectivity must be
assumed
• Limitations of mobile devices
and screen sizes must be accommodated
Object Technologies
Object technology – a software technology that defines a system in
terms of objects that consolidate data and behavior (into objects).
• Objects are reusable
• Objects are extensible
• Object-oriented programming languages include C++, Java, Smalltalk, and .NET

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 (not methodology) – 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.
Collaborative Technologies
Collaborate technologies are those that enhance interpersonal
communications and teamwork.
• E-mail
• Instant messaging
• Groupware
• Work flow
Enterprise Applications
• Virtually all organizations require a core set of enterprise
applications
• Financial mgmt, human resources, sales, etc.
• Frequently purchased
• Frequently need to have custom elements added

• Systems Integration - the process of building a unified

information system out of diverse components of purchases
software, custom-built software, hardware, and networking.
Enterprise Applications
Enterprise Applications - ERP
Enterprise Resource Planning (ERP) – a software application that
fully integrates information systems that span most or all of the
basic, core business functions.

An ERP solution is built around a common database shared by

common business functions.

Representative ERP vendors:

• SSA
• Oracle/Peoplesoft
• SAP AG
Enterprise Applications - EAI
Enterprise Application Integration (EAI) – the process and technologies used
to link applications to support the flow of data and information between
those applications.

Middleware – software (usually purchased) used to translate and route data

between different applications.

Representative EAI vendors:

• BEA Systems
• IBM (MQSeries)
• Mercator Software
• TIBCO Software
System Development Process
System development process – a set of activities, methods, best practices,
deliverables, and automated tools that stakeholders use to develop and
maintain information systems and software.
A Simple System
Development Process
Our Simplified System General Problem-Solving Steps
Development Process
System initiation 1. Identify the problem.
System analysis 2. Analyze and understand the problem.
3. Identify solution requirements or
expectations.

System design 4. Identify alternative solutions and choose the

“best” course of action.
5. Design the chosen solution.

System implementation 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.

System analysis – the study of a business problem domain to recommend

improvements and specify the business requirements and priorities for the
solution.

System design – the specification or construction of a technical, computer-

based solution for the business requirements identified in a system analysis.

System implementation – the construction, installation, testing, and delivery

of a system into production.
Project and Process Management
Project management – the activity of defining, planning, directing,
monitoring, and controlling a project to develop an acceptable
system within the allotted time and budget.

Process management – the ongoing activity that defines, improves,

and coordinates the use of an organization’s chosen methodology
(the “process”) and standards for all system development projects.
Objectives (Study
Guide):
• Describe seven types of information system applications; (p.16 - 22)
• Describe an information system and the role of the systems analyst;
(p. 11 - 12)
• Describe what systems analysis and design is; (p. 32 -33)
• Explain how modern business and technologies influence systems
development; (p. 22 - 30)
• Describe the role of each role player in the SDLC (Systems
Development Life Cycle); (p. 7 - 16)
• Explain what knowledge and skills are required to become a
successful systems analyst; and (p. 14 - 15)
• Approach the role of systems analyst with the ethically correct and
responsible attitude. (p. 15 - 16)
Objectives continue:
• distinguish between the waterfall and othrt iterative / incremental
approaches to system development;
• describe business and technology drivers influencing development;
and
• describe a simple process for the development of IS.
Homework
• Read the summary on p. 34 – 37
• Create a 2 page summary of Chapter 1.
• Finalise the group members of your team and decide
on possible topics for your project.