Changes between Version 16 and Version 17 of ITC 371 Project Management
- Timestamp:
- 12/04/13 20:37:22 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ITC 371 Project Management
v16 v17 49 49 50 50 === System Constraints === 51 The primary issue created by handling data this way would that the data is initially put in by users. Although data checking can be done for correct format, it would be very difficult to verify that an address is correct. Also, the person reporting the issue may not be physically on site. This would also create problems with pulling GPS information from a cell phone. The constraint would be that location information would need to be accurate for the system to be effective with geo-tagging.52 51 53 [[Image(Sahana Eden Ticketing System.jpg)]] 54 Resource Tagging Graphical Representation 52 The primary constraint will be that the address or latitude and longitude information provided by individuals requesting assistance must be accurate. Without accurate information, passing the information to other software for directions would be useless. The software would also require that authoritative users respond to requests for assignment in a timely fashion. If they do not, then incidents would cycle in an infinite loop without ever being resolved. This would ultimately create system resource issues until the system became non-responsive. 55 53 56 ----57 BluePrint
