2 Software Design Principles & Methods.ppt

2 Software Design Principles & Methods.ppt - Software...

Info icon This preview shows pages 1–16. Sign up to view the full content.

View Full Document Right Arrow Icon
Main issues: decompose system into parts many attempts to measure the results design as product design as process Software Design Modeling
Image of page 1

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

View Full Document Right Arrow Icon
Overview Polytechnic of Engineering: Software Engineering ©2009 2 Introduction Design principles Design methods Conclusion
Image of page 2
Programmer’s Approach to Software Engineering Polytechnic of Engineering: Software Engineering ©2009 3 Skip requirements engineering and design phases; start writing code
Image of page 3

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

View Full Document Right Arrow Icon
Point to ponder Polytechnic of Engineering: Software Engineering ©2009 4 Is this the same as eXtreme Programming? Or is there something additional in XP?
Image of page 4
Why this programmer’s approach? Polytechnic of Engineering: Software Engineering ©2009 5 Design is a waste of time We need to show something to the customer real quick We are judged by the amount of LOC/month We expect or know that the schedule is too tight
Image of page 5

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

View Full Document Right Arrow Icon
However, ... Polytechnic of Engineering: Software Engineering ©2009 6 The longer you postpone coding, the sooner you’ll be finished
Image of page 6
Up front remarks Polytechnic of Engineering: Software Engineering ©2009 7 Design is a trial-and-error process The process is not the same as the outcome of that process There is an interaction between requirements engineering, architecting, and design
Image of page 7

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

View Full Document Right Arrow Icon
Software design as a “wicked” problem Polytechnic of Engineering: Software Engineering ©2009 8 There is no definite formulation There is no stopping rule Solutions are not simply true or false Every wicked problem is a symptom of another problem
Image of page 8
Overview Polytechnic of Engineering: Software Engineering ©2009 9 Introduction Design Goals Design principles Design methods Conclusion
Image of page 9

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

View Full Document Right Arrow Icon
List of Design Goals Polytechnic of Engineering: Software Engineering ©2009 10 Reliability Modifiability Maintainability Understandability Adaptability Reusability Efficiency Portability Traceability of requirementsFault tolerance Backward-compatibility Cost-effectiveness Robustness High-performance Good documentation User-friendliness Well-defined interfaces Rapid development Reuse of components Minimum # of errors Readability Ease of learning Ease of use Low-cost Flexibility
Image of page 10
Relationship between Design Goals Polytechnic of Engineering: Software Engineering ©2009 11
Image of page 11

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

View Full Document Right Arrow Icon
Typical Design Trade-offs Polytechnic of Engineering: Software Engineering ©2009 12 ♦ Functionality vs. Usability ♦ Cost vs. Robustness ♦ Efficiency vs. Portability ♦ Rapid development vs. Functionality ♦ Cost vs. Reusability ♦ Backward Compatibility vs. Readability
Image of page 12
Overview Polytechnic of Engineering: Software Engineering ©2009 13 Introduction Design Goals Design principles Design methods Conclusion
Image of page 13

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

View Full Document Right Arrow Icon
Design principles Polytechnic of Engineering: Software Engineering ©2009 14 Decomposition, Abstraction Modularity, coupling and cohesion Information hiding Limit complexity Hierarchical structure
Image of page 14
Decomposition Polytechnic of Engineering: Software Engineering ©2009 15
Image of page 15

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

View Full Document Right Arrow Icon
Image of page 16
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern