Application Implementation Methodology: Difference between revisions
Appearance
Content deleted Content added
DaltonCastle (talk | contribs) added Category:Workflow software; removed {{uncategorized}} using HotCat |
mNo edit summary |
||
(13 intermediate revisions by 12 users not shown) | |||
Line 1: | Line 1: | ||
'''Application Implementation Methodology''' (AIM) is a [[system framework]] of related elements. It involves certain tasks, processes, phases and dependencies: |
|||
* A [[Task (project management)|task]] is a unit of work, which results in a single [[deliverable]] which may take many different forms like reports, schedules, codes, or test results. |
|||
⚫ | |||
⚫ | |||
== External links == |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
{{Management-stub}} |
|||
⚫ | |||
⚫ |
Latest revision as of 05:50, 16 September 2024
Application Implementation Methodology (AIM) is a system framework of related elements. It involves certain tasks, processes, phases and dependencies:
- A task is a unit of work, which results in a single deliverable which may take many different forms like reports, schedules, codes, or test results.
- A process is a closely related to a group of dependent tasks fulfilling a major objective. A process is always based on a common discipline.
- A phase is a chronological grouping or order of tasks. It is a flexible way of organising tasks, preparing schedule major deliverables, and deliver projects