This shows you the differences between the selected revision and the current version of the page.
| u:overview 2008/03/07 14:10 | u:overview 2008/03/07 14:14 current | ||
|---|---|---|---|
| Line 22: | Line 22: | ||
| * Administrator views and reports | * Administrator views and reports | ||
| * Time zone adjustment for use on international servers | * Time zone adjustment for use on international servers | ||
| + | |||
| Line 27: | Line 28: | ||
| ====== Scope and goals ====== | ====== Scope and goals ====== | ||
| - | * The focus of this project ease of use, functionality and extendibility relating to the tasks involved with handling TimeSheets.. | + | * The focus of this project ease of use, functionality and extendibility relating to the tasks involved with handling TimeSheets. |
| * TimesheetNG targets the activity of enterening and tracking time, based on projects and tasks. | * TimesheetNG targets the activity of enterening and tracking time, based on projects and tasks. | ||
| * TimesheetNG is written in PHP, uses MySQL as backend, and standard WebBrowser as frontend. | * TimesheetNG is written in PHP, uses MySQL as backend, and standard WebBrowser as frontend. | ||
| Line 42: | Line 43: | ||
| - | ===== What timesheetNG is Not ===== | + | |
| - | * Project Planning/Management System | + | ===== What TimesheetNG is Not ===== |
| + | * Project Planning/Management system | ||
| * Accounting system | * Accounting system | ||
| * CRM system | * CRM system | ||
| + | * Change or bug management system | ||
| + | |||
| ===== Extensibility and Integration ===== | ===== Extensibility and Integration ===== | ||
| - | *Bearing in mind that Timesheet NG targets the actual task of handling timesheets... From a Workflow perspective one could say that TimeSheet NG will get its actual Project and Task information from a Project Planning System, and present its output to Project Progress, Accounting, Invoicing and payroll systems. | + | *Bearing in mind that TimesheetNG targets the actual task of handling timesheets... From a Workflow perspective one could say that TimeSheetNG will get its actual Project and Task information from a Project Planning System, and present its output to Project Progress, Accounting, Invoicing and payroll systems. |
| - | *When planning such a system, it is very easy to forget the main target of the system, by overloading it with features that are a natural part of other systems like mentioned above | + | *When planning such a system, it is very easy to forget the main target of the system, by overloading it with features that are a natural part of other systems like mentioned above. |
| ==== Integration ==== | ==== Integration ==== | ||
| Possible points of Integration.. | Possible points of Integration.. | ||
| - | === Input to TimeSheet === | + | === Input to TimesheetNG === |
| * User Information (CRM or other) | * User Information (CRM or other) | ||
| * Client information (CRM or other) | * Client information (CRM or other) | ||
| * Project and task definitions (Project Management Systems) | * Project and task definitions (Project Management Systems) | ||
| - | === OutPut from Timesheet === | + | === Output from TimesheetNG === |
| * CRM systems | * CRM systems | ||
| * Project Management Systems | * Project Management Systems | ||
| Line 70: | Line 75: | ||
| - | ====== Discussion on "What TimeSheetNG should be..." ====== | ||
| - | The core functionality of TimeSheetNG should be that of time tracking. TimeSheetNG could easily become bogged down with trying to be a fully fledged PM system and this defeats the purpose - besides, there are many great PMSs out there already. | + | ====== Discussion on "What TimesheetNG should be..." ====== |
| + | |||
| + | The core functionality of TimesheetNG should be that of time tracking. TimeSheetNG could easily become bogged down with trying to be a fully fledged PM system and this defeats the purpose - besides, there are many great PMSs out there already. | ||
| I think this project could turn into a "killer app" the moment when it realises this! This project should be about the core functionality of being a really easy-to-use method for entering time spent on a particular task. This is worth saying again: recording time spent on tasks. | I think this project could turn into a "killer app" the moment when it realises this! This project should be about the core functionality of being a really easy-to-use method for entering time spent on a particular task. This is worth saying again: recording time spent on tasks. | ||
| Line 80: | Line 86: | ||
| 2. Developing plugins to extend the core functionality - reporting, sick days, etc. | 2. Developing plugins to extend the core functionality - reporting, sick days, etc. | ||
| - | If we successfully "pull off" point 1 we don't have to worry about how tasks break down into "client/project/tasks", it could even be "projects/versions/bugs" for all TimeSheetNG cares, as long as it accurately and easily tracks the time users spend working on whatever it is. | + | If we successfully "pull off" point 1 we don't have to worry about how tasks break down into "client/project/tasks", it could even be "projects/versions/bugs" for all TimesheetNG cares, as long as it accurately and easily tracks the time users spend working on whatever it is. |
| - | On top of this, if we can develop some really good plugins to integrate into the above then TimeSheetNG could become a really useful little tool. | + | On top of this, if we can develop some really good plugins to integrate into the above then TimesheetNG could become a really useful little tool. |
| - | I'm not sure how these thought will be taken in via the community using the current Timesheet.php project, but then again, this is a separate project?! Timesheet.php should be seen as a subset of TimeSheetNG functionality, so anyone who uses 1.2.1 should lose nothing (and gain everything) by upgrading. | + | I'm not sure how these thought will be taken in via the community using the current Timesheet.php project, but then again, this is a separate project?! Timesheet.php should be seen as a subset of TimesheetNG functionality, so anyone who uses 1.2.1 should lose nothing (and gain everything) by upgrading. |
| Thoughts please --- //[[ibrow@users.sourceforge.net|Rob Searles]] 2008/02/11 00:40// | Thoughts please --- //[[ibrow@users.sourceforge.net|Rob Searles]] 2008/02/11 00:40// | ||