V-LRN� VIRTUAL LEARNING NETWORK
MCS-014
�System Analysis and Design�
BLOCK – 1��INTRODUCTION TO SYSTEM�DEVELOPMENT
Block -1
Unit -1
Introduction to SAD
Topics to be covered
�SYSTEM �
SYSTEM :
It is defined as the orderly grouping of inter – dependent components linked together according to a plan to achieve a specific goal.
Each component is a part of total system and it has to do it’s own share of work for the system to achieve the desired goal.
System word is derived from Greek word ‘Systema’ which means an Organized relationship among components.
What is Information system?
�Classification of System�
BOUNDARY : It is the thin line between the firm and it’s environment.
Classification of systems
1.Formal (planed in terms of policies and procedure and scheduled in advance) /informal (need oriented like sales order processing system through telephone calls)
Characteristics of system
Characteristics of a system
The characteristic of a system are as follows :
�Types of users of system �
Types of users of system -
Types of Real time system
1.Hard real time system - that is task guarantee completed on time.
2. Soft real time – less restrictive to time as priority are measured like in scientific experiments /medical imaging system and industrial control system.
Distributed system
�Development of a Successful System�
SDLC – System Development Life Cycle is a standard methodology for the development of Information Systems. It mainly consist of four phases :
(a) System Analysis
(b) System Design
(c) System Construction
(d) Implementation and System support.
�Approaches to Development �
Information system Approaches
Approaches for the development of Information Systems :
Define JAD?
Joint Application Development – It is defined as a structured approach in which users, managers ,analyst, sponsors and system analyst work together for several days in a series of intensive meetings to specify or review system requirements.
Block -1
Unit -2
System Analyst – A Profession
MCS-014
�System Analysis and Design�
Topics to be cover
�SYSTEM ANALYST �
System analyst is basically a person that bridges the gap between the person’s belonging to the IT industry who are going to provide the solution to the problem of “industry peoples” or “system user’s” who are also known as “clients” who needs their system to get automated so that they can take decisions in the shortest span of time. (It is required for analysis and design of that system.)
�USER �
They are basically defined as the people who use information systems or who are affected by the information system on a regular basis. A common synonym is CLIENT.
There are two types of USER’S :
Role of a system Analyst
Duties of a System Analyst :
Skills of system Analyst :
Analytical skills
Communication skills
Management skills
Interpersonal skills
Block -1
Unit -3
Process of System Development
MCS-014
�System Analysis and Design�
Topics to be cover
Phases of SDLC
�System Development Life cycle �
Most organizations find it beneficial to use a set of steps, called a systems development methodology, to develop and support their information system.
The SDLC is a common methodology for system development in many organizations, featuring various phases that mark the progress of the system analysis and design effort.
�Phases of Life Cycle�
Block -1
Unit -4
Introduction to Documentation of System
MCS-014
�System Analysis and Design�
Topics to be covered
�Why documentation is required�
Documentation may be defined as the process of communication about the system.
The person who is responsible for the communication using documents is known as documenter.(Documentation involves recording of information generated during the process of software development life cycle.)
Documentation is required:
It is a process to help users of software and other people to use and interact with system. Effective and accurate documentation is very necessary for the success of any system.
�Types of Documentation�
Software requirements specification
SYSTEM REQRM. SPECIFICATION
SRS- It is a description of a software system to be developed, laying out functional and non-functional requirements, and may include a set of use cases that describe interactions the users will have with the software.
Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers.
System Design Specification�
SYSTEM DESIGN SPECIFICATION
SDS- It defines how the requirements of the system are to be implemented. It consists of final steps of describing the system in detail before the coding starts.
It is a complete document that contains all of the information needed to develop the system.
Test Design Document
TEST DESIGN DOCUMENT
User Manual�
USER MANUAL
A user guide or user's guide, also commonly known as a manual, is a technical communication document intended to give assistance to people using a particular system.
This document is complete at the end of the software development process.
Data Dictionary�
A data dictionary consists of data about data. The major elements of data dictionary are data flows, data stores and processes.
It doesn’t consist of actual data in the database. Data dictionary is kept hidden from users so that data in it is not tampered.
A data dictionary may consist of description of data elements and definitions of tables.
Data Dictionary
A data Dictionary is a catalogue of all elements in a system. Data dictionary stores details and description of all data used in system .
Block -1
Unit -4
Introduction to Documentation of system
Part-2
Topics to be cover
Documentation
A System cannot be completed effective unless it is adequately documented. Preparation of documentation is quite important as it depicts what the system is supposed be and how it should perform its functions.Documentation improves overall operation in addition to management and audit control.
Characteristics:
Objectivity:-It Must be clearly defined in a language that is easily understood..
Cross-referable:- It should be possible to refer to other documents.
Easy to maintain
Completeness:- It should contain everything needed.
Types of Documentation
Program Documentation:-
Before a program is developed, the system analyst should provide the programmer with the required documentation.Flowchart, Decision Tables are most appropriate for explaining the logic of a program.
Operations Documentation:-
For smooth running of the system, the console operator must have complete knowledge about the job.The instructions must be in a form which is easily readable and understandable.
User Documentation:-
System requires two general types of information:
1. Complete details to handle each case the system process.
2. Overall picture of the system so that they can see their role in the total operation of the company.
Types of Documentation
Management Documentation:-
The documentation required by corporate management.The System designer must know the requirements of the management and provide the documentation to enable management to perform functions:-
Evaluate progress on system development
Monitor existing systems.
Understand the objectives and method of new and existing systems.
Types of Documentation
System Documentation:-
The documentation of this plan must be thorough enough so that system designers could produce a complete and effective system.
Types of Documentation
Quality Assurance in Software Life Cycle
Quality Factors Specifications
Usability:- The efforts required to understand and operate a system.
Maintainability:- The ease with which the program errors are detected and removed.
Testability:- The effort required to test a program to ensure its correct performance.
Portability:- The ease of transporting a program from one hardware configuration to another.
Quality Assurance in Software Life Cycle
Software Requirement Specification:- This stage is to generate the requirement document for developing the software.
Software Design Specification:-The Software design document defines the overall architecture of the software
Quality Assurance in Software Life Cycle
Software Testing and Implementation:-The testing Phase is to ensure that completeness and accuracy of the system. Implementation phase provide a logical order for the creation of the modules.
Maintenance and Support:-This Phase provides the necessary software development for the system.
Quality Assurance in Software Life Cycle
Levels of Quality Assurance
Testing:-
System testing is expensive and time consuming process. Testing held by users is that it is performed to prove that program is error free.
Verification with Validation:-
Verification is also intended to find errors. It is performed by executing a program in a simulated environment. Validation refers to the process of using software in a live environment to find errors.
Certification:-
The last level of Quality assurance is to certify that the software package developed conforms to standard.Certification is issued only if the package is successful in all the tests.
Levels of Quality Assurance
BLOCK – 2��PLANNING AND DESIGNING�SYSTEMS
Block -2
Unit -5
Process of System Planning
MCS-014
�System Analysis and Design�
Topics to be covered
Fact finding Techniques
To learn the functions of the existing system, systems analyst needs to collect data related to the existing system. Usually, the data related to organization, staff, documents used, formats used in the input and output processes is collected.
Interviews
Personal Interview is a recognized and most important fact Finding technique, where the system analyst gathers information from individual through face to face interaction.
Group Discussion
A group of staff members are invited who are expected to be well versed in their own wings of the organization.
Site Visits
The engineers of the development organization visit the sites. Usually, the systems analysts visit sites to get first hand information of the working of the system.
Presentation
It is another way of finding the facts and collecting data. Presentation is the way by which the system analyst find hand knowledge of the project.
Questionnaires
These are special purpose documents that allow the analyst to collect information and opinion from
Respondents.
It is possible to collect responses or opinion from a large number of people.
�Feasibility Study�
Feasibility(Possibility) study consists of activities which determine the existence of scope of developing an information system to the organization. This study should be done throughout the life cycle.
In feasibility analysis, we have to study the fol. :
Technical Feasibility
Technical feasibility is concerned with the availability of hardware and software required for the development of the system, to see compatibility and maturity of the technology.
Operational Feasibility
Operational feasibility is all about problem that may arise during operations.
Economic Feasibility
It is the measure of cost effectiveness of the project. The Economic feasibility is nothing but judging whether the possible benefit of solving the problems is worthwhile or not.
Legal Feasibility
Legal feasibility studies issues arising out of the need to the development of the system. The Possible consideration might include copyright law, labour law, antitrust, foreign trade, regulation etc.
Block -2
Unit – 6
Modular and Structured Design
MCS-014
�System Analysis and Design�
Topics to be covered
�System Design �
It is the specification or construction of a technical, computer based solution for the business requirements identified in system analysis phase.
During design, system analysts convert the description of the recommended alternative solution into logical and then physical system specifications.
�Design Principles�
There are certain principles that can be used for the development of the system. The principles are :
Problem Partitioning
It is concerned with partitioning the large problems. Divide and Conquer is the best policy adopted here.
Abstraction
Abstraction is a technique for managing complexity of computer systems.
It is a tool that permits the designer to consider a component at an abstract level(outer view) without worrying about details of implementation of the component.
It is necessary when the problem is divided into smaller parts so that one can proceed with one design process effectively and efficiently.
Top Down Design
This method often result in some form of stepwise refinement, starting from an abstract design, in each step, the design is refined to a more concrete level until we reach a level where no more refinement is required and the design can be implemented directly.
Bottom Up Design
In this strategy, we start from the bottom and move upwards towards the top of the software.
Structure Charts
A structure chart depicts the modular organization of an information system. The organization is hierarchical.
A structure chart graphically shows the way the components of a program or a system are related.
The structure chart depicts various modules across different levels of the hierarchical organization. Always it has one coordinating module at the top.
A system consists of components called modules.
Structure Charts
Structure Chart
The organization of modules within a system is usually shown on a module / structure chart.
Structure Charts
�Modularity �
Modularity is a single attribute of software that allows a program to be intellectually manageable. It increases the design clarity that results in easy implementation, testing, debugging, documentation and maintenance of the software.
MODULARITY means decomposing a system into smaller components that can be coded separately.
Modules in Modularity
(2) Coupling:-Coupling is a measure of the relationship (i.e., dependency) between two modules.
(1) Data Coupling
(2) Stamp Coupling
(3) Control Coupling
(4) Common Coupling
(5) Content Coupling
(3) Cohesion:-It is a degree to which a module conforms (adjust) itself to the performance of a single task.
(1) Procedural Cohesion
(2) Temporal Cohesion
(3) Logical Cohesion
(4) Coincidental Cohesion
Data Coupling
Data Coupling:-Data coupling occurs between two modules when data are passed by parameters using a simple argument list and every item in the list is used.
Stamp Coupling
Two modules are stamp coupled if they communicate via a passed data structure that contains more information than necessary for them to perform their functions.
Control Coupling
Control coupling is one module controlling the flow of another, by passing it information on what to do (e.g., passing a what-to-do flag).
Common Coupling
Common coupling (also known as Global coupling) occurs when two modules share the same global data (e.g., a global variable). Changing the shared resource implies changing all the modules using it.
Content Coupling
Content coupling (also known as Pathological coupling) occurs when one module modifies or relies on the internal workings of another module (e.g., accessing local data of another module).
Therefore changing the way the second module produces data (location, type, timing) will lead to changing the dependent module.
Content Coupling
A Content Coupling with D
Cohesion
It is a degree to which a module conforms (adjust) itself to the performance of a single task.
Procedural Cohesion:- : A procedurally cohesive module contains elements that belong to a common procedural limit.
Temporal and Coincidental Cohesion
Temporal Cohesion:- operations related only by general time performed (i.e. initialization() or FatalErrorShutdown?()).
Coincidental Cohesion:- (Worst) Module elements are unrelated. There is no relationship between the instruction.
Cohesion
Logical Cohesion:- Elements perform similar activities as selected from outside module.
Block -2
Unit - 7
System Design and Modeling
MCS-014
�System Analysis and Design�
Topics to be covered
System Design
There are two level of process of design:
System Design
It include the following components:
(Integrity involves maintaining the consistency(stable), accuracy, and trustworthiness of data over its entire life cycle.)
System Design
System Design
System Design
Structured Design
Structured design is based on data flow. Structured design partitions a program into small, independent modules. They are organized in a top-down manner. Structured design is used to minimize the complexity.
Structured Design
�
� Data Flow Diagram is graphic tool. It is used to describe and analyze the movement of data through a system. They focus on the data flowing into the system, between processes and in and out of data stores.
Notation ‘s of a DFD
DATA FLOW (arrow).
PROCESS (circle).
EXTERNAL ENTITIES (Square box).
DATA STORE (Open box ).
Data Flow Diagram
DFDs only involve four symbols
| Process�Transform of incoming data flow(s) to outgoing flow(s) |
| Data Flow�Movement of data in the system. |
| Data Store�Data repositories for data that are not moving. It may be as simple as a buffer or a queue or a s sophisticated as a relational database. |
| External Entity�Sources of destinations outside the specified system boundary. |
�
Context Diagram
Context DFD is the entrance of a data flow model. It contains one and only one process and does not show any data store.
First Level DFD
A Data Flow diagram that represents a system’s major processes, data flows, and data stores at a high level of detail.
Context Level DFD
Ist Level DFD
Functional Decomposition Diagram
Basically, functional decomposition takes something complicated and simplifies it.
The individual elements of the process and their hierarchical relationship to each other are commonly displayed in a diagram called a functional decomposition diagram.��
ER Diagram
ER diagram is used to described the data in terms of entities and their relationship.
Components of ER diagram are:-
ip
ER Diagram
Entity-A person, partnership, organization, or business that has a legal and separately identifiable existence.
Student is the name of entity.�
ER Diagram
Attribute- An attribute is a quality or characteristic given to a person, group, or some other thing.
An attribute “Address” is the example.
ER Diagram
Relationship:- A relationship is a natural business association that exists between one or more entities.
The student links with the other entities or attributes.
ER Diagram
Cardinality:-It defines the min and max number of occurrences of one entity that may be related to a single occurrence of the other entity.
ER Diagram
Degree:- The degree of relationship is the number of entities that participate in the relationship.
ER Diagram
Recursive Relationship:- A relationship that exists between different instances (case) of the same entity is called Recursive Relationship.
Data Dictionary
A data dictionary is a collection of descriptions of the data objects or items in a data model for the benefit of programmers and others who need to refer to them.
Form Design
Form Design
Importance of Forms
Form Design
Classification of forms
Form Design
Requirement of form design
Form Design
Criteria for Form Design
Form Design
Decision Tables
A decision tables is a table of rows and columns,that show conditions and actions. Decision Rules included a decision table, state what procedure to follow when certain conditions exists.
The decision table has four section.
Decision Tables
A decision table is an excellent tool to use in both testing and requirements management.
Are presentation of decision variables that are graphics and sequential ,showing which condition to consider first ,which second and so, on.
A decision tree is diagram that presents conditions and actions in order.The root is on the left.
A decision tree is a decision support tool that uses a tree-like graph or model of decisions and their possible consequences, including chance event outcomes, resource costs, and utility. It is one way to display an algorithm.
Decision Trees:
�Decision Trees:�
A decision tree is a graph that uses a branching method to illustrate every possible outcome of a decision
BLOCK – 3��MORE DESIGN ISSUES�AND CASE TOOLS
Block -2
Unit - 8
Session – 9
MCS-014
�System Analysis and Design�
Topics to be cover
Importance of Forms�
FORMS and REPORTS deals with the interface of the software with users.
IMPORTANCE OF FORMS :
Seminar Form
Forms
Importance of Reports
Reports
Reports
Reports
�Types of Information�
�INTERNAL INFORMATION�
Internal Information is the Information that is collected, generated or consumed within an Organization.
�EXTERNAL INFORMATION�
External Information refers to the information collected from or created for customers, suppliers, competitors etc. Outside the Organization.
TURNAROUND INFORMATION
When there are several instances (examples) where the information output is again used as input to obtain new information. The document that consists of such information is called Turnaround document.
For example Warranty Card in which customers also adds new information (Ex.: Name, Address, etc.)
Block -2
Unit - 9
Session - 10
MCS-014
�System Analysis and Design�
Topics to be covered
�
Database Design
A database is a collection of information that is organized so that it can easily be accessed, managed, and updated.
Database design is the process of producing a detailed data model of a database.
Database Design
Flat File:- In databases a flat file refers to data files that contain records with no structured relationships. Flat files may contain only basic formatting, have a small fixed number of fields, and it may or may not have a file format or a file having no internal hierarchy.
Example:- A flat file which stores pin code of customer’s address. Any change in the size of the field will enforce changes in the entire program which uses the data related to customer’s address.
Steps in Database Design
Analysis- It is the process of creating a conceptual data model for the database system.
Design- It is the process of creating a logical data model for the database system.
Implementation- It is the process of creating a physical model for the database system
Design of Database Fields
Various types of fields in database are:-
Primary Key- Contain one or more columns whose combined values uniquely identify every row in a table. Each table can have only one primary key.
Secondary Key or Alternate Key- Contain one or more columns whose combined values uniquely identify every row in a table.
Foreign keys - Contain one or more columns whose values match a primary or alternate key in some other table.
Descriptive fields-Attributes that are not used as key but store business data.
Design of Database Fields
Example of Keys:
STUDENT {SID, FNAME, LNAME, COURSEID}
Here in STUDENT table keys are:
Candidate keys are: SID or FNAME+LAME
Primary Key: SID
Foreign Key: COURSEID
Alternate Key: FNAME+LAME
Types of Physical Files
Once the logical design has been finalized in consultation with the users, the details of physical design of the system can start. Physical database design involves actual implementation of the logical database in the DBMS.
TYPES OF PHYSICAL FILES :
Types of Physical Files
�Master File�
A Master File is a permanent file of all the data needed by a business.
Example, a file consisting of information about the customers.
�Transaction File�
A Transaction file is a temporary file of all the transactions (items bought, sold, deleted etc.) that have taken place in a given period.
Example, data related to daily sales activity.
The data of these files is used to update the Master File.
�Archive File�
An Archive File is a file of data in permanent storage (usually, the data is stored for legal reason or to perform the analysis.)
These files contains Information about Past dealings of the business and other activity.
Audit File
An Audit File that does not store business data but data related to transaction log.
Example, data and time of access, modification etc. Values of fields before and after modification.
Audit (inspection or investigation)- A systematic review or assessment of something.
Work File
A Work File is temporarily created to hold intermediate (middle) result of the data processing.
Example, a stored file of list of customers.
��File Organization��
File Organization is the physical organization of records on the disc.
�Serial File organization�
A serial File is created by placing the record as it is created. It leaves no gap between the records that are stored on the disc.
Examples:- print file, log files, transaction files etc.
�Sequential File organization�
In this organization, the records are physically ordered by primary key. To locate a particular record, the program starts searching from the beginning of the file till the matching primary key is found.
Alphabetic list of customers is a common
Example of Sequential File organization.
�Indexed Sequential File organization�
Indexing is a way of sorting a number of records on multiple fields.
In this organization, the records are not physically ordered. Index is created to facilitate searching of records. Index Records give a physical location of each data record.
�Hashed File organization�
A hash function, h, is a mapping function that maps all the set of search-keys K to the address where actual records are placed.
In this organization, the records are physically ordered according to hashing(mixture) algorithm. The address where each record is stored is determined using hashing algorithm.
Design Of Database
The following are various steps in Database design:-
Design Of Database
Selection of Database architecture-Selecting database architecture is one of the most challenging parts of database design for any information system.
Designing database schema-A database schema defines a database in terms of tables, keys, indexes and constraints.
Selecting Indexes-When an index is created on a table, a separate storage area is allocated to store the index structure. A database table can have one or more indexes associated with it.
Design Of Database
Estimating capacity of the database- Database administrator needs to calculate the amount of disk space required for the database.
DBMS
A database management system (DBMS) is a computer software application that interacts with the user, other applications, and the database itself to capture and analyze data.
A general-purpose DBMS is designed to allow the definition, creation, querying, update, and administration of databases.
DBMS
Data Definition Language (DDL) statements are used to define the database structure or schema. Some examples:
DBMS
Data Manipulation Language (DML) statements are used for managing data within schema objects. Some examples:
BLOCK – 3�CASE TOOLS FOR �SYSTEM DEVELOPMENT
Block -3
Unit - 10
Session - 11
MCS-014
�System Analysis and Design�
Topics to be cover
CASE Tools
The normal SDLC process is often seen as inflexible(non adjustable) and time consuming and expensive. Keeping in view of these limitations CASE came into existence.
CASE : Computer Aided Software Engineering
This uses various CASE tools to perform and automate many activities of SDLC.
It means, development and maintenance of software projects with help of various automated software tools.
�CASE Tools�
All the software that helps in the process of software engineering can be termed as CASE tools.
Use of CASE Tools :
CASE Tools
To facilitate(making easier) single design methodology-CASE tools help organization to standardize the development process. It also facilitates coordinated development.
Rapid Application Development-Organizations use CASE tools to improve the speed and quality of system development.
Testing-CASE tools help to ease and improve testing process through automated checking and simplify program maintenance.
Productivity and Reduction of Cost-Use of CASE tools makes the software easy to maintain and hence reduce the maintenance costs.
�Types of CASE Tools�
Types of CASE Tools
Planning and management tool-Begin the development process with information planning and project management.
Analysis tool-These tools ensure that business requirements are correctly captured during the analysis phase early in the development process.
Design toolset-It provides detailed specification of the system.
Code generator-It automatically generates code specific to a language based on the system specification.
Types of CASE Tools
Database design toolset-It suggests database design and generates system control information.
User interface generator-It generates user interface based on system specification.
Report generator-It generates reports based on specification
�Classification of CASE Tools�
Development tools : used for design support and code generation
Front end tools : support activities early in the life cycle of software development. Ex : DFD , ERD , prototyping tools
Back end tools : support activities later in the life cycle of software development process. Ex : flow chart , code generator etc.
Horizontal tools : These tools are not specific to a particular life cycle step but are common across a number of life cycle steps, eg – documentation tools
Vertical tools: These tools are specific to a life cycle.
�Reverse & Forward Engineering �
Reverse engineering is the process of recreation of model based on the existing code. First the existing code is scanned to generate the model. Then the model can be fine tuned in accordance with requirement.
��Forward Engineering� �
It is the process of generation of skeleton code out of the models. First step is to create the model for a system, then generate the relevant code for the model and then allow modification of this code.
Object Oriented CASE Tools
Object oriented CASE tools are similar to other CASE tools. These differ from others only in terms of their capability to create class diagrams and text specifications for reports.
The following are some of the features found across most of the Object Oriented CASE tools:
BLOCK – 4��IMPLEMENTATION AND �SECURITY OF SYSTEMS�AND MIS
Block -4
Unit - 11
Session – 12
Session – 13
MCS-014
�System Analysis and Design�
Topics to be cover
�Implementation of system�
This unit gives the overview of the actual implementation techniques when the new system is completely designed.
Where maintenance of the system after implementation is a major activity considering the total life of a software product.
�System Testing�
Conducting system tests :
System Testing
Recovery Testing:-Test the ability of the system to recover from errors.
Security Testing:-System used for processing sensitive information are prone (likely) to high security risks.
Stress Testing:-Stress test is designed to test the system as to how the system behaves in abnormal situation.
Performance Testing:-Performance testing is specifically important to embedded and real time systems. It checks the run time performance of the system.
Response Testing:-Testing of response time is of special importance in OLTP (on-line transaction processing systems like railway reservation system, points of sale, etc.). Testing is done to measure the response time.
�Conversion Approaches �
The process of conversion from the existing system
(manual or computerized) to the newly developed
system can be performed in several ways depending on
the criticality of the system and other related issues.
Converting to new system :
Conversion Approaches
Direct conversion:-This is sudden approach. The old system is shutdown and the new system starts.
Pilot conversion:-This is the middle path approach. Instead of converting all at once throughout the organization, this kind of pilot installation involves conversion/installation of system at a single pre-decided location.
Parallel conversion:- is least risk prone (especially face downwards). Under this kind of conversion, the old system is allowed to run alongside the new system until the management and the end user are satisfied with the result of the new system.
Phased conversion:- is an incremental approach to switch over to the new system.
�Types of Maintenance�
Maintenance of the system :
Types of Maintenance
Corrective maintenance:- This maintenance performed to return equipment to proper working order.
Adaptive maintenance:- It includes changes to the functionality of the system developed for specific customer needs.
Perfective maintenance:-This kind of maintenance activity involves adding new functionalities and features to the software to make it more versatile and user oriented.
Preventive maintenance:-Changes are made to software to make it easily maintainable and to prevent any kind of system failure in future. This reduces the need of corrective maintenance.
Block -4
Unit - 12
Session - 13
�Audit�
This is an assessment of an information system performed by an information systems professional of IS auditor to provide recommendations and advice to improve system performance and security.
Audit should be done regularly and the result should be used to refine the system.
An Audit is official inspection of an organization's (Company) accounts, typically by an independent body.
�Audit�
OBJECTIVE OF AUDIT :
�Audit�
Benefits of audit :
�Computer System & Security Issues �
Security is an important issue for modern IT systems. Even though technology provides immense possibilities to safeguard organizations computing infrastructure, there has been security lapses and security breaches which have cost the organization heavily.
Computer System & Security Issues
Block -4
Unit - 13
MCS-014
�System Analysis and Design�
Topics to be cover
Management Information System
The Three sub- components:-
Management, Information and System
Management:- focusing on the ultimate use of such information system for managerial decision making technology.
Information:- Means Processing data that have some meaning. Which it is used by end users.
System:-A system is defined as a set of related components, activities, processes and human being interacting together to achieve some common objective.
�Management Information System�
MIS helps the organization to produce information that organizations need to improve decision making, problem solving, control operations and creating new products or services.
Roles of MIS :
What is MIS?
Management Information system (MIS) generate information for Monitoring Performance (e.g Productivity information) and maintaining coordination (e.g between purchasing and accounts payable)
and Mgmt.
Management Information System
Computer Systems and MIS
7- M’s of Management
What is management system?
A mgmt. System provides the framework of processes and procedures used to ensure that an organization can fulfill all tasks required to achieve its objectives
“PLAN--->DO-🡪CHECK-🡪ACT”
Information system provides assistance to the manager for efficiently discharging his responsibilities.
Continue…
Examples of Mgmt. System
Some of the mgmt. System that have been computerized in various organization are :
1. Administrative mgmt. system
2. Human resource mgmt. System
3. A/c mgmt. System
4. Customer relationship mgmt. System
5. Knowledge mgmt. System
6. Logistics mgmt. System
7. Marketing mgmt. System
8. Operations mgmt. System
9. Project mgmt. System
10. Process mgmt. system
Continue…
11. Personal mgmt. System
12. Product mgmt. System
13. Quality mgmt. System
14. Resource mgmt. System
15. Risk mgmt. System
16. Supply chain mgmt. system
17. Time mgmt. system
�Types of Information Systems�
Types of Information Systems
Transaction Processing System:-It is an information system that supports business in the delivery of various business transactions.
Management Information System:- Management Information System (MIS) is a special kind of information system that helps managers to take decisions.
Decision Support System:-Decision Support Systems provide information to managers which will be helpful for them to make decisions. A manager at a higher level needs information for strategic planning and control.
Expert System:- An Expert System is a computer program that simulates the judgment and behavior of a human expert or an organization that has expert knowledge and experience in a particular field. Typically, such a system contains a knowledge base containing accumulated experience and a set of rules for applying the knowledge base to each particular situation that is described to the program.
�Types of Computers supported in MIS�
1. Network servers
2. Mainframe computers
3. Minicomputers
4. super computer
Continue…
Data processing means checking the character, structure, presentation, data design, data value checking, range/ limits checking, error correction or in other words data processing is handling raw material in a systematic manner to confirm to the data quality standards as determined by the designer of the information system.
Continue…
�Information system processing involves following functions�
1. Nature of business (Trading or
Manufacturing)
2. The type of business (Product or Service)
3. The complexity of business (Multiple
locations , divisions, products)
4. Management style (autocratic,
participative)
�Emerging Technologies used in MIS �
Decision mgmt. with IS
Decision making based on� 4-Dimensions
These dimensions would tend to have a logical, analytical , objective, critical and empirical decision making style.
Types of Decision in the organization
1. The decisions affecting the operations
mgmt.
2. The decisions affecting the execution and
control of the business
3. The strategic business decisions