teb exam 1
Customer Relationship Management (CRM)
connects ERP system to those of its customers, manages marketing sales and customer services
Supply Chain Management (SCM)
connects companies that supply's for products
systems development life cycle (sdlc)
waterfall, interative, agile
hardware diagram
storage (barrel) --> server (1) --> network (multiple servers) --> peripherals (several devices)
business analyst strategy
used to work as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization
project testing framework "v" model
validation: business need -----> system testing requirements -----> user acceptance test verification: design -----> integration and regression test construction -----> unit test
reasons data fails
- data migration: - data quality: data not maintained - lack of business analytics and intelligence
cutover
"opening" the new IT system for business processing, to go live
longterm challenges with failure
- organization (employee changes) - data (formatting errors)
reasons processes fails
- poor requirements - business cycle often faster than IT implementation - automation of poorly designed process
reasons hardware fails
- poor response time - poor testing
Reasons organization fails
- silo effect: you need to change how you think before you change how they think - culture and values, beliefs, practices - fear, uncertainty, doubt
reasons software fails
- software capabilities not meeting process (no effectiveness) - software defects/bugs (no accuracy) - inadequate documentation & training - poor testing
John Kotter's 8 Steps to Leading Change
- thaw 1) set the stage: create urgency 2) pull together guiding team 3) develop the change: how will the future be different - reshape 4) communicate for understanding 5) empower others to act - freeze 6) produce short term wins 7) don't let up 8) create a new culutre
IT asset support drill down
1. define and manage service levels 2. educate and train users 3. advise and assist users 4. manage problems 5. manage the configuration (change management) 6. identify & allocate costs
IT discovery portfolio
1. identify opportunities 2. manage and mature ideas 3. assess concept feasibility & risk 4. develop solution value proposition
IT project portfolio phases
1. planning 2. requirements 3. design 4. construction 5. testing 6. deployment
services oriented architecture (SOA)
1. web service 2. composite applications
process change strategies
Business process automation (run), business process improvement (grow), business process reengineering (transform)
Servers
Computers that exist only to provide things to others.
Local Area Network (LAN)
Connects a group of computers in close proximity, such as in an office building, school, or home
erp system
Demand to Supply (plan) supplier --> requisition to pay (buy) --> plan to produce (make) --> inquiry to sell (sell) --> customer Financial Accounting (track)
pilot (phased) implementation deployment
Deploy the new IT system for only a small group of people, typically a business segment
risk heat map
Frequency/severity Low/low - retain loss High/low- loss control Low/high - insurance High/high - avoid
Wide Area Network (WAN)
Spans a large geographic area such as a state, province, or country
single (big bang) cutover deployment
Stop the legacy IT system and cutover the new IT system in one-step
SIPOC
Suppliers, Inputs, Process, Outputs, Customers
parallel processing deployment
Utilize the legacy IT system in parallel with the new target IT system
project
a temporary endeavor undertaken to create a unique product, service, or result
norm
able and unwilling
perform
able and willing
IT assets portfolio phases (legacy)
accept assets --> supports assets (BA) --> evaluate assets --> disposition assets [ased]
Product Lifecycle Management (PLM)
administers research, design, product management
evaluate assets
assets the business value and fit of IT assets
four key skills of a business analyst in processing
business acumen, problem solving, process management, total work systems
buying software
characteristics: commercial off-the-shelf (COTS), change process to meet software pros: leverage best practices, develop configuration skills cons: possible legacy integration challenges, newly trained staff may leave. provider upgraders require regression testing
building software
characteristics: in-house, custom, can change software to meet process pros: satisfies unique requirements, develops coding skills cons: slow delivery, lower quality, company must maintain
enterprise IT (EIT)
cross-functional business processes
As-is system
current system, legacy
erp & inter-enterprise system
customer relationship management (CRM), product lifecycle management (PLM), supply chain management (SCM), supplier relationship management (SRM)
information
data in relationship
master data
defines entities used in execution
work breakdown structure:
defines the hierarchy of project tasks, subtasks, and work packages
factor rating method
determine criteria, assign weights to each criteria, weight X rating = score
disposition of assets
determine next steps for IT assets
function IT (FIT)
discrete task
transactional data
documents the outcome of executing business processes
network IT (NIT)
enables interactions without parameters
Supplier Relationship Management (SRM)
enables the quotation and contracts processes; an extension to the procurement and planning of ERP's
IT Portfolio Management
includes: IT asset portfolio, IT discovery portfolio, IT project portfolio
inter-enterprise processes
erp in the middle, plm (top), crm (right), scm (bottom), srm(left)
situational leaders
form, strom, norm, perform
business process automation (bpa) = run
goal: keep the lights on, limited changes, focus is on as-is system
network admin
hardware
evaluating risk
high risk low business value: disregard, high risk high business value: consider, low risk low business value: consider, low risk high business value: execute
evaluating technical fit
high tech fit low business value: reposition to maintain, low tech fit low business value: replace, low tech fit high business value: reengineer to maintain, high tech fit high business value: MAINTAIN.
what purpose does a business analyst serve
in between business needs and IT capability
inter-enterprise IT
information systems that are shared by two or more independent organizations
database admin
infrastructure
steps of transformation of people
invest --> understanding --> accountability --> ownership
networks
local area network (LAN), wide area network (WAN)
phase
major milestone or review point (gate)
accepting assets
manage the intake of the new IT assets from IT project portfolio
tasks
measurable units of work
business process improvement (bpi) = grow
more of the same, moderate changes, focus on as-is and to-be
data migration
moving data over from the legacy system to the new system
stabilization
offering support of the new IT system after cutover until users are using it effectively and efficiently
waterfall system development process
parallel processing deployment
IT system deployment strategies
parallel, phased, single
Enterprise Architecture
organization & people business process layer application (software) layer data (info/knowledge) layer infrastructure (hardware) layer
scope of business analyst (the largest)
organization, business process, application, data
knowledge
patterns/trends in information
business analyst
people, process, software, data
hardware
peripherals, network, servers, storage
organizational data
physical and logical structure of data
agile system development process
planning --> requirement to testing, then back to planning, until deployment sing
training
preparing users to effectively and efficiently operate new system
peripherals
printers, scanners and other devices used with a computer
system analyst
process, software, data
work package
produces a deliverable
support assets
provide support services for IT assets
business process reengineering (bpe) = transform
radical changes, improving productivity and end-to-end business process, focus on to-be
data
raw facts
storage
relational database management (RDBM) and storage area network (SAN)
iterative system development process
requirement to testing, then back to testing until deployment phased processing deployment
requirements management framework
requirements elicitation + requirements analysis + requirements verification + validation = requirements documentation (think about diagram!!)
it project portfolio phases that pertain to business analytics
requirements, testing, and deployment
systems admin
running the infrastructure
software engineer
software --> writes code for data
aggregate data
summarizes transactional data for use in business analytics (intelligence)
to be system
the new system that is based on updated requirements; occurs through a transformation
software
the programs and other operating information used by a computer.
client-server server
three-tier: 1. database 2. application 3.presentation
technology enabled business
to leverage information systems to automate and integrate the people and processes of an enterprise in a manner that enables sustainable competitive advantage.
functional organizational structure
top (analytics) --> middle --> operational (reporting data)
IT project portfolio
transformation
storm
unwilling and unable
form
willing and unable