MANAGEMENT INFORMATION SYSTEM & DSS

UNIT-2

SYSTEM ANALYSIS:-
 System analysis is the procedure where devlopers comes together to
understand the problems,needs and objective of the project.
 It is a problem solving technique that improve the system and ensure that
all the component of the system work efficiently to accomplish their
purpose.

SOME KEYS ASPECTS OF SYSTEM ANALYSIS:-

1.Problem Identification:-

 It involves identifying the issues that the system is aiming to address.

 Whether it is automating a business process,improving data management
or improve the user experience and understanding the problem is the first
and most important step.

2.Requirments Gathering:-

 Once the problem is identified the next step is to gather and write-down
the requirment.

3.Feasibility:-

 Before going into development it is important to check the feasibility of the

project.

4.Analysis And Modeling:-

 To get a deep insight into the system analysis develop various model such
as data flow diagram,use case and entity relationship diagram.these model
helps the customer to visualize system.
5.Scope Defination:-

 Defining the scope of the system is important to prevent adding excessive

feature to the system and ensure that the project stays within its limit.
 It identifies what is part of the system and what is not.

DEVELOPMENT AND ANALYSIS:-

 System development model specifies how the activities are organized in the
total system development effort.
 The various model for system development are-

1.Waterfall model:-

 The waterfall model is a linear and seqential model,which means that a

development phase can not being until the previous phase is completed.

Advantages:-

 This model is simple and easy to understand.

 This model is easy to manage.

Disadvantages:-

 Working software is not availble for very long during the development life
cycle.
 This not good model for large and complex project.

2.V-Model:-

 V-Model is widely used in the software development process and it is

considered a disciplined model.
 In v-model the execution of each process is sequential that is the new
phase starts only after the previous phase end.

Advantages:-

 This is a simple and easy to use model.

 Defects are detected in the initial stage itself.
Disadvantages:-

 This model is not suitable for any complex project.

 There remains both high risk and uncertainty.

3.Incremental Model:-

 The increamental model divide the system development process into

smaller,manageable increment.each increment is developed and delivered
separatly.

Advantages:-

 This model is flexible and less expensive to change requirments and scopes.
 Error are easy to identify.

Disadvantages:-

 This requires good planning and designing.

 The total cost of this model is higher.

4.RAD Model:-

 RAD model stands for rapid application development model.

 The methodology of rad model is similar to that of increamental model
orwaterfa;l model.
 It is used for small project.

Advantages:-

 It reduce the time taken in development.

 In this the component are reused.
 It is cost effective.

Disadvantages:-

 It is very difficult to manage.

 Automated code generation is very expensive.
 5.Protitype Model:-

 Prototype model is an activity in which prototype of software

application are created.
 First a prototype is created and the final product is manufacture based
on that prototype.

Advantages:-

 Flexibility in design.
 Missing functional can be easily figured out.

Disadvantages:-

 It may not accurate represent the final product due to limited functionality
or incomplete figure.

6.Spiral Model:-

 This model has combination of both waterfall model and iterative model.
 This model is used in project which are large and complex.

Advantages:-

 It is easy to estimate how much the project will cost.

 Suitable for large and complex project.

Disadvantages:-

 The cost of this model is quite high.

 This model is not suitable for small project.

NEED FOR SYSTEM ANALYSIS:-

 The analysis of the system is the basic necessity for an efficient system
design.
 The need of system analysis are :-
1.System objective:-

 it is necessary to define the system objective.

 many times it is observed that the system are historically in operation and
have lost their main purpose of achievement of the objectives.

2.system boudaries:-

 it is necessary to establish the system boundaries which would define the

scope and the coverage of the system.

3.system importance:-

 it is necessary to understand the importance of the system in the

organization.

4.Nature of the system:-

 the analysis of the system will helps the system designer to conclude
whether the system is closed type or open and determine or probabilistic.

5.Participation of users:-

 The startegic purpose of the analysis of the system is to seek the

acceptance of the people to a new development.

6.Understanding of resource need:-

 The analysis of the system helps in defining the resource requirement in

terms of hardware and software.

7.Assessment of feasibility:-

 The analysis of the system helps to establish the feasibility from different
agles.
 The system should satisfy the technical,economical and operational
feasibility.
STAGES IN SYSTEM ANALYSIS:-
The system analysis in management information system refers to be devloped in
analyzed using object-oriented method to define theproblem to be solved and
describe the system architechture.

