Difference between revisions of "Glossary"
From EITBOK
| Line 1: | Line 1: | ||
<table> | <table> | ||
<tr><td>'''Term'''</td><td>'''Meaning'''</td></tr> | <tr><td>'''Term'''</td><td>'''Meaning'''</td></tr> | ||
| − | <tr><td> | + | <tr><td>conceptual design</td><td>Describes the proposed solution in a functional manner that could be easily understood by a future user, including what the solution will look like and how it will behave</td></tr> |
| − | </td><td>Subject matter expert</td></tr> | + | <tr><td>domain</td><td>A specific sphere of activity or knowledge. A domain can correspond to the boundaries of an organization, a job function, or even a particular task.</td></tr> |
| − | <tr><td>SWOT | + | <tr><td>domain elicitation</td><td>Collecting the right information from SMEs, stakeholders, or consumers about how the solution should function</td></tr> |
| + | <tr><td>logical design</td><td>Defines objects, entities, their attributes, and their relationships. It also describes the business rules associated with these entities</td></tr> | ||
| + | <tr><td>physical design</td><td>Also called the technical design. Where the conceptual and logic designs are converted to a definition of how the solution will be implemented in hardware, software, and potentially other media. The physical design is developed by the construction team not by the requirements team.</td></tr> | ||
| + | <tr><td>SME</td><td>Subject matter expert</td></tr> | ||
| + | <tr><td>solution</td><td>A set of changes to the current state of an enterprise that will enable the enterprise to meet a need, solve a problem, or take advantage of an opportunity</td></tr> | ||
| + | <tr><td>SWOT</td><td>Strengths, weaknesses, opportunities. and threats involved in a project or in a business venture</td></tr> | ||
| + | <tr><td> </td><td> </td></tr> | ||
| + | <tr><td> </td><td> </td></tr> | ||
| + | <tr><td> </td><td> </td></tr> | ||
</table> | </table> | ||
Revision as of 18:47, 26 August 2015
| Term | Meaning |
| conceptual design | Describes the proposed solution in a functional manner that could be easily understood by a future user, including what the solution will look like and how it will behave |
| domain | A specific sphere of activity or knowledge. A domain can correspond to the boundaries of an organization, a job function, or even a particular task. |
| domain elicitation | Collecting the right information from SMEs, stakeholders, or consumers about how the solution should function |
| logical design | Defines objects, entities, their attributes, and their relationships. It also describes the business rules associated with these entities |
| physical design | Also called the technical design. Where the conceptual and logic designs are converted to a definition of how the solution will be implemented in hardware, software, and potentially other media. The physical design is developed by the construction team not by the requirements team. |
| SME | Subject matter expert |
| solution | A set of changes to the current state of an enterprise that will enable the enterprise to meet a need, solve a problem, or take advantage of an opportunity |
| SWOT | Strengths, weaknesses, opportunities. and threats involved in a project or in a business venture |
