BIA Final review

What are actors?

people and hardware

what are instructions?

Software and procedures

What is the bridge?

Data

What are the human categories of BIA

Procedures and people

What is the computer side 

hardware and software

What goes into an information system?

hardware, software, data, procedure, and humans

how does automation move?

from human side to computer side

What are the types of SDLC

predictive and adaptive

predictive SDLC

requirements are well understood and defined as well as low technical risks (waterfall method)

Adaptive SDLC

requirements and needs are uncertain and there is a high technical risk

What is the Systems Development Life Cycle?

planning, analysis, design, implementation, and maintenance

step 1 of SDLC

planning

step 2 of SDLC

Analysis

step 3 of SDLC

design

step 4 of SDLC

implementation 

step 5 SDLC

maitenance

the choice of SDLC…

varies depending on the project

Adaptive SDLC Uses

different iterations and plans for different scenarios, somewhat opposite of the waterfall effect as things from the past can be changed

what is the first planning activity?

1. project identification

what is the second planning activity?

project selection

what is the third planning activity?

project initiation & planning

origin of projects steps:

1. sources of potential projects
2. project identification and selection
3. project initiation and planning

sample ERP vendors:

oracle, SAP, Microsoft, INFOR, IFS, EPICOR, ACUMATICA, SYSPRO, Workday, and Sage

What goes into project selection?

* perceived needs
* existing resources
* list of ongoing projects
* current org. environment
* evaluation criteria

Decision outcome

* accept project
* Reject project
* Delay project
* Refocus project
* End-User development
* Proof of concept

Value chain alanylsis

where activities add value and costs when developing services

strategic alignment

project is viewed as helping the organization achieve its strategic objectives and long term goal

potential benefits

project is viewed as improving the organizations performance

resource availability

amount and type of resources the project requires and their availability

project size/ duration

number of individuals and the length of time needed to complete the project

prescriptive lingo

* resources
* scope
* project charter/ manager
* deliverables
* Critical path
* Gannt Chart
* Work breakdown structure

Adaptive lingo

* project charter
* scrum master
* product owner
* sprint schedule
* themes
* epics
* user stories
* daily scrum

Analyst Jobs & Roles

Business analyst, Systems analyst, Data Analyst, programmer

Good system analysts have characteristics like:

* impertinence
* impartiality
* relax constraints
* attention to detail
* reframing

system requirements are:

all the activities that the system must perform or support and the new systems must meet

functional requirements

are the activities that the system must perform

nonfunctional requirements

characteristics of the system other then those activities it must perform or support

FURPS

Functional

Usability

Reliability

Performance

Security

Methods of collecting system requirement types

traditional & contemporary

traditional methods of collecting system requirements include:

* interviewing and listening
* directly observing others
* analyzing procedures and other documents

contemporary methods of collecting system requirements include:

* JAD sessions
* Prototyping
* User Interface Modeling

drawbacks of interviewing individuals

* not as efficient
* new interviews may require new questions
* reconciling contradictions in information collected

group interview advantages

* more effective use of time
* allows synergy when groups can hear each other
* primary disadvantage is difficulty in scheduling with multiple people involved

interview guidlines

* phrase a question so that the interviewee can give their own answer rather than provide a question with an implied answer
* seek a variety of perspectives from the interviews

Studying business documents

to discover reported \n issues, policies, rules, and \n directions as well as concrete \n examples of the use of data \n and information in the \n organization. \n 1. Written Work Procedures \n 2. Forms \n 3. Reports \n 4. Documents that describe \n how the system is used.

Business Process Model

Key!!!!- swim lane charts show the flow of a business and the internal connections

Joint application design (JAD)

structured \n process in which users, managers, and \n analysts work together for several days in a \n series of intensive meetings to specify or \n review system requirements

prototyping

An iterative process of systems development in \n which requirements are converted to a working \n system that is continually revised through close \n collaboration between an analyst and users \n ▪ Quickly converts basic requirements into working, \n limited version of final information system \n ▪ Viewed and tested by the user \n ▪ Prompts user for modifications for final system

evolutionary prototyping

Begin by modeling part of the target system \n ▪ If successful, evolve rest of the system from those parts \n ▪ Prototype becomes the actual production system

throwaway prototyping

Prototype is not preserved once system is built \n ▪ Quickly developed as a mockup \n Prototyping

When is prototyping most useful

