1. If software does not wear out, why does it deteriorate (1.4) 2. Is software engineering applicable when web applications are built? If so how it can be modified to accommodate unique characteristics of web apps. (1.7) 3. Develop a software failure scenario (Dooms Day) which could do great harm to humans. (1.8) 4. Describe a process framework in your own words. Is framework activities is applied to all projects regardless of size and complexity? (1.9) 5. Do Umbrella activities occur evenly across all processes or some concentrated in one or more frame work activities. (1.10)
1. Provide three examples of Software projects that would be amenable to the waterfall model. Be specific. 2. Is there ever a case when the generic activities of the software engineering process do not apply? If so, describe it. 3. Is it possible to combine process models? If so, provide an example. 4. Discuss the meaning of “crosscutting concerns” in your own words as the phrase applies to aspect-oriented programming (AOP). 5. What is the difference between a Unified Process (UP) phase and UP workflow?
1. Describe agility (for software projects) in your own words. 2. Try to come up with one more “agile principle” that would help a software team become even more maneuverable. 3. Describe the XP concepts of refactoring and pair programming in your own words. 4. Using the FDD feature template (from section 3.5.5), define a feature set for an E-Mail client. Now develop a set of features for the feature set. 5. What activities are addressed during each iteration of the agile unified process?