Title -: Task Descriptions as Functional Requirements Article Summary A software system is built based on requirements. Therefore requirements elicitation is an important aspect. Functional requirements describe what the system does to achieve its goal. A functional requirement is an action performed by the user/system to achieve a specific goal. Authors Marianne Mathiassen and developed the Tasks & Support method, which uses annotated task descriptions. According to the authors, using this process, the computer and the user must perform together without indicating which actor performs which parts of the tasks. The author claims that this approach produces higher quality requirements that are faster to produce and easier to verify and validate. This follows a similar phenomenon to Alistair Cockburn's definition of use case, i.e. use case is what the system does and how it interacts with the user. But task-based requirements analysis delays the division of work between the system and the user. In this approach it is considered a decision to be made later. The activity has the following components. The work area description indicates the formal requirement (R2: The system must...). It also explains the overall purpose of the task, the environment, the user information. Further conditions and business rules of the task are captured, such as task preconditions or individual task steps, mainly by a precondition. The task can have several 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, in most cases what may have the greatest chance of changing is the way businesses operate. Too bad... half of the document... the analysis is done at the task level, it is easier to identify the dependencies of each task for its completion, what needs to be respected, what are the non-functional requirements to satisfy the task requirements . Subtasks in a task can be implemented sequentially or non-sequentially. Effective business analysis takes time. If adequate time is not allocated in the initial project planning, a schedule variance will occur. Furthermore, during the test it will be difficult to perform the integration test. Furthermore, their will is more hidden and requires attention and difficulty in arriving at estimates. After completing the task, how the result of a task might affect 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