University of Calicut

Master of Business Administration

BUS 2C 15 Management Information Systems

MODULE 4

Prepared By:
Mohammed Jasir PV
Asst. Professor
 Module 4 - Syllabus

Systems Development and Implementation

• System development methodologies - SDLC approach; prototyping
approach and user development approach
• Systems Analysis; systems Design
• Concepts of database and database design
• System implementation - MIS projects; system documentation
• Information system audit
System Development
 Introduction

• An organization has a software house with three departments:

• Sales, Production and System development
• The production department delivers a complete system to the customers,
who places their orders at the sales department
• The systems should be seen as sets of packages of functionality,
or service packages
• New service packages should only be constructed when the customers
have demands which the existing packages cannot offer
 System Development

Requirement System
 System Development

• It is the procedure of defining, designing, testing,

and implementing a new software application or
program
• It comprises of the internal development of
customized systems, the establishment of database
systems, or the attainment of third party developed
software
 Purpose of System Development

• To build and maintain computer based information system

• To organize documents online
• To create an information technology framework for e-commerce
• It helps to boost efficiency
 Why is systems development difficult and risky?

• Many system development projects are never finished

• Difficulty to determine the requirements of a system
(Includes data, procedures, communications and processing
requirements)
• Changing requirements
• Scheduling and budgeting are difficult
• Changing technology
• Large development team
System Implementation
 “Implementation is the process of
converting the manual or old
computerized system with the newly
developed system & making it
operational, without disturbing the
functioning of the organization.”
Types of System Implementation

Modified
Implementation

Fresh System
Implementation

Replacement
Implementation
 Software
Development Life
Cycle
(SDLC)
7 Phases of SDLC
 5 Phases of SDLC

1. Problem Definition
2. System Analysis
3. System Design & Programming
4. System Testing & Implementation
5. System Maintenance
• SDLC is a framework that defines the steps
involved in the development of software at each
phase
• It covers the detailed plan for building, deploying
and maintaining the software
• It is a process used by the software industry to
design, develop and test high quality softwares
• The SDLC aims to produce a high-quality software
that meets or exceeds customer expectations,
reaches completion within times and cost
estimates
 More about SDLC

• SDLC is the acronym of Software Development Life Cycle

• It is also called as Software Development Process
• SDLC is a framework defining tasks performed at each step in the software
development process
• ISO/IEC 12207 is an international standard for software life-cycle processes
 Why SDLC is Important

• Basis for project planning, scheduling and estimating

• Provides a standard framework for activities
• It is a mechanism for project tracking and control
• Increases visibility of project planning
• Increased and enhance development speed
• Improved client relations
• Helps you to decrease project risk
 Stage 1: Planning

• This is a preliminary plan (or a feasibility study) for a company’s business

initiative to acquire the resources to build on an infrastructure to modify
or improve a service
• The purpose of this step is to find out the scope of the problem and
determine solutions
• Resources, costs, time, benefits and other items should be considered at
this stage
 There are mainly five types of Feasibilities checks

1. Economic
2. Legal
3. Operation feasibility
4. Technical
5. Schedule
 Stage 2. Requirement Analysis

• This is the crucial part of the project

• Software development team leadership must understand the essence of
the software to be developed, the specifics of the business case and the
potential positioning of the software being developed against the
products of competitors (assuming they exist in the market)
• The outcome of this stage, usually, is the SRS document, which stands for
Software Requirements Specification.
 SRS- Contents

• Functional Requirement Specification

• Business Requirement Specification
• Client/Customer Requirement Specification
• User Requirement Specification
• Business Design Document
• Business Document
 Stage 3. Design

• The design of the software clearly outlines the architectural modules of the
product as well as data flow and communication diagrams within the
product itself
• This document sometimes called the System Design Specification (SDS)
• The best scenario is that the SDS is reviewed by the important stakeholders
of the project from different outlooks, such as: risk assessment, product
robustness, design modularity, budget and time constraints
• The best design model is then discussed and selected for the product
 Stage 4. Implementation

