Title -: Task Descriptions as Functional RequirementsArticle SummaryA software system is built based on requirements. Requirements elicitation is therefore an important aspect. Functional requirements describe what the system does to achieve its objective. A functional requirement is an action performed by a user/system to achieve a specific objective. Authors Marianne Mathiassen developed the Tasks & Support method, which uses annotated task descriptions. According to the authors using this process, the computer and the user must accomplish together without indicating which actor performs which parts of the tasks. The author claims that with this approach, higher quality requirements are produced, faster to produce and easy to verify and validate. This follows a similar phenomenon to Alistair Cockburn's definition of the use case, i.e. the use case is what the system does and how it interacts with the user. But task-based requirements analysis delays the distribution of work between the system and the user. In this approach, this is seen as a decision to be made later. The task has the following elements. The description of the work area indicates the formal requirement (R2: The system must…). It also explains the general objective of the task, the environment and user information. Other conditions and business rules of the task are captured, in the form of task preconditions or individual task steps, primarily by a precondition. The task can have multiple subtasks that support the task. There is no sequence of operations in subtasks. This provides greater flexibility when requirements change often. In the real-world scenario, most of the time, what might have the greatest opportunity to change is the way businesses operate. Sin...... middle of paper ...... the analysis is carried out at the task level, it is easier to identify the dependencies of each task for its completion, what must be respected, what are non-functional requirements to complete the tasks. Subtasks of a task can be implemented sequentially or non-sequentially. Effective task analysis takes time. If sufficient time is not allocated in the initial project planning, it will be necessary to allow for variances. Additionally, when testing, it will be difficult to perform integration tests. Additionally, they will have more hidden things to take into account and difficulty in arriving at estimates. After completing the task, how the outcome of a task would impact other parts of the system. Article Citation Faculty of Engineering and Information Technology University of Technology Sydney, PO Box 123 Broadway, NSW 2007, Australia (mairiza, didar, nur)@it.uts.edu.au