While developing software we use files but we generally talk not about files but classes, but files construct the software, we use not classes but files in configuration management, and files are reused not classes, one file can carry many classes. Can I have your thoughts on this issue?
I think there are two viewpoints of these. I we are talking about integrity of project history, talking about version control or dependency management, it is clear that it is assuming the project development from files because these are process inside the configuration management area. However if we a talking about business, modeling and we are trying to catch an speceific domain it obvious that we are dealing with domain objects that can represent classes and its relationships. For summarizing it has no problem the level of file dependency, it is a normal issue in software development, so i consider it useful.
Configuring classes, their instances and relationships (dependencies) using files is a common and useful approach that has been introduced by dependency injection (DI) and object-relational-mapping (ORM) frameworks such as Spring. In this case the configuration is done in a declarative manner using XML-files for example. With the rise of JavaScript even a class definition would make sense using JSON. This file approach is useful in my opinion.
Configuration Management Repositories are based on files, so there is no way around that - especially when you want to track change history. Nothing precludes you from having an enforceable policy of object definitions in .h files and methods in the .c files (as an example).
Ada had the specification part and the body part when implementing objects and their associated methods.
Newer implementations via XML (and other) may allow for single file use for object definition and method implementation, but some other parser would have to be able to separate out the parts. Again, still have a file.
- Badges
- Science topic
- Similar topics
- Engineering
- Modeling