Use Cases Configuration Manager, proposal
- 1. AbTLinux configManager F elix Cillessen A lex Rachmann R ogier de Leeuw FAR beyond RE RE
- 2. About Time Linux toolset The configManager acts as a service provider to the packageManager by gathering and delivering information about configurations
- 3. Context configManager Configuration: A state of all configuration files of a package at a given time. Configuration file: File that contains parameters and settings used by the package. Package: A Linux package consists of one or more programs with associated documentation that will perform a specific function either for the operating system or add additional capabilities.
- 4. Mission, Vision, Value Mission Deliver well documented requirements as extension for AbTLinux for developing the configManager. Vision A document based on a precise framework according to a modern way of software engineering. Values The main value is the clear documentation using Use Cases, goal analysis and ORM. To facilitate the stakeholders to get a clear and shared understanding of the functionality of the configManager before it is actually build.
- 5. Business rules packageManager is always the actor for the configManager configManager itself never performs any write actions The configManager is an information delivery service for the packageManager
- 6. Overview of all Use Cases
- 7. Identify configuration files Configuration files of a package are discovered. BCoE: configManager identifies possible configuration files. configManager creates a list of possible configuration files. configManager returns this list.
- 8. Heuristic for identifying configuration files The file has to be in text-format, not in a binary format. Standard names should be used. Standard extensions should be used. Standard directories should be used.
- 9. Interlude: Content of configuration files Package foo v1 has no configuration files. Package foo v2 has 2 configuration files, content of foo.ini is SERVER=www.foo.com Package foo v3 has 2 configuration files, content of foo.ini is SERVER=www.foo.org PROTOCOL=http Package foo v4 has the same configuration files as foo v3.
- 10. Identify configuration files (scenario) configManager identifies possible configuration of foo v3 files by their format (textcode) and extensions, in this scenario Foo.ini Foo.conf configManager creates a list out of these two. configManager returns this list.
- 11. Provide configuration item One or more (could be all) items of a configuration are requested and returned
- 12. Provide configuration item (scenario 1) configManager gathers the values of SERVER and PROTOCOL of foo v3 configManager returns the chosen items SERVER = www.foo.org and PROTOCOL = http
- 13. Provide configuration item (scenario 2) configManager tries to gather the values of SERVER and PROTOCOL of package foo v1 The configManager returns the message “Package foo version 1 has no configuration.”
- 14. Provide configuration item (scenario 3) configManager gathers all items of foo v3 by using the wildcard *, in this case SERVER and PROTOCOL configManager returns the chosen items SERVER = www.foo.org and PROTOCOL = http
- 15. Provide differences overview The items of two configurations are compared This comparison can be done between Two stored configurations (inside a tar.gz. file) One stored configuration (tar.gz.) and an installed configuration (e. g. home directory)
- 16. Provide differences overview (scenario 1) configManager reads the files foo.ini and foo.conf of foo version 2 (Outcome SERVER = www.foo.com) configManager reads the files foo.ini and foo.conf of foo version 3 (Outcome SERVER = www.foo.org PROTOCOL = http) The differences are returned. "The configuration of package foo version 2 has a different value of the item SERVER than the configuration of the package foo version 3. (foo version 2: SERVER = www.foo.com; foo version 3 SERVER =www.foo.org) The configuration of package foo version 3 has an item that is not defined in the configuration of package foo version 2 (PROTOCOL = http)."
- 17. Provide differences overview (scenario 2) configManager reads the files foo.ini and foo.conf of foo version 3 (Outcome: SERVER = www.foo.com PROTOCOL = http) configManager reads the files foo.ini and foo.conf of foo version 4. (Outcome: SERVER = www.foo.org PROTOCOL = http) The message "There are no differences between the configuration of foo version 3 and configuration of foo version 4." is returned.
- 18. Provide summary Provides information about a configuration, listed according to configuration files. Properties of a file: size, last changed by, last changed at, created by, created at, number of items, text code, location
- 19. ORM of Use Case “Provide summary”
- 20. Domain Model
- 21. Non-functionals Data integrity Integrability Reliability Extensibility
- 22. Questions?
- 23. Thank you! On behalf of the FAR beyond RE group Our best wishes for this Xmas and a happy new year