Wiki.js backup
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 

5.1 KiB

title description published date tags
Ukiyo Personalized Smart Signage w/ Machine Learning true 2019-11-17T00:42:32.210Z <nil>

Ukiyo

Ukiyo

Junction

Status

License


Ukiyo is an encompassing solution to student oriented digital signage, giving both users and owners insights on information that is useful to them.

On the user side, tenants coming or going into the building are provided information on their day, following events, weather and all the smart mirror things.

Once a student gets closer, things change. We are able to identify them (with their permission, of course) and show them personalized information that is more relevant to them, such as their following classes.

However, to the building owners, Ukiyo is a strong data analysis platform, able to capture outlier communities and help them solve problems faster.

Is someone mining bitcoin in their dormitory? Is there a water leak? Are those more common in summer? These questions can be answered automatically by it.


📝 Table of Contents

🧐 Problem Statement

It is useful to design and follow a specific format when writing a problem statement. While there are several options

for doing this, the following is a simple and straightforward template often used in Business Analysis to maintain

focus on defining the problem.

  • IDEAL: This section is used to describe the desired or “to be” state of the process or product. At large, this section

should illustrate what the expected environment would look like once the solution is implemented.

  • REALITY: This section is used to describe the current or “as is” state of the process or product.

  • CONSEQUENCES: This section is used to describe the impacts on the business if the problem is not fixed or improved upon.

This includes costs associated with loss of money, time, productivity, competitive advantage, and so forth.

Following this format will result in a workable document that can be used to understand the problem and elicit

requirements that will lead to a winning solution.

💡 Idea / Solution

This section is used to describe potential solutions.

Once the ideal, reality, and consequences sections have been

completed, and understood, it becomes easier to provide a solution for solving the problem.

⛓️ Dependencies / Limitations

  • What are the dependencies of your project?

  • Describe each limitation in detailed but concise terms

  • Explain why each limitation exists

  • Provide the reasons why each limitation could not be overcome using the method(s) chosen to acquire.

  • Assess the impact of each limitation in relation to the overall findings and conclusions of your project, and if

appropriate, describe how these limitations could point to the need for further research.

🚀 Future Scope

Write about what you could not develop during the course of the Hackathon; and about what your project can achieve

in the future.

🏁 Getting Started

These instructions will get you a copy of the project up and running on your local machine for development

and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

What things you need to install the software and how to install them.


Give examples

Installing

A step by step series of examples that tell you how to get a development env running.

Say what the step will be


Give the example

And repeat


until finished

🎈 Usage

Add notes about how to use the system.

⛏️ Built With

✍️ Authors

🎉 Acknowledgments

  • Hat tip to anyone whose code was used

  • Inspiration

  • References