The ability to delegate specific tasks to individual programmers is a key benefit of a program's structure that uses methods. Consider this idea carefully when you respond to the following questions: Do you prefer working in a team where each programmer creates one or more modules, or would you rather design a massive piece of software by yourself? Why? How do you think you'll deal with the difficulties of a huge development team? How may you handle or get beyond these obstacles?

One of the advantages of writing a program that is subdivided into methods is that such a structure provides the opportunity for different programmers to write separate methods, thus dividing the work. With this concept in mind, answer the following questions: Would you prefer to write a large program by yourself or work in a team in which each programmer produces one or more modules? Why? What challenges would you foresee in working with a large development team? What methods might you employ to overcome or manage these challenges?

Facts: Software design is the process of defining software methods, functions, objects, and the overall structure and interaction of your code so that the resulting functionality will satisfy your user's requirements. There are many different ways of designing software, almost all of which involve coming up with an initial design and refining it as necessary. Different developers prefer different amounts of design upfront or during the implementation phase. Generally, the overall design should be well thought out and reviewed before coding starts. Refer to our section on Design reviews to learn how to review your design. It is easier to try out different designs upfront and discover problems early in the development cycle than to make a major design change after much of the code has been written. Your software design should include a description of the overall architecture. This should include the hardware, databases, and third-party frameworks your software will use or interact with.…

Several models are used during software development, with the relative importance of each model depending on the nature of the program being created. Could you classify these models in accordance with your own tastes and experiences?