![]() Each vendors will need to be given a unique number, and we'll need to store the vendor number for each asset. We need to have a list of vendors, because we typically obtain several assets from each vendor. The default method is "Not Applicable" because some types of assets are not depreciated. It must be possible to change useful life for individual assets. The default useful life for each type of depreciation is 5 years. The new system must implement various techniques for calculating depreciation. The way depreciation is done effects taxes and financial statements. Procurement Methodĭepreciation is the accounting term for writing off an asset's value over its useful life. This refers to the method we use to obtain the asset. What do you mean by "procurement method"? "Disposed" is for assets that the business has sold or discarded. "Expired" is for assets that the business still has but no longer uses. "Missing" is for assets that were not found the last time an audit was done. "In Use" is for assets that are currently being used by an employee or department. "In Store" is for assets that are kept in storage and allocated as needed, for example printer cartridges. "On order" is for assets that have been ordered but have not yet arrived. Product Typeīusiness impact is a way of indicating how important the asset is to the company. Product type "Software" is particularly important, because we need to track additional information for software. We need to be able to maintain the list of product types. We already covered locations and departments when we talked about business organization. The new system must store the product name, product type, manufacturer name, vendor name, procurement method, date obtained, cost, the business impact of the asset, the state of the asset, depreciation method, and the location and department it was purchased for. We can use a simple sequential number (1, 2, 3) as the asset number. The first thing that comes to mind is a unique asset number. What is the basic information that must be recorded for all assets? Each asset is of a certain type, and we also have to capture type-specific information. There is a basic set of information that we need to capture for all assets. What are your requirements for tracking IT assets? The company already has off-the-shelf asset management software that can be used for things like that. We don't want to track non-IT assets like furniture. We would like to track tangible IT assets like computers (laptops, workstations and servers), printers, switches, routers and access points. What are your requirements for tracking assets with the new system? Prepare a PDF document named XYZ_ITSD_UI.pdf that contains screenshots of: o Justinmind XYZMainForm similar to the above screenshot (list all the screens on the left and show the onClick event details for the Employees button/link on the right) o Simulate your prototype and take exactly one screenshot for each screen in your prototypeįOLLOWING ARE THE INTERVIEWS REQUIRED FOR MAKING THE PROTOTYPES ((ONLY NEED ON THE FOLLOWING THREE CATEGORIES)) Prefix the screen title of all screens with XYZ (e.g., XYZ Information Technology Service Desk) Prefix the name of your screens with XYZ (e.g., XYZMainForm, where X, Y, Z are the first letters of the last name of each team member). ![]() You can use a "switchboard" form like the one below as the main form, or use another approach to navigation that you prefer. This is a systems design course, not a web design course, so plain but professional forms with the necessary inputs are sufficient. Layout and align labels, inputs and buttons/links in an orderly fashion. Implement navigation so that a person who clicks on the Justinmind Simulate button can click back and forth through all of the forms. For list boxes and select lists enter at least three demonstration/example values. Enter demonstration/example values for all inputs. input text field, list box, check box.) for each input. Be sure to include all necessary inputs for each form. Model the forms listed in the assignment 2 marking scheme and shown in the screen capture below. See the interviews in the ITSD case study to find out what needs to be captured for each form. The goal is to create wireframe mockups of the main web forms in the application. Use Justinmind to create a user interface (UI) prototype for the Information Technology Service Desk (ITSD).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |