MVC Architecture for a Personal Financial Management Application: 25-Comp-B11 Advanced Software Design, December 2019, Q18

Question 18 of 28: MVC Architecture for a Personal Financial Management Application

Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)

Notes on this paper

17-Comp-B11 Advanced Software Design — National Exams, December 2019. 3 hours, closed book exam with one aid sheet allowed (written on both sides), no calculator permitted. The paper is organized into five parts, and candidates were instructed to answer any five (5) questions in Part I, any three (3) in Part II, any four (4) in Part III, any two (2) in Part IV, and any five (5) in Part V — only the first questions answered, in each part, as they appear in the answer book are marked. All questions carry equal weight, so the 19 questions actually marked (5+3+4+2+5 of 28) each count for 100/19 ≈ 5.26% of the paper. All 28 questions are answered below for completeness.

Reference texts: Sommerville, Software Engineering (10th ed., Pearson) — software processes, requirements engineering, design principles, testing, dependability; Pressman, Software Engineering: A Practitioner's Approach (9th ed.) — supplementary process and quality coverage; Gamma, Helm, Johnson & Vlissides (GoF), Design Patterns: Elements of Reusable Object-Oriented Software — creational/structural/behavioural pattern catalogue and the "program to an interface, not an implementation" / "favor object composition over class inheritance" principles; Sebesta, Concepts of Programming Languages (12th ed.) — polymorphism, dynamic binding, visibility, and multiple inheritance semantics; Bertrand Meyer, Object-Oriented Software Construction — design by contract, preconditions/postconditions/class invariants; Barbara Liskov's 1987 substitutability paper for Question 12; Karl Wiegers, Software Requirements (3rd ed.); Myers, The Art of Software Testing, for Question 6.

PART I — General Principles (answer any 5 of 7)

PART IV — GUI Design (answer any 2 of 4)

Question 18: MVC Architecture for a Personal Financial Management Application (Part IV)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

FinanceModel holds transaction data and business logic; TransactionView displays it and forwards user actions to FinanceController; FinanceController updates the Model, which in turn notifies the View.

Extensibility — HELPS. Because FinanceModel has no dependency on any specific view technology, a new view (e.g. a mobile UI or a plain-text report view) can be added by writing a new View class that observes the same Model, with zero change to the business logic. A new Controller can likewise be added to support a new input mechanism (e.g. voice command) without touching the Model.

Response time — may HURT (slightly). The extra indirection — the Controller mediating user actions into Model updates, and the Model notifying the View rather than the View reading data directly — adds a small amount of call/notification overhead compared to a single monolithic class handling everything inline. For a desktop-scale personal finance application this overhead is negligible; it would only matter in a genuinely latency-critical rendering loop, which this application is not.

Modifiability — HELPS. Because presentation (View) and business logic (Model) are separated, redesigning the transaction list's visual layout requires changing only TransactionView, and changing the balance-calculation rule requires changing only FinanceModel — each kind of change is confined to the layer responsible for it, rather than requiring a change to be threaded through a single undivided class.

Concept & Theory: Separation of Concerns Trades a Little Overhead for a Lot of Flexibility

Topic: MVC's help/hurt profile follows directly from where it adds indirection.

Key relations: Decoupling Model from View → helps extensibility and modifiability; the notification/mediation machinery itself → small response-time cost.

Why this works: The SAME separation that enables adding/changing a layer independently is also the source of the small extra indirection cost — they are not independent trade-offs, they are the same mechanism viewed from two angles.

Common pitfall: Assuming MVC always improves EVERY quality attribute — it specifically trades a (usually negligible) amount of runtime overhead for design-time flexibility.

Source: Sommerville, Software Engineering, ch. "Architectural Design," MVC pattern.