Distributed Services Management Team - Release 1
Release 1 focuses on implementing the baseline functionality of the job tracking system.
Jobs can be created and tracked via input from a barcode scanner or manual keyboard entry.
Job Creation
The system must support four different types of job requests:
- Service Requests: Requests for software support by clients at the client's site.
- Repair Requests: Repairing hardware at Reach Technology's workshop.
- Build Requests: Building a new computer at Reach Technology's workshop based on the client requirements.
- Refurbishment Requests: Refurbishing a donated computer at Reach Technology's workshop
Job Information
When created, each job has a summary and description associated with its job's ID. Additionally, each job has the ability to record comments as jobs progress through their lifecycle. This information must be displayed whenever a job is viewed.
Job Status
A job, through it's lifecycle, will have many changes in status. The system knows whenever a job's status
has changed, and can track those changes. When viewed, the system reflect the latest status of a job.
Barcode Tracking
Of the four types of job requests, Repairs, Builds and Refurbishments have the ability to have a barcode associated with them. The system can read a Reach Technology barcode from a barcode scanner and associate that barcode to a specific Job ID.
Time Management of Jobs
The system timestamps all job entries. Timestamping must occur whenever a job is created, updated or closed. This ensures accurate billing and reporting for jobs.
Job Subtasking
Jobs can have dependent subtasks which are viewed as a separate and independent task. For this reason we have implemented subtasking in order to track any dependencies a job may have. For example, a build job also requires the installation of software once the system is built. The software installation generates a subtask, which must be completed in order for the parent job to be closed. The subtask is created as a separate job, with it's own unique JobID, but has a link to the parent job. The parent job also has a link to it's child job. In this way, entire job families can be tracked together.
Job Searching
Users of the system can search the database in order to find specific jobs. Searching is performed on any item of data encapsulated by a JobID.
Consequently, search may be performed on JobID, Job Type, Job Status, Barcode, Summary Text, Description Text, Comment Text and Dates. Users can
also perform date searches on specific dates and date ranges.
Web Interface
The system is accessible through a web interface. When first accessing the system, users are presented with a Summary Screen, showing all existing jobs within the system. Users can create, modify, subtask and close jobs as well as search the system for specific jobs. Finally, users can customise the appearance of the Summary Screen by selecting which aspects of jobs they wish to view on the Summary Screen as well as the parameters they wish to display on the Advanced Search Screen.
The Summary Screen displays existing jobs in a sortable table. Each row of table represents a job, and is a link to view that job's particulars in greater detail. The Create Job Screen gives users all of the options to create a job. The Advanced Search Screen provides all the parameters to search the database. The Preferences Screen provides all of the areas where the user may customise the system's interface. The View Job Screen allows users to view a job in greater detail, change a job's status, create comments and subtask a job.
Database
A relational database is used to house all of the system's data. The database has been designed to allow for fast searching and updates.
Content Management and Security
Since the system is web-accessible and will be mult-user capable in future releases, a security model has been implemented into the initial design. This was accomplished by using a content management system, which funnels all web traffic through a centralised security chokepoint. Security is provided for all content, including images.
Object-Oriented Design
The system was designed and developed using Object-Oriented principles. This allows the system to be extensible and scalable and provides the framework to build future functionality.