Object-Oriented Modelling and Design: Coupling, Cohesion, and MVC
VerifiedAdded on 2023/01/18
|8
|1491
|37
Report
AI Summary
This report provides a comprehensive overview of object-oriented modeling and design (OOAD) principles. It begins by defining and explaining the concepts of coupling and cohesion, emphasizing their importance in effective software design. The report then critically evaluates cohesion and coupling within a class diagram, highlighting their strengths and weaknesses. Following this, the Model-View-Controller (MVC) pattern is determined and described, outlining its architectural design and the roles of the Model, View, and Controller components. The report concludes by demonstrating how to redesign the class diagram using the MVC pattern, showcasing how the pattern enhances the structure and functionality of the software design. References to relevant academic sources are included to support the analysis.

Object-Oriented
Modelling and Design
Modelling and Design
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser


Table of Contents
INTRODUCTION...........................................................................................................................1
1. Define and explain coupling and cohesion.............................................................................1
2. Critically evaluate cohesion as well as coupling for the class diagram..................................1
3. Determine as well as describe Model-View-Controller pattern .............................................2
4. Redesigning the class diagram with the help of MVC pattern................................................3
CONCLUSION ...............................................................................................................................4
REFERENCES................................................................................................................................5
INTRODUCTION...........................................................................................................................1
1. Define and explain coupling and cohesion.............................................................................1
2. Critically evaluate cohesion as well as coupling for the class diagram..................................1
3. Determine as well as describe Model-View-Controller pattern .............................................2
4. Redesigning the class diagram with the help of MVC pattern................................................3
CONCLUSION ...............................................................................................................................4
REFERENCES................................................................................................................................5
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

INTRODUCTION
Object-oriented development is the concept which is known through various inventers.
But these inventers outcomes from a broader process towards overall software development life
cycle which is known as the object oriented analysis as well as design (Dimitrakopoulos and
et.al., 2019). OOAD is defined as the techniques for analysing and designing applications as per
the system object model. The purpose of this report is to describe the object oriented modelling
and design key aspects and concepts within software development. Apart from this, cohesion and
coupling as well as MVC pattern are also discussed in this report.
1. Define and explain coupling and cohesion
Coupling is utilised for qualifying the comparative dependencies among classes as class
have a connection to other class. This is also ascertained at the arrangement design stages as well
as depends upon class interface complication. Thus, it is the degree to which class is related with
another one into arrangements (Farzaneh, Monfet and Forgues, 2019). Where as Cohesion is
considered as the qualities strong point within class, it refers how characteristics are interacted
into class. In case coupling is always related with consolidation as well as compliance that is
higher, the alliance is less as well as vice versa.
Cohesion provides a stronger points that is relation among class characteristics as well as
is concept where module totally captures the interior. Thus, it is utilised fro governing how class
internal characteristics is adjusted. This provides designers an idea of either a diverse class fit
qualities is similar to same.
2. Critically evaluate cohesion as well as coupling for the class diagram
Effective software design golden rule is lower coupling as well as higher cohesion,
respective do not has to be very much dependable. The class among them as well as business and
procedures of classes are to be utilised as particular as it can and obviate multiple task for them.
Thus, within this work is explained an development of class diagram.
1
Object-oriented development is the concept which is known through various inventers.
But these inventers outcomes from a broader process towards overall software development life
cycle which is known as the object oriented analysis as well as design (Dimitrakopoulos and
et.al., 2019). OOAD is defined as the techniques for analysing and designing applications as per
the system object model. The purpose of this report is to describe the object oriented modelling
and design key aspects and concepts within software development. Apart from this, cohesion and
coupling as well as MVC pattern are also discussed in this report.
1. Define and explain coupling and cohesion
Coupling is utilised for qualifying the comparative dependencies among classes as class
have a connection to other class. This is also ascertained at the arrangement design stages as well
as depends upon class interface complication. Thus, it is the degree to which class is related with
another one into arrangements (Farzaneh, Monfet and Forgues, 2019). Where as Cohesion is
considered as the qualities strong point within class, it refers how characteristics are interacted
into class. In case coupling is always related with consolidation as well as compliance that is
higher, the alliance is less as well as vice versa.
Cohesion provides a stronger points that is relation among class characteristics as well as
is concept where module totally captures the interior. Thus, it is utilised fro governing how class
internal characteristics is adjusted. This provides designers an idea of either a diverse class fit
qualities is similar to same.
2. Critically evaluate cohesion as well as coupling for the class diagram
Effective software design golden rule is lower coupling as well as higher cohesion,
respective do not has to be very much dependable. The class among them as well as business and
procedures of classes are to be utilised as particular as it can and obviate multiple task for them.
Thus, within this work is explained an development of class diagram.
1
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Initially, we evaluate the current design of above diagram as well as ascertain the strengths. As
an outcomes we utilised object-oriented inheritance principles such as particular admin, teacher
and students inherit behaviours as well as procedures from user base class as well as high class is
explained here as particular business have been added to several classes for effective designs.
3. Determine as well as describe Model-View-Controller pattern
Model view Controller is defined as an architectural design which is generally utilised
into representation of web based. This includes 3 keys levels that are views, models as well a
controller (Fu and et.al ., 2019). The practices of various designers MVC is considered as the
standard design pattern. It is an encompassing outline. MVC facilitates 3 class that are discussed
below:
Model: This level is utilised for applying the data filed judgement. These level are usages
for recovering, adding or updating information related with the record associated with
them.
View: The view level is utilised for formulating its presentation edge. Utilising this
intervention, clients may perform with its presentation.
2
an outcomes we utilised object-oriented inheritance principles such as particular admin, teacher
and students inherit behaviours as well as procedures from user base class as well as high class is
explained here as particular business have been added to several classes for effective designs.
3. Determine as well as describe Model-View-Controller pattern
Model view Controller is defined as an architectural design which is generally utilised
into representation of web based. This includes 3 keys levels that are views, models as well a
controller (Fu and et.al ., 2019). The practices of various designers MVC is considered as the
standard design pattern. It is an encompassing outline. MVC facilitates 3 class that are discussed
below:
Model: This level is utilised for applying the data filed judgement. These level are usages
for recovering, adding or updating information related with the record associated with
them.
View: The view level is utilised for formulating its presentation edge. Utilising this
intervention, clients may perform with its presentation.
2

