Identify the assumptions you have made about what your project will entail. What do your assumptions imply about how much data the program needs to take as input, and do what with it?
Develop your first cut in a flowchart form or as an initial draft. Simple RAPTOR or pseudocode "prototypes" can spell these out, as well as check both your math and your design assumptions. This does not need to be a fully working program. This "assumptions analysis" will also help you discover more functional requirements!
This activity will require you to assume various "roles" in the development process. Each member of the group your instructor has placed you in will assume the role of both the PD and the AD.
In your role as PD, post your current "SDP Project step work" (RAPTOR file) as early as possible so your AD(s) (other group members) can evaluate your work.
In your role of AD, collaborate and participate by providing the support requested or needed in the form of a reply to the initial post.
In your role as the Principle Developer (PD), post your current "SDP Project step work" (RAPTOR file) by Day Four of the module and answer the following questions: