Guided Project TH Köln - 0.2: Show some dishes at the homepage or login page

[aburghcap]

Part of the Guided Project at Technische Hochschule Köln - #48

Idea: To get started with our student's OASP project we wanted to extend the restaurant application's homepage and/or login page with an impressive list of some selected dishes - similar to a real restaurant placing a sign at the street with its actual offerings.

After having planned this at the sprint planning last thursday the students send the attached UI designs.

Any comments on that?

Should we place the dishes at the homepage or login page?

[tomaszwawrzyniakit]

It looks good, but i think that only restaurant employees can see this website

[sobkowiak]

Perhaps you could implement a new page for customers, where someone could make a table reservation in the restaurant? Such a dialog could display selected dishes (or even the complete menu). Probably a new use case will be necessary in the restaurant backend.

[tomaszwawrzyniakit]

I think, new page for customers or restaurant menu management will be a nice part of app. Probably menu management will be easier.

[dumbNickname]

Hey,

I would also see those recommended dishes elsewhere. I would rather think about a view that can be displayed on restaurant monitors to show the customers what are the dishes of the day or some recommended ones. Something like a nice carousel would be enough.

When it comes to the design of proposals, personally I like the second one most. Nevertheless, I agree with szendo that those nice designs do not fit the business requirements. It should be clear who is supposed to use the app. Current state of the app suggests that it is designed for employees. There are still many things missing and some of the existing views are not so exciting, so I would consider to fulfill existing implementation needs instead of adding new business requirements.

Cheers, Bartek

[aburghcap]

Greet to see your comments on this. Please let me comment on this.

As stated in #48 the idea of the Guided Project of TH Köln where this issue belongs to is to extend the existing restaurant application with some eye-catchy features in order to convince customers and colleagues of using OASP4JS in projects.

As our business goal regarding the restaurant app we plan to implement a suggestion mechanism for recipes / dishes. Part of that will be an editor for recipes.

The nice-looking list of dishes that can be seen before login has two goal: it takes little effort and can be implemented in the first Scrum sprint. it would help to make the existing restaurant application more interesting for all visitors because it appears without even having a login.

Later a list will appear in other pages, but this takes more time and will be implemented in future sprints.

Ok?

[dumbNickname]

I do not mind adding eye-catchy features (just the opposite - I would strongly (:D) recommend to do so), however I would simply like to have those new features useful and aligned with application goal (and imho we really need to find some new ideas for existing views, where we unnecessarily overuse trNgGrid tables). I think that developing proposed components on a separate branch will not be a problem. I really hope that the students will take lots of fun out of this task! :) Later on, one of the admins/architects will decide how they feel about those changes. I am only sharing my personal feelings/opinions :P

Last, small remark: Please design and later implement all the views with interface responsiveness in your minds (what you probably do anyway) . I just wanted to remind that we have bootstrap included in the project, so it would be great to take advantage of its layouting and grid system features wherever possible (this is another thing that is not really visible in our current views).

In this particular case it would be nice to show some view proposals for mobile devices as well.

Cheers, Bartek

[aburghcap]

Hello, agreed that new functionality should fit business requirements and existing functionality should be improved.

Two points on that:

• The students need a bigger goal than to work on issues in our existing dialogs so that they can benefit for their study. Under this constraints we have negotiated to work on new functionality. Our main goal is to demonstrate the potential of OASP4JS.
• Are there any business requirements we can read? My past investigations had brought no result so far.

[dumbNickname]

Hi,

Unfortunately I am quite new to OASP project as well and I do not know the docs very well, moreover I would not be surprised if such business requirements were not defined at all or at least not written down.

But if I can meddle, I would propose to address some of the administration related topics, e.g.

• tables management (adding/removing/setting capacity). Imho, we could also think about introducing data such as tables placement in the restaurant, what would later give some visualization possibilities (something like a small map for new/fresh employed waiters to check where the order should be delivered. It would be also useful for bigger restaurants, but there many rooms might be available, so again some thinking needs to be done about the user interface).
• menu management (adding/removing dishes/setting recommended meals)
• employee management
• admin dashboard with some statistics etc.
• and whatever more an admin would like to do :P

You can also think about some other topics like:

• face recognition login
• food ordering for takeaway
• new redesigned view for the cooks that can be properly used with a screen reader and fully operated via speech recognition or gestures (the cooks would not need to wash their hands just to switch the state of the order)
• collecting data about most popular dishes or other user preferences grouped by some factor like a day of a week in order to provide estimated shopping needs for next weeks or just for monitoring how user preferences change in order to adjust the menu. All of those are just rough ideas from the top of my head, but maybe somebody will extend those with some reasonable, more or less related proposals.

If any new ideas come to my mind I will share those as well.

Disclaimer - I have no power to decide about OASP development direction, I am just sharing my opinions.

Cheers, Bartek

[aburghcap]

After this discussion above and having talked with a leading community member we decided that the students of TH Köln will a) implement the second UI design showing three dishes with big photos, b) integrate this list of dishes into the existing login dialog of the devonfw Restaurant sample application, c) implement one (perhaps random) selection of the three dishes to be listed, c) localize the title "Unsere Topseller".

Further development will form a new additional domain of the restaurant application called Recipes - decoupled from the existing functionality.

[MarcoRose]

Most ideas presented here are very valid and need to be developed in a sustainable way. So far a community-approach for this is missing.

So, yesterday I opened a new WIKI to colloboratively work on a comprehensive vision of the business background of the OASP restaurant example. You will find it in the new Repo: https://github.com/oasp/oasp-business-vision/wiki. Please contribute.

If possible, university activities should be directed to add to the big picture, though this is not imperative. Sometimes a little freedom motivates better.

[aburghcap]

gut!

From: Marco Rose [mailto:notifications@github.com] Sent: Donnerstag, 29. Oktober 2015 14:22 To: oasp/oasp4js Cc: Burghof, Axel Subject: Re: [oasp4js] Guided Project TH Köln - 0.2: Show some dishes at the homepage or login page (#72)

Most ideas presented here are very valid and need to be developed in a sustainable way. So far a community-approach for this is missing.

So, yesterday I opened a new WIKI to colloboratively work on a comprehensive vision of the business background of the OASP restaurant example. You will find it in the new Repo: https://github.com/oasp/oasp-business-vision/wiki. Please contribute.

If possible, university activities should be directed to add to the big picture, though this is not imperative. Sometimes a little freedom motivates better.

— Reply to this email directly or view it on GitHubhttps://github.com/oasp/oasp4js/issues/72#issuecomment-152177340.

---

Firma: Capgemini Deutschland GmbH Aufsichtsratsvorsitzender: Antonio Schnieder • Geschäftsführer: Dr. Michael Schulte (Sprecher) • Jost Förster • Dr. Peter Lempp • Dr. Volkmar Varnhagen

Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

[aburghcap]

STATUS UPDATE: Mostly done.

The authentification necessary for getting the recipe data before a user has logged caused some trouble. The students have fixed this in their fork. Looks as attached when I reviewed it on the student's integration environment.

They are getting to finish this for a pull request into OASP4JS dev during the actuall sprint (to weeks to go)...

[aburghcap]

closed - no further work planned on this