There are seven stages…

1.Planning stages:-

 Define the project scope,goals and resources.

 In this stage the problem or pain the software target is clearly defined.first
devlopers and other team member outline objective for the system and
draw a rough plan of how the system will work.

2.Analysis:-

 Once the planning is done its time to switch to research and analysis stage.
 In this stage includes gatherings all the specific details required for a new
system as well as determining the first idea for prototype.

3.Design:-

 Devlopers will first outline the details for the overall application,along side
specific aspects.such as user interface,system interface,network
requirment,database.

4.Implementation:-

 Transform the design into an operation system.

 Devlopers write the code for the CRM(Customer Relationship Manager).

5.Testing:-

 Verify that the system meets specified requirment.

 The CRM system undergoes various testing procedure such as unit
testing,integration testing to ensure that functionality,performance and
security.
6.Deployment:-

 Introduce the system to its intended enviroment.

 The CRM system is deployeed for use by the organization employees.

7.Maintenance:-

 Ensure thr ongoing functionality and adress any issue that arise.
 Regular update,bug fixes and user support for the CRM system to canging
business requirment and dress any emerging issues.

STRUCTURED SAD AND TOOLS LIKE DFD:-

Structured System Analysis And Design:-

 Feasiability:-
It investings the goal and implications of a project to detemine whether the
project is achievable.
 Investigation:-
Investigation of thr current enviroment studies the current system and its
requirment.
 Business system option:-
Identify ways the system can be improved.
 Requirment system specification:-
Define what the new system should do.
 Technical system option:-
Look at how the project can be implemented.
 Logical design:-
Lays out the new system function without focusing on physical.
 Physical design:-
Details the physical structure and operation of the new system.

DFD:-
 DFD stands for data flow diagram.
 It is graphical representation of flow of data in an information system.
Types of DFD:-

1.Logical DFD:-

 This type of DFD concentrates on the system process and flow of data in
the system.

2.Physical DFD:-

 This type of DFD shows how the data flow is actually implemented in the
system.

COMPONENT OF DFD:-

A Data Flow Diagram (DFD) consists of several key components:

1.External Entities:

 Depicted as squares or rectangles, external entities are sources or

destinations of data outside the system. They interact with the system but are
not part of it.

2.Processes:-

 Represented by circles or ovals, processes transform incoming data flows

into outgoing data flows. They indicate what happens to data within the
system.

3.Data Stores:-

 Represented by open-ended rectangles or parallel lines, data stores hold data

that is used by processes. They indicate where data is stored for later use.
4.Data Flows:-

 Shown as arrows, data flows indicate the direction of data movement

between processes, data stores, and external entities. They represent the data
being transferred.

Lable of DFD:-

 Level 0 DFD (Context Diagram): This is the highest-level view of the system.
It shows the system as a single process and highlights its interactions with external
entities (like users or other systems). No internal processes are depicted, only
inputs and outputs.

 Level 1 DFD: This breaks down the single process from the Level 0 DFD into
major sub-processes. It shows how data flows between these processes and the
external entities, providing more detail about the internal workings of the system.

 Level 2 DFD: This level further decomposes the processes from the Level 1
DFD into more specific sub-processes. It gives a clearer view of how data is
handled within the system.

CONTEXT DIAGRAM:-
 A context diagram is a high-level representation of a system that shows
how it interacts with external entities. It’s typically the first step in creating a
Data Flow Diagram (DFD) and provides a clear overview of the system's
boundaries.

Key Components of a Context Diagram:

1. System: Represented as a single process (usually a circle or rectangle) that

encompasses the entire system being analyzed.
2. External Entities: These are sources or destinations of data outside the
system. They can be users, other systems, or organizations, typically
represented as rectangles.
3. Data Flows: Arrows indicate the flow of information between the system
and external entities. Each arrow should be labeled to clarify what data is
being exchanged.
Use:-

 Business operation analysis.

 Software engineering and development.
 IT infrastructure planning.
 Project management etc.

DECISION TABLE:-
 A decision table is a structured way to represent and analyze complex
decision-making scenarios. It consists of rows and columns that detail
conditions, actions, and outcomes. Here's a simple overview of its
components:

Components of a Decision Table:-

1. Conditions:-These are the various factors or criteria that influence the

decision.
2. Actions:-These are the potential decisions or actions that can be taken based
on the conditions.
3. Outcomes:- The results of the actions taken under different conditions.

Example-

