The waterfall model requires clients to commit to particular set of requirements before design begins and designer to commit to particular design strategies based on those set of requirements formally assigned to the system by the clients. If there is any change happens, they will have to go through the entire rework process again which is costly and takes more time.
Popular Posts
-
WHAT IS AN OPERATING SYSTEM? I think its hard to pin down what an operating system is other than saying it is the software that runs in ke...
-
Project specification: A comparator compares two n-bit inputs and generates three status signals. The input and output signals are inp...
-
What are the 4 levels at which software reuse is possible? Answer: 1. The abstraction level : At this level, you don’t reuse software direc...
-
Project specification: A dual-priority encoder returns the codes of the highest and second-highest priority requests. The input is the 10-...
-
What are the strategic options for legacy system evolution? Answer: There are four strategic options: 1. Scrap the system completely: Th...
-
The 4 sectors in each loop in Boehmʼs spiral model are: 1. Objective setting: Specific objectives for that phase of the project are define... -
What are the advantages of inspections over testing? Answer: 1. During testing, errors can mask other errors. When an error leads to unexp...
-
Using Thunderbird Turn Signal digital circuit lab, you can learn how the logic of finite state machine is implemented in real life embedde... -
What are the advantages of explicitly designing and documenting software architecture? Answer: 1. Stakeholder communication: The architectu...
-
Give 5 reasons why eliciting requirements is difficult? Ans: (a) Stakeholders often do not know exactly what kind of system/services they wa...
-
Subscribe To
Posts
Comments
0 comments:
Post a Comment