Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 CS 106 Computing Fundamentals II Chapter 13 “Design Specification” Herbert G. Mayer, PSU CS status 6/29/2013 Initial content copied verbatim from CS.

Similar presentations


Presentation on theme: "1 CS 106 Computing Fundamentals II Chapter 13 “Design Specification” Herbert G. Mayer, PSU CS status 6/29/2013 Initial content copied verbatim from CS."— Presentation transcript:

1 1 CS 106 Computing Fundamentals II Chapter 13 “Design Specification” Herbert G. Mayer, PSU CS status 6/29/2013 Initial content copied verbatim from CS 106 material developed by CS professors: Cynthia Brown & Robert Martin

2 2 Syllabus Problem Solving Techniques Problem Solving Techniques “When” Problems “When” Problems Gantt Charts Gantt Charts Napoleon’s Army in Russia Napoleon’s Army in Russia How Many/How Much How Many/How Much Flow Charts “How” Flow Charts “How” Simple Process Simple Process Variables Variables Algorithm Algorithm From Use Cases to Flow Chart From Use Cases to Flow Chart

3 3 Four Steps of Problem Solving * OrientPlanExecuteTest These steps are generic; they apply to any kind of problem, not just spreadsheet development, programming, or process design, but we will focus on those in CS 106 * Carlson and Bloom, “The Cyclic Nature of Problem Solving: An Emergent Multi-Dimensional Problem Solving Framework”, Educational Studies in Mathematics, Vol. 58 Number 1, 2005 3

4 4 Specification We covered requirements (the orient phase… what we want to have happen)We covered requirements (the orient phase… what we want to have happen) Now we’re ready to talk about the specification or design phase (the planning phase… how it should happen)Now we’re ready to talk about the specification or design phase (the planning phase… how it should happen) Our tool for developing and communicating a design is the flow chartOur tool for developing and communicating a design is the flow chart 4

5 5 Problem-Solving Techniques Flowcharts are a visual technique for designing a process (figuring out how to do something)Flowcharts are a visual technique for designing a process (figuring out how to do something) Before we learn about flow charts (a technique for “how” problems), let’s look at a couple of useful visual techniques for solving other kinds of problemsBefore we learn about flow charts (a technique for “how” problems), let’s look at a couple of useful visual techniques for solving other kinds of problems For more on the ideas here, see Dan Roam’s website, www.digitalroam.comFor more on the ideas here, see Dan Roam’s website, www.digitalroam.com 5

6 6 “When” Problems Suppose we want to make a master plan showing team leaders when each step of a complex process they are directing and coordinating will take placeSuppose we want to make a master plan showing team leaders when each step of a complex process they are directing and coordinating will take place Thus we need a When -> TimelineThus we need a When -> Timeline Since we need to convey a large amount of precise information, a Gantt Chart is an appropriate visual toolSince we need to convey a large amount of precise information, a Gantt Chart is an appropriate visual tool 6

7 7 Gantt Chart Example 7

8 8 GANTT with Dependencies 8

9 9 Baseline GANTT (shows comparison, change) 9

10 10 Napoleon’s Army in Russia – drawn by Charles Minard 10

11 11 How Many/How Much Suppose we need to answer how many/how muchSuppose we need to answer how many/how much Bar charts are often usedBar charts are often used Pie charts are another option (controversial because it is harder to compare pie slices than bars)Pie charts are another option (controversial because it is harder to compare pie slices than bars) There are plenty of interesting and clever variations… such as the word usage chart (next slide)There are plenty of interesting and clever variations… such as the word usage chart (next slide) 11

12 12 Variation on Bar Chart Word Usage in 2008 McCain Speech 12

13 13 Example: Seeing the Market These charts show how much versus when. They give much more insight than a numerical list of prices. 13

14 14 Flowcharts: “How” Flowcharts are a visual tool for specifying a processFlowcharts are a visual tool for specifying a process They can be as high level or as detailed as we need them to beThey can be as high level or as detailed as we need them to be They use symbols and arrows to represent steps and choicesThey use symbols and arrows to represent steps and choices 14

15 15 Flowchart Symbols Flowline: Connects symbols and indicates the flow of logic. It is a one way street. Input/Output: Data to be read or displayed are described inside. Terminal: Represents the beginning or end of a task. Processing: The process description is included inside the symbol. Decision: Used for logic/comparison operations. Has one entry and two exits. 15

16 16 One more… Continuation 16

17 17 Simple Processes A simple process has no decisions in it; you always do it the same wayA simple process has no decisions in it; you always do it the same way As a result, its flowchart is just a straight line of boxes connected by arrowsAs a result, its flowchart is just a straight line of boxes connected by arrows Example: most recipes, instruction sheets with assemble-it-yourself furniture, simple calculationsExample: most recipes, instruction sheets with assemble-it-yourself furniture, simple calculations 17

18 18 Simple Process: Compound Interest Goal: Given a number N of years, an amount P of money (principal), and an annual interest rate R, calculate the total amount of money T you will have after P is invested for N years at rate R, using interest which is compounded annually. T = P(1+R) N Goal: Given a number N of years, an amount P of money (principal), and an annual interest rate R, calculate the total amount of money T you will have after P is invested for N years at rate R, using interest which is compounded annually. T = P(1+R) N Test 1: P = 100, N = 1, R = 5% (.05): 105 Test 2: P = 100, N = 7, R =.05: 140 Test 3: P = 0, N = 7, R =.05: 0 Test 4: P = 100, N = 7, R = 0: 100 Test 5: P = 100, N = 0, R =.05: 100 18

19 19 Just for interest P = 100, N = 20, R =.05 gives 265 P = 100, N = 30, R =.05 gives 432 By contrast, simple interest at 5 percent gives $5 per year, so after 20 years you have a total of $200; after 30 you have $250. If R is, say, 8%, the difference is even more striking. 19

20 20 Storing Information In this process we have to keep track of some information, like how much principal we have, what the interest rate is, etc.In this process we have to keep track of some information, like how much principal we have, what the interest rate is, etc. We’ll use VBA variables to store these valuesWe’ll use VBA variables to store these values

21 21 Variables Variable is a named container used to refer to a quantity whose value is stored, can be recalled, and can changeVariable is a named container used to refer to a quantity whose value is stored, can be recalled, and can change You can think of a variable as the name of a container that holds a valueYou can think of a variable as the name of a container that holds a value Constant is a name for a quantity whose value does not changeConstant is a name for a quantity whose value does not change A spreadsheet cell is a good example of a container that can hold a valueA spreadsheet cell is a good example of a container that can hold a value 21

22 22 Math Variables vs. Programming/Spreadsheet Variables In math, a variable is used in an equation to represent some scalar quantityIn math, a variable is used in an equation to represent some scalar quantity Given the equation 3x = x + 6, we can solve this equation for x and get x = 3. You can check the correctness by substituting 3 for x on each side and seeing that you get the same value (9)Given the equation 3x = x + 6, we can solve this equation for x and get x = 3. You can check the correctness by substituting 3 for x on each side and seeing that you get the same value (9) An “equation” like x = x + 1 would be meaningless; it has no solution; we call it a contradictionAn “equation” like x = x + 1 would be meaningless; it has no solution; we call it a contradiction 22

23 23 Programming Variables Programming variables and spreadsheet locations are a place to store a value, which can changeProgramming variables and spreadsheet locations are a place to store a value, which can change The assignment statement x = 4 means to store the value 4 in location x. It is not purely an equation, though it looks like oneThe assignment statement x = 4 means to store the value 4 in location x. It is not purely an equation, though it looks like one The pair of assignments:The pair of assignments: x = 4 x = x + 1 means to first store a 4 in location x, and then take the current contents (4), add 1, and store the result (5) in location x. The order of the statements is extremely important. 23