• In this stage of SDLC the actual development starts and the product is
built
• The programming code is generated as per DDS during this stage
• The better the SRS and SDS, the easier it is for the software engineers to
develop the required software modules
• If the design is performed in a detailed and organized manner, code
generation can be accomplished without much hassle
• Different high level programming languages such as C, C++, Pascal, Java
and PHP are used for coding
 Stage 5. Testing

• This stage is usually a subset of all the stages as in the modern SDLC
models
• The testing activities are mostly involved in all the stages of SDLC
• However, this stage refers to the testing only stage of the product where
product defects are reported, tracked, fixed and retested, until the
product reaches the quality standards defined in the SRS
Testing Contd…

• The testing phase of the SDLC is arguably one of the most important
• It is impossible to deliver quality software without testing
• There is a wide variety of testing necessary to measure quality:
o Code quality
o Unit testing (functional tests)
o Integration testing
o Performance testing
o Security testing
 Stage 6. Maintenance

• The operations and maintenance phase is the “end of the beginning,” so

to speak
• Software must be monitored constantly to ensure proper operation
• Bugs and defects discovered in Production must be reported and
responded to, which often feeds work back into the process
• Bug fixes may not flow through the entire cycle, however, at least an
abbreviated process is necessary to ensure that the fix does not introduce
other problems
System Development Methodologies
Types of System Development Methodologies

Waterfall Prototyping Incremental

Spiral RAD AGILE

 Timeline of Methodologies

1950s Code & Fix

1960s Design-Code-Test-Maintain
1970s Waterfall Model
1980s Spiral Model
1990s Rapid Application Development
2000s Agile Methods
 1 Waterfall /Linear-sequential Life Cycle Model

• The waterfall model is a classical model used in system development life

cycle to create a system with a linear and sequential approach. It is
termed as waterfall because the model develops systematically from one
phase to another in a downward fashion.
• This model is divided into different phases and the output of one phase is
used as the input of the next phase. Every phase has to be completed
before the next phase starts and there is no overlapping of the phases.
Sequential Phases in the Waterfall Model
 Waterfall Model - Application

• Requirements are very well known

• Product definition is stable
• Technology is understood and is not dynamic
• There are no ambiguous requirements
• New version of an existing product
• The project is short
• Porting an existing product to a new platform
 Advantages

• Easy to manage due to the rigidity of the model

• Each phase has specific deliverables and a review process
• Phases are processed and completed one at a time
• Works well for smaller projects where requirements are very well
understood
• Well understood milestones
• Easy to arrange tasks
• Process and results are well documented
 Disadvantages

• No working software is produced until late during the life cycle

• High amounts of risk and uncertainty
• Not a good model for complex projects
• Not suitable for the projects where requirements are at a moderate to
high risk of changing. So, risk and uncertainty is high with this process
model
• It is difficult to measure progress within stages
• Cannot accommodate changing requirements
 2 Prototype Model 

• In this Prototype Model before designing phase, a prototype is

developed, tested, reviewed and approved by the customer, after that
design will be ready for coding, testing, installation and maintenance
will takes place
• This prototype is prepared based on the customer requirements
• Prototype testing is checking for the required components are present
or not
• It is the approach where systems are developed swiftly, without having
undergone a complete analysis & specification
Prototype Diagram or Model
 Types of Prototyping

Prototyping

Rapid Throwaway Incremental Evolutionary Extreme

Prototyping Prototyping Prototyping Prototyping
 When to use Prototype model

• Whenever the customer not clears about the requirement

• If it is very complex project
• Prototyping make sure that the customer constantly work with the
system and provide a feedback about the system
 Advantages of Prototype model

• If there is missing functionality can be identified easily

• There will be less chance of software rejection
• Requirement changes are allowed
• Due to customer approval we can find the errors at early stage
• Customer involvement will be there in the development where its leads to
better solutions for any confusion / complexity / difficult functions
• The developed prototype can be re-used by developer and test engineer
 Disadvantages of Prototype model

• There are no parallel deliverables

• It is a time consuming if customer ask for changes in prototype
• This methodology may increase the system complexity as scope of
the system may expand beyond original plans
• The invested effort in the preparation of prototypes may be too
much if not properly monitored
• Customer may get confused in the prototypes and real systems
 3 Incremental Model/Iterative Enhancement Model

• It is a process of software development where requirements are broken

down into multiple standalone modules
• During the implementation phase, the project is divided into small
subsets known as increments that are implemented individually
• This model comprises several phases where each phase produces an
increment
• These increments are identified in the beginning of the development
process and the entire process from requirements gathering to delivery
of the product is carried out for each increment
The various phases of incremental model
Contd…

Incremental Phases Activities performed in incremental phases

Requirement Analysis Requirement and specification of the software are collected

Design Some high-end function are designed during this stage

Code Coding of software is done during this stage

Test Once the system is deployed, it goes through the testing phase
 Characteristics of an Incremental module includes

• System development is broken down into many mini

development projects
• Partial systems are successively built to produce a final total
system
• Highest priority requirement is tackled first
• Once the requirement is developed, requirement for that
increment are frozen
 When to use Incremental models?

• Requirements of the system are clearly understood

• When demand for an early release of a product arises
• When software engineering team are not very well skilled or
trained
• When high-risk features and goals are involved
• Such methodology is more in use for web application and
product based companies
 Advantages & Disadvantages

Advantages Disadvantages

• The software will be generated quickly • It requires a good planning designing

during the software life cycle • Problems might cause due to system
• It is flexible and less expensive architecture
• Throughout the development stages • Each iteration phase is rigid and does
changes can be done not overlap each other
• This model is less costly compared to • Rectifying a problem in one unit
others requires a lot of time
4 Rapid Application Development (RAD) Model

• It’s a model that represents one method as to how software can

be developed
• RAD is a lightweight approach to development
 RAD Model – 4 Phases

It is divided into four phases :–

1. Requirements Planning Phase
2. User Design Phase
3. Construction Phase
4. Cutover Phase
 RAD - Four Phases

1. Requirements Planning Phase

• Also called “Joint Requirements Planning (JRP) Phase”
• Combines the Planning and Analysis phases from the
Waterfall Model
• End-users and IT staff agree on business needs, project
scope, constraints, and system requirements
• This phase ends when the team agree on the key issues and
obtain management authorization to continue
 RAD - Four Phases

2. User Design Phase

• End-users and IT staff jointly develop the system processes,
inputs, and outputs
• They use a combination of Joint Application Design (JAD) and
CASE tools
• This needs to be a continuous interactive process that allows
End-users to understand, modify, and eventually approve a
working model of the system that meets their needs
 RAD - Four Phases

3. Construction Phase
• Similar to the Development phase in the Waterfall model, but
End-users continue to participate and can still suggest changes
or improvements as actual screens or reports are developed
• The key tasks in this phase are programming and application
development, coding, unit-integration and system testing
 RAD - Four Phases

4. Cutover Phase
• Similar to the Installation, Testing and Maintenance phases of
the Waterfall model, including data conversion, testing,
changeover to the new system, and user training
• Compared with traditional methods, the entire process is
compressed, and as a result, the new system is built, delivered,
and placed in operation much sooner
 RAD - Advantages

• Significantly reduced development time compared to other models

• The approach increases reusability of components
• Quick initial reviews occur
• It encourages customer feedback
• Integration from very beginning solves a lot of integration issues.
 RAD - Disadvantages

• Depends on strong team and individual performances for

identifying business requirements
• Only system that can be easily modularized can be built using RAD
• Requires highly skilled developers/designers
• High dependency on modelling skills
• Inapplicable to cheaper projects as cost of modelling and
automated code generation is very high
 5 Agile Model

• Agile model believes that every project needs to be handled differently

