SElec-7 SoftwareArch (1)

SElec-7 SoftwareArch (1) - LECTURE 7: Software Architecture...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Ivan Marsic Rutgers University LECTURE 7: Software Architecture
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Topics Software Architecture Definition Architectural Styles Documenting Architecture: Views
Background image of page 2
3 Hierarchical Organization of Software System or product Subsystems/Modules Packages Classes/Objects Methods highest abstraction level lowest level Product line (or product family) Source code We know there are different views of abstraction in software …
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Software Architecture Definition Software Architecture = a set of  high-level  decisions  tha t de te rm ine  the  ke y e le m e nts   o f the  s ys te m -to -b e  a nd the ir re la tio ns hips Principal decisions made throughout the development and evolution of a software system made early and affect large parts of the system (“design philosophy”) — such decisions are hard to modify later S o ftwa re  Arc hite c ture  is   not  a  pha s e  o f de ve lo pm e nt Does not refer to a specific product of a particular phase of the development process (labeled “high-level design” or “product design”)
Background image of page 4
5 We Already Made Some Architectural  Decisions … Subsystem for device control Subsystem for administration Subsystem for remote data access On embedded computer On office desktop On tenant’s smartphone Saf e Home Access Syst em Decision on software-to- hardware mapping Decision on system decomposition
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Architectural Decisions —A matter of scope Product/system A scope Product B scope Product line scope Subsystem scope product or system architecture decisions product line architecture decisions Given the current level of system scope, a decision is  architectural ” if it can be made only by considering the present  scope I.e. could not be made from a more narrowly-scoped, local perspective Architectural decisions should focus on high impact, high priority areas
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 23

SElec-7 SoftwareArch (1) - LECTURE 7: Software Architecture...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online