SWE 3633 Lecture 8: L8 Software Architecture and design

• School: KSU
• Department: Software Engineering
• Course: SWE 3633
• Professor: Hassan Pournaghband

Document Summary

Elicit needs: answer questions, be subjects of empirical studies. Analyze needs: answer questions, review and validate models and documents, participate in analysis with designers. Generate/improve alternatives: participate in generation and improvement. Evaluate alternatives: answer questions, be subject of empirical studies, participate in evaluation with designers. Select alternatives: participate in selection with designers. Finalize design: review and validate requirements. Stakeholder needs and desires define the product design problem. Note: important technique to do interviews while recording responses. Better than having people explain their work. Several of the right people, several times. Prototype demonstrations prototype is a working model of part or all of a final product. Many kinds of models can represent the problem and help designers understand it. Many modeling notations and techniques are useful for analysis: Use case descriptions, user interface diagrams, dialog maps. Product design begins with design problem analysis. Stakeholders can play many roles in product design. Needs define the product design problem requirements state the solution.