{INF2009F}
[SYSTEMS ANALYSIS]
WEEK 1 - 6
WEEK 1: SYSTEMS DEVELOPMENT & PROJECT FAILURE
WEEK 2: UML & THE BUSINESS ANALYST
WEEK 3: ACTIVITY DIAGRAMS
WEEK 4: THE BUSINESS CASE & PACKAGE DIAGRAM
WEEK 5: FACT FINDING TECHNIQUES & USE CASE DIAGRAMS
WEEK 6: USE CASE NARRATIVES
Chloe Walt
YEAR 2, SEMESTER 1, 2021
,MAIN CASE STUDY: Phumla Kamnandi (Rest Well) Hotels Case Study:
Þ Phumla Kamnandi Hotel Group is a new empowerment group formed to
manage a portfolio of small hotels around SA.
Þ There are 30 hotels in the group, each of which run independently.
Þ These hotels benefit from being part of a group, as marketing is done at a
group level.
Þ Many of the hotels were previously private owned, that have now been
purchased by the group.
Þ All the hotels have different facilities; however, the aim is for the interaction
with customers to be the same and consistent across all the hotels.
Þ The group is moving towards a standardized business process.
Þ The same computer needs to be implemented at each hotel to maintain
standardized practices, a standard image, standardized management and
financial reporting & reduce total cost of ownership (TCO) of hardware,
software and training across the group.
Þ Planning happens through Exco, the Executive Committee at the HQ in
Century City
Þ Marketing works on implementing a growing Customer Relationship
Management (CRM) function.
Þ All the hotels have the same room lay out, same deals, same facilities.
Þ The only inconsistency is the software and hardware implementation. These
are not standardized across all the hotels.
Þ Account payment is inconsistent, all use computers, but some use
spreadsheets/ home grown applications while other hotels use accounting
packages.
Þ Bars, restaurant, laundry, room service etc. are "service points"/ "cost
centers" which run on a paper voucher system called "chits". All services run
on the chit system besides the Room Tariffs and Phone bills.
Þ Each hotel has its own system for dealing with creditors.
, WEEK 1: INTRODUCTION TO SYSTEMS ANALYSIS:
Information System: is a set of interrelated components that collect, process, store data
and provide as output information needed to complete business tasks. It always includes
people who operate the system, carry out some work or consume the output.
Computer application: is a computer software program that executes on a computer device
to perform a specific function or a set of related functions.
Systems Analysis: is the activities that a person performs to understand and specify what a
system must do.
System Analysis is therefore all about: What is required for the system to solve the problem?
Not only one statement but a detailed description what is required to satisfy the need or solve the
problem. (ordering process at Takealot)
The initial development of a new information system is usually done as a project.
A Project: is a planned undertaking that has a beginning and an end and produces some end result.
A project unfolds a temporary purposeful action. It as an initial phase, middle and final
phase.
So where have projects failed?
1. London Heathrow - FEB 2020: 100 flights distrupted due to technical issues.
2. Facebook - 2019: Facebook and all the platforms that it owns crashed.
3. Fiat Chrysler: over a million trucks recalled due to software glitch. Glitch disabled airbags
and seatbelt functionality.
Every two years the Standish Group publish a new CHAOS Report. These reports include
classic CHAOS (Comprehensive Human Appraisal for Originating Software) data in different
forms with many charts.
Five cards of a winning hand for project success were introduced:
If one can maintain the following 5 elements:
§ First card: The project needs to be small
§ Second card: The product Owner or sponsor must be highly skilled
§ Third card: The process must be agile
§ Fourth card: the agile team must be highly skilled in both the agile process and the
technology
§ Fifth card: The organization must be highly skilled at emotional maturity
Then a project would have a greater possibility of success
, Root causes of project failure:
1. ad hoc requirement management
2. Poor communication
3. Brittle architectures
4. Overwhelming complexity
5. Undetected inconsistencies
6. failure to attack risks
7. Uncontrolled change propagation
8. Poorly defined project scope
9. Cultural differences in global projects
What are the symptoms of project failure?
1. Requirements
- System does not meet user requirements
- Inability to deal with changing requirements
2. Time/ Cost
- Project is over time/ over budget
3. Quality
- Hard to maintain and upgrade
- Poor quality - errors and omissions
4. Integration:
- Problems with integration
- In 2015: 29% of companies successful, 52% challenged, 19% failed.
- The iron triangle: time, scope & budget
[SYSTEMS ANALYSIS]
WEEK 1 - 6
WEEK 1: SYSTEMS DEVELOPMENT & PROJECT FAILURE
WEEK 2: UML & THE BUSINESS ANALYST
WEEK 3: ACTIVITY DIAGRAMS
WEEK 4: THE BUSINESS CASE & PACKAGE DIAGRAM
WEEK 5: FACT FINDING TECHNIQUES & USE CASE DIAGRAMS
WEEK 6: USE CASE NARRATIVES
Chloe Walt
YEAR 2, SEMESTER 1, 2021
,MAIN CASE STUDY: Phumla Kamnandi (Rest Well) Hotels Case Study:
Þ Phumla Kamnandi Hotel Group is a new empowerment group formed to
manage a portfolio of small hotels around SA.
Þ There are 30 hotels in the group, each of which run independently.
Þ These hotels benefit from being part of a group, as marketing is done at a
group level.
Þ Many of the hotels were previously private owned, that have now been
purchased by the group.
Þ All the hotels have different facilities; however, the aim is for the interaction
with customers to be the same and consistent across all the hotels.
Þ The group is moving towards a standardized business process.
Þ The same computer needs to be implemented at each hotel to maintain
standardized practices, a standard image, standardized management and
financial reporting & reduce total cost of ownership (TCO) of hardware,
software and training across the group.
Þ Planning happens through Exco, the Executive Committee at the HQ in
Century City
Þ Marketing works on implementing a growing Customer Relationship
Management (CRM) function.
Þ All the hotels have the same room lay out, same deals, same facilities.
Þ The only inconsistency is the software and hardware implementation. These
are not standardized across all the hotels.
Þ Account payment is inconsistent, all use computers, but some use
spreadsheets/ home grown applications while other hotels use accounting
packages.
Þ Bars, restaurant, laundry, room service etc. are "service points"/ "cost
centers" which run on a paper voucher system called "chits". All services run
on the chit system besides the Room Tariffs and Phone bills.
Þ Each hotel has its own system for dealing with creditors.
, WEEK 1: INTRODUCTION TO SYSTEMS ANALYSIS:
Information System: is a set of interrelated components that collect, process, store data
and provide as output information needed to complete business tasks. It always includes
people who operate the system, carry out some work or consume the output.
Computer application: is a computer software program that executes on a computer device
to perform a specific function or a set of related functions.
Systems Analysis: is the activities that a person performs to understand and specify what a
system must do.
System Analysis is therefore all about: What is required for the system to solve the problem?
Not only one statement but a detailed description what is required to satisfy the need or solve the
problem. (ordering process at Takealot)
The initial development of a new information system is usually done as a project.
A Project: is a planned undertaking that has a beginning and an end and produces some end result.
A project unfolds a temporary purposeful action. It as an initial phase, middle and final
phase.
So where have projects failed?
1. London Heathrow - FEB 2020: 100 flights distrupted due to technical issues.
2. Facebook - 2019: Facebook and all the platforms that it owns crashed.
3. Fiat Chrysler: over a million trucks recalled due to software glitch. Glitch disabled airbags
and seatbelt functionality.
Every two years the Standish Group publish a new CHAOS Report. These reports include
classic CHAOS (Comprehensive Human Appraisal for Originating Software) data in different
forms with many charts.
Five cards of a winning hand for project success were introduced:
If one can maintain the following 5 elements:
§ First card: The project needs to be small
§ Second card: The product Owner or sponsor must be highly skilled
§ Third card: The process must be agile
§ Fourth card: the agile team must be highly skilled in both the agile process and the
technology
§ Fifth card: The organization must be highly skilled at emotional maturity
Then a project would have a greater possibility of success
, Root causes of project failure:
1. ad hoc requirement management
2. Poor communication
3. Brittle architectures
4. Overwhelming complexity
5. Undetected inconsistencies
6. failure to attack risks
7. Uncontrolled change propagation
8. Poorly defined project scope
9. Cultural differences in global projects
What are the symptoms of project failure?
1. Requirements
- System does not meet user requirements
- Inability to deal with changing requirements
2. Time/ Cost
- Project is over time/ over budget
3. Quality
- Hard to maintain and upgrade
- Poor quality - errors and omissions
4. Integration:
- Problems with integration
- In 2015: 29% of companies successful, 52% challenged, 19% failed.
- The iron triangle: time, scope & budget
