Classification:
Workflow engine
1. Physical tangible entities that
maybe static or dynamic.
2. Abstract conceptual
3. Open interact with the
environment
4. Closed do not interact with the
environment
5. Adaptive respond to the
changes in the environment
6. Non-Adapative does not
respond to the environment
7. Permanent long term system
8. Temporary made for specific
time and after it is being
destroyed.
9. Natural created by nature
10. Manufactured man made
system
11. Deterministic operates in a
predictable manner and
interaction is known in certainty.
12. Probabilistic unknown
behavior.
13. Social made up of people
14. Human Machine involves both
human and machine
15. Machine human interference
is neglected.
16. Man made information system
- Formal IS flow of info
from top to lower
management
- Informal IS employee
based
- Computer based IS relies
on computer
PLAYERS IN THE SYSTEM PRINCIPLE:
1. User
2. Management (User Manager,
IS/IT Manager, General
Management)
3. Auditors, Quality Assurance and
standard bearer
4. System Analyst (Archaeologist
and Scribe, Innovator, Project
Leader)
5. System Designer
6. Programmer
7. Web Designer
8. Operations personnel
Embedded system a
microcontroller or
microprocessor based system
which is designed to perform a
specific task.
3 components: 1. Has hardware;
2. Has application software; 3.
Has real time operating system
(RTOS)
Workflow movement of information or
material from one activity or worksite to
another. Includes procedure, people and
tools.
Business Process collection of related,
structured activities or task that leads to
produce a service or product.
3 types of BP:
1. Primary or essential direct
contact with the customers,
reaching and exceeding the
company standard.
2. Support Process supports
primary, no contact with the
customer
3. Management coordinates the
activities of primary and support
process, seek business efficacy
and efficiency.
2 main factors that contribute to business
processes: 1. Contact with customer
should always be satisfactory and exceed
their expectation; 2. Customer
characterize the degree of benefit they
receive by whether or not the process
meets their expectations or exceed its.
Main goals are to increase the customer
value and reduce cost for an organization.
Characteristics for a BP: Definability,
Order, Customer, Value-adding,
embeddedness, Cross-functionality,
analysis.
Other types of BP:
1. Business Process re-engineering
(BPR) change the way an
individual performs work such
that better results are
accomplished.
- BPR Steps
1. Define objectives and
Framework
2. Identify customer
needs
3. Study the existing
business process
4. Formulate a redesign
business plan
5. Implement the
redesign plan
2. Business Process Automation
(BPA) -uses to automate
processes in order to contain
costs.
3. Business Process Management
systematic approach to making
organizations workflow more
effective, more efficient and
more capable of adapting to an
ever-changing environment.
5-Basic components of BPM:
1. Process discovery and
project scoping
2. Process modeling and
design
3. Business rules engine
4.
5. Simulation and testing
4. Business Process Modeling
method for improving
organizational efficiency and
quality.
Purpose: - A Business Process Model
diagram is a tool - a means to an end.
- The final output is improvement in
the way that the business process
works.
- The focus of the improvements is on
'value added' actions that make the
customer service and experience
better, and on reducing wasted time
and effort.
There are two main different types of
Business Process Models:
- the 'as is' or baseline model (the current
situation)
- and the 'to be' model (the intended new
situation)
which are used to analyze, test,
implement and improve the process.
5. Business Process Model and
Notation (BPMN) graphical
representation for designing and
modeling business process
visually. It is a standard for
business process modeling and
provides a graphical notation for
specifying business processes in
a Business Process Diagram
BPMN's four basic element categories
are:
Flow objects- Events, activities, gateways
Connecting objects- Sequence flow,
message flow, association
Swim lanes- Pool, lane
Artifacts- Data object, group, annotation
6. Business Process Mapping - It
essentially defines how a
particular activity in a business is
carried out
The Major Steps of Process Improvement
using Process Mapping: 1. Process
identification - identify objectives, scope,
players and work areas. 2. Information
gathering - gather process facts (what,
who, where, when) from the people who
do the work. 3. Process Mapping - convert
facts into a process map. 4. Analysis - work
through the map, challenging each step. 5.
Develop/Install New Methods - eliminate
unnecessary work, combine steps,
rearrange steps, add new steps where
necessary.
Characteristics of A good analyst:
 1. The system analyst must be able
to communicate in writing and
orally.
2. The analyst must easily get
along with people.
3. The analyst must be a good
listener and be able to react to
what people say.
4. The analyst must be
knowledgeable of technology.
The analyst is not expected to
know the intricacies of
programming, but a decent
general knowledge of concepts
and terms are essential.
5. The analyst must be
knowledgeable of business. The
analyst is not expected to be an
expert in business but a decent
understanding of the client's
world is required.
Problems of Analysis:
1. Contradicting/Conflicting
requirements
2. Communication problem
3. Undocumented process
4. Lack of access to end-users
5. Instability of UI preferences
6. Abundance of choice
7. Stakeholders designs
8. Bad requirements
9. Stakeholder change their mind
10. Stakeholders are not willing to
speak up or they are being too
expensive
11. Stakeholders have conflicting
priorities.
When a computer-based information
system is developed, system analysis
(according to the Waterfall model) would
constitute the following steps:
- The development of a feasibility study
- Fact-finding measures, designed to
ascertain the requirements of the system's
end-users
- Gauging how the end-users would
operate the system and what the system
would be used for and so on
Another view outlines a phased approach
to the process. This approach breaks
system analysis into 5 phases:
- Scope Definition
- Problem analysis
- Requirements analysis
- Logical design
- Decision analysis
LIMITATIONS OF SYSTEMS ANALYSIS
1. Some business problems are beyond Document requirements or
the scope of systems analysis techniques. contribute to user manuals.
2. Systems analysis efforts cost time and Whenever a development
money. process is conducted, the system
3. The human element can cause analyst is responsible for
complications. People tend to oppose designing components and
change. They resist adjusting to unfamiliar providing that information to
situations. the developer.
4. Effort is required to sell a system. No
matter how promising a systems analysis Vision: A World-Class University
project may seem, it cannot self itself. Producing Leaders and Change
ADVANTAGES OF SYSTEMS ANALYSIS Agents for Social Transformation and
1. Costs, Efficiency and Flexibility Development.
When a system analysis is Mission: The Bicol University shall
properly performed, it makes give professional and technical
certain that the correct path is training, and provide advanced and
taken with regards to application specialized instruction in literature,
and it helps to minimize errors philosophy, the sciences and arts,
which reduce future IT besides providing for the promotion
requirements for fixing of technological researches (RA 5521,
problems. Sec.3.0).
2. Better Managements or Better Controls Quality Policy: Bicol University
System analysis allows for better commits to continually strive for
management through changing excellence in instruction, research,
the software to suit any business and extension by meeting the highest
changes, this means that the level of clientele satisfaction and
final product will be totally adhering to quality standards.
controllable.
3. Quality
The quality of the systems is
ensured through the checking of
the system constantly through
system analysis.
4. Effective skill use
Since systems analysis does not
demand the use of special skills,
it is easily teachable to the
employees.
RESPONSIBILITIES OF A SYSTEM ANALYST
Identify, understand and plan for
organizational and human
impacts of planned systems, and
ensure that new technical
requirements are properly
integrated with existing
processes and skill sets.
Plan a system flow from the
ground up.
Interact with internal users and
customers to learn and
document requirements that are
then used to produce business
requirements documents.
Write technical requirements
from a critical phase.
Interact with software architect
to understand software
limitations.
Help programmers during
system development.