Data Analysis and

Synthesis & Techniques of

System Design
By
Dr. Heshalini Rajagopal
Data Analysis
and Synthesis
Outline
• Introduction
• Data Analysis and Synthesis
• Techniques of system design
• SADT
• OOADT
Introduction
When justifying the conclusions or results of your project, you need to establish what you
measured them against.

Setting the level for success (e.g., benchmark) helps you to decide on an acceptable measure for
the program.

This step of justifying conclusions involves more than just analyzing and comparing data.

It also includes interpreting your findings and judging them against an established basis.

Not much can be conveyed by simple presenting a huge collection data in your report. Hence, data
analysis is important.
Data Analysis
• Art of finding patterns
• Begins with open questions that progressively narrow
• Checking reliability of assumptions
• Integration of different types of data
Synthesis
• “Synthesis is the process of making meaning through inference-based
sensemaking” (J. Kolko)
• Synthesis goals:
• Make sense of the data
• Understand intent
• Move towards insights
Types of Data
Analyzing data
• Quantitative analysis uses mathematical operations to investigate the properties
of data.
• The best way to conduct quantitative analysis is by using statistics.
• One of the primary purposes of scientific investigation is to discover relationships
between variables so that we can explain, predict and control them.
• Statistical methods serve as a valuable tool for discovering and quantifying these
relationships.
• You do not have to be a mathematician to use this special language, as there are
various user-friendly computer packages (e.g. SPSS, Matlab, MS Excel, PowerBI)
will do all the calculations for you.
Analyzing data
• Qualitative analysis expresses the nature of elements and is
represented as a new concepts and theory.
• The analysis tools for this include:
• Categorisation and theme- based analysis
• Quantitative analysis on text based- data using statistical packages such as
SPSS, etc.
Synthesizing Data

• After, data analysis, you will need to present the findings of your study.
• This should be done effectively in the Results and Discussion chapter of your final
report.
• It is important to present your results appropriately using words and graphics.
• You will need to:
• Properly use text and visual aids
• Interpret the results
• Use proper language of reporting
• Refer to figures or tables correctly (Always cite the Figures/ Tables that you are
explaining)
Example of a good and bad chart
Example of data interpretation
Example of proper language usage
Common mistake made when explaining figure/table
Techniques of
System Design
SADT

• A model of the problem is constructed, which is composed of hierarchy of

diagrams.
• Each diagram is composed of boxes and arrows.
• The topmost diagram, called the context diagram, defines the problem most
abstractly.
• As the problem is refined into sub-problems, this refinement is documented
into other diagrams.
• Boxes should be given unique names that should always be verb phrases,
because they represent the functions.
SADT – Basic Elements
Top down decomposition structure
OOADT

• THREE (3) major steps:

1. Identify the objects
2. Determine their attributes and services
3. Determine the relationships between objects
Use Case Diagram

20
Sequence Diagram
The Transition to Systems Design
• Preparing for Systems Design Tasks
– It is essential to have an accurate and understandable system requirements
document
• Logical and Physical Design
– The logical design defines the functions and features of the system and the
relationships among its components
– The physical design of an information system is a plan for the actual
implementation of the system

22
Steps in Design Phase

• Select design strategy

• Design architecture
• Select hardware and software

23
Systems Design Guidelines
• Overview
• A system is effective if it supports business requirements and meets user
needs
• A system is reliable if it handles input errors, processing errors, hardware
failures, or human mistakes
• A system is maintainable if it is flexible, scalable, and easily modified

24
Systems Design Guidelines
• Overview
• User Considerations
• Carefully consider any point where users receive output from, or provide input
• Anticipate future needs
• Provide flexibility
• Parameter, default

25
Systems Design Guidelines
• Overview
– Data Considerations
• Enter data as soon as possible
• Verify data as it is entered
• Use automated methods of data
entry whenever possible

26
Systems Design Guidelines
• Overview
• Data Considerations
• Control data entry access and report all entries or changes to critical
values – audit trail
• Log every instance of data entry and changes
• Enter data once
• Avoid data duplication

27
Systems Design Guidelines
• Overview
• Architecture considerations
• Use a modular design
• Design modules that perform a single function are easier to understand, implement, and
maintain

28
Systems Design Guidelines
• Design Trade-Offs
• Design goals often conflict with each other
• Most design trade-off decisions that you will face come down to the basic
conflict of quality versus cost
• Avoid decisions that achieve short-term savings but might mean higher costs
later

29
Thank You.