Name Card: Mission Reflection

1. Recap the process -->

First, in empathize, my partner asked me a question for what he wanted to know about me. For example, he asked what sports I like. After asking 10 questions, he thought what he wanted to make for me. That was the digging deeper step. The next step was define. I gave answers to the 6 questions that my partner asked. I also defined the theme and what problems and challenges I had making my product. The next step was ideate. I drew out my first draft of my invention or product on a paper and got some feedback from my classmates. Then, prototype. I made the product with construction paper. I got more feedback. They told me what was good and what was bad. That was the test step.

2. Why is each step important in making your product.

Each step is important because you want to do what your consumer wants. Each part has a specific part that is important.

3. How will you improve your product if given a chance to make it again?

I would make it shoot farther and make the cartridge bigger

Name Card: Test

It was hard to make it shoot farther, but I did it. I had to cut the rubber band and replace them but with more stretchiness. I also made it hole more bullets. I had to cut out the cartridge and re-shape it. Now it holds 10.

Name Card: Prototype

Paul (consumer) : It needs to shoot farther

Varun: More bullets

Blake: Different Look

Kristen: Its great

Software Development Life Cycle (SDLC

Systems analysis, requirements gathering: Defines project goals into defined functions and operation with the objective in mind. It is the process of gather user requirements. diagnosing problems and recommending improvements to the future system.

A series of steps followed by the analyst are

1. Gather facts: End user requirements are obtained throw documentation, client interviews, observation and questionnaires - asking what the sure is currently doing and 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 cons in the new system.

3. Analyzing the proposed system: Solutions to shortcomings in step two are found and any specific user proposals are used to prepare the specifications.

• Systems design: Describes desired features and operation in detail, including screen layouts rules guidelines. processes( data flow and entity relation) diagrams pseudocode and other documentation. 
• Development : The real code is written here. 
• Integration and testing: brings all the modules( pieces together into a social 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 involved continuous evaluation of the systems in terms of its performance and completing the change requested based on the feedback.

Name Card: Define

Digging Deeper:

Name card; Blue/Green/ Black Gun

Advise:
Reina: It needs black
Arusha: That looks cool
Richard: Needs a cartridge
Sachi: Very Unique

Problem: How am I gonna make a gun?

Theme: My User needs a gun shaped slingshot that is blue.

Namecard: Empathize

Empathize:

Question	Answer
What do you like?	I like slingshots
What type of slingshot?	I like a gun shaped slingshot.
What type of gun shape?	A pistol
What is your favorite color?	Blue
What do you need to do?	He wants a target with it
What do you like to do on your free time?	Sleep or play basketball
If you were to have a kid, what would you name he/she?	Paul Jr.
What time of things do you want it to shoot?	Paper
What is your second favorite color?	Green

Digging Deeper:

Name card; Blue/Green/ Black Gun

Advise:
Reina: It needs black
Arusha: That looks cool
Richard: Needs a cartridge
Sachi: Very Unique

Name Card: Ideate

Digging Deeper:
Green, Blue, Gun Shaped, Cartridge

Problem: How am I gonna make a gun?

Theme: My User needs a gun shaped slingshot that is blue.

Software Development Life Cylce (SDLC) - Design Thinking Process

Software Development Life Cylce (SDLC) - Design Thinking Process SDLC Analysis Design Code Test Maintenance Design Thinking Process: 1. Empathize: Put yourself in the customers shoes.Ask what the costumer wants. Define: Find all the products or theme. Is it going to be fun or relaxing? Ideate: Design the product, like an outline, then ask other people. Prototype: Like a draft, you have it but you ask the costumer what they thing and fix what they do not like. Test: Before giving it to the customer, test it first. Then change it based on your opinion for the next time.

My perspective on Computer Science

What do you think (know) about Computer Science? Computer Science is where we learn about programing and other computer skills. What have you learned earlier? I have done computer science the past two years. I remember almost everything from 6th grade, but not much from 7th. I can remember scratch a little. What do you plan to learn here? I plan on learning computer skills. To reach your goals, what do you promise to do? I will have an open mind and so what ever Ms. Misra asks me to do

My perspective on Computer Science

What do you think (know) about Computer Science? Computer Science is where we learn about programing and other computer skills. What have you learned earlier? I have done computer science the past two years. I remember almost everything from 6th grade, but not much from 7th. I can remember scratch a little. What do you plan to learn here? I plan on learning computer skills. To reach your goals, what do you promise to do? I will have an open mind and so what ever Ms. Misra asks me to do