[DOCUMENT TITLE]

[Document subtitle]

[DATE]
[COMPANY NAME]
[Company address]
Table of Contents
An Honest Assessment of Group Modelling Exercise...............................................................3

How hard and soft models can be used to complement each other to improve problem and
solution understanding...............................................................................................................4

Rich Picture............................................................................................................................5

Block Diagram.......................................................................................................................5

Context Diagram....................................................................................................................5

Activity Diagram....................................................................................................................5

Root Definition.......................................................................................................................6

Use Case Diagram..................................................................................................................6

Hierarchy Diagram.................................................................................................................7

1
Table of Figures

No table of figures entries found.

2
An Honest Assessment of Group Modelling Exercise
System Modelling is a method of software development that enables users to create
complicated applications using streamlined abstractions of pre-made parts. These pictorial
basic components demonstrate the business demand and potential technical solutions rather
than simply informing. It is the cornerstone of low-code development and serves as a conduit
for the collaboration of IT and business domain specialists in the creation of valuable
applications.

Mostly under, System Modelling decreases the need for human interaction in processes while
abstracting complexity. Rather than being interpreted into code, the model in projects using
model-driven development is executable at runtime. This makes it possible for System
Modelling to avoid typical operational and quality problems with code-centric initiatives.

Through this, I think following are the benefits of group modelling assessments and exercises
we have achieved; It increases the system's decomposition and modularization, which
facilitates the system's evolution and maintenance. It decreases the number of bugs in the
final code. It increases the development team's productivity. It increases the system's
understandability, which makes it easier for new team members to integrate. It improves the
overall productivity of the team.

Overall, we had learned a lot of new things and changes while modelling the system within
the team because the best benefit we could have been abstraction through group assessments.
New changes, and suggestions made us think that the other perspectives matter as well.

If we think about the disadvantages of the group assessments, was out of the scope thinking
and modelling of new features which are totally out of the box and may be irrelevant to some
extent. Due to the diversity of opinions, disputes frequently arise while people are working
together. We had trouble accepting advice from friends and believing what other people had
to say. Additionally, introvert people frequently encounter difficulties to explain their ideas in
a group context and may find it uncomfortable to collaborate with individuals that do not
regularly interact with. They might therefore come seen as being sluggish, which might lead
to confrontation.

We commonly stray from the subject when collaborating in groups, especially whenever the
task necessitates conversation. Some students might utilise the opportunity to chat, engage in
other activities, or simply unwind. The result is that teamwork becomes less beneficial and

3
productive.Collaborating with others might take a lot of time for a student.Meetings need to
be planned well outside of school hours and accommodate everyone's schedule.Due to their
already packed schedules, sixth-form students may find this particularly
challenging.Cooperative learning can be beneficial regardless of a student's socioeconomic
status or the length of time they spend in the same group.

In contrast, the advantages of this dynamic learning environment can only be observed when
it is carried out appropriately.The number of participants, the assignment of groups, and the
teacher's management of the groups all have an impact on learning, either positively or
negatively.

According to some research, knowledge sharing should only be used sparingly due to its
potential drawbacks, which allow for the completion of more complex tasks in groups while
simpler ones can be completed independently.

Specifically, there is also some unequal participation of the work which was also a main issue
in the task. We were unable to conclude with the task and it was quite hectic for us overall to
considerate who is doing which part and there was a lot of delay in completing a small
module even.

How hard and soft models can be used to complement each other to
improve problem and solution understanding
Through soft systems, a solution will be developed with input from all relevant groups of
people, which will guarantee that the human factor is included early on in the process. Hard
systems can be employed to maximize some parts of the solution within the context of this
review of soft systems.

Soft systems perspectives on the world are characterized by complicated, challenging, and
frequently enigmatic occurrences for which it is impossible to create clear goals and for
which development requires learning. Such systems exist within and among businesses where
complex, frequently ill-defined patterns of behavior are noticed, restricting the enterprise's
potential to progress. They are not just present in the social and political spheres.

The "hard" and "soft" methods approach models in different ways.A common assumption in
a "hard" approach is that a model accurately depicts a particular aspect of reality.It is

4
acknowledged that this model simplifies and abstracts reality. From this point of view, the
model's function must be thoroughly tested against a portion of something similar to the
reality being simulated in order to ensure that it is accurately representative. Soft techniques,
on the other hand, do not necessitate such presumptions. The idea behind these is that models
are made to help people think about their own points of view and talk to other people about
possible actions.

Rich Picture
We benefit from the rich picture because it allows us to investigate, acknowledge, and
identify a situation while also visually expressing it in order to construct a rough mental
model.A rich picture, a detailed description, makes conversation easier and results in a
comprehensive understanding that is shared by all parties.s

Block Diagram
Block diagram representation has the benefit of making it possible to assess the contribution
of each element to the system's overall performance. Block diagrams aid in the creation of
linkages within a system and help us better comprehend its functioning. The rectangular
components that make up this kind of diagram give it its moniker as a block diagram. They
are utilized to portray processes as well as to explain hardware and software systems.

Context Diagram
The context diagrams depict a system interaction with other actors (or external factors) with it
is intended to communicate. Understanding the context in which the system will operate may
be facilitated by system context diagrams. They are typically included in a requirement
specification and are utilized early on in a project to achieve consensus on those limits. A
context diagram depicts the entire system as if it were a single process.

Activity Diagram
In Activity Diagrams, we refer to the stages of a use case's execution and the system's control
flow. We model both sequential and concurrent activities with the help of activity diagrams.
As a result, we simply visualize workflows using an activity diagram. The flow state and the
order in which it occurs are highlighted in an activity diagram. We can demonstrate or
explain the steps that lead to a particular event by using an activity diagram.

By depicting the control flow from a starting point to an end point, an activity diagram
demonstrates the numerous decision routes that are accessible throughout the course of an

5
activity's execution. In business and process modeling, they are mostly used to represent the
dynamic parts of a system.

Root Definition
The Root Definition is a purpose statement that captures the essence of a certain situation
(system) of interest. In general, a collaborative effort produces a more thorough outcome. It is
crucial to note that the experience of the team or person impacts the caliber of the result.

The Root Definition can be utilized to gain a shared understanding of any system(s) of focus
while examining a scenario. The Root Definition is a technique for achieving clarity and a
shared comprehension of a system's function and context. We made sure the root definition
was of the greatest caliber feasible by employing the CATWOE approach. The acronym
CATWOE stands for Customers, Actors, Transformation, World View, Owner, and
Environmental Constraints.

Use Case Diagram

A use case diagram illustrates how a system behaves dynamically. It captures the
functionality of the system by incorporating actors, use cases, and their interactions. It
describes the jobs, services, and requirements that a system or subsystem of an application
has. It describes both the high-level functionality of a system and how a user interacts with it.
A use case diagram's primary objective is to demonstrate how a system evolves over time.
The requirements for the system are gathered, and these come from both internal and external
elements. It mentions people, use cases, and a variety of other factors that contribute to the
execution of use case diagrams. It shows the possible interactions between an outsider and a
system part.

A use case diagram serves the following purposes:

 It compiles the system's needs.

 It provides an exterior view of the system.
 It is aware that both internal and external influences have an impact on the system.
 It shows the interactions between the performers.

6
Hierarchy Diagram
The Structure or Hierarchal Chart shows the hierarchical structure of the modules. It gives a
more detailed description of each module's functions and sub-functions and breaks the system
down into its lowest functional modules. The Structure Chart splits the system into "black
boxes," which means that users are aware of the functionality of the system but are not aware
of its inner workings. The black boxes take inputs and produce the appropriate outputs.

When one module calls another, the called module functions as a black box, passing the
required arguments and getting the results. Low-level modules are modules at the top level.
The components are read from left to right and from top to bottom.