Question
Student presentation concepts from another source
Letitia - a step-by-step process of breaking down glucose into energy
Mana - repeating process of the steps of the cell division, going from interphase to division, and back to interphase.
Paul - a series of organisms that show similar characteristics and compare them to those that do not
Which best describes the SmartArt graphic layout each student should use?
Answer:
Letitia would use a process, Maria would use a cycle, and Paul would use a relationship.
Explanation:
Letita's assignment requires her to show how glucose can be broken down into energy, this requires a series of steps in s linear fashion, meaning it would be best suited to a process-style diagram.
Marta's project involves showing the steps of the cell cycle: the clue is in the name. This process is not linear, and instead repeats itself, meaning it fits to a cycle diagram (i.e. a circular diagram)
Paul is comparing and contrasting different organisms. Therefore, he should use a relationship diagram to show shared characteristics as well as features that differ.
Answer: Walkway Over the Hudson, a bridge that crosses the Hudson River in Poughkeepsie, is 2.063 kilometers long. Anping Bridge, which was built in China 850 years ago, is 2.07 kilometers long.
HOPE IT HELPED:)
I would go with A) Tablet because that's basically a bigger phone and mobile cmp combined, its not D) because that's a synonym for a smartphone and not C) because paper and pencil is not like a smartphone, and not B) because that's like reading online books.
Answer:Table
Explanation:A relational database has structures and thus have more than one table. The tables consist of row (for entry) and column (for data). As a result, data are organized in a simple manner and are normally consistent.
Answer:
I think it's false
Explanation:
I don't think so. What makes me hesitate is that you may have been told that in your text or in the classroom.
Here are the steps as I understand them.
- Understand the problem you are trying to solve.
- Design a solution.
- Draw a flow chart.
- Write pseudo-code.
- Write code.
- Test and debug.
I think you've done the designing long before you start writing code or even pseudo-code.