24 24 Compound Interest Calculator begin R = annual rate N = num. of years P = principal R = annual rate N = num. of years P = principal T = P*(1+R)^N Output T end 24 We used variables R, N, P, and T. Arrows in a flowchart are like one-way streets; once you go down one, you can’t back up

25 25 Example Spreadsheet The spreadsheet called Interest Calculator 1 has this formula in itThe spreadsheet called Interest Calculator 1 has this formula in it Let’s see how to build this spreadsheetLet’s see how to build this spreadsheet 25

26 26 Algorithm The interest rate calculator is an example of a simple algorithm: an effective method in which a sequence of well-defined instructions for completing a task will, given an initial state, proceed through a well-defined series of steps, eventually terminating in an end-stateThe interest rate calculator is an example of a simple algorithm: an effective method in which a sequence of well-defined instructions for completing a task will, given an initial state, proceed through a well-defined series of steps, eventually terminating in an end-state Thought to be named for Al-Khwārizmī, Persian astronomer and mathematicianThought to be named for Al-Khwārizmī, Persian astronomer and mathematician 26

27 27 Back to the Candy Machine… 27

28 28 User Interface The first step in the design is often to think about the user interfaceThe first step in the design is often to think about the user interface What does the user interact with?What does the user interact with? What are the possible events that can occur?What are the possible events that can occur?

29 29 Candy Machine Objects, Events Coin slot User inserts a coin Candy slot Opens so a piece of candy can come outHandle The user attempts to turn the handle Coin receptacle It can be full, partly full, or empty These are all the objects in the requirements that have events However: how does the machine know if there is a correct coin in the coin slot? Or any coin at all? It looks like the handle turning mechanism needs to be able to check some things.

30 30 Handle Functions Turning the handle can send a coin to the coin receptacle. The handle only allows the correct coins through and won’t turn otherwiseTurning the handle can send a coin to the coin receptacle. The handle only allows the correct coins through and won’t turn otherwise The handle should not turn if the coin receptacle is fullThe handle should not turn if the coin receptacle is full The designer, a mechanical engineer, figures out whether she can build a handle mechanism like this within our budget, and what the tradeoffs areThe designer, a mechanical engineer, figures out whether she can build a handle mechanism like this within our budget, and what the tradeoffs are We won’t look at the mechanical aspect of this, but we can express the logical flow of the solution in a flow chartWe won’t look at the mechanical aspect of this, but we can express the logical flow of the solution in a flow chart 30

31 31 Turning the Handle The next slide shows the flowchart for the event where someone tries to turn the handle of the candy machineThe next slide shows the flowchart for the event where someone tries to turn the handle of the candy machine It shows the use of the begin/end, conditional, and process step boxesIt shows the use of the begin/end, conditional, and process step boxes

32 32 Handle Flowchart start begin attempt to turn handle correct coin in slot? handle does not turn handle turns coin goes into receptacle candy slot opens receptacle has room? end noyes noyes

33 33 From Use Cases to Flowchart In the candy machine example, we have several objects, but only one event that requires a process: trying to turn the handleIn the candy machine example, we have several objects, but only one event that requires a process: trying to turn the handle The use cases were various complete scenarios of an interaction with the machineThe use cases were various complete scenarios of an interaction with the machine We abstracted information from several use cases to design the handle turning eventWe abstracted information from several use cases to design the handle turning event We use the tests to make sure we put the pieces together correctlyWe use the tests to make sure we put the pieces together correctly

34 34 Event-Driven Design This type of design is called “event driven” because it works by analyzing what the events are in the process and what should happen as a result of each eventThis type of design is called “event driven” because it works by analyzing what the events are in the process and what should happen as a result of each event This has turned out to be a highly effective way of designing processesThis has turned out to be a highly effective way of designing processes And is used in VBAAnd is used in VBA 34


Download ppt "1 CS 106 Computing Fundamentals II Chapter 13 “Design Specification” Herbert G. Mayer, PSU CS status 6/29/2013 Initial content copied verbatim from CS."

Similar presentations


Ads by Google