Mis Question Bank With Answers
Mis Question Bank With Answers
Module: 1
Q-1 Interdependence between organization and Information System
The Interdependence Between Organizations and Information Systems
1.Operational Excellence
• Improved efficiency results in higher profits
• Information systems and technologies help improve efficiency and productivity
• Example: Walmart
– Power of combining information systems and best business practices to achieve operational
efficiency—and over $573 billion ($ 57,300 Crores) in sales in 2022
– Most efficient retail store in world as result of digital links between suppliers and stores
• Advantages over competitors e.g. Amul collects huge quantity of fresh milk everyday (260
Lakh Litre/day) from its village level milk suppliers and makes good taste, fresh quality of milk
and milk products for its consumers at an affordable cost!
• Amul knows how to use MIS/DSS/EIS to get business insights, make strategic planning ,
smoothen the business process, add value for its stakeholders and organization/company!
• Strategy is a general plan to achieve one or more long-term or overall goals under conditions
of uncertainty.
• Business strategic planning or Business Startegy creates
• 1 Value for its Stakeholders & organization
• 2 Competitive advantage for the organization in an uncertain environment!
• Value is the monetary, material, or assessed worth of an asset, good, or service. Like increased
turnover/profit for the organisation, accepting supplies at all times & paying prompt prices
to suppliers, charging affordable prices, giving consistent quality, timely availability of
products to consumers !
6. Survival
• Businesses may need to invest in information systems out of necessity; simply the cost of doing
business!
• Govt. insists upon sending quarterly income tax return using internet. All business need to
comply!
• Govt. requires paying toll-tax on highways compulsorily through Fast Tag on vehicles!
• Your local grocery shop displays UPI QR Code for accepting payment digitally from
consumers! It may lose customers if it does not give this facility as its competitors are providing
the same!
Top Management
Chairman / MD / BOD
1) Organizations
Separation of business functions
o Sales and marketing
o Human resources
o Finance and accounting
o Manufacturing and production
▪ Unique business processes
▪ Unique business culture “Every Business is different”
▪ Organizational politics among stakeholders!
2. Management
What are the various information systems/tools used by managers for various business
functions?
a) Business Intelligence (BI) tools and Business Analytics (BA) are used in Decision Support &
Decision Making as part of strategic control by senior managers and top management of
the organization.
b) Project Management Information Systems (PMIS) are used for managerial control of any
project to check that the project is completed within given time & cost.
c) Supplier Chain Management (SCM) & Supplier Network information systems helps
managers to manage their suppliers and enhance supplier intimacy
d) Customer Relationship Management (CRM) information system helps them to enhance
customer intimacy
e) Enterprise Resource Planning (ERP) helps to manage their internal resources effectively
and co-ordinate across various departments managing these resources e.g. manpower,
assets, time
f) Geographical Information Systems (GIS) helps them to observe and get the information of
events in various locations using digital maps
g) Collaborative/Team information software helps them to work with various internal &
external teams which are remotely connected.
3. Technology
• Computer hardware and software
• Data management technology
• Networking and telecommunications technology
– Networks, the Internet, intranets and extranets, World Wide Web
• I T infrastructure: provides platform upon which the Information System is built !
• Example:
• MIS & IT Employees: “We have not got promotions in the last 5 years and you are increasing
our workload by bringing new MIS/IT !”
• Sales Manager: “We are sales people who go to market everyday and not like our MIS Manager
who sits in office the whole day! There is no need to use DSS, we can give you the sales
prediction right now!”
• Data Entry Operator: “This MIS/IT software is not useful , it takes a lot of time in entering
data!”
Benefits of IoT
1. Enhanced Efficiency: Automation reduces manual interventions and operational costs.
2. Real-Time Data Analytics: Informed decision-making through data-driven insights.
3. Cost Reduction: Predictive maintenance minimizes equipment downtime.
4. Improved Quality of Life: Smart devices simplify everyday tasks and enhance
convenience.
Challenges in IoT Adoption
1. Data Privacy and Security: Risks of unauthorized access to sensitive information.
2. Interoperability Issues: Diverse IoT devices often lack standardization, complicating
integration.
3. High Initial Costs: Developing and deploying IoT solutions can be expensive.
4. Scalability Concerns: Managing and analyzing data from a growing number of
devices is complex.
Current Market Statistics and Trends (2024)
1. Market Size: The global IoT market is projected to reach $1.1 trillion by 2025,
growing at a compound annual growth rate (CAGR) of 10.6% from 2020.
2. Connected Devices: According to Statista, there were over 15 billion IoT-connected
devices globally in 2023, with projections exceeding 29 billion by 2030.
3. Major Players: Key companies include Amazon (AWS IoT), Microsoft (Azure IoT),
Google (Google Cloud IoT), and Cisco.
4. Adoption in Industry: Manufacturing remains the largest IoT-adopting sector,
followed by healthcare and retail.
5. Sustainability Focus: Smart IoT applications are increasingly used for energy
conservation, reducing carbon footprints, and enabling a circular economy.
IT infrastructure refers to the collection of hardware, software, networks, data centers, and
other technology resources that support an organization’s IT-enabled operations. Here’s
why it is vital in today’s business context:
A database management
A database is a collection of connected system (DBMS) is a
Definition information about people, locations, or collection of programs that
things allow you to create, manage,
and operate a database.
The retrieval of information from the We can retrieve the data from
databases can be done manually, the database management
Data Retrieval
through queries, or by using programs system through queries
(C, C++, Java, etc.). written in SQL.
As a computer system is
As databases can be handled manually
involved in a database
or via computers, when SQL is not
Speed management system, the
used to retrieve information, it can be
retrieval of information is
very slow.
very quick.
A database management
Data Data is stored in databases. system (DBMS) manages and
manipulates data.
6. Collaboration
Cloud environments enables better collaboration across teams: developers, QA, operations,
security and product architects are all exposed to the same infrastructure and can operate
simultaniously without stepping on each other toes. Cloud roles and permissions help with
better visibility and monitoring on who did what and when, to avoid conflicts and confusion.
Different cloud environments can be built for specific purposes like staging, QA, demo or pre-
production. It’s much easier to collaborate in a transparent manner and the cloud encourages it.
7. Unlimited Storage Capacity
Related to the scalability benefit above, the cloud has essencially unlimited capacity to store
any type of data in various cloud data storage types, depending on the availability, performance
and frequency the data has to be accessed. The rule of thumb is that the cost of storage goes up
according to the levels of availability of the data, performance and access frequency. Creating
and optimizing the cloud cost stucture policy can reduce the cost of cloud storage significantly
while maintaining the company’s business goals related to data storage in the cloud.
8. Back-up and Restore Data
The fact that data can be stored in the cloud without capacity constrains also helps with backup
and restore purposes. As end-users data changes over time and needs to be tracked for
regulations or compliance reasons, older software versions can be stored for later stages, in
cases they would be needed for recovery or rollback.
9. Disaster Recovery
Having previous versions of software stored in the cloud, and having production instances
running on multiple cloud availability zones or regions allow for faster recovery from disasters:
if your application is deployed on multiple locations and for some reason one region goes
down – the traffic can automatically failover to the working regions without any interruptions
to the end-users. In other cases where there is a major bug in the software release, a quick
rollback can be initiated to restore a previously released, more stable version to minimize
damage.
10. Mobility
Cloud computing allows mobile access to corporate data via smartphones and devices, which is
a great way to ensure that no one is ever left out of the loop. Staff with busy schedules, or who
live a long way away from the corporate office, can use this feature to keep instantly up-to-date
with clients and coworkers.
Resources in the cloud can be easily stored, retrieved, recovered, or processed with just a
couple of clicks. Users can get access to their works on-the-go, 24/7, via any devices of their
choice, in any corner of the world as long as you stay connected to the internet. On top of that,
all the upgrades and updates are done automatically, off-sight by the service providers. This
saves time and team effort in maintaining the systems, tremendously reducing the IT team
workloads.
11. Data Loss Prevention
Data loss is a major concern for all organizations, along with data security. Storing your data in
the cloud guarantees that data is always available, even if your equipment like laptops or PCs,
is damaged. Cloud-based services provide quick data recovery for all kinds of emergency
scenarios – from natural disasters to power outages.
Cloud infrastructure can also help you with loss prevention. If you rely on a traditional on-
premises approach, all your data will be stored locally, on office computers. Despite your best
efforts, computers can malfunction for various reasons — from malware and viruses to age-
related hardware deterioration, to simple user error.
But, if you upload your data to the cloud, it remains accessible for any computer with an
internet connection, even if something happens to your work computer.
12. Control
Having control over sensitive data is vital to any company. You never know what can happen if
a document gets into the wrong hands, even if it’s just the hands of an untrained employee.
Cloud enables you complete visibility and control over your data. You can easily decide which
users have what level of access to what data. This gives you control, but it also streamlines
work since staff will easily know what documents are assigned to them. It will also increase
and ease collaboration. Since one version of the document can be worked on by different
people, and there’s no need to have copies of the same document in circulation.
13. Competitive Edge
Not every company will migrate to the cloud, at least not yet. However, organizations which
adopt cloud find that many benefits that cloud offers positively impacts their business .
Cloud adoption increases every year, since companies realize that it offers them access to
world-class enterprise technology. And, if you implement a cloud solution now, you’ll be ahead
of your competitors.
MODULE 3
1. Various Types of Organizational Structure
If you could, you’d want to make sure you knew each of your customers well, as if you were
running a small-town store. And you’d want to make your good customers feel special.
• “A project life cycle that is tailored specifically towards the creation, alteration, and
maintenance of software applications, hardware platforms, and information technology
systems.”
• It is a series of steps offering a foundation for software development.
• A structure to build software is fundamental, which is why there are multiple software
development methodologies to choose from.
• All SDLC methodologies share a common ground of distinct phases: planning,
analysis, design, building, testing, deploying, and maintenance.
• These SDLC phases provide the outline of what a software application project entails.
2. SDLC phases
1. Formation phase
• Inception of an idea for a solution that improves an existing solution or develops an
entirely new one.
• Helps define the magnitude of the project to plan resources.
2. Requirement/Planning Phase
• Gathers requirements to formulate a design plan for the software application solution.
• Entails a thorough analysis to assess user needs, feasibility, development,
improvements, and more.
• Include documentation to refine requirements and keep a record of the solution’s
development.
• Involves the creation of a project charter that defines technical and functional
requirements.
3. Design Phase
• Focuses on the design aspect of the software application solution in terms of the
selected technical and functional requirements and the results of the thorough analysis
of the software’s viability.
4. Development Phase
• Focus solely on building a prototype of the solution to perform a code review and
ultimately create the solution.
• The team works on transforming software specifications into a working and reliable
solution.
5. Testing Phase
• This crucial phase tests the software to ensure everything works as intended.
• In the testing phase, software engineers can detect defects, bugs, and errors in the
software solution and ultimately have a quality product that meets business
expectations.
• Quality Assurance (QA) specialists perform a series of tests to evaluate the status of the
solution.
Entire information system's performance depends on this phase.
• You can critically damage your entire project, loss or misinterpret user data, or
temporarily suspend a system by not prioritizing the testing phase.
• Poor testing practices can lead to enormous losses and damage your software's quality.
6. Release Phase
• When thoroughly tested and ready, the software goes live and is released to the end user
for actual use of the product.
• The software is fully operational in a live environment where end-users utilize it.
7. Maintenance Phase
This post-release phase is tasked with keeping the software completely operational, updating it
to meet quality standards, and enhancing it throughout its life to ensure it continues to attract
and retain users.
3. SDLC METHODOLOGY
1. Waterfall Methodology
• Known as the traditional methodology, Waterfall is a sequential and linear flow for
developing a software application. The process is outlined by a series of finite stages,
each of which must be fully completed before moving on to the next one. The Waterfall
approach follows this order: requirements, design, execution, testing, and release.
Advantages of Waterfall
• It is structured and easy to follow.
• The activities are well defined and foster careful planning of the project.
• Has specific deliverables at each stage of the process.
Drawbacks of Waterfall
• It is unyielding and complex to go back to any stage after it is finished.
• It has little flexibility to adjust to changing scopes.
• Relatively more expensive than other methodologies and is more time-consuming.
2. Prototyping
• Prototyping is mainly used to visualize software solution components and match them
with customer requirements.
• Main Two Category: throwaway and evolutionary.
• Throwaway prototyping creates a model that will eventually be discarded
• Evolutionary prototyping refers to a robust prototype that will be constantly refined to
reach its final version.
Advantages of Prototyping
• Help identify potential risks and threats that can be dealt with on time,
• Reducing costs and time investment.
• The user is involved and can visualize a working version of the software.
Drawbacks of Prototyping
• Confusion with the finished version
• Waste of a significant amount of time creating a prototype
• Additionally, it can be costly to implement functioning prototypes.
• Client audiences tend to assume a good-looking prototype means the software is almost
done.
4. Spiral Model
• The Spiral Method is described by Barry Boehm in his 1986 paper “A Spiral Model of
Software Development and Enhancement.”
• The Spiral Model boils down to a meta-model, which evaluates the specific risk profile
of the project before recommending an approach that blends aspects of the other
popular methodologies of the day, including Iterative and Waterfall.
• As such, it rejects a one size fits all approach to process model adoption.
5. V-SHAPE MODEL
• The V-Shape model is named after its two key concepts: Validation and Verification.
• In the Verification Phases, requirements and designs are created. Each Validation Phase
has a corresponding Verification Phase, where testing and user acceptance occurs.
• These two phases are linked together by the Implementation (or coding) phase.
6. AGILE METHODOLOGY
The Agile Manifesto’s 4 Core Values
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
Agile Roles
Product Owner - The Product Owner, also known as the “voice of the customer”, defines the
product vision based on all insights, feedback, and ideas gathered. He or she is the owner of the
product requirements and works closely with the development team to communicate the vision
by documenting it in short narratives called User Stories. User Stories typically include a name,
description, reference to any external documents, and an explanation of how to test the
implementation. Product Owners often maintain a backlog of User Stories if there are too many
to be executed concurrently.
Scrum Master - Similar to a project manager, this role is all about making sure the team is
following Agile principles, values, and processes.
Team Member - All members of the development team have different skills and collaborate
together to build functional software. Teams can include QA engineers, business analysts,
designers, database engineers, and more depending on the project scope.
Docker:
• Containerization technology that allows developers to package their code and
dependencies into portable containers.
• In OSSD its used to ensure that code runs consistently across different environments.
Slack:
• For Communication and collaboration of developers
Jenkins:
• Jenkins is another continuous integration and deployment tool that is used to automate
testing and deployment of code changes in open-source development.
MODULE 6
1. Detailed note Project Management Information System and Features
• A Project Management Information System is designed to assist
all elements of project management;
• including information that must be monitored or collected.
• PMIS can be used for
I. Project scope management,
II. Integration management,
III. Project time management,
IV. Project cost management,
V. Project quality management,
VI. Project risk management,
VII. Communications management
ESSENTIAL FEATURES OF A PMIS
1. Schedule and Planning
It is one of the primary functions of project management. PMIS computes the critical path,
slack times, and early and late schedules.
2. Resource Management
Resources in a project include everything, from material to human. Project Management
Information System makes this management of resources easy by including resource input,
allocation, resource leveling, and more. In addition, it helps keep track of the task's expenses
spent on procurement and allocation.
3. Budget
PMIS keeps track of all costs associated with individual tasks since the entire project's budget
depends on the estimates of each task. Thus, for more accurate budget estimation - the
customer's budget, resources allotted, and time available is taken into consideration, and then
the budget is generated.
4. Control and Performance
PMIS provides performance management by analyzing and controlling cost and performance,
updating existing plans as new information becomes available or existing data changes, and
providing what-if scenarios for the project manager.
5. Reporting and Communication
The Project Management Information System generates reports for every task, creates charts
and graphs of all the collected information and analyzes data that can be shared with the team
and stakeholders. It facilities effective communication among team members.
6. Integration and Ease of Use
PMIS might even access data from several projects for multi-project analysis and integrate it
with other systems such as inventory, payroll, and so on. The easier it is to operate a PMIS, the
less cost and time it takes to train.
2. Detailed note Project Management Information System and Phases
Project Initiation Phase
• Estimating a preliminary budget for the project that includes cost and resource
estimations
• Outlining the scope of the project and preparing bids
• Scheduling project activities and allocating them to the appropriate team members
• Organizing project data and preparing required reports for presentation to key project
stakeholders
Project Planning Phase
• Extensive project scheduling, including analysis of critical paths and associated tasks
• Cost and budget management assistance, including the implementation of budget
analysis, cost controls, and other KPI metrics
• Conducting resource planning for the overall project, identifying existing resources, and
developing a backup plan for those that may be required later
• Creating baseline metrics for the project's time, cost, and scope
Project Execution Stage
• The team discussions, documents, and files are all stored in a unified hub that all
stakeholders can access safely and easily.
• It allows for an easy comparison of current project data with the project's baseline
estimations.
• Project managers can evaluate cost, budget, and schedule projections halfway through
the project and make changes based on current project requirements.
• It helps in efficiently completing several project modules, including project reporting,
cost management, material management, and project performance measurement.
Project Review and Closure Stage
• Allows for a thorough evaluation to confirm that the project's goals were fulfilled or
exceeded.
• All project information is organized and stored in a centralized hub for future access
and
• evaluation.
• All project information is archived for future projects.
• Aids in producing productivity analysis metrics and final project reports for stakeholder
decision-making.
3. Change Management in Project Management
4. TYPES OF CHANGE MANAGEMENT
Anticipatory
This type of change management involves planning the changes before they happen.
Anticipatory planning happens when there is a general idea or likelihood that change will
happen in the near future, so change managers start working on the project beforehand. This
type of change management is helpful when someone is planning to retire soon, and the job
still needs to be filled, so change managers will start planning ways to make everything work.
Reactive
The reactive approach to change management means that the change was unforeseen and must
be managed on the fly. This type of change happens when no one saw an event coming, there is
little time to make a plan, so managers must think fast to find a new solution. No one wants
reactive change management to be necessary, but life will always throw unforeseen events at
us, and reactive change management is there to help when it happens.
Incremental
This type of change management is best suited for gradual change that happens over a period
of time. Many incremental changes are small but are still intricately connected to the success of
the overall project. Incremental changes can be the plan to add new features to your website
over time, and while these changes are unlikely to upend or derail entire projects, they should
still be handled correctly, so incremental changes do not become reactive changes.
Strategic
These types of changes are much more impactful and can affect the direction of the entire
project or company as a whole. A strategic change could be adding new technology, which
requires new documentation, training, workflows, and maybe even new team members. This
level and scale of change is significant and must be handled correctly to get everyone back on
track with the changes.