# Integration of BIM and GIS for the Digitization of the Built Environment
## 4 Results and Discussion
### Open-Source and Closed-Source Comparison  
When choosing software, the most important question is whether it is free or not. Unfortunately, the decision is not so clear-cut, and depends on the needs of the end user. The following is a comparison of the strengths and weaknesses of closed-source software (CSS) and open-source software (OSS). In the traditional development model, software is copyrighted and sold to users to make money, whereas in the OS paradigm, software is freely available to users to use and modify. In the traditional way, software development is systematic and formal work done by experienced developers to improve quality; a centralized management team helps them to improve the software in new versions, whereas in the OSS development model there are frequent releases in which the software is improved by users and developers worldwide. There are no specific people or places for physical discussion. In the OS development model, the improvement of code quality may depend on the personality of everyone who participates by registering on host sites, and it remains the responsibility of each person to ensure that the system works better and improves quality. The quality success of closed software is related to its central management, whereas in OSS the quality comes from its openness, because many programmers can examine it and find bugs, even though this may lead to iterative corrections and some developers may correct the same thing. In addition, quality is improved in the OSS development model compared to closed software because the development processes of OSS, such as review, testing and maintenance, take place in parallel. Openness in OS helps to identify user requirements better than in CSS, because in this type of software, users themselves can contribute and intervene, even as developers. The number of teams working on quality assurance is an effective way of assessing quality, and this issue is maintained by companies in closed software, whereas in OS it can be deduced from commitment logs and the source code itself. The goal of CSS is to develop software that can be released to the public for market penetration and profit. The objective of CSS is the development of software to be presented to the public in order to gain market penetration and profit, while OS is a personal idea that can spread and receive contributions from users all over the world to implement and develop it, bearing in mind that coordinating a large number of contributions requires the use of standardization platforms to manage all processes. The main differences between OSE and CSE are summarized below. * Development models:
* CSS: software is copyrighted and sold for profit. Development is systematic and formal, managed by a central team;
* OSS: software is freely available for use and modification. It is continuously improved by a global community of users and developers. * Software quality:
* CSS: quality is guaranteed by a central team that releases new versions;
* OSS: quality is improved by many programmers examining the code and finding/fixing bugs, as well as continuous iterative corrections, parallel revisions and dedicated testing. * User involvement:
* CSS: users do not contribute to software development;
* OSS: users can actively contribute to the development and definition of software requirements. * Main objectives:CSS: the goal is market penetration and profit;  
OOSS: the objective is collaborative sharing and evolution, with the support of standardization platforms to manage developer contributions. - Community:  
O CSS: Smaller community, often limited to users and the organization's development team;  
OOSS: Strong community of developers and users who actively participate in the development and improvement of software. - Security:  
O CSS: Security depends on the policies and resources of the company developing the software;  
OOSS: Security tends to be based on the principle of \"security through transparency\". Many users check the code for vulnerabilities.