2. organization, managment and the networked enterprise

5/12/2018 2. Organization, Managment and the Networked Enterprise - slidepdf.com

http://slidepdf.com/reader/full/2-organization-managment-and-the-networked-enterprise 1/28

1

Autumn 2011

Lesson - 2

Organizations, Management

and the Network Enterprise

MBA508



2

Figure 1-5

CH1: IS in Global Business Today

Dimensions of information systems

± Organizations

An organization is a social group which distributestasks for a collective goal.

± Management

Management in all business and organizationalactivities is the act of getting people together toaccomplish desired goals and objectives usingavailable resources efficiently and effectively.

± Technology

Information Technology is one of the many toolsmanager use to coop with changes. ( e.g.. Software,Hardware, Data Management Technology,

Networking and telecommunication technology.)

What is an information system?A set of interrelated components that collect (or retrieve), process, store, and distribute information

to support decision making and control in an organization



3

How information systems are transforming business and what is their relationship to

globalization?

Software

Enterprise System

Supply Chain Management System

Customer Relation Management System

K nowledge Management System

Hardware

Data Management System

Telecommunication System

Email

Video Conferencing

VOIP Internetwork


The Interdependence Between OrganizationsThe Interdependence Between Organizationsand Inf ormation Technologyand Inf ormation Technology

Figure 1-2



4

The R ole of Inf ormation Systems in Business Today


Operational excellence

New products, services, and business models

Customer and supplier intimacy

Improved decision making

Competitive advantage

Survival



5

Technical approach:Emphasizes mathematically based models, physical technology, and formal capabilities of systems

Behavioral approach:

Studies issues arising from development and maintenance of systems, such as businessintegration and utilization

Contemporary Approaches to Information Systems




6

Business Processes and Inf ormation Systems

CH2: E-Business: How Business use IS

Fulf illing a customer order involves a complex set of steps that requires theclose coordination of the sales, accounting, and manuf acturing functions.

A Business process is a logically related set of activities that define howspecific business tasks are performed, and it represents a unique way in whichan organization coordinates work, information and knowledge.

The Order Fulf illment ProcessThe Order Fulf illment Process



7

Functional Perspective :-

± Sales and marketing systems

± Manufacturing and production systems

± Finance and accounting systems

± Human resources systems

Constituency Perspective: -

± Transaction processing systems

± Management information systems anddecision-support systems

± Executive support systems

Relationship of systems to one another

Types of Business Inf ormation Systems


Overview of an Inventory Overview of an Inventory SystemSystem



8

Interrelationships Among SystemsInterrelationships Among Systems

Types of Business Inf ormation Systems


TPS ( Transaction Processing Systems): A TPS is a

computerized systems that performs and records the

daily routine transactions necessary to conduct

business such as sales order entry, hotel reservations,

payroll, employee record keeping and shipping

DSS ( Decision Support Systems): A DSS is a

computerized system that supports business or

organizational decision-making activities. DSSs

serve the management, operations, and planning

levels of an organization and help to make decisions,

which may be rapidly changing and not easily

specified in advance.

ESS ( Executive Support Systems): A ESS help

senior management make these decisions. ESS

address non routine decision requiring judgment,

evaluation, and insight because there is no agreed on

procedure for arriving at a solution.



9

SystemsTh

at Span th

e Enterprise


Enterprise Applications : Enterprise applications automate processes that span multiple business

functions and organizational levels and may extend outside the organization.

Four Major Type of Enterprise Application

Enterprise systems: Also known as enterprise resource planning (ERP) systems solve this problem

by collecting data from various key business process in manufacturing and production, finance andaccounting, Sales and marketing , human resource and storing the data in a single central data

repository.

Supply chain management systems : Also known as SCM which helps businesses manage

relationships with their suppliers. SCM systems are one type of inter-organizational system because

they automate the flow of information across organization boundaries.

Customer relationship management systems : Also know as CRM system which help firms

managing their relationships with their customers. This system provide information to coordinate all of

the business processes that deal with customers in dales, marketing and service to optimize revenue,

customer satisfaction and customer retention

Knowledge management systems: This will enable organizations to better manage processes for

capturing and applying knowledge and ex pertise.



10


Enterprise Application ArchitectureEnterprise Application Architecture

