Ch 2.1-2.2 Discussion Questions

  1. On p.36 of the textbook, it is mentioned that incremental development can be “either plan-driven, agile, or more usually, a mixture of both” In what ways can incremental development be purely plan based?

  2. On p.44 of the textbook, figure 2.6 is a diagram of the stages of testing. This diagram indicates that it is possible to go from component testing to customer testing without having to do system testing. When would it be appropriate to skip system testing?

  3. Software processes that use the waterfall model require a lot of documentation and thought before starting the project. Throughout the process of developing software, requirements are likely to change a number of times. Why is the waterfall method used instead of a process that allows for some documentation and less time spent formally analyzing and documenting each phase?

  4. The integration and configuration model of development relies on using pre-existing code. I know that a lot of code is open source and free to use and modify, but are there any situations where using someone else's code may get you in trouble?

  5. What will a requirements or design document look like for our class projects? Seeing an example document would be very helpful.

  6. What kind of access will be have to reusable components? I assume we will not be purchasing expensive 3rd-party configurable software, but, on the other end, students may bring in old code from previous projects (e.g. a word-search function). Where, approximately, is the line?

  7. For Customer Testing, how is that handled? Is it just released to a small pool of people (if so, how are they chosen), or is it an actual update to the public, that then just gets highly monitored?

  8. What are no-functional requirement? and why is it important for a system to meet them?

  9. Could you please elaborate on information systems design and the different ways one can deal with data and why we would choose one way over the other?

  10. When is it appropriate to release a new version or update for testing or use, what requirements must be met first?

  11. When working as one of many teams on a software system, what precautions can be taken to ensure that your design choices will be supported/compatible with other teams' code?

  12. I'd like to see a good real-life example of the design process. This is because these involve so many moving parts such architectural design, design outputs et cetera.

  13. Due to the comment regarding the lack of new systems now and how old ones are being recycled and used and improved upon, I was thinking that whether this implies that the incremental development and waterfall models are being somehow incorporated with the ideas of integration and configuration. I'd like to see how these models interact with one another.

  14. What exactly does user and system documentation entail? In what stage are these documentations compiled and what are they used for?

  15. What exactly can be reused in reuse-oriented models? Is it simply code reuse or also taking used ideas? What about issues with copyrights and free-riding?

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2018-01-19 - JimSkon
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback