ddsf:public:guidebook:06_append:glossary:m:module
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
ddsf:public:guidebook:06_append:glossary:m:module [2020/08/03 13:41] nick created |
ddsf:public:guidebook:06_append:glossary:m:module [2021/07/14 16:42] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Module ===== | ===== Module ===== | ||
| - | [[ddsf:private:cookbook:06_append:glossary| Return to Glossary ]] | + | [[ddsf:public:guidebook:06_append:glossary:start| Return to Glossary ]] |
| A **Module** is a separate, interchangeable, self contained component that represents a unit of functionality. It is best to define a Module what it does: | A **Module** is a separate, interchangeable, self contained component that represents a unit of functionality. It is best to define a Module what it does: | ||
| Line 6: | Line 6: | ||
| * It encapsulates code and data into a single unit (usually a file) that implements a specific functionality | * It encapsulates code and data into a single unit (usually a file) that implements a specific functionality | ||
| * It provides an interface as a contract between the users of the module (i.e., clients) to access the functionality in an consistent way | * It provides an interface as a contract between the users of the module (i.e., clients) to access the functionality in an consistent way | ||
| - | * It allows for the functionality to be plug-gable into other modules (i.e., clients) that use the interface | + | * It allows for the functionality to be plug-able into other modules (i.e., clients) that use the interface |
| * It is packaged in a single unit so that it can be easily deployed. Generally it is stored as a file, but it could be an entry into a database (i.e., stored procedure), a datastream, etc. | * It is packaged in a single unit so that it can be easily deployed. Generally it is stored as a file, but it could be an entry into a database (i.e., stored procedure), a datastream, etc. | ||
| - | For example, ''dapper.net'' encapsulates database access. It has an [[ddsf:private:cookbook:06_append:glossary:a:api]] to access its functionality. It is a single file that can be plugged into a source tree. | + | For example, ''dapper.net'' encapsulates database access. It has an [[ddsf:public:guidebook:06_append:glossary:a:api]] to access its functionality. It is a single file that can be plugged into a source tree. |
| Source: [[https://softwareengineering.stackexchange.com/questions/167859/what-actually-is-a-module-in-software-engineering ]] | Source: [[https://softwareengineering.stackexchange.com/questions/167859/what-actually-is-a-module-in-software-engineering ]] | ||
ddsf/public/guidebook/06_append/glossary/m/module.1596476473.txt.gz · Last modified: 2020/08/03 13:41 by nick