\
* User requirements are not clear. \n ▪ Few users are involved in the system \n ▪ Designs are complex and require concrete form \n to evaluate. \n ▪ Communication problems have existed in the \n past. \n ▪ Tools and data are readily available to rapidly \n build a prototype.

prototyping drawbacks

▪ A tendency to avoid creating formal \n documentation. \n ▪ Difficult to adapt to other potential users. \n ▪ Built as standalones makes it difficult to \n adapt to other users. \n ▪ SDLC checks are often bypassed.

Wireframes

▪ Outline only broad \n structural characteristics \n of an application

mockups

Include key controls \n fields, buttons, menus, \n etc., and sample data. \n BIA350 (Ames)

\

What are the primary analysis activities?

1. determine requirements
2. requirements structure

model

a conceptual representation or abstraction of some aspect of the system being built

Why do analysts build models?

* to describe system requirements and
* to communicate with users and designers

modeling can help

the analyst demonstrate understanding of the users requirements

How are models created?

by using \n specialized software tools, or sometimes \n drawn quickly over lunch on a paper napkin

interactive approach

used for creating models where the first draft of the model has MOST of the details worked out and then the second iteration of the model will fill in more details

Benefits of modeling

▪ Learning from the modeling process \n ▪ Reducing complexity by abstraction \n ▪ Remembering all the details \n ▪ Communicating with a variety of users and \n stakeholders \n ▪ Documenting what was done for future \n maintenance/enhancement

what is the greatest benefit models can offer?

a comprehensive view

what are the different types of models?

User Interface models

business process models

Data models

Logic Models

Textual Models

What are user interface model examples?

Mockups and wireframes

Data flow diagram

process model

decision table

logic model

Data models

Entity relationship models & Dimensional Data Models

user story format

As a (role played), I want to (goal or desire) so that (reason of benefit).

Business process

is a standrad method for accomplishing a particular task necessary for an organization to function

a business process can

come from any business function and can cross business functions as well

BPMN

Business Process Modeling Notation

What do user stories do?

* describe a goal to a user
* are a basic agile development concept
* answer who, what, and why

Methodology consist of

SDLC or Analysis activities

Modeling techniques

BMPN and User Stories

Data Modeling phases are:

1. Conceptual model
2. logical model
3. physical model

physical model

detailed technical solution used to adapt to work within a set of hardware, software, and network tools

logical model

detailed representation of data requirements usually in support of a specific usage of context

conceptual model

\
captures the high-level data requirements as \n a collection of related concepts. It contains only the basic and \n critical entities within a given realm and function,

Entity-relationship Model

* for processing transactions
* characteristics:
* removes data redundancy
* ensures data consistency
* expresses a range of relationships

Dimensional Model

for conducting analytics:

* captures critical measures
* views along dimensions
* intuitive to business users

transactional modeling

apply ERD modeling

analytical

apply dimensional modeling

Another example of a Dimensional model is…

a star schema

ETL

Extract Transform and Load

Dimensional design process

1. select the business process
2. Declare the grain
3. Identify the dimensions
4. Identify the facts

Business processes

the operational activities performed \n by your organization, such as taking an order, processing an \n insurance claim, registering students for a class, or \n snapshotting every account each mont

facts are the…

measures that result from a business process event and are almost always numeric

Traditional ETL

extracts and \n transforms data from different sources \n before loading it into a data warehouse.

ELT processing ….

is enabled by cloud technology and

1\. EXTRACT the data from multiple data sources. \n 2. LOAD data into the cloud data warehouse. \n 3. TRANSFORM data using the power and scalability of the cloud \n platform.

analytics architecture consists of

data sources→ data warehousing→ analytic tools

questions to ask when using the report

1\. Who will use the report? \n 2. What is the purpose of the report? \n 3. When is the report needed and used? \n 4. Where does the report need to be \n delivered and used? \n 5. How many people need to use or view the \n report? \n

dashboards

Provide visual displays of \n important information that is \n consolidated and arranged \n on a single screen so that \n information can be digested at \n a single glance and easily \n drilled in and further \n explored. \n

three layers of information required for a good dashboard include:

monitoring, analysis, and management

monitoring:

graphical abstracted data to monitor key performance metrics

analysis

summarized dimensional data to analyze the root cause of problems

management

detailed operational data that identify what actions to take to resolve a problem

Design steps

1. design databases
2. design forms/ reports
3. design interfaces

implementation requires

1. coding
2. testing
3. installation
4. documentation
5. training
6. support

testing occurs in

analysis, design, and implementation