Controller: This is the class which is utilised for answering the users requests. The
controller class works the practices requested through customers. These level usages the
typical classes as well as prefer the appropriate interpretation that have to be represented
to clients with the request of user's.
MVC mode style is crucially a 3 tier architecture. This divides application properties.
Moreover, the fundamental level is associated with logic inputs of user, another level is related
with judgement of business as well as last level is utilised for applying user interface logic. The
MVC facilitates a very bad connection among all these 3 levels. Moreover, the mode of MVC is
applied for determining every judgement positions within presentation. Also, it render
functionality for parallel development (Ozturk and Aydin, 2019). It considered that all the
presentation level is liberates from one another which is the three developers may at the same
time manage an individual application. One developer concentrates upon the user input logic,
another concentrates upon judgement edge as well as third developed perform a business logic at
similar time.
4. Redesigning the class diagram with the help of MVC pattern.
The diagram of last class utilises the principles of object oriented but do not obey a
particular pattern, being hybrid of various design patterns (Randall and et.al., 2019). Herein,
MVC pattern three layers plays crucial role that are discussed below:
Model is appropriately explained upon diagram right side as well as open up of 3 main
classes that are reservation model, room model and user model. Some characteristics are
undertaken from previous design. Moreover, they finds that class diagram model part is
accountable for undertaking information as well as likewise into Usermodel has few logic
procedures for updating controller in case data is altered.
View is find into left side of class diagram as well as comprises of 3 aspects that are
reservation view, room view as well as user view. As per the......, this represents
information visualisation that is controlled through model, likewise upon its class
diagram we develop view classes for serving as interface of user for information
accumulated form model.
Controller considered as the glue among model and view, controlling data movement
into model as well as upgrading view at the time new modification are done upon
3
controller class works the practices requested through customers. These level usages the
typical classes as well as prefer the appropriate interpretation that have to be represented
to clients with the request of user's.
MVC mode style is crucially a 3 tier architecture. This divides application properties.
Moreover, the fundamental level is associated with logic inputs of user, another level is related
with judgement of business as well as last level is utilised for applying user interface logic. The
MVC facilitates a very bad connection among all these 3 levels. Moreover, the mode of MVC is
applied for determining every judgement positions within presentation. Also, it render
functionality for parallel development (Ozturk and Aydin, 2019). It considered that all the
presentation level is liberates from one another which is the three developers may at the same
time manage an individual application. One developer concentrates upon the user input logic,
another concentrates upon judgement edge as well as third developed perform a business logic at
similar time.
4. Redesigning the class diagram with the help of MVC pattern.
The diagram of last class utilises the principles of object oriented but do not obey a
particular pattern, being hybrid of various design patterns (Randall and et.al., 2019). Herein,
MVC pattern three layers plays crucial role that are discussed below:
Model is appropriately explained upon diagram right side as well as open up of 3 main
classes that are reservation model, room model and user model. Some characteristics are
undertaken from previous design. Moreover, they finds that class diagram model part is
accountable for undertaking information as well as likewise into Usermodel has few logic
procedures for updating controller in case data is altered.
View is find into left side of class diagram as well as comprises of 3 aspects that are
reservation view, room view as well as user view. As per the......, this represents
information visualisation that is controlled through model, likewise upon its class
diagram we develop view classes for serving as interface of user for information
accumulated form model.
Controller considered as the glue among model and view, controlling data movement
into model as well as upgrading view at the time new modification are done upon
3
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

