Professional Documents
Culture Documents
Information is processed data presented in a form that is meaningful to the recipient and is of real value in the current context or decision making process
Data Storage
Data
Processing
Information
Data is the raw material for processing information. Data itself has no meaning or value. It is a set of facts about the Entities in the Real World 1
Better Productivity
Changing Organization Structures Flattening and De-Centralizing To Empower the Employees with Information at the Right Time Legal Manifestations
Definition of MIS
A Management Information System Is An Integrated User Machine System For Providing Information To Support the Operations, Management, Analysis and Decision Making Functions In an Organization
A Management Information System Utilizes Computer Hardware and Software Manual Procedures A Database Models for Analysis, Planning, Control and DM
Procedures Which comprises of User Manuals and the the Work Flows that need to be followed to work with the MIS. For Example How to Book a Sales Order
Operating Personnel Are the People who work on the MIS, Systems Analysts, Data Preparation Personnel, Database Administrator Etc
6
Transaction Processing
Operational Control
Information Processing
DATABASE
9
Top Management
Production
Marketing
Logistics
Personnel
EIS
OAS
DSS
MRS
TPS
10
Information Rights
PRIVACY: Right to be left alone Fair information practices (FIP):
No secret personal records Individuals can access, amend information about them Use info only with prior consent Managers accountable for damage done by systems Governments can intervene
11
KNOWLEDGE
MANAGEMENT
STRATEGIC
TPS OAS
SEMISTRUCTURED PROJECT SCHEDULING
MIS
BUDGET PREPARATION
DSS KWS
FACILITY LOCATION
ESS
NEW PRODUCTS NEW MARKETS
UNSTRUCTURED
PRODUCT DESIGN
12
Report Processing
Inquiry Processing Eg are Transactions for inventory withdrawal, or checking of inventory levels, Orders pending for a specified duration
13
14
Information Requirements
Characteristics Operational of Information Control Source Largely Internal Well Defined, Narrow Detailed Management Control Strategic Planning External
Scope
Wide
Level of Aggregation
Aggregate
16
It is the core of any MIS. The Other information systems work by utilizing the information that is captured by TPS
17
MRS is typically used for planning and management control. Essentially the data captured by TPS is summarized into a more meaningful form to allow the managers have a global picture of the heath of the business
Various Categories of MRS Scheduled Reports Exception Reports Demand Reports
18
MIS
MIS
REPORTS
2.23
19
The DSS must support the Decision and not replace the normal Human Decision Making Behavior
DESIGN
CHOICE
21
Decision Making
Structured Decisions v Are Frequent Unstructured Decisions
v Are Infrequent v Thrive in Ambiguous Environments v There is no pre-established decision procedure v Flourish in Definite Environments v The decision can be expressed as a set of steps / flowchart / decision tree / formula v Data requirements are well known in advance v Low / No Risk Decisions
22
23
Decision Tables
1 Conditions 2 3 4 5 6
Actions
Rules
24
27
KBS / ES is an knowledge intensive program that solves a problems by capturing the expertise of a human brain in limited domain of knowledge and experience. It is a self learning system
There are 5 main areas of AI research
Expert Systems Natural Languages Vision Systems Robotics Neural Networks
28
Quality if Information : How efficiently it motivates human actions and contributes to effective decision making
Utility of Information Form Time Place Possession Value of Information : Change in the Decision Behavior the cost of procuring the information
29
30
Prototype Model
Requirements Gathering and Refinement Engineer the Product Quick Analysis and Design
Build Prototype
31
Differences
Waterfall Model
Prototype Model
Mature Processes & clear requirements Low involvement of user Key emphasis on each phase Structured and less time consuming Lesser Costs Appropriate where requirements are stable and implementation cycles are small
Requirements not very clear to the user High involvement of user Lack of focus on design, coding and testing phases Repeated Iterations, hence more time consuming Greater costs Appropriate where implementation cycles are small and requirements are changing
32
Spiral Model
Planning Risk Analysis
Customer Evaluation
Engineering
33
34
35
Feasibility Analysis
Technical Feasibility Economic Feasibility Legal Feasibility Operational Feasibility Schedule Feasibility
36
Requirements Analysis
Is a communication intense activity It is the prime phase wherein the requirements are captured It is really a complex activity, which involves converting a set of nebulous, confused thoughts in the minds of a User into a set of clear, well defined and well represented facts that are to be furnished by the system Why do projects fail
Cost Overruns Time Overruns Poor Quality of the Product Requirements Changed or were not understood properly
37
Requirements Analysis
RA is a communication Intense Activity a process of discovery, refinement, modeling and specification, wherein both the developer and customer take an active role in the requirements analysis and specification The Activities for RA are broadly divided into
Problem Recognition
Review
This process helps to lay down the specifications for Software Function and Performance, Softwares Interface with other systems and establish the design constraints to be met 38
Requirements Analysis-Modeling
Models are developed during the Requirements Analyst that allow the user and the Analyst to gain a better understanding of the system. The Models Focus on What to Do and not How to Do Utility of Models Aid in understanding Information, Function and Behavior of a system thereby Making RA more easy and more systematic Models are the focal point of Review and hence the key to determine Completeness, Consistency and accuracy of Function
Become the Foundation of Design Providing designer in Essential Representation of the Software that can be mapped to implementation
39
Manual Electronics
Requirements Analysis
To Reach a Clear common Understanding between the User and the Development Team - modeling, flowcharting, structured English representation and other specific methods are used to capture the Various Complex Business Scenarios Data Flow Diagrams (DFDs) is a graphical technique that depicts information flow and the transforms that are applied as data flows from input to the output Rules for drawing a DFD
Sources cannot leak data directly into data store A store cannot directly pass on information to a destination Data cannot flow directly from one store to another Any process producing output must be a source itself Any process with only input should be a data destination Each Subsystem must be further exploded in the next level DFD
41
Requirements Analysis
Process or Function that operates upon a data to perform a specific function
External Entity that represents the source or sink of data Represents a data storage that is generally a permanent data storage
42
Information
4. Teller
Signature, Card
6. Pay Balance
5. Process Transaction
New Balance
Debit Amt
Valid A/C
Data Dictionary
Is a structured Repository of data about data (MEDADATA). It is a rigorous definitions of all the DATA elements and Data Structures
Data Elements are the smallest unit of data that provides for no further decomposition. Eg. Date Data Structure A group of data elements handled as a unit. For Eg the Customer Account info is a data structure of data elements like AccNo, Name, Address, Balance, Signature, Credit and Debit Information and so on. Data Flows and Data Stores
46
Systems Design
Systems Design is Defined as the process of applying various techniques and principles for the purpose translating the requirements into a representation of the software in sufficient details to permit its physical realization The Importance of design
Maintenance Test Implementation Design Maintenance Test Implementation
47
Systems Design
Informational Model Functional Model Behavioral Model Data Design Architectural Design
Design
Design Code and testing Phase absorb almost 75% of the Software Cost
Code
Test
48
Systems Design
System design can be categorized into various factors such as Input Design : All care must be taken to take the correct system inputs in the most efficient and simple way. Input Design includes determining the various means by which the System would receive the inputs from the surrounding such as data Entry Screens, Bar Code Readers etc. It also accounts for the validations that would be performed by the system in order to check for the correctness of the data being entered. A correct input a very essential in order to allow successful functioning of the system in desired fashion
Output Design : Implies the careful design of the out interfaces such as screen designs and Report Layouts. The output response time should be carefully designed and should be the maximum possible 49
Systems Design
Data Design : Implies defining the data dictionary that would be used to capture the data the would be captured / generated by the system. This is one of the most important design phases since the Data Design directly would affect the performance of the system A good database design is one that not only allows you to store the correct representation of data, but also allows you to retrieve the data in a simple and efficient Manner Care should be taken to defined the low level database parameter at this phase. Instead ER Diagram and the Data Integrity constraints should be explicit, allowing the flexible choice of the database details to be taken care of at the implementation level
50
Systems Design
Architectural Design : The prime Objective is to develop a modular program structure and represent the control relationship between the various components. It also includes the design of program structure and data structure, defining the interfaces that enable the data to flow throughout the program
P1 P1 P5 P2 P3 P5 P4 P3 P2 P4 P1 P3 P5
51
M P2 P4
Systems Design
Procedural Design : This occurs generally after the data and architectural designs have been accomplished. It is used to define the algorithmic details to implement the various operations that would be performed on the data. The procedural design can be done by using Structured English, Graphical Design Notations, etc
Examples
If <Condition-Description> Then <Block Pseudo code> Else < Block Pseudo code > End If
52
Coding
Coding Involves the translation of the Detail Design Representation into a Programming Language Representation Thus to Code you need a Programming Language. The choice of the Language generally determines the complete life Cycle. A good Programming Language Will
Support Modularization (Functions, Procedures, Logical Units)
Coding
The Output of the Coding Phase is Lines of Code
Software Design
Coding
Lines Of Code
Compile
Testing
Testing is the critical element of Software Quality Assurance representing the ultimate review of specification, design and coding. Testing cannot show the absence of a defects, it can only show that the defects are present Unit Testing : Is used to test the a individual component and takes place as soon as a unit component is developed
Integration Testing : Is carried out between the various dependant components to ensure that the various components are able to perform the designation Function in relation to each other
Functional Testing : Is carried out to ensure that the product meets the acceptance criteria that has been defined during the RA Phase. In short it ensure that the system
55
Testing Strategies
System Engineering
S R D C
U
I V / FT
ST
Integration Testing
Functional Testing System Testing
56
Implementation of MIS
There are two scenarios of Information Systems implementation
information systems hold important data, which is useful to the organization and cannot be done away with The data from existing systems need to be ported to the new information systems
57
Implementation of MIS
The specific four approaches for Information systems Replacement by new Systems are
58
Implementation of MIS
Direct Approach
Refers to the case in which implementation of new system is done and immediately the old system is discontinued. It is also referred to as the Cut-off Approach. It is Applicable when
Old system is very small or simple It is judged absolutely worthless The new System is radically different from the existing one
59
Implementation of MIS
Parallel Approach
The new system is installed and operated in parallel with existing system till it has been tested thoroughly., then the current system is cut off The outputs from new and existing system are compared from each system during the parallel phase and differences are reconciled It is expensive since it requires duplication of effort to maintain dual systems It is need for critical operations
Old System
New system New system
60
Implementation of MIS
Modular Approach
61
Implementation of MIS
Phase-in Implementation
This method is referred to as cut over by segments approach and is similar to the modular approach The system itself is segmented and not the organization New data collection activities are implemented and an interface mechanism with old system is develop, which allows old system to operate with new data Later new data access, storage and retrieval activities are implemented Then , again interfaces with old systems are developed Note : High Costs are involved but needed for large enterprises
Old System
Function (a) Old Function (b) New
62
Database Management
Entity
Data Item
Attributes
Record
File
Database
63
Database Management
The Initial Approach was to develop files to store information
Thus data files were developed and maintained separately for individual applications Problems
Data duplication
Information spread across different files, need complex programs for data extraction Applications in file processing systems are data dependant Applications / Program manipulate the information in the files
Data Dependence
Program Dependence
64
Controlled data redundancy Enhanced data consistency Data independence Concurrency Control Ease of Use Economical Recovery from failure
65
SOCIAL ISSUES
ETHICAL ISSUES
SYSTEM QUALITY
4.5
QUALITY OF LIFE
66
Weaknesses
Short development times Relatively inefficient Slow transaction processing May carry high cost Large files can degrade performance Nonprocedural approach may hamper logic & updating requirements Lack of Consistency and approach to Software Development Disassociation from Primary Job for which the person was hired
Lack of a process approach for software Development Lack of quality approach (Testing, Documentation etc)
67
Improved requirements determination Increased user involvement & satisfaction Reduced application backlog Meet organizational objectives? Quality assurance? Inadequate methodology; testing; documentation? Lost control over data?
68
Management Problems: