I ended up adding some methods to my Ticket class so that I could get some of the information off a ticket when I was producing the report. I ended up with the two constructors, getClient, getAgent, getProblem, getTicketID, toString, and equals as methods in the Ticket class.
In the TechSupportSystem class I ended up with the following:
- the constructor
- getDate
- getFileNames
- readTickets
- readOneTicket
- readAgents
- readOneAgent
- main
The time stuff is a little confusing. Here is an example.
Say that the client is a Basic level client and his request came in 50 minutes ago. We have promised to fix problems for Basic clients in 60 minutes so we only have 10 minutes left. Say that we assign the ticket to Brandon who averages 10 minutes per machine. In that case we can project that the request is on time. But if we assign the ticket to Dee who averages 20 minutes per machine, then we can project that we are 10 minutes behind schedule.
When you are assigning tickets to agents, you will always have one agent who handles PCs, one who handles Macs, and one who can handle anything. Just match the client's system to the specialty of the agents. Assign PCs to the PC agent, Macs to the Mac agent, and all others to the agent who can handle anything.
Keep working. To make the wisest use of your time, write the easy classes first and then work on Ticket and TechSupportSystem. I found it useful to have the text files open in TextPad along with the Java files I was working on. I also compiled and tested as I worked. Saving compilation and testing until the end is just asking to be frustrated beyond words.
No comments:
Post a Comment