Question

System analysis and design

Why software is usually divided into modules? Name all specific principles of OOD suggested by “S.O.L.I.D Principles”.

Answer 1

a) why software is usually divided into modules? complex set Solution: Software is a very og programs which have its own issues, if we are not able to break it down into smaller modules / components. Development software as a whole is a very complex phenomenon, so software usually divided into modules. Motivations for Modular Puogeamming : of is a.) Development can be divided : Modular programming allows development to be divided by splitting down a puoguam puoguams. This enables developers to work simultaneously and minimizes time taken fore development into smaller (6) Eurous are to detecti It minimizes the risks easy of ending up with programming eurous and makes easy to spot evrou. This is because the enrous can be narrowed down to a specific function. CS Scanned with CamScanner

smaller sub- (C) Improves Manageability: Having a program besten into programs allows for easiere management The separate modules are easy to test , implement and design. codes: of A proguam module is capable which minimizes the (d) Allows re-use of being re-used in a proguem development of redundant codes. Collaboration : immers can with modular approach, progua: le:) collaborate and wouk on same application. Designing a progrem also becomes simpler because small teams can focus on individual parts of the code. CS Scanned with CamScanner

ood suggested by be Name all specific principles of SOLID Principles". SOLID Sol": is an acronym for first-five object oriented design Coon), principles by Robert C. Moetin also known / as Uncle Bob. These principles makes easy for a programmer to develop software that are easy to maintain and extend. S → Single - Mesponsibility principle Open-closed puinciple o → Liskou- substitution puinciple I Interface segregation puinciple 2 Dependency Inversion principle. 1) S ( Single Responsibility Principle). - 9t states that: A class should have one and only one reason to one change, meaning that a class should have only job. CS Scanned with CamScanner

) O (Open-Clowed Puinuple) gt states that. Objects ou entities should be open for extension, but closed for modification. 1 i) (Liskou substitution puinciple): It states that: Let q (x) be a properly provable type T about objects of x of Then q1y) should be provable for objects y of where s is a subtype of T. S type 10) I ( Interface seguegation principle): gt stades that A client should never be forced to implement an interface that it doesn't use ou clients should not be forced to depend on methods they do not use. uy s Adependency Inversion principle): 9+ states that Entities must depend on abstractions not on concretions. gt states that high level module must not depend on they should depend on low level module but - abstractions. CS Scanned with CamScanner