Computer Architecture Notes

Input Devices

• Keyboard
• Mouse/Trackpad
• Screen
• Camera
• Microphone
• Graphics Tablets
• Barcode Reader
• Gamepad
• Joystick
• Keyboard (Piano)
• Scanner
• Webcam
• Touchpads
• Pen Input
• Electronics Whiteboard
• Magnetic Key Cards

Output Devices

• Screen Monitor
• Printers
• Plotters
• Projector
• LCD Projection Panels
• Computer Output Microfilm
• Speakers
• Radios

Both

• Moderns
• Network Cards
• Touch Screen
• Hedsets
• Speakers
• Audio Cards
• Sound Cards
• USB
• Fax Machine

RAM (random access memory) is a volatile memory, meaning it erases all the memory when the power is switched off. It stores the current programs and data. 

CPU (Central Processing Unit) is into Control Unit and ALU

ALU (arithmetic logic unit) performs arithmetic operations and evaluates logical statements true or false.

Control Unit oversees the execution of the program statement after statement. 

Computer Architecture Diagram

Fundamentals of Computer Architecture

• What gives life to this laptop?
• It's the electricity!
• use the power button
• the zero is for off, the one is for on
• Binary was chosen for the two states
• on and off
• 0 is called a bit
• 1 is called a bit
• 8 bits make up 1 byte
• the unit of computer memory is a byte
• Every symbol on this keyboard is called a Character
• letters a-z, numbers, shift, space, special symbols
• Example: A = 0100 1100 (not true, just an example)
• see, it's 8 bits!
• It goes through pulses of electricity
• every 1 says go, every 0 says no
• Every symbol has its own pulse
• When you press a key on the keyboard, electricity moves from the key in patterns
• If you press one key down wrong, it doesn't work
• Programming Languages are a little bit like English
• Java, C, C++, Python
• { Begin } End
• Computers need to process information
• like we use translators to translate from english to other languages, computers use their translator to translate from code to binary
• Compiler
• It goes through the source code and points out any errors and when the entire source code is correct, it will convert into zeros and one
• Machine Language
• interpreter
• It goes through the source code and points out any errors and when the entire source code is correct, it will convert it line by line, statement by statement
• Source Code ---> Compiler or Interpreter ---> Object Code
• HLL (High Level Languages)
• like Java, C++, Python
• Binary Code/Lang
• machine code/Lang
• Lang = Language
• Systems Program
• Driver Program
• Connection between the printer and the computer
• Application Program
• Hospital Management System
• Banking System

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 hug source file.
This is a very bad idea.
The resulting code is likely to have many issues in it that include

• Poorly documented code
• very hard to maintain and update
• Spaghetti code
• tangled mess of jumps and loops all over the code, very hard for someone to understand. even by the original coder a few days later!
• Duplication of code
• wasting memory and running speed
• Very hard to develop by  more than one person
• there is only one file 
• Very hard to debug
• it either works or it doesn't

There are more issues, but hopefully the list shows that it is best to have a methodical, professional approach to coding which this mini-web will cover.

Points to Consider for Presentation

Some points I would consider to keep my audience engaged during the presentation are

• Using humour/jokes to appeal to the audience at hand
• Using interesting points
• Making sure everything I saw is not redundant, and that it is all interesting
• Making sure the presentation itself is interesting
• Using good vocabulary
• Being able to get the point across whilst giving the audience time to understand what I am saying
• Maybe give the presentation a soundtrack?
• Also, speaking clearly and loudly
• Have new information to keep them engaged
• Interact with the Audience
• Always OVERestimate them incase they question you
• 
  

Systems Thinking

• What comes to your mind when you hear the word "System?" What is a system? How does it work? Give some examples.
• When I think of the word System, I normally think of laptops or other forms of technology. I think a system is something with multiple steps that all rely on each other in some sort of way or form. Each thing in a system builds a bigger whole, and that is what helps a system work. Most laptops work with a sort of system that helps them get turned on or get fired up.
• Some sorts of systems include the Design Thinking Process. All the little steps go together to make a complex whole. Laptops are also a sort of system; they work together. Most big companies and offices are systems in the sense that they require multiple people to create one unified product. Sports teams are also examples of systems. 

Name Card Mission Reflection

1. Why is each step required?
1. I think each step is required because it helps every designer pause and process the needs of their client. The steps make it much easier to make an idea and follow through with it, along with keeping the client's needs in mind. When you empathize, you think of the needs of your client and create a product. When you define a challenge and theme you build upon the ideas you formed when you were empathizing with your client. The challenge is constantly put through out the process, and when you ideate something, you have to keep that challenge in mind. When you make a protoype or you test something, you use skills and ideas that you have built throughout the entire process. Each step is required because it builds upon the one before it, and wihtout it, the whole process would collapse.
2. What did you learn?
1. I learned a lot about my peers, and I also learned a lot about the design process. I also learned about disruptive innovation and what makes a good design. This mission taught me what a successful designer must do.
3. What is your contribution towards disruptive innovation for this project?
1. Apart from just enjoying my 'artistic ability', I am proud of my project because it is seen as disruptive innovation. The idea of using calligraphy to write my name was new, and my idea of using the soccer ball to showcase my other interests was disruptive as well. My peers would often remark, "i wish I had done that!" as I showed them my work.

Name Card Prototype/Test (feedback from Ryan)

I think my namecard was pretty good. Ryan agreed with me, but she had some feedback.

• Make a sunset in the background!
• Use more color in the Background!
• Putting colors like yellow in the sunset is going to be great. 

Overall, he thought I did great!

Name Card-Ideate

Feedback from mine:

• Color in Middle Patch of the Soccer Ball
• Draw in stuff in the patches of soccer ball
• put star wars in the sky
• Add a quote from your favorite book
• Add something about favorite soccer player (Messi or Morgan)

Name Card- Define

My Digging Deeper Questions: 

• Favorite Sport
• Theme: Soccer
• Challenge: How to Draw a Soccer Ball
• Favorite Music
• Theme: Music/Instruments
• Challenge: How to incorporate the two instruments/music notes
• Favorite Classes/Profession
• Theme: English/History
• Challenge: How to incorporate writing/a map
• Favorite Hobby
• Theme: Writing/Music
• Challenge: How to incorporate books/music notes
• Favorite Color
• Theme: Black
• Challenge: Make it Black with it still being visible

Name Card-Empathize

I am making a name card for Ryan Brown. My name card will have my information.
Some questions and answers Ryan Brown asked me were:

• What is your favorite Book?
• Around the World in 80 Days by Jules Verne
• What is your favorite color?
• Black
• What is your favorite movie?
• The Interview
• What is your favorite sport?
• Soccer
• What is your favorite Food?
• Sushi
• What is your favorite Drink?
• Coffee
• What is your favorite Hobby?
• Writing/Music
• What is your favorite TV show?
• Friends
• What is your favorite Class?
• English/History
• What is your favorite place
• Washington DC/Towns like Mendocino
• What is your favorite instrument
• I play piano and viola but I like viola better
• What kind of music do you like
• 70's-90's rock, modern rock, and classical
• What do you want to be when you grow up
• Writer

Digging Deeper

• Favorite Sport
• Favorite Music
• Favorite Classes/Profession
• Favorite Hobby
• Favorite Color

Software Development Life Cycle and the Design Thinking Process

Software Development Life Cycle and the Design Thinking Process:

• 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
• The steps are:
1. Gathering facts
1. End user requirements are obtained through documentation, client interviews, observation 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
1. Identify pros and cons of the current system in-place, so as to carry forward the pros and avoid the cons in the new system.
3. Analyzing the proposed system
1. Solutions to the shortcomings in step two are found and any specific user proposals are used to prepare the specifications
• Systems Designs
• Describes desired features and operations in detail, including screen layouts, rules, guidelines, process (data flow and entity relation) diagrams, pseudocode, and any other documentation
• Development
• The real code is written here.
• Integration and Testing
• Brings all the modules (pies) together into a special testing environment, then checks for errors, bugs, and interoperability
• Maintenance:
• During the maintenance stage of the SDLC, the system is assessed to ensure it does not become obsolete. This is also where updates are made to the initial software. It involves continuous evaluation of the system in terms of its performance and completing the change requests based on feedback.

Below, there is a picture of the Design Thinking Process, which a lot of designers use to fabricate their product.

1. Empathize
1. Work to fully understand the experience of the user for whom you are designing. Do this through observation, interaction, and immersing yourself in their experiences.
2. Define:
1. Process and synthesize the findings from your empathy work in order to form a user point of view that you will address with your design
3. Ideate:
1. Explore a wide variety of possible solutions through generating a large quantity of diverse possible solutions, allowing you to step beyond the obvious and explore a range of ideas
4. Prototype:
1. Transform your ideas into a physical form so that you can experience and interact with them and, in the process, learn and develop more empathy
5. Test:
1. Try out high-resolution products and use observation and feedback to refine prototypes, learn more about the user, and refine your original point of view

Help Me Remember Someone's Name

Meeting someone new can be difficult. If you are like me, then remembering someone's name is not a challenge. Most of the time, it is not hard for me to do because I use some tricks to help me remember their name. When I meet someone, their name will normally stick with me. If they don't, some of the methods I use are...

• Puns! I love making puns and I do so every day. Puns help me remember things.
• I listen to their interests and try making a rhyme out of that.
• If all else fails, I just add their contact to my phone and I look at that if I need to.
• Worst case, I'll just ask them if I forget.

Empathize-Ways I Would Think on Behalf of My User

As someone who finds herself surrounded with people asking her for favors and advice, I believe I have reasonable tactics that can help me empathize with someone. Empathy is feeling the emotions someone else expresses and thinking thoughts they would think. When empathizing with someone, it's important to take in many factors into the situation, such as their age, their hobbies and interests, their sense of humour (if they even have one), their music taste, the little details that make that person their idiosyncratic self, their lifestyle, and most importantly, the reasons why they came to me for advice or a favor. Even after working on a plan, I believe it is important to pause after every step, focus on their needs and ponder their response and their future goals in relation to the project.