Condition Rule 1 Rule 2 Rule 3 Rule 4

User name False True False True
password False False True True
Action - - - -
output false false False True

Steps To Creat A Decision Table:-

1. Identify the Conditions: Determine the factors that affect the decision.
2. List the Possible Actions: Outline the different actions that can be taken.
3. Define the Outcomes: Describe the results of each action based on the
conditions.
4. Fill in the Table: Populate the table with appropriate outcomes for each
combination of conditions and actions.

Advantages
 1. Clarity:
o Provides a clear, visual format that simplifies complex decision-
making processes.
2. Structured Approach:
o Organizes information logically, making it easier to analyze and
interpret.
3. Enhanced Communication:
o Serves as a common reference point for teams, improving
collaboration and alignment.
4. Error Reduction:
o Helps identify logical inconsistencies or gaps in reasoning,
minimizing potential errors.
5. Facilitates Automation:
o Can be easily translated into algorithms for automated systems,
improving efficiency.
6. Quick Reference:
o Acts as a handy reference tool, speeding up decision-making in
complex scenarios.

Disadvantages

1. Complexity for Large Tables:

o become unwieldy and difficult to manage.
2. Maintenance Challenges:
o Updating decision tables can be cumbersome, especially if changes
occur frequently in the underlying conditions or actions.
3. Limited Flexibility:
o Can be less adaptable to situations that require dynamic or non-linear
decision-making.

STRUCTURAL DIAGRAM:-
A structural diagram visually represents the components and relationships within
a system or process. It helps illustrate how parts of a system interact and is useful
in various fields, such as software engineering, architecture, and business
processes.

TYPES OF STRUCTURAL DIAGRAM:-

Here are some common types of structural diagrams, each serving specific
purposes in various fields such as software engineering, systems design, and data
modeling:

1. Class Diagram (UML)

 Purpose: Represents the static structure of a system by showing classes,

their attributes, methods, and relationships.
 Components: Classes (rectangles), associations (lines), generalizations
(arrows).

2. Entity-Relationship Diagram (ERD)

 Purpose: Illustrates the relationships between data entities in a database.

 Components: Entities (rectangles), relationships (diamonds), attributes
(ovals).

3. Component Diagram

 Purpose: Describes the organization and dependencies among a set of

components in a system.
 Components: Components (boxes), interfaces (circles), relationships (lines).

4. Deployment Diagram

 Purpose: Shows the physical deployment of artifacts on nodes (hardware) in

a system.
 Components: Nodes (3D boxes), artifacts (rectangles), associations (lines).

5. Package Diagram

 Purpose: Groups related classes or components into packages to show their

organization and relationships.
 Components: Packages (rectangles with tabs), classes (within packages),
dependencies (dotted lines).

6. Object Diagram

 Purpose: Provides a snapshot of instances of classes (objects) and their

relationships at a particular moment.
 Components: Objects (rectangles), links (lines), attributes (within objects).
7. Network Diagram

 Purpose: Represents the layout of a computer network, showing nodes

(devices) and connections.
 Components: Nodes (circles/squares), links (lines), can include labels for
devices.

8. Data Flow Diagram (DFD)

 Purpose: Illustrates the flow of data within a system, showing how inputs
are transformed into outputs.
 Components: Processes (circles), data stores (open rectangles), external
entities (squares), data flows (arrows).

BENEFIT :-

1. Visual Clarity

 Simplifies Complexity: They break down complex systems into

manageable visual representations, making it easier to understand
components and their relationships.

2. Documentation

 Standardized Representation: Acts as a formal record of system design

and architecture, useful for future reference and onboarding new team
members.
 Supports Maintenance: Provides essential information that aids in
maintaining and updating systems.

3. Design Validation

 Modeling and Prototyping: Allows for the visualization of design concepts

before implementation, helping validate ideas and designs.
 Conflict Resolution: Helps identify potential conflicts in design early in the
process, allowing for adjustments before implementation.

4. Planning and Organization

 Structure and Hierarchy: Clearly outlines the hierarchy and organization

of components, aiding in project management and resource allocation.
  Guides Development: Acts as a roadmap for developers and designers,
guiding implementation efforts.

5. Risk Management

 Identifies Vulnerabilities: Helps in spotting weak points in system

architecture that may lead to risks or failures.
 Supports Contingency Planning: Facilitates planning for alternative
approaches or backup solutions.

SYSTEM DEVELOPMENT MODEL:-

Waterfall model:-

 The waterfall model is also known as linear and sequetial model.

 This model is the theoritical model not a practical model.
 In this each and every phasemust be completed before moving to next
phase.
 This model is suitable for small project where the technical issues are very
clear.

Phase of waterfall model:-

1. Requirements Analysis

 Objective: Understand and document what the software needs to achieve.

 Activities:
o Gather requirements from stakeholders through interviews, surveys,
and workshops.
o Document functional and non-functional requirements.
o Create a Software Requirements Specification (SRS) document.
 Outcome: A clear and detailed SRS that outlines what the system should do.

2. System Design

 Objective: Create a blueprint for the software based on the requirements.

 Activities:
o High-Level Design (HLD): Define the system architecture and
components.
o Detailed Design (DD): Specify the data structures, interfaces, and
algorithms.
o Create design documents and diagrams (e.g., UML diagrams).
 Outcome: Design specifications that guide the development process.

3. Implementation

 Objective: Build the actual software based on the design documents.

 Activities:
o Write code according to the specifications.
o Conduct unit testing for individual components.
o Use version control systems to manage code changes.
 Outcome: A functional software product that is ready for integration.

4. Integration and Testing

 Objective: Ensure that the software components work together and meet the
requirements.
 Activities:
o Integrate individual components into a complete system.
o Perform various types of testing (e.g., system testing, acceptance
testing).
o Identify and fix defects or bugs.
 Outcome: A tested software product that meets quality standards and user
requirements.
5. Deployment

 Objective: Release the software to users.

 Activities:
o Prepare deployment plans, including installation procedures.
o Provide user training and documentation.
o Deploy the system in the production environment.
 Outcome: The software is operational and accessible to end users.

6. Maintenance

 Objective: Support the software post-deployment.

 Activities:
o Address any issues or bugs that arise in production.
o Implement updates and enhancements as needed.
o Monitor performance and user feedback for continuous improvement.
 Outcome: The software remains functional and relevant over time.

Key Characteristics

 Sequential Process: Each phase must be completed before the next one
begins, making it easy to manage but inflexible.
 Documentation-Heavy: Each phase generates significant documentation,
providing clarity and a reference point.
 Less Iterative: Changes during later phases can be costly and complex, as
the model is not designed for frequent iterations.

Advantages

1. Simplicity: Easy to understand and manage due to its linear structure.

2. Clear Documentation: Comprehensive documentation at each phase.
3. Defined Milestones: Clear timelines and deliverables for tracking progress.
4. Early Requirement Definition: Requirements are gathered upfront,
minimizing misunderstandings.
5. Best for Stable Projects: Works well for projects with fixed, well-defined
requirements.

Disadvantages

1. Inflexibility: Difficult to accommodate changes once phases are completed.

 2. Late Testing: Issues may be discovered late, increasing fixing costs.
3. Limited User Involvement: Stakeholders may have little engagement until
the end.

Prototype Model:-
The Prototype Model is a software development approach that emphasizes creating
a working model of the software early in the project lifecycle. Here’s an overview
of its key aspects:

Key Phases of the Prototype Model

1. Requirements Gathering:
o Initial requirements are collected from stakeholders. These may be
incomplete or unclear, leading to the need for a prototype.
2. Quick Prototype Development:
o A basic version of the software (prototype) is built, focusing on core
functionalities. This model is often developed using rapid prototyping
tools.
3. User Evaluation:
o Stakeholders interact with the prototype and provide feedback. This
helps clarify requirements and identify issues early.
4. Refinement:
o Based on user feedback, the prototype is revised and improved. This
process may involve multiple iterations of development and
evaluation.
5. Final Development:
o Once the prototype meets user expectations, the final version of the
software is developed, incorporating all required features.
6. Deployment:
o The completed software is released to users, often including user
training and support.
7. Maintenance:
o Ongoing support, bug fixes, and updates are provided after
deployment.

Advantages

1. User Involvement: Early user feedback helps ensure the final product aligns
with user needs.
 2. Clarifies Requirements: Helps clarify vague or incomplete requirements by
demonstrating a working model.
3. Reduces Risk: Issues can be identified and addressed early in the
development process, reducing project risk.
4. Faster Development: Rapid iterations can lead to quicker adjustments and
improvements.

Disadvantages

1. Incomplete Prototypes: Early prototypes may lack complete functionality,

leading to misunderstandings about the final product.
2. Potential Scope Creep: Continuous user feedback can lead to changing
requirements, complicating project scope.
3. Higher Costs: Frequent revisions based on user feedback may increase
development costs.
4. User Expectations: Users may confuse the prototype with the final product,
leading to unrealistic expectations.

Spiral model:-
The Spiral Model is a software development approach that combines
iterative and incremental development with a focus on risk assessment and
management. Here’s an overview of its key aspects:

Key Phases of the Spiral Model

1. Planning:
o Identify objectives, constraints, and requirements. This phase sets the
groundwork for the project.
2. Risk Analysis:
o Analyze potential risks associated with the project, including technical
feasibility, resource constraints, and budget issues. Strategies for
mitigating these risks are developed.
3. Engineering:
o Develop the software by implementing the features defined in the
planning phase. This phase often involves designing, coding, and
testing.
4. Evaluation:
 o Review the progress and gather feedback from stakeholders. This
includes validating the software against requirements and assessing
risks.
5. Iteration:
o Based on feedback, the process iterates through the four phases. Each
cycle produces a refined version of the software, incorporating user
input and addressing risks.

Advantages

1. Risk Management: Early identification and mitigation of risks reduce

project uncertainty.
2. Flexibility: Allows for changes and refinements at various stages,
accommodating evolving requirements.
3. User Feedback: Regular stakeholder involvement ensures the final product
aligns with user expectations.
4. Incremental Development: Each iteration produces a working version of
the software, facilitating gradual progress.

Disadvantages

1. Complexity: The model can be complex to manage due to its iterative

nature and focus on risk analysis.
2. Cost: The emphasis on risk assessment and multiple iterations can lead to
higher costs.
3. Documentation: Requires extensive documentation to track progress and
changes, which can be time-consuming.
4. Potential for Over-Engineering: Continuous refinement may lead to
unnecessary complexity in the final product.

RAD Model:-
The RAD (Rapid Application Development) Model is a software development
approach that emphasizes quick development and iteration of prototypes over
rigorous planning and testing. Here’s an overview of its key aspects:

Key Phases of the RAD Model

1. Requirements Planning:
o Gather initial requirements from stakeholders. This phase is brief but
focuses on identifying the project’s goals and objectives.
 2. User Design:
o Users interact with prototypes to design the system. Feedback is
collected to refine and iterate on the design, allowing users to have a
direct impact on the development.
3. Construction:
o Develop the actual software based on the refined prototypes. This
phase includes coding, testing, and integrating components.
4. Cutover:
o Implement the final system into production. This phase includes user
training, data conversion, and system installation.
5. Maintenance:
o Ongoing support and updates based on user feedback and system
performance.

Advantages

1. Speed: Focuses on quick development and iteration, allowing for faster

delivery of a usable product.
2. User Involvement: High levels of user engagement lead to a product that
better meets user needs.
3. Flexibility: Easier to accommodate changes in requirements due to iterative
design and development.
4. Reduced Risk: Early prototypes help identify and address issues before full-
scale development.

Disadvantages

1. Limited Scalability: May not be suitable for larger projects or those

requiring extensive documentation.
2. User Dependency: Requires active user involvement, which can be a
challenge if users are not available.
3. Quality Control: The speed of development can sometimes compromise
thorough testing and quality assurance.

Roles and responsibilities:-

In a Rapid Application Development (RAD) system, various roles and
responsibilities are essential to ensure successful project delivery and user
satisfaction. Here’s a breakdown of key roles involved in a RAD environment:

1. Project Manager
  Role: Oversees the entire RAD project.
 Responsibilities
o Coordinate project activities and resources.
o Manage timelines and budgets.
o Communicate with stakeholders and team members.

2. Business Analyst

 Role: Acts as the liaison between stakeholders and the development team.
 Responsibilities:
o Gather and document user requirements.
o Facilitate user feedback sessions and design reviews.

3. Prototyping Team

 Role: Develops prototypes to visualize the system.

 Responsibilities:
o Create initial prototypes based on gathered requirements.
o Iterate on prototypes based on user feedback.

4. Developers

 Role: Write and implement the actual code for the application.

 Responsibilities:
o Develop features based on the refined prototypes.
o Conduct unit testing to ensure quality.

5. Technical Support

 Role: Provide assistance to users during and after implementation.

 Responsibilities:
o Address user inquiries and troubleshoot issues.
o Provide training and documentation for users.
o Support system maintenance and updates.