Principle I. The primary goal of the software team is to build soft- ware, not c

Question

Principle I. The primary goal of the software team is to build soft- ware, not create models. Agility means getting software to the customer in the fastest possible time. Models that make this happen are worth creating. but models that slow the process down or provide little new insight should be avoided. Principle 2. Travel light-don't create more models than you need. Every model that is created must be kept up-to-date as changes occur. More importantly, every new model takes time that might otherwise be spent on construction (coding and testing). Therefore, create only those models that make It easier and faster to construct the software. Principle 3. Strive to produce the simplest model that will describe the problem or the software. Don't overbuild the software [Amb02b|. By keeping models simple, the resultant software will also be simple. The result is software that is easier to integrate, easier to test, and easier to maintain (to change). In addition, simple models are easier for members of the software team to understand and critique, resulting In an ongoing form of feedback that optimizes the end result. Principle 4. Build models in a way that makes them amenable to change. Assume that your models will change, but in making this assumption don't get sloppy. For example, since requirements will change, there Is a tendency to give requirements models short shrift. Why? Because you know that they'll change anyway The problem with this attitude is that without a reasonably complete requirements model, you'll create a design (design model) that will invariably miss important functions and features. Principle 5. Be able to state an explicit purpose for each model that is created. Every time you create a model, ask yourself why you're doing so. if you can't provide solid justification for the existence of the model, don't spend time on it.

Explanation / Answer

--> principal 1 : during the software engineering process, modeling is an important aspect, but when considering the time constraint, if you understand the software well, and if u can make the customers understand the software, you should not spend much time on the modeling process, and concentrate more in coding and testing , which takes up most of the development life along with maintenance. --> principal 2 : know what is required and directly hit the point, dont waste time in stating new rules. --> principal 3 : rather than spending time on a big model, try to think out a method of simplifying the model.Same as in principal 2 your model should hit the software directly. It should be a straight forward solution to the question. --> principal 4 : with time, you will generally understand to software better, leave a scope in the model so that u can change at will, as you keep moving forward in coding and testing stages, where you feel u need to make some changes in model. --> principal 5 : though you understand your model , there is no guarantee the customer will understand, stating the purpose will help him realize your point of view of the model, so that their would be better understanding between you and the customer.

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.