- Author: Brian Thompson
- Client: Lucas Chumley
"The "Endpoint Profile" page displays a list of all known desktop and laptop computers (aka "endpoints") on the network. This page provides the user "at-a-glance' feedback about: the hostname of each endpoint, the operating system installed on the endpoint, and if the endpoint is currently on the network. By clicking on any of the endpoints the page provides more detailed information about the selected endpoint including: FQDN, IP address, MAC address, Operating System, Processor, and RAM. The user can search for endpoints matching any of these properties."
- List screen that displays the following:
- Hostname of each endpoint
- OS installed on each endpoint
- Network status of each endpoint
- Detail screen that display the following:
- FQDN
- IP address
- MAC address
- OS
- Processor
- RAM
- Search functionality that can match any of the properties from F1 and F2.
sessionStoragewill be leveraged in the browser- MongoDB used to store larger amounts of data (when
sessionStoragebecomes ineffecient)
- Rest API
- "list" endpoint
- Contains data for all endpoints to be displayed
- F1.1 - F1.3 in JSON format
- Unique ID for each endpoint
- "detail" endpoint
- Contains detailed data for a single endpoint
- F2.1-F2.6 in JSON format
- Endpoint IDs will be leveraged to map the detail page URLs.
- Unexposed functionality
- A listener needs to be created to process new connections to a network
- "list" endpoint
The API will be written in Node with the Express framework. Node provides very powerful OS operations out-of-the-box, and is tailored to the ACs for this particular API.
Angular's built in HTTP works well with Rest APIs. Additionally, Angular Material will be used to align Google's "Material Design" best practices.
A NoSQL database will be created when sessionStorage begins to slow down the browser.