Lec_02 - Click to edit Master subtitle style ECOM 6339...

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

View Full Document Right Arrow Icon
Click to edit Master subtitle style 27/02/2011 Lec 02 ECOM 6339 Software Modeling Lec 02 ______________________ Hatem M. Hamad Computer Engineering Department Islamic University of Gaza __________________________________________________ ___________
Image of page 1

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 Outline Introduction to Design process Software Design Terminology Design Elements Design Attributes Structured Design 22
Image of page 2
27/02/2011 Lec 02 Design process 1980s: OO design: added inheritance, multiple inheritance, and polymorphism to ADT. In process added complexity and increased some types of connectivity. Lots of claimed advantages -- so far empirical evaluation is not supporting them well. 1990s: Architecture, Patterns, Frameworks, etc. 33
Image of page 3

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 Software Design Principles 44 Design is a creative, problem-solving activity. - No recipe for doing it - always need some type of "magic". -Quality and expertise of designers is determinant for success. An expert has large knowledge of domain at hand. - Solving a problem involves mapping into knowledge available. - The larger this knowledge and the more accessible, the more successful the process will be.
Image of page 4
27/02/2011 Lec 02 55 Software Design Principles (2)
Image of page 5

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 66
Image of page 6
27/02/2011 Lec 02 77
Image of page 7

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 Boundary between Requirements & Design • Black Box Requirements Methods – Distinct split between Requirements and Design • Software Analysis methods – Problem-oriented perspective – Define problem-oriented components (functions, objects) & interfaces • Most software design methods – Have analysis phase • Decisions made in Analysis – Have major impact on Design • Scope of component • How it interfaces to other components • Problem-Oriented Analysis – Considered part of Design Process – Usually first phase of design 88
Image of page 8
27/02/2011 Lec 02 What is design? Design is the process of deciding how to satisfy a program’s requirements Four essential elements Client Focus Organizing Principles Structure Performance 99
Image of page 9

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 Design Elements: Client Focus A designer’s first responsibility is to the user of the program This should be the primary concern during the initial stages of design Important Aspects: Minimizing amount of information user supplies Program flexibility Need enough to satisfy user’s needs Informing the user about program inputs Informing the user about progress Helping the user understand what the program is doing Helping the user interpret the program’s results User refers to human or another software component 1010
Image of page 10
27/02/2011 Lec 02 Design Elements: Organizing Principles Organizing principles are the main design ideas on which the program’s implementation is based Developing organizing principles is the most creative part of design You have a good set of organizing principles when you are sure you could implement the program even though not all implementation problems have not been solved 1111
Image of page 11

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

View Full Document Right Arrow Icon
27/02/2011 Lec 02 Design Elements: Structure Structure is the physical way that code is formed for implementation Design issues: How should the system be divided into parts?
Image of page 12
Image of page 13
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