Class
Class
Class
1
MIS SUPPORTS DECISION MAKING PROCESS
Decisions Taken
Strategic Unstructured
Tactical Semi-structured
Structured
Operational
DECISION STYLES – MIS BASED VIEWS
MIS HAS COMPONENTS ACROSS LAYERS OF ORGANIZATION
TPS AND ROLES AND RESPONSIBILITIES
OF OPERATIONAL LAYER
Roles: This layer consists of employees who execute day-to-
day tasks, such as technicians, support staff, and frontline
workers.
Responsibilities: Their primary responsibilities involve
carrying out specific tasks, following procedures, and
ensuring daily operations run smoothly. They may also be
responsible for reporting progress, issues, and other
relevant information to their supervisors or managers.
TPS LAYER OF MIS
What it should look for?
• Transaction Processing System (TPS) needs-
• Transaction Owner
• Service Provider
• Transaction Processor (Rules/Logics)
• Transaction Monitor (Databases and Events)
• Transaction Logs
• Transaction Sessions (Cycles)
MRS AND TACTICAL LAYER
Roles: This layer includes middle management, team leaders,
and supervisors who oversee the operational staff.
Responsibilities: Tactical roles involve planning, organising,
and coordinating the activities of the operational layer to
meet short-term and medium-term goals. They are
responsible for allocating resources, monitoring performance,
problem-solving, and ensuring the operational layer meets
its targets. They also link the strategic and operational
layers, communicating goals, priorities, and feedback
between the two.
MANAGEMENT REPORTING SYSTEM
Does not look into details of Transactions
What is a Report?
Aims at serving Middle Management •Data / Information arranged
in a sequence or
Mostly looks at the Routine Reports received in a manner that
would provide inputs for
Example: Trial Balance/Raw material utilization product wise/ employee decisions
attendance reports
Stock holding costs product wise
Involvement
Involvement
of
of
Users
IT- Centre
Systems
Analysis #2
Systems
Design #3
Systems
Implementation #4
Systems
Maintenance #5
CONTEXT DIAGRAM
ONE POSSIBLE ANSWER: PURSUE SDLC
Tools: Use Systems Thinking approach;
Systems Requirement Events analyses; MCS of OMNIS model;
Determination #1 Context Diagrams; Estimates of projects
(Time, efforts, cost…)
Tools: Functional Systems of OMNIS
Systems model – Processes (Rules/Logics),
Analysis #2 Events…Transactions.., Process Flow
Diagrams…
Systems
Design #3
Systems
Implementation #4
Systems
Maintenance #5
CHAPTER-7,MIS-PRM43
PROCESS FLOW DIAGRAM
ONE POSSIBLE ANSWER: PURSUE SDLC
Tools: Use Systems Thinking approach;
Systems Requirement Events analyses; MCS of OMNIS model;
Determination #1 Context Diagrams; Estimates of projects
(Time, efforts, cost…)
Tools: Functional Systems of OMNIS
Systems model – Processes (Rules/Logics),
Analysis #2 Events…Transactions.., Process Flow
Diagrams…
Systems Tools: E-R Diagrams (one of the tools which is
Design #3 included in this course- there are others..);
Information Matrices; Data and Process
Matrices…
Systems Tools: User involvement through quality
Implementation #4 systems mapping; Tests- Unit, White Box, Black
Box, Integration, Validations, Performance tests
– Alpha, Beta; Installation Tests……
Systems
Maintenance #5
SDLC- THE LIMITATIONS
Traditional SDLC methodology for current IT Projects are not
always appropriate:
Many systems projects fail to meet objectives
Difficulty in estimating costs
Each project is often so unique that previous experience may not provide
the necessary skills
Objectives may be too broad or too narrow
Opportunity may not be appropriately leveraged.
There may not be enough time to comply each step of the SDLC
ORGANIZATIONAL LEVEL (CONT.)
20