Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend
Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend
Ridhima
Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend
Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend
Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend
Pair Design / HTML. Transfer design to layout. Much of this could simply be converting Ideas to HTML. Objective is to get your own STYLE, COLORS, FONTS; NAVIGATION into the site. Establish your VIBE or Groove. Try a couple of prototype experiments and get feedback from similar pair in Crossover.
Pair Prototyping / Thymeleaf. Try using Class objects in Thymeleaf. Most simple Class would be to use String methods (Links to an external site.) and Number methods, (Links to an external site.) more complex is to use your own defined Class include Images or other Media. Objective is to produce a 3 by 3 grid using Bootstrap Grids, Bootstrap Tables, Bootstrap Cards. Try to incorporate into Project or consider as Mini Lab depending on your design. Try changing 3 x 3 to 4 x 4 or other orientation would be showing ability to manage page dynamically.
As you move Issues into review, individuals link Tangible assets to add to the Issue. Those assigned to issue are required to add comments that highlight anything Scrum master should report to Teacher. Videos or previews prior to 1 v 1 event are HIGHLY encoraged.
At close of Sprint and each week update README with links to issues completed, it is HIGHLY suggested to use table to display Issues with highlighting descriptions. Time box the week or sprint in README as a section declaring Sprint and dates as section Header.
Designer. Wire Frame (at least three theme pages, team mini-labs, and about)
on our website page
Technical Lead. Coordinate brain write session, after preliminary wire frames, make sure you capture technical complexities as an output of this exercise (input, saving data, comments, visual actions, animations, ...)
Navigators. Capture or build highlight of Ideation in README.md, this allows ideas to persist with Project, Make sure that work from Developers works to expectations (testing, suggestions for improvement)
Our idea is to create a website that would be a to do list or planner for students in order to organize their tasks and their schedules. We wanted to help them organize their lives and keep them on track. We are planning on having different features such as notifications that would alert them of future tasks that need to be done, also a calendar that would list the tasks, and a login page that would require the user to create a username/password in order to enter the website.
