VM Q paper solution 2017-18 SEM I.docx - Paper solution Subject Visual Modeling Submitted by Mr.P.B.Bhalerao Academic Year 2017 NOV\/DEC-Q.1 solve any

VM Q paper solution 2017-18 SEM I.docx - Paper solution...

This preview shows page 1 - 3 out of 15 pages.

Paper solution Subject : Visual Modeling Submitted by : Mr.P.B.Bhalerao Academic Year 2017 NOV/DEC --------------------------------------------------------------------------------------------------------------------- Q.1 solve any two a) Explain the principle of modeling Ans: First principle of modeling : The choice of what models to create has a profound influence on how a problem is attacked and how a solution is shaped. Choose your models well. The right models will highlight the most nasty development problems. Wrong models will mislead you, causing you to focus on irrelevant issues. Second principle of modeling : Every model may be expressed at different levels of precision. Sometimes, a quick and simple executable model of the user interface is exactly what you need. At other times, you have to get down to complex details such as cross-system interfaces or networking issues etc. In any case, the best kinds of models are those that let you choose your degree of detail, depending on who is viewing it. An analyst or an end user will want to focus on issues of what and a developer will want to focus on issues of how. Third principle of modeling : The best models are connected to reality. In software, the gap between the analysis model and the system’s design model must be less. Failing to bridge this gap causes the system to diverge over time. In object-oriented systems, it is possible to connect all the nearly independent views of a system into one whole. Fourth principle of modeling : No single model is sufficient. Every non-trivial system is best approached through a small set of nearly independent models. b) Explain complexity of software system Ans: A dying star on the verge of collapse, a child learning how to read, white blood cells rushing to attack a virus: these are but a few of the objects in the physical world that involve truly awesome complexity. Software may also involve elements of great complexity; however, the complexity we find here is of a fundamentally different kind. As Brooks points out, "Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. Much of the complexity that he must master is arbitrary complexity" [1]. We do realize that some software systems are not complex. These are the largely forgettable applications that are specified, constructed, maintained, and used by the same person, usually the amateur programmer or the professional developer working in isolation. This is not to say that all such systems are crude and inelegant, nor do we mean to belittle their creators. Such systems tend to have a very limited purpose and a very short life span. We can afford to throw them away and replace them with entirely new software rather than attempt to reuse them, repair them, or extend their functionality, Such applications are generally more tedious than difficult to develop; consequently, learning how to design them does not interest us.
Image of page 1
The distinguishing characteristic of industrial-strength software is that it is intensely difficult, if not impossible, for the individual developer to comprehend all the subtleties of its design.
Image of page 2
Image of page 3

You've reached the end of your free preview.

Want to read all 15 pages?

  • Spring '16
  • 213
  • Design pattern

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes