Infromation gathering
What information do we need to gather? First of all, the manager plans to be the only one to access the database. One of her computer technicians thinks that he and the other technicians would find it useful to have access to the database as well. Therefore, we need to find out if the manager intends to not allow her employees to access data at all, or if they will be allowed to access it but with restrictions, and what those restrictions could be. We also need to know what fields are in the current database, so that we can get an idea of the new database she would like to have built. The manager has also said that she would like to have a reminder set monthly for machine maintenance. We need to know if there is a preferred calendaring software for her purposes (Steltor or Outlook are UNC’s most mainstream choices), and what information she needs in the reminders. Does she just want information about where the equipment is, or would she like information about the software updates and work previously done? She would like an action request system implemented. Sam and I are familiar with Remedy, which is used throughout ATN, and have found it fairly useful for tracking information. Remedy
Constraints on Design: Both the manager and her boss have to approve of the changes. There could be possible confusion about the exact design of the project. The manager feels the need for the system because she is in constant contact with computer users. Her boss might find it useful, but there is a chance he will want to change some things possibly changing the whole idea. The manager has had past designs made for her that has not pleased her and was thrown out. How We Will Record and Organize: We plan to start organizing information by starting with a model of the IOG’s current processes. This initial model will help us breakdown existing problems the manager has. This workflow model can also help determine how many different small projects will exist and where other systems should be implemented. Information gathered during meetings and conversations will be shared throughout with the team members in this group. This will keep everyone updated on what is going on in the project. All drawn models of the project will be recorded using various software applications such as Microsoft Visio and Microsoft Windows Draw 6. These models will be printed out and also saved onto a computer so that the information can be shared. We also need to know if there is any existing database software such as ColdFusion, MySQL, etc., and if we will have to work with that software or if they are open to change. The IOG may already have a variety of software for us to choose from. An employee has said that the IOG is also subject to budget problems, which may prevent us from purchasing any software they do not already have. includes information about a client’s past tickets, current tickets, and tickets are easily reassigned to others. A possible problem with Remedy is that it requires the use of a PID number, and although IOG employees should ha
Some topics in this essay:
PID IOG,
Constraints Design,
Record Organize,
Gathering Plan,
Outlook UNC’s,
Institute Government,
Adair Sam,
Remedy Adair,
ColdFusion MySQL,
Sam IOG,
computer technicians,
iog employees,
access database,
sam responsible,
field added,
database manager,
iog website,
webpage interface,
application programmer,
calendaring software,
Join now to see the rest of the essay!
Approximate Word count = 1251
Approximate Pages = 5 (250 words per page double spaced)
|