programmes (Rauzy and Haskins, 2019). layer of controller upon mid of class diagram
that are user, reservation and room controller.
CONCLUSION
As per the above report, it has been concluded that object oriented design procedures is
actually a expansion of last analysis process of this, except for one key warning that is evaluation
as well as execution of constraints. In another term, procedures of object- oriented design usages
the theoretical ideas which is planned into the attributes phases of object-oriented as well as also
try to identify a path for planning as well as that through utilising codes which utilises any
platform and languages that is defined through development team.
4
that are user, reservation and room controller.
CONCLUSION
As per the above report, it has been concluded that object oriented design procedures is
actually a expansion of last analysis process of this, except for one key warning that is evaluation
as well as execution of constraints. In another term, procedures of object- oriented design usages
the theoretical ideas which is planned into the attributes phases of object-oriented as well as also
try to identify a path for planning as well as that through utilising codes which utilises any
platform and languages that is defined through development team.
4
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

REFERENCES
Books and Journals
Dimitrakopoulos, G. and et.al ., 2019. Α capability-oriented modelling and simulation approach
for autonomous vehicle management. Simulation Modelling Practice and Theory. 91.
pp.28-47.
Farzaneh, A., Monfet, D. and Forgues, D., 2019. Review of using Building Information
Modeling for building energy modeling during the design process. Journal of Building
Engineering.
Fu, Y. and et.al ., 2019. Equation-based object-oriented modeling and simulation for data center
cooling: A case study. Energy and Buildings. 186. pp.108-125.
Ozturk, A. and Aydin, G., 2019. A Tactical Simulation in Simulink with Object Oriented Design
Approach. In AIAA Scitech 2019 Forum (p. 1478).
Randall, M. and et.al ., 2019. Geographic Object Based Image Analysis of WorldView-3
Imagery for Urban Hydrologic Modelling at the Catchment Scale. Water. 11(6).
p.1133.
Rauzy, A.B. and Haskins, C., 2019. Foundations for model‐based systems engineering and
model‐based safety assessment. Systems Engineering. 22(2). pp.146-155.
Rohrer, E., Severi, P. and Motz, R., 2019, June. Meta-Modelling Ontology Design Pattern.
In Iberoamerican Knowledge Graphs and Semantic Web Conference (pp. 102-117).
Springer, Cham.
Saralioğlu, M.Ö. and et.al ., ., 2019. Data model design for qualified natural-protected area in
Turkey. Survey review. 51(365). pp.154-165.
Schewe, K.D. and Thalheim, B., 2019. The Co-Design Framework. In Design and Development
of Web Information Systems (pp. 3-30). Springer, Berlin, Heidelberg.
Tagg, R. and Mabon, J., 2019. Object Management. Routledge.
5
Books and Journals
Dimitrakopoulos, G. and et.al ., 2019. Α capability-oriented modelling and simulation approach
for autonomous vehicle management. Simulation Modelling Practice and Theory. 91.
pp.28-47.
Farzaneh, A., Monfet, D. and Forgues, D., 2019. Review of using Building Information
Modeling for building energy modeling during the design process. Journal of Building
Engineering.
Fu, Y. and et.al ., 2019. Equation-based object-oriented modeling and simulation for data center
cooling: A case study. Energy and Buildings. 186. pp.108-125.
Ozturk, A. and Aydin, G., 2019. A Tactical Simulation in Simulink with Object Oriented Design
Approach. In AIAA Scitech 2019 Forum (p. 1478).
Randall, M. and et.al ., 2019. Geographic Object Based Image Analysis of WorldView-3
Imagery for Urban Hydrologic Modelling at the Catchment Scale. Water. 11(6).
p.1133.
Rauzy, A.B. and Haskins, C., 2019. Foundations for model‐based systems engineering and
model‐based safety assessment. Systems Engineering. 22(2). pp.146-155.
Rohrer, E., Severi, P. and Motz, R., 2019, June. Meta-Modelling Ontology Design Pattern.
In Iberoamerican Knowledge Graphs and Semantic Web Conference (pp. 102-117).
Springer, Cham.
Saralioğlu, M.Ö. and et.al ., ., 2019. Data model design for qualified natural-protected area in
Turkey. Survey review. 51(365). pp.154-165.
Schewe, K.D. and Thalheim, B., 2019. The Co-Design Framework. In Design and Development
of Web Information Systems (pp. 3-30). Springer, Berlin, Heidelberg.
Tagg, R. and Mabon, J., 2019. Object Management. Routledge.
5
1 out of 8
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.