Other

CSE 591 Unit 2 Notes

0 purchase

Course
CSE 591

Institution
Arizona State University

Module 2 Summary ## Overview ### Software Design - Describe the contents of a software design - Explain the enabling techniques (common principles) for design - Explain common design viewpoints - Identify different architectural styles and the types of applications they are appropriate for ...

[Show more]

Preview 2 out of 10 pages

View example

Uploaded on June 19, 2024
Number of pages 10
Written in 2023/2024
Type Other
Person Unknown

tinahmasterall Member since 3 year 11 documents sold

$5.99

Add to cart

Add to wishlist

100% satisfaction guarantee
Immediately available after payment
Both online and in PDF
No strings attached

# Module 2 Summary

## Overview

### Software Design

- Describe the contents of a software design
- Explain the enabling techniques (common principles) for design
- Explain common design viewpoints
- Identify different architectural styles and the types of applications
they are appropriate for
- Understand what a software design pattern is and explain the use of the
device, and publish/subscribe patterns
- Describe how to evaluate the quality of a design
- Understand how to perform a design review
- Create uml class, sequence and state diagrams

### Software Construction

- Explain issues in reusing software
- Understand factors that affect software reusability
- Explain the need for software configuration management (SCM)
- Describe the 4 SCM activities
- Describe capabilities of SCM tools
- Define software configuration terminology (CCB, build, release,
configuration item, version)
- Identify benefits of utilizing open source software
- Identify factors to consider in selecting open source components

------

## Software Design

### Lecture 1

In the big picture, we start with system requirements, then system
design, then software requirements, and then software design.

Another term we hear a lot is "software architecture" and "software
architects."

- Create plans/blueprints
- How to solve the customer's requirements and find a way to
conceptualize that that can be implemented by a software engineer

How do you train a (building) architect? What do you teach them?

- _Patterns!_
- Business/economics (understand cost, economics, etc.)
- Constraints (laws, regulations, etc.)
- Quality attributes

_Software architecture_: the structure which comprises the software
elements, externally visible properties of those elements, and the

, relationships among them.

- Software elements: modules, components, entire programs, systems,
services (viewed as "black boxes")

**Architecture Importance**

- Critical to quality of the system (and its assessment)
- Errors are costly (if we create architectural errors, they are very
costly to eventually fix)
- Changes (assess impact of making changes)
- Communication vehicle (stakeholders, development team, integration-test
team, management and customers supporting ideas of estimation, schedule,
cost, and tracking)

**History**

- 1970's: Top-down design; attempt to solve a problem by breaking it into
functions, then subfunctions, etc.; problem decomposition
- 1980's: Data-flow design; in additional to a functional decomp, we were
also taking into account information flow; if we could understand those
flows, maybe we could better optimize those flows
- 1990's: Object-oriented design
- 2000's: services; service-oriented architecture

**Design Principles**

- Iterative: design is iterative; consider it along the lines of doing a
term paper right
- Objective for paper (persuasive? informative?)
- Outline
- Key points
- Key paragraphs
- (Drafting!)
- Finalize
- Traceability: important to trace design aspects to requirements; all
requirements need to be traced to elements of the design
- Reflect problem domain: if we're trying to solve a problem, we would
like to be able to have the design elements map to the problem
domain/system ("conceptual modeling")
- Maintainable
- Do *NOT* contain implementation details: abstract; provide flexibility
- Manage complexity: not to create the most complicated architecture;
keep it simple, stupid
- Minimize coupling (connections between components)
- Maximize cohesion (each elements are well-defined; code all fits
together and works towards a common objective)
- Isolate areas likely to change

**Identify Design Goals**

Anyone who designs a product needs to start with the goals of that
product.

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller tinahmasterall. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for $5.99. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

69411 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 15 years now

Start selling

Other

CSE 591 Unit 2 Notes

Document information

Subjects

Written for

Seller

Reviews received

Content preview