Skip to content
- What development model would be the best from the side of the development team and from the side of the customer?
- When support for systems designed with waterfall models do end, how easy will it be to replace them?
- It is hard to objectively test the things you make. How do you trust the developers in a company with software validation?
- The textbook mentions that most software development processes are a combination of waterfall, incremental and integration. How did the textbook end up categorizing the three models if they are never used in their “pure” form?
- The software implementation and validation under the incremental and integration approaches.
- What is the difference between software verification and software validation?
- Why is it so expensive to create software?
- Analysis paralysis describes an individual or group process when overanalyzing or overthinking a situation can cause a stall in the project. Recognizing that there is no one-size-fits-all process model for all software projects, and that there is hardly a perfect model, how does one decide when a model is “good enough”? What is the cutoff point?
- Software validation can easily take a long time and cost a lot, placing a burden on the developing team. How does a developing team anticipate and alleviate this potential problem?
- Why is it necessary to repeat requirements engineering during implementation of the
- integration and configuration model?
- How deliverable do versions of a software have to be during incremental development in terms
- of U.I. and documentation?
- What are some examples of when the waterfall method should and should not be used?
- How does the “software platform” fit into the models of software development?
- If the team working on the project is small, but the definitions cannot be flexible due to the nature of the project, will the waterfall model still be very applicable?
- What are some of the problems of a reuse oriented approach based on reusable software components?
- On October 4, 2021, at 15:39 UTC, the social network Facebook and its subsidiaries, Messenger, Instagram, WhatsApp, Mapillary, and Oculus, became globally unavailable for a period of six to seven hours. As a student of Software and System Design Course, discuss what mistakes might have led to this kind of issue and what lessons can be learned from it. Create a discussion scenario that happens at Meta’s (formerly Facebook) headquarter.
- What are the common design activities and what are each of theirs’ functions?
- Describe the software evolution and its software’s lifecycle.
- What exactly would a program specification look like? Can we find examples and show how they differ from each other?
- To me it seems like the waterfall method is a bit much planning. Can we find specific programs where we think waterfall method was or should have been used?
What kind of programs or software are inflexible or not maintainable? What makes these programs/software inflexible? Are programs made with some languages more inflexible compared to others? - How do the integration & configuration and incremental development models differ from one another? Isn’t one just a version of the other?
- Is the integration and configuration model the only model that uses software/code reuse for a project? What about the waterfall and incremental development models? Do they also include reusing pre-written codes to some extent or how do they operate otherwise?
- For a messaging app, say Whatsapp, you need customer feedback to improve your products in the coming years but you also need to pay extra attention to the safety and security of customers, the requirements of the users, implementation and unit testing etc., which is a plan-driven process. In such scenarios, how is the software process model ultimately decided and what factors affect the decision? (In this case, you could be stuck in choosing one between Waterfall and Incremental).
- What does documents mean in software designing terminologies? Why would iterations of a stage in the waterfall model be made so costly by the reproduction of just paper documents (if that is the definition of product documents in software engineering)?
- How can feasibility study be conducted on a program idea before its requirements are elicited and analyzed? Could you give an example of software specification activity? Especially the feasibility testing part.
- Which software development model is most relevant to our community projects and what have you used most frequently in your prior programming work?
- What are the strengths and weaknesses of each software development model?