and the existing methods need to be tailored to best suit the project
requirements
• The tasks are divided to time boxes (small time frames) to deliver
specific features for a release
• Iterative approach is taken and working software build is delivered after
each iteration
• Each build is incremental in terms of features; the final build holds all
the features required by the customer
 Agile Model

2 – 3 Months
2 – 3 Months
 Agile Manifesto Principles

Individuals and Working software

interactions
Agile
Manifesto
principles
Customer Responding to change
collaboration
 Agile V/S Traditional SDLC Model

Agile Traditional

Adaptive software
Predictive approach
development methods

Based on Customer Requirement analysis and

Interaction planning
 Agile Vs Traditional SDLC Model

• Agile is based on the adaptive software development methods, whereas

the traditional SDLC models like the waterfall model is based on a
predictive approach. Predictive teams in the traditional SDLC models
usually work with detailed planning and have a complete forecast of the
exact tasks and features to be delivered in the next few months or during
the product life cycle.
• Predictive methods entirely depend on the requirement analysis and
planning done in the beginning of cycle. Any changes to be incorporated
go through a strict change control management and prioritization.
 Contd…

• Agile uses an adaptive approach where there is no detailed planning and

there is clarity on future tasks only in respect of what features need to be
developed. There is feature driven development and the team adapts to
the changing product requirements dynamically. The product is tested
very frequently, through the release iterations, minimizing the risk of any
major failures in future.
• Customer Interaction is the backbone of this Agile methodology, and
open communication with minimum documentation are the typical
features of Agile development environment. The agile teams work in close
collaboration with each other and are most often located in the same
geographical location.
 Advantages of Agile Model

• Functionality can be developed rapidly and demonstrated

• Resource requirements are minimum
• Suitable for fixed or changing requirements
• Delivers early partial working solutions
• Minimal rules, documentation easily employed
• Enables concurrent development and delivery within an overall
planned context
• Little or no planning required
• Easy to manage
• Gives flexibility to developers
 Disadvantages of Agile Model

• Not suitable for handling complex dependencies

• Depends heavily on customer interaction, so if customer is not clear,
team can be driven in the wrong direction
• Strict delivery management dictates the scope, functionality to be
delivered, and adjustments to meet the deadlines
• Transfer of technology to new team members may be quite
challenging due to lack of documentation
 6 Spiral Model

• The spiral model was first mentioned by Barry Boehm in his 1986 paper
• This Spiral model is a combination of iterative development process
model and the waterfall model with a very high emphasis on risk analysis
• It allows incremental releases of the product or incremental refinement
through each iteration around the spiral
 Risk Analysis Phase Planning Phase

Spiral Model

Engineering Phase Evaluation Phase

 Risk Analysis Phase Planning Phase

Spiral Model

Engineering Phase Evaluation Phase

 When to use Spiral Methodology?

• When project is large

• When releases are required to be frequent
• When risk and costs evaluation is important
• For medium to high-risk projects
• When requirements are unclear and complex
• When changes may require at any time
• When long term project commitment is not feasible due to
changes in economic priorities
 Phases of Spiral Model

Planning
Phase

Evaluation Risk
Phases
Phase Analysis

Engineerin
g Phase
 Planning Phase

Phase Name Activities performed Deliverables / Output

• Requirements are studied and • Requirements

gathered understanding
Planning • Feasibility study document
• Reviews and walkthroughs to • Finalized list of
streamline the requirements requirements
 Risk Analysis Phase

Phase Name Activities performed Deliverables / Output

• Requirements are studied and

brain storming sessions are done • Document which
Risk Analysis to identify the potential risks highlights all the
• Once the risks are identified , risk risks and its
mitigation strategy is planned mitigation plans
and finalized
 Engineering Phase

Phase Name Activities performed Deliverables / Output

• Code
• Actual development and • Test cases and test
Engineering testing if the software takes results
Phase place in this phase • Test summary report
and defect report
 Evaluation Phase

Phase Name Activities performed Deliverables / Output

• Customers evaluate the • Features implemented

Evaluation software and provide their document
Phase feedback and approval
 Advantages of Spiral Model

• Changing requirements can be accommodated

• Allows extensive use of prototypes
• Requirements can be captured more accurately
• Users see the system early
• Development can be divided into smaller parts and the risky parts can
be developed earlier which helps in better risk management
 Disadvantages of Spiral Model

• Management is more complex

• End of the project may not be known early
• Not suitable for small or low risk projects and could be expensive
for small projects
• Large number of intermediate stages requires excessive
documentation
System Analysis
 Systems Analysis

• It is a process of collecting and interpreting facts,

identifying the problems, and decomposition of
a system into its components
• Analysis specifies what the system should do
 It is a detailed study of

• Information needs of the organization and its end users

• The activities, resources, and product of any present information system
• The information system capabilities required to meet the information need of
the users
 Activities in System Analysis

System
Requirements
System Reporting
Requirement
Analysis of any Analysis
Present System
Analysis of
Organizational
Environment
 Reasons for Initiating System Analysis

• Problem Solving
• New Requirement
• Implement anew idea
• Broad System I6mprovement
 Structured System Analysis

System Study Proposal

System Survey

Problem Specification

System study proposal Review

System Analysis

System Requirement Specification Report

 Role of System Analyst

• The system analyst is a person who is

thoroughly aware of the system and
guides the system development project
by giving proper directions

His responsibilities are

• System Analysis only
• System analysis and Design
• Programming
Skills Required for an System Analyst
 Skills Required for an System Analyst

Interpersonal Analytical Management Technical

Skills Skills Skills Skills
System Design
 System Design

• The process of defining elements of a system

• Like modules, architecture, components, their
interfaces and data for a system based on the
specified requirements
• It is the process of defining, developing and
designing systems which satisfies the specific
needs and requirements of a business or
organization
Types of System Design

Input
Procedure
System
Design
Design

Output
Design
 Types of System Design

Logical Design Physical Design Architectural Design Detailed Design

It describes the It focuses on how It defines the It follows

inputs, outputs, data is entered structure and Architectural
databases, into a system, relationship design and
procedures all in a verified, between various focuses on
format that meets processed, and modules of system development of
the user displayed as development each module.
output. process.
requirements
 Advantages of System Design

• It reduces the cost of designing

• It eliminates inconsistencies
• It speeds up the process
• It makes the life of the customer easier and simpler
• It provides a lot of resources
DBMS – Database Management System
 Basic properties need in a database

• A database is a collection of information

that is organized so that it can be easily
accessed, managed and updated
• Computer databases typically contain
aggregations of data records or files,
containing information about sales
transactions or interactions with specific
customers.
 Basic properties need in a database

• Stability
• Reliability
• Scalability
• Security
 DBMS - Database Management System

• A database is a collection of related data

which represents some aspect of the real
world
• A database system is designed to be built and
populated with data for a certain task
• DBMS in short refers to the technology of
storing and retrieving users data with utmost
efficiency along with appropriate security
measures
DBMS
DBMS allows users the following tasks

• Data Definition
• Data Updation
• Data Retrieval
• User Administration
 Characteristics of DBMS

• Provides security and removes redundancy

• Self-describing nature of a database system
• Insulation between programs and data abstraction
• Support of multiple views of the data
• Sharing of data and multiuser transaction processing
• DBMS allows entities and relations among them to form tables
• DBMS supports multi-user environment
 Example of DBMS

Sector Use of DBMS

For customer information, account activities, payments,
Banking deposits, loans, etc.
Airlines For reservations and schedule information
For student information, course registrations, colleges and
Universities grades

Telecommunication To keep call records, monthly bills, maintaining balances, etc.

Finance For storing information about stock, sales, and purchases of

financial instruments like stocks and bonds
Sales Use for storing customer, product & sales information
Types of DBMS / Database Systems
Relational Database
 Relational Database

• A relational database is a type of database

• It uses a structure that allows us to identify and access data in relation to
another piece of data in the database
• Often data in a relational database is organized into tables.
• A relational database is a type of database that stores and provides access
to data points that are related to one another.
• In this, each row in the table is a record with a unique ID called the key
• The columns of the table hold attributes of the data, and each record
usually has a value for each attribute, making it easy to establish the
relationships among data points.
Hierarchical Database
 Hierarchical Database

• Model created by IBM in the 1960s

• A hierarchical database model is a data model in which the data are
organized into a tree-like structure
• The data are stored as records which are connected to one another
through links
• A record is a collection of fields, with each field containing only one value
• The type of a record defines which fields the record contains
• The hierarchical database model mandates that each child record has only
one parent, whereas each parent record can have one or more child
records
• In order to retrieve data from a hierarchical database, the whole tree
needs to be traversed starting from the root node
Network Database
 Network Database

• It’s a type of DB model wherein multiple

member records or files can be linked to
multiple owner files and vice versa
• The model can be viewed as an upside-
down tree where each member
information is the branch linked to the
owner, which is the bottom of the tree
Relational & Non-Relational
Object Database
Object Database
 Object-oriented Database

• A OODBMS or ODBMS is a database that is based on object-oriented

programming (OOP)
• The data is represented and stored in the form of objects
• OODBMS are also called object databases or object-oriented database
management systems
• Object databases are different from relational databases which are table-
oriented
• Object–relational databases are a hybrid of both approaches
System Implementation
 System Implementation

• Systems Implementation is the fourth of five phases in the systems

development life cycle (SDLC)
• It includes application development, testing, documentation,
training, data conversion, system changeover, and post-
implementation evaluation of the results
• Systems implementation is the process of installing hardware and
software and getting the system up and running
 System Implementation

• Installing the system

• Convert from old system to new system
• Train end users
• Compile final documentation
• Testing & Evaluating the new system
 System Implementation

• Implementation is a process of ensuring that the information system is

operational
• It involves
• Constructing a new system from scratch
• Constructing a new system from the existing one
• Implementation allows the users to take over its operation for use and
evaluation
• It involves training the users to handle the system and plan for a
smooth conversion
 Systems Implementation

Implementation Planning

Develop and Prepare Site; Select

test software Install and and train
programs test hardware personnel

Complete
Test system
Documentation

Conversion
 Systems Implementation: Implementation Planning

• An implementation plan consists of implementation tasks, expected

completion dates, cost estimates, and the person or persons responsible
for each task
• Planning should include adjustments to the company’s organizational
structure
 Systems Implementation: Develop and test software
programs

• Seven steps are followed when developing and testing software programs.
1. Determine user needs
2. Develop a plan
3. Write program instructions (code)
4. Test the program
5. Document the program
6. Train program users
7. Install and use the system
 Systems Implementation: Site Preparation

• A PC requires little site preparation

• A large system may require extensive changes, such as additional
electrical outlets
• Site preparation should begin well in advance of the installation date
 Systems Implementation: Select and train personnel

• Employees can be hired from outside the company or transferred

internally
• Effective system training should include employees’ orientation to new
policies and operations
• Training should occur before systems testing and conversion
 Systems Implementation: Complete Documentation

• Three types of documentation must be prepared for new systems

1. Development documentation
2. Operations documentation
3. User documentation
 Systems Implementation: Test the System

• There are three common forms of testing

1. Walk-through
2. Processing of test transactions
3. Acceptance tests
Systems Implementation: Conversion

• There are four conversion approaches

• Direct conversion
• Parallel conversion
• Phase-in conversion
• Pilot conversion / Modular Approach
Conversion : Direct Conversion Method
 Conversion : Direct Conversion Method

• Direct Approach Direct installation of the new system with immediate

discontinuance of the old existing system is reffered as “cold turnkey”
approach
• This approach becomes useful when these factors are considered
1. The new system does no replace the existing system
2. Old system is regarded absolutely of no value
3. New system is compact and simple
4. The design of the new system is inexpensive with more advantages
and less risk involved
Conversion : Parallel Conversion
 Conversion : Parallel Conversion

• The selected new system is installed and operated with current

