[PROGRESS] Initial Client Brief

[LiamTownsley2]

The client requests that a software system is designed and developed to track assets within the
company. All asset information should be stored in an online database. It is envisioned that this
database could be used by other company systems in the future and thus descriptive and consistent
naming conventions should be used.

Assets include any hardware being used on the company network. It must be possible to add, view,
edit, or delete asset data. A unique identifier should be automatically generated for each asset. The
client would like the software to automatically get hardware data from the system on which it is
running including system name, model, manufacturer, type, and IP address. Some assets have a
physical sticker with the purchase date, which would be useful to capture. It should also be possible
for a text note to be added, which can contain any extra data the company may want to capture
about the specific asset.

Each asset is linked to an employee who is responsible for it. The first name, last name, and email
address of the employee should be stored. Note that an employee may be responsible for one or
more assets. Employees work within a department, which should also be captured. The departments
within ScottishGlen include finance, human resources, operations, sales, and information
technology.

The system must make data acquisition as easy as possible. It is expected that database
communication will have a minimal response time and that screen refresh time will not delay entry
of data. Clear instructions must be visible to the user who will capture asset data, and a minimal
learning curve is expected (user training time should be less than 30 minutes). The client operates a
Microsoft environment, and the system must be able to run as a desktop application on a Windows
machine.

Todo

• A Hardware Asset Object should be created with the following information: Unique ID, Systen Name, Model, Manufacturer, Type and IP Address. There should also be two optional variables for the purchase date and an extra note. #52
• It should be possible to add/view/edit/delete Hardware Asset Data. #53
• Hardware Asset data should automatically be entered into the database. #54
• Each hardware asset is linked to an employee who is responsible for it. #55

Employee

• An Employee Object should be created with the following information: Unique ID, First Name, Last Name, E-Mail address and department. #56
  The departments are: Finance, Human Resources, Operations, Sales & Information Technology.

The Initial Client brief also sets out the Non-Functional Requirements in #17.

[LiamTownsley2]

double check that the requirements for the initial brief have been met and then ensure change requests are accurate and accounted for within github

[LiamTownsley2]

Initial Client Brief requirements have been met. Issue closed.

This may be reopened should the client state that my implementation does not meet the specifications given.

API:types/hardware-asset