Skip to main content

Posts

Showing posts from 2016

Architecture Diagram Explanation

Input Devices: Microphone, trackpad, camera, phone, scanner, USB Output Devices: Monitor, speaker, printer, projector, USB Program [stored in Random Access Memory (RAM)] Ask students for name, score Save the name and score Add scores Save scores in sum Calculate Average Save Avg Print... RAM Volatile Memory When the power is off, everything that is stored in RAM, is erased Temporary Central Processing Unit (CPU) Control Unit (CU) Sees through the execution of line by line statements of the program Arithmetic Logic Unit (ALU) Logical deduction If Avg is greater than 90, then... Evaluates logical statements

Computer Architecture Diagram

Fundamentals of Computer Architecture

Our computer always responds to electricity We choose binary number system (our power button) Of/On (2 states) 0: bit 1: bit Combination of 8 bits: byte  ex. Mega byte Byte: Unit of memory Every symbol on the keyboard: character  A; a to Z; z; all numbers...etc. Each character is represented by a combination of bits (1 byte) ex. 01000100 Based on code, alphabet shows up Compiler Translates the entire source code into binary Takes in code Points out errors When it is correct, it converts the source code into machine language/binary code/binary language/object code  Interpreter   Translates line by line Easier to find mistake in some situations (Has same features as compiler) Source Code (Java, C++) ---> Compiler/Interpreter ---> Object Code (binary: 01001111)  "My source code is not compiling/interpreting"  ______________________________________________________________ Systems programs that helps us to...

Points to Consider for Presentation

Some points I would consider to keep my audience engaged during the Presentation. Concise slides  Bullet points Topics which concern a general audience Ask questions to the audience Sound interested and excited Start with simple ideas Introduce unique fun facts Appropriate font size for audience Add some humor Powerful images Articulate, project, and vary tone while speaking Add personal stories Audience will connect and believe in you Know information  Don't read off slides

Software Approach, Top Down Design

One way of coding is to simply have a rough idea of what you want to do and then start typing away to produce one huge source file. This is a very bad idea. The resulting code is likely to have many issues with it that include: Poorly documented code, so very hard to maintain and update 'Spaghetti Code' - which means a tangled mess of jumps and loops all over the code, very hard for someone to understand. Even by the originial coder a few days later! Duplication of code, so wasting memory and running speed Very hard to develop by more than one person as there is only one file Very hard to debug - the file either works of it doesn't

Systems Thinking

What comes to your mind when you hear the word, system? Gears and settings icon Small error can have a large impact and effect the outcome (different than expected) What is a system, and how does it work? A system is an orderly and efficient process where tasks are completed. A system works similarly to an assembly line.

Name Card - Mission Reflection

1) What and why did you do each step in design thinking process? Each step of this process is necessary because they all build on top of each other. In Empathize, I asked the user for the requirements which I need to fulfill in my name card. I also had my partner tell me what were the most important parts so I remember to incorporate those (Digging Deeper). In Define, I established a common theme which was relevant to all of the digging deeper topics and I made a list of challenges that I might encounter. This is so I know what to do if any difficulties do come up. Ideate is when I created my first hard copy. I drew a simple sketch that had the digging deeper topics and I took feedback so that I can fix those problems for my final project. In this step I also started to brainstorm solutions. As I completed each step including my final prototype, I asked for more feedback so my name card would be completely to the users satisfaction. 2) What did you learn?  I learned that each...

Name Card - Post Prototype/Test

Feedback: Jason said to outline the black on the music note. I did this by using 2 different duct tape patterns.

Name Card - Ideate

Feedback: The dog looks creepy Make hills ice cream Add lots of color Make bigger cloud Draw sunset

Name Card - Define

Theme: Favorite food, season, color, pet, hobby Challenge: How am I supposed to create the pet? Do I just make the generic animal I have (dog) or specific? How do I incorporate weather in this card? Should I put a sun for sunny, or rain and clouds for cold?

Name Card - Empathize

I am making a name card for Jason . My name card will have my information. Questions: Food Weather What do I want to be when I grow up? Sports Carpet Pet Candy Cuisine Tech device Chair Favorite band Preferred brand of earbuds Tree Vacation Spot Color Digging Deeper: Food Weather Pet Candy Color

Software Development Life Cycle & Design Thinking Skills

Software Development Life Cycle System analysis, requirements gathering:  Defines project goals into defined functions and operation with the objective in mind. It is the process of gathering user requirements, diagnosing problems, and recommending improvements to the future system.   A series of steps followed by the developer are: 1. Gathering facts: End user requirements are obtained through documentation, client interviews, obervation and questionnaires - asking what the user is currently doing and if there are any specific improvements they want or prefer. 2. Scrutiny of the existing system: Identify pros and cons of the current system in-place, so as to carry forward the pros and avoid the ons in the new system. 3. Analyzing the proposed system: Solutions to the shortcomings in step two are found and any specific user proposals are used to prepare the specifications.  Systems design: Describes desired features and operations in detail, including...

Analysis - Empathize on behalf of the user

Ways I would think on behalf of the user: Ask a wide variety of targeted customers questions through a survey. Mainly on their opinions on what would be comfortable, efficient, and useful Be open minded and make room for growth. Give benefits to the customers to entice and interest them in the product. Think about common and daily struggles to fix with your product. This should be appealing to the customer's concerns and issues. Create a support and help area for customers who do not quite understand. Make a user-friendly environment. Organized but unique

Remembering someone by their name

What are the things that help me remember someone's name? I try to associate them with common day objects. ex. Aarzu - "Our zoo" (but with less emphasis on the "ou") I also match the face with the name. Nicknames are also helpful. If you use the name in conversations, it may become easier to remember. Asking for the spelling and correlating will help with pronounciation.

My perspective on Computer Science

1. What is computer science? Computer science is the study of computers whether its software or hardware. 2. What do I know: I know a little bit of some languages. Java, Java Script, Python, HTML, and CSS are all languages that I have been experienced with. Although I have taken classes on all of these, I still do not completely understand them. 3. What do I expect to learn? I expect to learn how a computer functions and responds to the user's inputs. Organizing code is another component that I want to know.