system
• This method is expensive because of duplicating facilities and
personal to maintain both the systems
• In this approach a target date must be fixed when the operations
of old system cease and new one will operate on its own
Conversion : Phase-in Conversion
• This approach is similar to modular method but it differs because of
segmentation of system, however, not the organization
• It has advantages that the rate of changes in a given Organization can be
totally minimized and the data processing resource can be acquired
gradually over a period of time
• System exhibits certain disadvantages such as limited applicability, more
costs incurred to develop interface with old system and a feeling in the
Organization that system is never completed
Conversion : Pilot conversion / Modular Approach
 Conversion : Pilot conversion / Modular Approach

• This is generally recognized as “Pilot approach”, means the

implementation of a system in the Organization on a piece-meal basis.
• This has few advantages / merits
• The risk of systems failure is localized
• The major problem can be easily identified and corrected before further
implementation
• Operating personal can be trained before system is installed in a location.
 Steps in Implementations

• Hiring and Training of Personnel

• Program Development
• Site preparation
• Acquisition and installation of hardware
• Software Acquisition
• File conversion
• Documentation
• System Conversion
 Factors for Successful Implementation

• Involving users in project implementation

• Setting up a cohesive project management group for implementation
• Using project management tools like PERT,CPM
• Use formal control tool to monitor project implementation
• Overcoming user resistance
 Causes in Implementation Failure

• Low user involvement in project implementation

• Lack of commitment from top management for the projects
• Complexity of projects
• Poor management of implementation process
Project Management Information System
 Project Management Information System (PMIS)

• A PMIS is how information needed to run a project is organized

• It collects and uses project information through one or more software
applications
• It helps project managers to plan, execute and close their project
• It’s a way to organize that flood of information, so you don’t drown in data
 Definition PMIS

• The Project Management Book of Knowledge (PMBOK) states that a PMIS

is “an information system consisting of the tools and techniques used to
gather, integrate, and disseminate the outputs of project management
processes. It is used to support all aspects of the project from initiating
through closing and can include both manual and automated systems.”
 Essential Features of a PMIS

Schedule and Resource

Budget
Planning Management

Reporting and Integration and Control and

Communication Ease of Use Performance
 Importance PMIS

1. Monitoring & control system of a project needs the support of a PMIS

2. PMIS would cover the complete life- cycle of a project
3. Provide the necessary support for decision making
4. To receive the actual data about the status of a project
5. Assist project managers in planning, budgeting, and resource allocation
6. Perform analyses such as variance, performance and forecasting
7. PMIS allow for quick review and easy periodic updating
Information System Audit
 Auditing

Auditing is the process of assessment of financial, operational,

strategic goals and processes in organizations to determine whether
they are in compliance with the stated principles ,regulatory norms,
rules and regulations.
 Information System Audit

• Information System should be periodically audited to review and

evaluate whether
• Proper and adequate information system controls
• Procedural controls
• Facility controls
• Other managerial controls are implemented
• Aim of information audit is to safe guard the assets, to maintain data
integrity, to achieve system effectiveness and to achieve system
efficiency
• The audit can be conducted internally by employees of the organization,
or externally by an outside firm
IS Auditing Approaches
 Need for Control & Audit of Computers

• Computers assist in the processing of data and decision making.

• Factors:
1. Organizational cost of data loss
2. Incorrect decision making
3. Cost of computer abuse
4. Value of hardware, software
5. High costs of computer error
6. Maintenance of privacy
7. Controlled evolution of computer use
 Advantages of using computers in audit techniques

• Increase the accuracy of audit tests

• Perform audit tests more efficiently
• Enable the audit team to test a large volume of data
accurately and quickly
• Reduce the level of human error in testing
• Provide a better quality of audit evidence
 Module 4 - Syllabus

Systems Development and Implementation

• System development methodologies - SDLC approach; prototyping
approach and user development approach
• Systems Analysis; systems Design
• Concepts of database and database design
• System implementation - MIS projects; system documentation
• Information system audit
Thank You .