Question

Maya and Darius are using the software development life cycle to develop a career interest app. They wrote the program pseudocode and have a mock-up of how the software will look and how it should run. All their work at this step has been recorded in a design document. What should the team do next?

Analyze the scope of the project
Design the program by editing pseudocode
Identify bugs and document changes
Write the program code

Answer 1

am i rigjht with D?

Answer 2

@axie

Answer 3

@extrinix

Answer 4

Usually after analyzing how the pseudocode will run, you most of the time want to find any errors in your code, so I would say you are incorrect

Answer 5

but i was looking at the process and

Answer 6

coding was next so just went with that

Answer 7

wait

Answer 8

i mean c?

Answer 9

@smokeybrown

Answer 10

I think you had the right idea to begin with, Gucchi, in terms of the design process.

They've already analyzed the scope of the project and written the pseudocode, so that part is done.
It would be difficult to identify bugs in the code or to document changes to the code, considering that, at that point, the code is not written.

So, I think the next step would be to write the code, based on the design concepts and pseudocode they have. As the code is being written, it would be appropriate to test for bugs, make changes, document those changes--but they need to start writing code first!

Answer 11

yeah same thing i was thinking

Answer 12

thank you

Answer 13

Sure thing, and good reasoning on you :)

Answer 14

btw i only have a few more questions left

Answer 15

That's good! Let's see if we can finish that up