ÍÃ×ÓÏÈÉú

Catalog description:

An in-depth look at software design. Study of software architecture, design patterns and software product lines. Designing for quality attributes such as performance, safety, security, reusability, reliability, etc. Measuring internal qualities and complexity of software designs. Evolution of designs. Basics of software evolution, reengineering, and reverse engineering.  Application of formal methods to specify and evaluate designs.

Prerequisite:

CSE 201 and CSE 202

Required topics (approximate weeks allocated):

• Architecture, Design, and Development Process (1)
• Quality Attributes (1)
• Software Architecture (2)
• Design Notations (1)
• Design Patterns (1)
• Software Product Lines (2)
• Detailed Design (1)
• Design Review and Design Evaluation (2)
• Formal Methods (2)
• Design Rationale (1)
• Reverse Engineering and Design Recovery (2)

Course Outcomes

• To be able to make the transition from requirements analysis to software design.
  • The student will be able to identify quality attributes relevant to a design based on the specified requirements
  • The student will be able to identify different views related to a software architecture
  • The student will be able to partition a system based on different views of the software architecture
• To be able to specify software designs
  • The student will be able to apply a wide variety of design patterns and architectural styles in designing a wide variety of software
  • The student will be able to apply domain analysis techniques to specify software product line architectures
  • The student will be able to use sound quality metrics (quality attributes) to identify design objectives
  • The student will be able to measure and assess designs to ensure the design objectives have been met
  • The student will be able to use design patterns to create designs when appropriate
• To be able to facilitate design maintenance and recovery
  • The student will be able to apply design rationale approaches to capture rationale and to assess or evaluate a design
  • The student will be able to use reverse engineering techniques to recover the design of software
  • The student will be able to evolve a software design to account for new or changed requirements
• To be able to apply formal methods to the design activity
  • The student will be able to use basic formal techniques to specify a design
  • The student will be able to use formal techniques to validate a design
• To be able to apply the use of tools for software design
  • The student will be able to use standard UML tools to specify software designs
  • The student will be able to use formal analysis tools such as model checkers to verify design properties
  • The student will be able to use design rationale tools to capture rationale