id
stringlengths
6
9
content
stringlengths
41
444
summary
stringclasses
1 value
layer
stringclasses
2 values
r1.txt
Create a new task which typically has a start date and an end date. Tasks are activities that one or more persons resources are expected to complete in the specified time frame.
High Level Requirement
r10.txt
Add/Remove Resources to Tasks Dependencies;Dependencies between tasks and resources indicate the resources who are supposed to complete a task. Each task could be worked on by multiple persons and each person could work on multiple tasks. Dependencies may also be annotated to capture how many hours each person is supposed to work on a task on a daily basis.
High Level Requirement
r11.txt
Change Task Begin/End Times manually with user changes; Change the start or end date either by editing its properties or by dragging-and-dropping the bar in the GUI.
High Level Requirement
r12.txt
Change Task Begin/End Times automatically with dependency changes;The start or end date should be changed automatically if links among tasks are changed
High Level Requirement
r13.txt
Change Task Begin/End Times automatically with dependency changes; The start or end date should be changed automatically if one of its subtasks changes.
High Level Requirement
r14.txt
Prevent Circular Dependencies;Links among tasks may not be circular in that task 1 cannot depend on task 2 if task 2 already depends on task 1.
High Level Requirement
r15.txt
Show Critical Path; The critical path indicates which tasks will cause project delays if they are delayed.
High Level Requirement
r16.txt
Add/Remove Holidays and Vacation Days;Holidays and vacation days are properties of persons (resources). changing this information also changes the availability of a person on certain days.
High Level Requirement
r17.txt
Show Resource Utilization (underused or overused person);Tasks may be assigned to persons and it should be indicated if a person receives more tasks than he/she is able to handle (e.g., the person hours per task for all tasks exceeds the allowed 8 hours a day) or if the person is not available due to holidays or vacation days. it should also be indicated if the person is under-utilized in that he/she is working less than the 8 hours a day.
High Level Requirement
r2.txt
Delete Tasks; Delete an existing task and all its associated information such as links to other tasks or knowledge on what resources are supposed to work on them.
High Level Requirement
r3.txt
Maintain task properties; Edit and update task properties including start and end date, name, or progress(% complete).
High Level Requirement
r4.txt
Add/Remove Tasks as Subtasks;A task can be made a subtask of another. For example, task 1.1 is a subtask of task 1.
High Level Requirement
r5.txt
Handle Milestones; A milestone is a special task. Whereas a task typically has a timeframe specified (the time needed to complete the task), a milestone is typically an event. For example, the release date of a software is an event rather than a timeframe.
High Level Requirement
r6.txt
Create Resources (person);GanttProject supports Persons as resources. Persons have names and holidays or vacation days. Persons can be assigned to work on tasks.
High Level Requirement
r7.txt
Delete Resources (person); Delete a person and all its associated information such as dependencies to all tasks the person is supposed to work on.
High Level Requirement
r8.txt
Maintain Resource Properties;A resource has a range of properties, including name and holidays
High Level Requirement
r9.txt
Add/Remove Task links; Tasks can be linked with one another to indicate the sequence in which they have to be performed. For example, if there is a link from task 1 to task 2 then task 2 can only be started after task 1 is completed. The start date of task 2 must thus be after the end date of task 1.
High Level Requirement
d10_1.txt
A class is used to represent the dependency between one task and one human resource. The dependency class provides functions to get the task and the human resource.
Low Level Requirement
d10_2.txt
A collection of resource assignments is used to manage the relationships between multiple human resources and a task. It contains multiple objects of the human resource assignment class. The collection provides functions to add and remove human resource assignments.
Low Level Requirement
d10_3.txt
The class of task uses an object of the assignments collection class to manage its assignments.
Low Level Requirement
d10_4.txt
The human resource class can have multiple objects of resource assignments which assigns this resource to tasks. The class provides function to get the list of these objects.
Low Level Requirement
d10_5.txt
A GUI class of task property provides interface and functions to add and remove human resource assignments.
Low Level Requirement
d10_6.txt
A GUI class uses an object of resource tree table model class to display the resource tree. The resource tree table model provides functions build subtrees based on dependencies.
Low Level Requirement
d10_7.txt
A GUI class of human resource load distribution uses objects of a load distribution class to capture the hours each person is supposed to work.
Low Level Requirement
d10_8.txt
The load distribution class provides functions to calculate the distribution based on tasks and human resources. The functions uses the task manager.
Low Level Requirement
d11_1.txt
GUI needs to provide ability to change length of a task.
Low Level Requirement
d11_2.txt
Using GUI user should be able to change the length of a task by dragging-and-dropping the bar on the GUI.
Low Level Requirement
d11_3.txt
Using GUI user should be able to change the length of a task via date picker control.
Low Level Requirement
d12_1.txt
A dependency class contains a dependant task and a dependee task. It provides functions to get the dependant task and the dependee task. The dependency class also contains constraint to show the constraint of the dependency.
Low Level Requirement
d12_2.txt
A class is used to represent the constraint that the start date of the dependee task should not be earlier than the end date of the dependent task.
Low Level Requirement
d12_3.txt
A collection of dependency class is used to manage dependencies. It contains objects of dependency classes and provides functions to create, delete, and get dependencies.
Low Level Requirement
d12_4.txt
A GUI class of task property provides interface and functions to add and remove dependencies by using an object of the dependency collection.
Low Level Requirement
d12_5.txt
A GUI class of graphic area provides function to draw dependency. The function uses an object of task manager to add dependencies.
Low Level Requirement
d12_6.txt
The task manager class uses an object of dependency collection class to manage dependencies.
Low Level Requirement
d12_7.txt
An object of the recalculating task schedule algorithm class is used to change the start or end date based on dependency changes. The algorithm class provides functions to fulfill the constraints and to modify the start or end date of the tasks.
Low Level Requirement
d13_1.txt
Application needs to keep track of task's begin and end times.
Low Level Requirement
d13_2.txt
Application needs to keep track of subtasks in a task.
Low Level Requirement
d13_3.txt
Every time Start/End time for a subtask changes, the start/end time for the parent task need to change accordingly.
Low Level Requirement
d13_4.txt
Every time Start/End time for a task changes, the start/end time of one or more its subtasks need to change as well.
Low Level Requirement
d14_1.txt
A GUI class of graphic area provides a function to draw dependency. The function uses an object of the task manager to add dependencies. 1
Low Level Requirement
d14_2.txt
The task manager class uses an object of dependency collection class to manage dependencies.
Low Level Requirement
d14_3.txt
The class of dependency collection provides a function to check if the new dependency will cause a loop each time a object of dependency class is created. The function returns an exception if there is a loop.
Low Level Requirement
d15_1.txt
GUI needs to provide ability to display critical path and make the changes affecting critical path updated.
Low Level Requirement
d15_2.txt
The system should be able to evaluate critical path in a project.
Low Level Requirement
d16_1.txt
The human resource class contains the variable holidays. The class provides functions to change and to get holidays. There can be multiple holidays.
Low Level Requirement
d16_2.txt
There is a class to represent holiday. The holiday class provides functions to set the begin date and the end date of the holiday, to check if a date is in the holiday, and to get the duration of the holiday.
Low Level Requirement
d16_3.txt
The human resource class provides a function to change the availability of the person based on holidays.
Low Level Requirement
d17_1.txt
GUI needs to provide ability to assign task to persons.
Low Level Requirement
d17_2.txt
GUI needs to provide ability to assign persons to tasks.
Low Level Requirement
d17_3.txt
GUI needs to provide ability to show utilization of a person.
Low Level Requirement
d17_4.txt
GUI needs to provide ability to show is a person is underutilized and overbooked.
Low Level Requirement
d1_1.txt
To create a new task an object of TaskManager class is passed to the class constructor. The TaskManager in its turn takes care of a resource allocation using ResourceAssignmentCollection class.
Low Level Requirement
d1_2.txt
The Task class provides a public method SetStart() which allows to specify starting date for the task. As input argument the method takes an object of GanttCalendar class.
Low Level Requirement
d1_3.txt
The Task class provides a public method SetEnd() which allows to specify starting date for the task. As input argument the method takes an object of GanttCalendar class.
Low Level Requirement
d1_4.txt
The Task class provides a public method SetDuration() which allows to specify the duration of the task. As input argument the method takes an object of TaskLength class
Low Level Requirement
d2_1.txt
To delete a task from the Calendar the GanttProject class call delete method and supplied TaskId paramenter. The adjustment of allocated resources and links to other tasks takes place through interfacing with the following classes DefaultMutableTreeNode, GanttTreeTableNode, TaskNode, and AdjustTaskBoundsAlgorithm.
Low Level Requirement
d2_2.txt
When deleting a task the GanttProject class calls GanttTreeTableNode and DefaultMutableTreeNode classes to identify the parent of the task being deleted.
Low Level Requirement
d2_3.txt
When deleting a task the GanttProject class calls AdjustTaskBoundsAlgorithm and passes the parent of the deleted task as a parameter. The AdjustTaskBoundsAlgorithm takes care of handling and releasing resources associated with the deleted task.
Low Level Requirement
d3_1.txt
GUI should able to provide ability to change task name.
Low Level Requirement
d3_2.txt
GUI should able to provide ability to change start/end date of a task.
Low Level Requirement
d3_3.txt
GUI should able to provide ability to set progress on a task.
Low Level Requirement
d3_4.txt
When the start/end date of a task are changed, the start/end dates of the subtasks need to change accordingly.
Low Level Requirement
d4_1.txt
To add tasks as subtasks a method which indent the selected task nodes in GUI and change them to be subtasks is used. A manager of task hierarchy provides functions to update the relationship between tasks.
Low Level Requirement
d4_2.txt
The manager of task hierarchy provides a method to move a task node to a specific position.
Low Level Requirement
d4_3.txt
To remove tasks as subtasks GanttTree2 class calls a method which dedent selected task nodes in GUI so that they will not be subtasks of their original parents tasks. An object of a class is used to remove relationship between selected tasks and their original parents and add relationship between selected tasks and their new parents.
Low Level Requirement
d4_4.txt
To remove tasks as subtasks a method which dedent selected task nodes in GUI so that they will not be subtasks of their original parents tasks is used. The task tree model provides methods to remove relationship between selected tasks and their original parents and add relationship between selected tasks and their new parents.
Low Level Requirement
d5_1.txt
Milestone is a task with no duration. It has only time point of occurrence.
Low Level Requirement
d5_2.txt
User should be able to create milestones.
Low Level Requirement
d5_3.txt
User interface should be able to provide an ability to specify whether a specific task in a milestone.
Low Level Requirement
d5_4.txt
Milestone should be displayed visually differently from regular tasks.
Low Level Requirement
d6_1.txt
A GUI of task property provides interface and functions to add and remove human resource assignments by using an object of the resource assignments collection class.
Low Level Requirement
d6_2.txt
The human resource class contains name, phone, email, and holidays. The class provides functions to set and get these properties. A class is used to represent the holidays. There can be multiple holidays.
Low Level Requirement
d6_3.txt
The class for holidays provides functions to get the start date and the finish date. The class also provides a function to check if a special date is in holiday.
Low Level Requirement
d6_4.txt
A human resource assignment class is used to represent the relationship between one task and one human resource. The class provides functions to get the task and the human resource.
Low Level Requirement
d6_5.txt
A collection of resource assignments is used to manage the relationships between multiple human resources and a single task. It contains multiple objects of the human resource assignment class. The collection provides functions to add and remove human resource assignments.
Low Level Requirement
d6_6.txt
The class of task uses an object of the assignments collection class to manage its assignments.
Low Level Requirement
d7_1.txt
GUI needs to provide ability to delete resources from a project.
Low Level Requirement
d7_2.txt
An assignment of a resource to a task is captured as a relationship.
Low Level Requirement
d7_3.txt
When a resource is removed, all the tasks where the resource is assigned need to be updated.
Low Level Requirement
d8_1.txt
The human resource class contains name, phone, email, and holidays. The class provides functions to set and get these properties. A class is used to represent the holidays. There can be multiple holidays.
Low Level Requirement
d8_2.txt
A GUI provides interface and functions to edit the properties of objects of the human resource class.
Low Level Requirement
d8_3.txt
The class for holidays provides functions to get the start date and the finish date. The class also provides function to check if a special date is in holiday.
Low Level Requirement
d9_1.txt
GUI needs to provide ability to link tasks in a project.
Low Level Requirement
d9_2.txt
The fact of linking of one task to another should be captured as dependency between two tasks.
Low Level Requirement
d9_3.txt
When a two or more tasks are link, there should be check conducted for potential collisions on the chart.
Low Level Requirement
d9_4.txt
The start and end dates for the graph can be either flexible or rigid for the purpose of adjusting and fixing potential collisions.
Low Level Requirement
README.md exists but content is empty.
Downloads last month
41