הנדסת תוכנה - מעודכן
- 23 שאלות
- -- תגובות
- 0% הושלמו
- equalizer סטטיסטיקות
- share שתף
מנהלים:
Discuss, Learn and be Happy דיון בשאלות
help
brightness_4
brightness_7
format_textdirection_r_to_l
format_textdirection_l_to_r
Use case diagrams give a fairly simple overview of an interaction, so you have to provide more details to understand what is involved. Below is the list of relevant/irrelevant documents that include required details. 1. Simple textual description. 2. Architectural design. 3. Sequence diagram. 4. Metrics (מדדים/שיטות)for specifying non-functional requirements. 5. Structured description in a table.
1
| done | ||
מיין לפי
Consider the advantages of the incremental development model. Below is the list of correct/incorrect items. 1. The cost of accommodating changing customer requirements is reduced. 2. The progress is not visible. 3. It is easier to get customer feedback on the development work that has been done. 4. More rapid delivery and deployment of useful software to the customer possible. 5. System structure tends to degrade as new increments are added.
1
| sentiment_very_satisfied | ||
מיין לפי
Below is the list of correct/incorrect examples of software process activities that help predict changes and/or make the software being developed more resilient to change. 1. Regression testing. 2. Requirements traceability (שניתן לעקוב אחריהן) that shows dependencies between requirements and between the requirements and the design/code of the system. 3. Design modeling where the design model documents the structure of the software. 4. Code refactoring that improve code quality and so makes it more amenable to change.
1
| done |
מיין לפי