BLOCK DIAGRAMS. Block diagrams A way to show schematically the individual subsystems of a design with arrows to show the direction that signals flow through.

Slides:



Advertisements
Similar presentations
Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
Advertisements

Introduction to Flowcharting
Introduction to Flowcharting
CHAPTER 1: AN OVERVIEW OF COMPUTERS AND LOGIC. Objectives 2  Understand computer components and operations  Describe the steps involved in the programming.
Introduction to Flowcharting
Introduction to Flowcharting A Supplement to Starting Out with C++, 4th Edition by Tony Gaddis Published by Addison-Wesley.
BIF703 System Analysis & Design Diagramming – Part II: System Flowcharts / Gantt Charts.
Documentation Letts Study Guide Information Systems - IT Chapter 19.
Fundamentals of Algorithms MCS - 2 Lecture # 4
Steps of a Design Brief V Obtained from workshop-July, 2014-in Guildford County.
CS 151 Digital Systems Design Lecture 37 Register Transfer Level
Electronic Design Project and Skills 2
Flowchart Diagram Risanuri Hidayat. What A Flow Chart is a sequential diagram that shows the steps involved in an operation or task and the decisions.
Programming Logic and Design, Introductory, Fourth Edition1 Understanding Computer Components and Operations (continued) A program must be free of syntax.
The Program Design Phases
(C)opyright 2003 Scott/Jones Publishers Introduction to Flowcharting A Supplement to Starting Out with C++, 4th Edition by Tony Gaddis Scott/Jones Publishers.
CSC103: Introduction to Computer and Programming
1. Know the different types of flow block 2. Understand how problems can be broken down into smaller problems.
Flow Charting. Goals Create Algorithms using Flow Charting procedures. Distinguish between Flow Charting and Pseudocode. Top-Down Design Bottom-up Design.
Flow Charts.
Flowchart IDT. What is a flowchart? Visual representation of a flow of data Outline of process or a solution to a problem Outline the basic logic behind.
Design the program Create a detailed description of program –Use charts or ordinary language (pseudocode) Identify algorithms needed –Algorithm: a step-by-step.
1 Introduction to Flowcharting. 2 Writing a program Defining the problem –Write down what the program will do Planning –Write down the steps, draw a flowchart.
1 Introduction to Flowcharting. 2 Writing a program Defining the problem –Write down what the program will do Planning –Write down the steps, draw a flowchart.
Flowcharting A Quality Improvement Tool. Quality = Inspection Statistical methods assisted in prevention of defects – The need for inspection declined.
Algorithms & Flowchart
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
`. Lecture Overview Structure Programming Basic Control of Structure Programming Selection Logical Operations Iteration Flowchart.
Flowcharting An Introduction. Definition A flowchart is a schematic representation of an algorithm or a process.
Steps of a Design Brief V  Is a Plan of work A written step-by- step process by which the goal is to be accomplished The plan can include expected.
(C)opyright 2000 Scott/Jones Publishers Introduction to Flowcharting.
Flowcharts & Sitemaps Integral part of the design process –Show all possible paths and the various activies such as navigation, games, tests, transactions,
Fundamentals of Algorithms MCS - 2 Lecture # 5. Representation of Algorithms (continued) Flowcharts.
1 Introduction to Flowcharting Computer Science Principles ASFA.
Algorithms and Pseudocode
Flow Charts. Flow charts A flowchart is a schematic (idea of doing something) representation of a process. They are commonly used in Computer Science.
FLOW CHARTS IN PROCESS DESCRIPTION FRANK CHINGARANDE.
Algorithms and Flowcharts
Creating Flowcharts Principles of Engineering
Creating a Flowchart Computer Integrated Manufacturing
GC101 Introduction to computers and programs
Creating Flowcharts Name of PowerPoint CIM Name of Lesson
Introduction to Flowcharting
Basics of Computer Programming
System Design.
Introduction to Flowcharting
Algorithms An algorithm is a sequence of steps written in the form of English phrases that specific the tasks that are performed while solving the problem.It.
Lecture 2 Introduction to Programming
Introduction To Flowcharting
Numbering System TODAY AND TOMORROW 11th Edition
Basics of Computer Programming
What is a Flow Chart ? An organized combination of shapes, lines, and text that graphically illustrates a process or structure A pictorial representation.
Basics of Computer Programming
Introduction to Flowcharting
Basics of Computer Programming
Creating Flowcharts Principles of Engineering
Creating Flowcharts AIM:
Unit# 9: Computer Program Development
Creating Flowcharts Principles of Engineering
Creating Flowcharts Name of PowerPoint CIM Name of Lesson
MSIS 655 Advanced Business Applications Programming
الفصل الثاني الخوارزمية
` Structured Programming & Flowchart
ME 142 Engineering Computation I
Introduction to Programming
Creating Flowcharts Name of PowerPoint CIM Name of Lesson
Creating Flowcharts Principles of Engineering
Introduction to Flowcharting
Creating Flowcharts Principles Of Engineering
Creating Flowcharts Name of PowerPoint CIM Name of Lesson
Presentation transcript:

BLOCK DIAGRAMS

Block diagrams A way to show schematically the individual subsystems of a design with arrows to show the direction that signals flow through the subsystems. It is a quick way to determine what the subsystems do in the system without analysing the full circuit or looking at an entire software program.

Block diagrams A way to show schematically the individual subsystems of a design with arrows to show the direction that signals flow through the subsystems. Sometimes the blocks are labeled with the name of the subsystem.

Block diagrams A way to show schematically the individual subsystems of a design with arrows to show the direction that signals flow through the subsystems. Sometimes the blocks are labelled according to the mathematics that the subsystem performs on the input signal

Electronic Design Project I expect to see at least one block diagram for the entire system – the optical pulse meter in: Each team member’s notebook Changes in the design of subsystems should be shown by changes to the block diagram. For example, there will need to be a filter and an amplifier in the analogue portion of the circuit. If the order in which these two are changes as the team designs the pulse meter, then a new block diagram should be added to everyone’s lab notebook. The old block diagram should stay in the notebook! The final report The final presentation.

FLOWCHARTING

Flowchart Visual representation (a diagram) of the activities that will be performed to complete a task or project. Used frequently to describe the sequence of steps in a software programme. Also used to outline the tasks that need to be done on a manufacturing line or to complete a design project. In these cases, the flow chart is usually coupled with a Gantt chart.

Charts Flowchart Gantt Chart

Common Shapes NameDescription ActionA process or action such as a calculation, assignment, etc. Start/Begin and Stop/EndShows where the flow starts and stops DecisionIndicates that a decision has been made between 2 or more choices FlowlinesShows the order in which actions are to be completed ConnectorShows where a flow restarts when it doesn’t fit on a single page. Input/OutputIndicates where date is either collected, stored, or stored.

Examples of Flowcharts

Loops These are some times called Do loops For-Next loops If-Then statements If-Else statements While statements

Infinite Loops In Microelectronic Systems, we used while(1) to continuously loop through the mbed programs.

Single and Multiple Ends

Connector

Other Symbols flowchart

Electronic Design Project I expect to see at least one flowchart for the mbed software program in: Each team member’s notebook Use it when first thinking through how the program should be written. Use it to document the final version of the program. The final report The final presentation.