 |
| Software code files, data files, and supporting files (such as online help files) that represent the raw parts of a system that can be built. |
| Domains: Development |
|
Purpose
To represent the physical parts that compose the system to be built, and to organize the parts in a way that is
understandable and manageable.
|
Relationships
| Fulfilled Slots |
|
| Tasks | Input To:
| Output From:
|
| Process Usage |
|
Description
| Main Description |
This artifact is the collection of one or more of these elements:
-
Source code files
-
Data files
-
Build scripts
-
Other files that are transformed into the executable system
|
Tailoring
| Impact of not having | Without this artifact, there is no way to produce the application to be delivered as part of the solution. |
| Reasons for not needing | You do not need to produce this artifact if the actual development of an application is not in the scope of the solution. |
| Representation Options |
Implementation files are represented as files in the local file system. File folders (directories) are represented as
packages, which group the files into logical units.
|
|
