Analysis of the Usefulness of Modeling in Software Development

This report investigates the usefulness of modeling in software development, focusing on the challenges and benefits of using UML and use case diagrams. The report begins with an introduction to system modeling and the limitations of using UML diagrams, such as the time required for management, the need for synchronization with code, and the potential for developer confusion. A use case diagram for a checker game is presented as a practical example, highlighting the need for in-depth analysis before coding. The report also discusses the challenges of interpreting use case diagrams and the time investment required for software developers. Overall, the report provides a critical analysis of the modeling process, emphasizing the need for careful consideration and effective use of modeling tools in software development projects. The report concludes with a bibliography of relevant sources.

Running had: USEFULNESS OF MODELLING
Usefulness of Modelling
Name of the Student
Name of the University
Author’s Note

1
USEFULNESS OF MODELLING
Table of Contents
1. Proposal of system using the system modelling tool.......................................................2
2. Technical Description of the Proposed System...............................................................3
Bibliography........................................................................................................................4

2
USEFULNESS OF MODELLING
1. Proposal of system using the system modelling tool
The unified modeling tools are used for the development of an information system and it
helps in visualizing the specification and construction of the software intensive systems.
Emphasis is given on the flow of the data and graphics. There are several disadvantage faced by
the software development company for the development of the information system using the
UML modelling language (Lewis 2016). The software developers needs more time to manage
and maintain the UML diagrams and for utilizing the UML diagram in the software development
process it is required to be synchronized with the software code. It is unclear for the software
developers because the software developer have to code the program for the development of the
information system and the UML diagram does not provide any information about the code.
For the creation of the UML diagram for development of a software it become
complicated and thus the developer may get confuse to map the scenario using the development
tool. The software development team can spent more time in using the UML tool and designing
the software project and thus it can cause loss in focus in the development process (Yin 2013).
The diagram can be used by the software development team to analyze the problem associated
with the development of the system but it can cause unnecessary in the software development
and missing of deadline. There is no standard format maintained in the UML diagram and there
is limitation in the final result provided from the UML diagram. There are different UML
diagrams and the designer can use different diagram causing a difficulty for the software
developer to maintain a consistency in the development process.

3
USEFULNESS OF MODELLING
2. Technical Description of the Proposed System
Figure 1: Use Case Diagram for Checker Game
(Source: Created by Author)
The use case diagram is created for a checker game and it is required to be programmed
by the software developer but an in depth analysis is required to be made on the use case for
starting the programming. The software developer need to code the different module and it can
be complex for the development team to code the project following the use case diagram. The
software development team does not have a clear view of the requirement from the use case
diagram and thus they need to spend more time in analysis of the diagram and start the
development of the game.

4
USEFULNESS OF MODELLING
Bibliography
Kolodner, J., 2014. Case-based reasoning. Morgan Kaufmann.
Lewis, W.E., 2016. Software testing and continuous quality improvement. CRC press.
Little, R.J. and Rubin, D.B., 2014. Statistical analysis with missing data. John Wiley & Sons.
Yin, R.K., 2013. Case study research: Design and methods. Sage publications.