Introduction to Design

Slides:



Advertisements
Similar presentations
Reading and writing reports
Advertisements

© The McGraw-Hill Companies, 2006 Chapter 9 Software quality.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
Software Development, Programming, Testing & Implementation.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Activity 1 - WBs 5 mins Go online and spend a moment trying to find out the difference between: HIGH LEVEL programming languages and LOW LEVEL programming.
Introduction to Design. What is Design? Blueprint of your solution Blueprint of your solution All decisions you have made about solution? All decisions.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Testing. 2 Overview Testing and debugging are important activities in software development. Techniques and tools are introduced. Material borrowed here.
Lego Mindstorms Robot Tracey Zhang. LEGO MINDSTORMS STATMENT The design challenge my group experimented with is the Lego Mindstorms robot. Our goal is.
The Software Development Process
Lecture 6: Writing the Project Documentation Part IV.
Phase Test 2 You have been provided with a finished application available from the module web site called Phase Test 2 Sample Application. This application.
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
YOUR FESTIVAL START PLANNING IN MORE DETAIL. WORD DOCUMENT Transferred spider diagram and headings into a word document. Add more details to this document.
HOME SECURITY USING PLC Ryan Badgett EKU, Dept. of Technology, CEN.
Differentiating Your Instruction Through Guided Reading.
Table of Contents I: Create an automatic TOC Get started on a table of contents A TOC may be a simple list of chapter titles, or it can include several.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
Adding and Eating Worms Mrs. C. Furman August 23, 2010.
Detailing your features for your second client meeting What to put on your Google Group for them to review!
Vex Robotics program three: using motors and sensors together.
CSC 108H: Introduction to Computer Programming Summer 2011 Marek Janicki.
 Programming methodology: ◦ is a process of developing programs that involves strategically dividing important tasks into functions to be utilized by.
The Scientific Method.
Good Morning  Please be sure to take care of your belongings.
VEX IQ Curriculum Smart Machines Lesson 09 Lesson Materials:
ECE 353 Lab 3 Pipeline Simulator
They’re there, but are they YOURS?
Practical Office 2007 Chapter 10
Template for Science Fair Presentations
CSCI-235 Micro-Computer Applications
Java on the LEGO Mindstorms EV3
Good Morning  Please be sure to take care of your belongings.
Introduction To Programming with LEGO NXT 2
Red Badge of Courage Webquest
Software Myths Deep Mann.
Types of SQL Commands Farrokh Alemi, PhD
Reading and writing reports
TRANSLATORS AND IDEs Key Revision Points.
Resources BTEC National.
Lights! Camera! Graphs! Photos!
Answering Text-Dependent Questions with Evidence Based Claims
Automation and Robotics
Approve Documents (Requisitions) in Owl Link
Introduction to Systems Analysis and Design
Lecture Set 3 Introduction to Visual Basic Concepts
Software Testing and Maintenance Maintenance and Evolution Overview
Line Following Behavior
Storing Values as Variables
Documentation for Developers
EV3 Programming guide to “Following”
Program Documentation
Use Case Model Use case diagram – Part 2.
Defining Classes and Methods
ROBOT DESIGN JUDGING Without A ROBOT Game Table
Template for Science Fair Presentations
ECE 353 Lab 3 Pipeline Simulator
Memo Writing.
Use Case Analysis – continued
Running a Java Program using Blue Jay.
Red Badge of Courage Webquest
Obstacle Detection.
PSS0 Configuration Management,
Four Rules for Effective Writing
Getting started with LEGO EV3 Mindstorms software
Software Development Techniques
EQ: What are the building blocks of Geometry?
Lecture 3: Communicate in Writing
Refactoring.
Presentation transcript:

Introduction to Design

Instructor: G. Rudolph, Summer 2006 Where should I be? Completed Mechanical Model with modifications Code should control the drive motors smoothly, light sensor detects boundaries, Ultrasonic sensor detects opponent Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Where should I be? “To Be Completed” (90%) Clean up code Comments in code Document Hardware Design Software Design Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Code Cleanup May have borrowed code and modified it Now we have to “make it ours” Show that we understand it Make sure everything is clear Want the code to match our design, whether or not the design is Documented, or In our heads Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Code Cleanup Make sure Object, Method, and variable names match our application Add/ Update Comments to match our application & style Compile and run periodically to make sure everything still works Remove any commented blocks of code Remove unused code Variables, methods, objects Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Comments Enough that you can remember what it is you were doing and thinking, if you had to maintain the code 6 months from now Comments for Class Each method Variables Lines of code as needed We will formalize this with Javadoc templates during Project 2 Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Hardware Design Assume the reader (me) has access to the Lego Set and the model books Describe what you added or changed Assemblies may be difficult to put into words without the aid of pictures Do your best Assume you can show them the parts you are using (optional) Hand drawings of pieces are acceptable Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2006 Software Design 3 things to show 1. Objects 2. Their INTERESTING interrelationships 3. Their behaviors Instructor: G. Rudolph, Summer 2006

Instructor: G. Rudolph, Summer 2008 Where is the Design? Comments in code are closest to the code Pictures (or equivalent models) can Give “the big picture” Help communicate important details in ways that are difficult to see from code Instructor: G. Rudolph, Summer 2008