Q1- Discuss the term coupling in software design. In a good software design, why
ID: 3702313 • Letter: Q
Question
Q1- Discuss the term coupling in software design. In a good software design, why modules should have low coupling? Justify with your answer. ?
Q2- Draw the associations that are described by the following business rules. Include the multiplicities for each relationship.
(I)A patient must be assigned to only one doctor and a doctor can have one or many patients.
(II)An employee has one phone extension, and a unique phone extension is assigned to an employee.
(III) A movie theater plays at least one movie, and a movie can be shown at up to four other movie theaters around town.
(IV) A movie has either one star, two co-stars, or more than ten people starring together. A star must be in at least one movie?
Q3- An ATM allows us to access bank accounts through an automated software process by ATM card to withdrawal money, transferring money, balance enquiry and depositing money. Draw the sequence diagram step by step considering four objects Patron, ATM, Control and database for ATM process ?
Explanation / Answer
Answer 1) Coupling basically defines how closely two modules are connected to each other. Their dependency on each other is identified by the coupling. The larger the coupling, the larger a module is dependent on the other module for proper functioning.
In a good software design, the different modules should have low coupling as with the high coupling the dependency of one module over the other increases. If the other module is not available or having some issues, then it may affect the proper functioning of that dependednt module as well. Thus reducing the overall efficiency.
Therefore, in a good software design, there should be low coupling so that the modules can work properly independently.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.