We desperately need some organization so it can be searched. Prepared by Gary B. A character alphanumeric field holding the first and last name of the person reporting a service request. What would that look like? The other items are more complex.

The following tables contain the attributes identified from each form and the interview. Another reason is so on continuing problems we can see what was tried before. For things such as RAM, I need to track a quantity, too. Then, we will construct a Context Data Model that graphically depicts each of the entities and the relationships they have with each other. Specify all data types your instructor will specify the target database or allowable set of data types.

A character alphanumeric information value stored in a software configuration record.

case study ctts milestone 4 solution

The primary keys are based on how the user milestons identifies each entity. So we need that tracked. Add the data attributes for each entity. I would say we should have all that data handy in the system. So I should call it equipment instead of PC.

Case Study CTTS – Milestone 05 Data Model

Then we need to have it documented. This is just a spreadsheet that we currently use to keep track of equipment in each PC. For each machine, we should be able to enter any number of components. A system-generated large integer numeric value unique to each service request.


Case Study CTTS – Milestone 04 Data Modeling

What kind of general information do we need to keep on each client? Prepared by Gary B.

case study ctts milestone 4 solution

A time field holding the time a technician finished work ftts a request. These two entities could be combined into one entity, but with their different uses, a case can be made for have two entities. A date field holding the date a service request was resolved. Upload document Create flashcards. I’ll put that on my open issues list to check out.

case study ctts milestone 4 solution

The following tables contain the attributes identified from each form and the interview. You have to think about how we buy and upgrade.

If you buy it as one unit, do you get all the detailed component information and enter it to the columns? I’m glad xolution agree.

Case Study CTTS – Milestone 04 Data Modeling Solution_图文_百度文库

We had also milestons about an automatic resolution mechanism after a tech does work. A date field consisting of the date a technician did work on a request. Plus we would need you to scan the barcode. A character field holding the name of the vendor from whom a component was purchased. So we don’t want to just write over the information of the old ssolution with the information of the new component. Well, I think this new system could eliminate those searches.


So we ought to move away from having specific components as fields. A component that has been checked into inventory A piece of information concerning software configuration for the Client and possibly for a piece of equipment. I type in model number, a description of the item, quantity, date purchased, and the vendor.

That’s where that Check In Inventory use case comes in. But then we would end up with the equivalent of this spreadsheet filled with identifiers. When you scan the barcode, that identifier is entered into the computer just as if someone had typed the identifier on the keyboard. Not the purchase price? This system is about client service requests and client equipment and client configurations.

The identifier is printed just above or below the barcode symbol, so you can actually see what it is.