Enterprise applications automate processes that span multiple business functions

and organizational levels and may extend outside the organization.



11

Supply Chain Management SystemSupply Chain Management System

Systems That Span the Enterprise

Customer orders, shipping notif ications, optimized shipping plans, and othersupply chain inf ormation f low among Haworth¶s Warehouse Management System(WMS), Transportation Management System (TMS), and its back-end corporate

systems.




12

What is the difference between software

engineering and computer science?

Computer Science Software Engineering

is concerned with

System Engineering is concerned with all aspects of computer-based

systems development including hardware, software and process engineering.

theory

fundamentals

the practicalities of developing

delivering useful software



13

What is a software process?

A set of activities whose goal is the development or evolution of software. Generic activities in all software processes are:

± Specification - what the system should do and its development constraints

± Development - production of the software system

± Validation - checking that the software is what the customer wants

± Evolution - changing the software in response to changing demands.

Upper-CASE

± Tools to support the early process activities of requirements and design Lower-CASE

± Tools to support later activities such as programming, debugging and

testing

CASE (Computer-Aided Software Engineering) :Software systems which areintended to provide automated support for software process activities, such asrequirements analysis, system modelling, debugging and testing



14

What are the attributes of good software?

The software should deliver the required functionality andperformance to the user and should be maintainable, dependableand acceptable.

Maintainability± Software must evolve to meet changing needs (scalable);

Dependability± Software must be trustworthy (reliable, secured and safe);

Efficiency± Software should not make wasteful use of system resources;

Acceptability± Software must accepted by the users for which it was designed. This

means it must be understandable, usable and compatible with othersystems.



15

What are the key challenges facing

Software Engineering?

Heterogeneity

± Developing techniques for building software that can cope withheterogeneous platforms and execution environments;

Delivery

± Developing techniques that lead to faster delivery of software; Trust

± Developing techniques that demonstrate that software can betrusted by its users.

± Reliable, Secured and Safe.



16

Generic Software Process Models

A simplif ied representation of a software process,presented from a specific perspective

Examples of process perspectives:

± Workf low perspective represents inputs, outputs and

dependencies± Data-f low perspective represents data transformation activities

± R ole/action perspective represents the roles/activities of thepeople involved in software process

Generic process models

± Waterf all

± Evolutionary development

± Formal transf ormation

± Integration from reusable components



17

Engineering Example

Building a house:

Land and finances

garden, garage, you are used to age wine,

enjoy to sit by the fireplace, lots of storage,

don¶t like Bauhaus

Architect will define number of floors and

rooms, orientation of the driveway, size of the

garage «

type of bricks, color of the walls,«

Construction

Entering

Living in the house

Fixing minor problems, leaking in the roof «



18

The Waterfall Model

System Feasibility Validation

Plans +

RequirementsValidation

Product Design Verification

Detailed Design Verification

Code Unit Test

IntegrationProduct

Verification

Integration System Test

Operation +

MaintenanceRevalidation

Waterf all WeaknessHigh risk for new systems because of specificationand design problems.

Low risk for well-understood developments usingfamiliar technology.

Usually requirements change, are incomplete or

