Unit - 1 & 2 - Mis
Unit - 1 & 2 - Mis
Introduction
Meaning
Data
Data – the data that the information system records. Business Procedures – procedures put in place on how
to record, store and analyze data. Hardware – these include servers, workstations, networking equipment,
printers, etc. Software – these are programs used to handle the data.
Management Information Systems (MIS) is the study of people, technology, organizations, and the
relationships among them. MIS professionals help firms realize maximum benefit from investment in
personnel, equipment, and business processes. MIS is a people-oriented field with an emphasis on service
through technology.
Objectives of MIS
The scope of MIS also involves understanding the objectives of MIS. mentioned
below are the various objectives of MIS for your reference.
• Gathering Data– MIS professionals work on gathering data which might be
useful and relevant in the decision making process for various internal and
external sources of the organization.
• Data Processing- The gathered data needs to be processed in a systematic way
so as to be of some help to the management. The data is processed into
information which is used for planning, controlling, organizing and directing
functionalities at different levels of the organization. Data processing means
sorting data, making calculations with data etc.
• Information Storage– It means storing information in a safe manner so as to
make it available for any future use.
Nature of MIS
The MIS helps the top level management in goal setting, strategic planning and
evolving the business plans and their implementation. The MIS plays the role of
information generation, communication, problem identification and helps in the
process of decision-making.
Evolution
The computer crunched numbers summarizing and organizing
transactions and data in the accounting, finance, and human resources
areas. Such systems are generally called transaction processing systems
(TPSs).
Management Information Systems (MISs)
Intelligent Support System (ISSs)
Automation Systems (OASs)
Knowledge Management Systems
Data Warehousing
Functional Information System (FIS)
Finance (FIN):
provide internal and external professional access to stock, investment and capital
spending information.
Accounting (ACC):
similar to financial MIS more related to invoicing, payroll, receivables.
Marketing (MKT):
pricing, distribution, promotional, and information by customer and salesperson.
Operations (OPS):
regular reports on production, yield, quality, inventory levels. These systems typically
deal with manufacturing, sourcing, and supply chain management.
Human Resources Management (HR):
employees, benefits, hiring‘s, etc.
System development methodologies
Strengths:
• Ideal for supporting less experienced project teams and project managers, or
project teams whose composition fluctuates.
• The orderly sequence of development steps and strict controls for ensuring the
adequacy of documentation and design reviews helps ensure the quality,
reliability, and maintainability of the developed software.
Weaknesses:
• Inflexible, slow, costly and cumbersome due to significant structure and tight
controls.
• Project progresses forward, with only slight movement backward.
• Little room for use of iteration, which can reduce manageability if used.
System development methodologies
Prototyping
Basic Principles
• Not a standalone, complete development methodology, but rather an approach to
handling selected portions of a larger, more traditional development methodology (i.e.,
Incremental, Spiral, or Rapid Application Development (RAD)).
• Attempts to reduce inherent project risk by breaking a project into smaller segments and
providing more ease-of-change during the development process.
Strengths
Helps to easily identify confusing or difficult functions and missing functionality.
May generate specifications for a production application.
Encourages innovation and flexible designs.
Weakness
Requirements may frequently change significantly.
Identification of non-functional elements is difficult to document
System development methodologies
Incremental
• The initial software concept, requirements analysis, and design of architecture and
system core are defined using the Waterfall approach, followed by iterative Prototyping,
which culminates in installation of the final prototype (i.e., working system).
System development methodologies
Strengths:
• Potential exists for exploiting knowledge gained in an early increment as later increments are
developed.
• Moderate control is maintained over the life of the project through the use of written
documentation and the formal review and approval/signoff by the user and information
technology management at designated major milestones.
Weaknesses:
• When utilizing a series of mini-Waterfalls for a small part of the system before moving on to the
next increment, there is usually a lack of overall consideration of the business problem and
technical requirements for the overall system.
System development methodologies
Spiral
Basic Principles:
• Focus is on risk assessment and on minimizing project risk by breaking a project
into smaller segments and providing more ease-of-change during the
development process, as well as providing the opportunity to evaluate risks and
weigh consideration of project continuation throughout the life cycle.
• Each cycle involves a progression through the same sequence of steps, for each
portion of the product and for each of its levels of elaboration, from an overall
concept-of-operation document down to the coding of each individual program.
Strengths
Enhances risk avoidance.
Useful in helping to select the best methodology to follow for development of a
given software iteration, based on project risk.
System development methodologies
Weaknesses:
• Challenging to determine the exact composition of development methodologies to use for each
iteration around the Spiral.
• Highly customized to each project, and thus is quite complex, limiting reusability.
Meaning
A knowledge management system comprises a range of practices used in an
organization to identify, create, represent, distribute, and enable adoption to insight
and experience. Such insights and experience comprise knowledge, either embodied
in individual or embedded in organizational processes and practices.
Example
Some examples of knowledge work systems are computer-aided design
(CAD)systems, virtual reality systems, and financial workstations. Computer-aided
design (CAD) systems: These systems are used for automating the creation and
revision of designs using computers and graphics software.
Knowledge Management System (KMS)
1. Class (Blueprint)
2. Object (Approach System design)
3. Encapsulation (Protect some components of the object)
4. Inheritance
5. Polymorphism
UML Diagram
Meaning
A UML diagram is a diagram based on the UML (Unified Modelling
Language) with the purpose of visually representing a system along
with its main actors, roles, actions, artefacts or classes, in order to
better understand, alter, maintain, or document information about the
system. The main aim of UML is to define a standard way to visualize
the way a system has been designed.
UML Diagram Types
Class Diagram
Class diagrams are the main building block of any object-oriented solution. It
shows the classes in a system, attributes, and operations of each class and the
relationship between each class. (Super Market)
Component Diagram
A component diagram displays the structural relationship of components of a
software system. These are mostly used when working with complex
systems with many components. (Super Market)
Deployment Diagram
A deployment diagram shows the hardware of your system and the software in that hardware. Deployment diagrams are useful
when your software solution is deployed across multiple machines with each having a unique configuration (Vehicle Registration)
Object Diagram
Object Diagrams, sometimes referred to as Instance diagrams are very similar to class diagrams. Like class
diagrams, they also show the relationship between objects but they use real-world examples. (Online
Shopping)
Package Diagram
As the name suggests, a package diagram shows the dependencies between different packages in a system.
Check out this wiki article to learn more about the dependencies and elements found in package diagrams.
(Departments)
Profile Diagram
This is a diagram type that is very rarely used in any specification. For more profile
diagram templates, visit our diagram community. (School)
Use Case Diagram
As the most known diagram type of the behavioral UML types,
Use case diagrams give a graphic overview of the actors involved in a
system, different functions needed by those actors and how these
different functions interact. (Airline Company)
Activity Diagram
Activity diagrams represent workflows in a graphical way. They can be used to describe the
business workflow or the operational workflow of any component in a system. (ATM)
State Machine Diagram
State machine diagrams are similar to activity diagrams, although notations and usage change
a bit. They are sometimes known as state diagrams or state chart diagrams as well. (Games)
Sequence Diagram
Sequence diagrams in UML show how objects interact with each other and the order those interactions
occur. It’s important to note that they show the interactions for a particular scenario. (Whatsapp, face
Book)
Communication Diagram
In UML 1 they were called collaboration diagrams. Communication diagrams are similar
to sequence diagrams, but the focus is on messages passed between objects. (Department)
Interaction Overview Diagram
Interaction overview diagrams are very similar to activity diagrams. While activity diagrams show a
sequence of processes, Interaction overview diagrams show a sequence of interaction diagrams. (Like ATM)
Timing Diagram
Timing diagrams are very similar to sequence diagrams. They represent the behavior of objects in a given time frame.
If it’s only one object, the diagram is straightforward. But, if there is more than one object is involved, a Timing
diagram is used to show interactions between objects during that time frame.
(E-mail)