even not known ( Result: µThat¶s not what I meant !¶ (

go back to last step )

WF-Model reacts very statically: Each stage must

be completed before next one starts

Too expensive

Doesn¶t force to discipline



19

ValidationFinalversion

Development Intermediateversions

SpecificationInitialversion

Outlinedescription

Concurrentactivities

Evolutionary Process Model

Process Model Weakness:Prototyping

Low risk for new applications because specification and program stay in step.High risk because of lack of process visibility.

Transf ormationalHigh risk because of need for advanced technology and staff skills.



20

Risk analysis

Risk

analysis

Risk analysis

Risk

analysis Proto-type 1

Prototype 2

Prototype 3Opera-tionalprotoype

Concept of Operation

Simulations, models, benchmarks

S/Wrequirements

Requirement

validation

DesignV&V

Productdesign Detailed

design

Code

Unit test

Integration

testAcceptance

testService Develop, verify

next-level product

Evaluate alternativesidentify, resolve risks

Determine objectives

alternatives andconstraints

Plan next phase

Integrationand test plan

Development

plan

Requirements planLife-cycle plan

REVIEW

Spiral Process Model

Focuses attention on reuse options.

Focuses attention on early error elimination.Puts quality objectives up front.Integrates development and maintenance.Provides a framework for hardware/softwaredevelopment.Contractual development often specifiesprocess model and deliverables in advance.

Requires risk assessment expertise.



21

CH4: Ethical and Social Issues in IS

Software engineering involves wider responsibilities than simply the application of technical skills. Software engineers must behave in an honest and ethicallyresponsible way if they are to be respected as professionals. Ethical behaviour is morethan simply upholding the law.

Confidentiality

± Engineers should normally respect the confidentiality of their employers or clients

irrespective of whether or not a formal confidentiality agreement has beensigned.

Competence

± Engineers should not misrepresent their level of competence.

± They should not knowingly accept work which is outside their competence.

Intellectual property rights

± Engineers should be aware of local laws governing the use of intellectual property

such as patents, copyright, etc.± They should be careful to ensure that the intellectual property of employers andclients is protected.

Computer misuse

± Software engineers should not use their technical skills to misuse other people¶scomputers.

± Computer misuse ranges from relatively trivial (game playing on an employer¶smachine, say) to extremely serious (dissemination of viruses).



22


The professional societies in the US have cooperated to produce a code of ethicalpractice.

Members of these organisations sign up to the code of practice when they join.

The Code contains eight Principles related to the behaviour of and decisions madeby professional software engineers, including practitioners, educators, managers,supervisors and policy makers, as well as trainees and students of the profession.

PUBLIC

CLIENT AND EMPLOYER

PRODUCT

JUDGMENT

MAN

AGE

MENT

PROFESSION

COLLEAGUES

SELF



23


PUBLIC± Software engineers shall act consistently with the public interest.

CLIENT AND EMPLOYER

± Software engineers shall act in a manner that is in the best interests of their client and employerconsistent with the public interest.

PRODUCT

± Software engineers shall ensure that their products and related modifications meet the highestprofessional standards possible.

JUDGMENT

± Software engineers shall maintain integrity and independence in their professional judgment.

MANAGEMENT

± Software engineering managers and leaders shall subscribe to and promote an ethical approach tothe management of software development and maintenance.

PROFESSION

± Software engineers shall advance the integrity and reputation of the profession consistent with the

public interest.

COLLEAGUES

± Software engineers shall be fair to and supportive of their colleagues.

SELF

± Software engineers shall participate in lifelong learning regarding the practice of their professionand shall promote an ethical approach to the practice of the profession.



24

The Relationship Between Ethical, Social, and Political Issues in an Inf ormationThe Relationship Between Ethical, Social, and Political Issues in an Inf ormationSocietySociety

Figure 4-1

The introduction of new information

technology has a ripple effect, raising

new ethical, social, and political issuesthat must be dealt with on the

individual, social, and political levels.

These issues have five moral

dimensions: information rights and

obligations, property rights and

obligations, system quality, quality of

life, and accountability and control.

Understanding Ethical and Social Issues Related to Systems




25

Information rights: Privacy and freedom

in the Internet Age

The European directive on data protection

Internet challenges to privacy

Technical solutions

Property rights: Intellectual property

Trade secrets

Copyright

Patents

Challenges to intellectual property rights

The Moral Dimensions of Inf ormation Systems


Accountability, liability, and control

Computer-related liability problems

System quality: Data quality and system errors

Quality of life: Equity, access, and boundaries

Balancing power: Center versus periphery

Rapidity of change: Reduced response time to

competition

Maintaining boundaries: Family, work, and

leisure

Dependence and vulnerability



26

The Moral Dimensions of Inf ormation Systems

How Cookies Identif y Web VisitorsHow Cookies Identif y Web Visitors

Figure 4-3

Cookies are written by a Web site on a visitor¶s hard drive. When the visitor returns to that Web site, the

Web server requests the ID number from the cookie and uses it to access the data stored by that server onthat visitor. The Web site can then use these data to display personalized inf ormation.




27

The Moral Dimensions of Inf ormation SystemsThe Spamming ProblemThe Spamming Problem

This f igure shows the major types of products and services hawked through spam e-mail messages and theindustries that receive the most spam.




28

Question???

Autumn 2011

2. organization, managment and the networked enterprise

Documents