GithubHelp home page GithubHelp logo

maxpatiiuk / eecs-448-pixelland Goto Github PK

View Code? Open in Web Editor NEW
2.0 2.0 1.0 10.16 MB

A Canvas-based walking & building simulator

Home Page: https://maxpatiiuk.github.io/eecs-448-pixelland/eecs-448-project-3/

License: MIT License

JavaScript 85.32% HTML 6.19% CSS 8.49%

eecs-448-pixelland's Introduction

Note: my GitHub username recently changed from @maxxxxxdlp

Hi there!

Hi! ๐Ÿ‘‹

I'm Max.

LinkedIn โ€ข Twitter โ€ข Instagram

Find beauty in simplicity

eecs-448-pixelland's People

Contributors

austin-ng105 avatar dependabot[bot] avatar maxpatiiuk avatar nathanrdodson avatar snmcmillan avatar zachmccrayku avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

Forkers

nathanrdodson

eecs-448-pixelland's Issues

Describe software architecture

Within the context of your chosen design paradigm, describe the software architecture
of your prototype (250-350 words โ€“ 5%).

Identify design patterns

Identify the design patterns you used in your design and explain how you applied them
(250-350 words - 5%).

Create UML diagrams

Use one or more of the UML modeling diagrams to design your prototype (5%).

Add a test suite

Test Suite (20%)

  • Must add a one-click test option in your final product
  • Prints to screen, console, or file the summary of test suite being ran and the results of those tests
You should run a suite of tests to verify the core functionality
You are not required to test API, libraries, or other code you didn't write
Recall, writing every possible test isn't feasible.
Write smart tests for the essential functionality of your project

Make movement speed dynamic

Make different surfaces change movement speed (shallow water slows you down. deep water blocks you completely)

Add details about time estimate

Estimate of person-hours for completing the project (5%)

Provide the details of how you arrived at the estimate (e.g., LOC, using the Agile user story method where Projects 1, 2, and 3 represent your inventory of projects)

Prepare video demo

From the project requirements:

Your team will present your project in a video lasting between 8-10 minutes followed by 5 minutes of Q&A on the date list below. The first team listed will present first, the second team will present second, etc.

  • Monday, November 22, 2021 Teams (4-6)

What the video should cover?

  • Project Description (no more than 1 minute)
  • Demonstration of the software (most of the video)

Examples of videos can be found at:

Submit the video in your github repository in a folder labeled "project presentation"

Identify used design paradigms

Identify the design paradigm you (i.e., the team) chose for your prototype and explain
why you chose that paradigm (250-350 words โ€“ 5%).

Add sound effects

Download minecraft sound effects (place/remove block, walking on stone/sand) and integrate them into the game

Undertake a code review

Code Review (500-700 words โ€“ 5%)

  • Undertake, as part of a team activity, an inspection of a medium-size code segment using either a Walkthrough or Inspection as described in the lecture on Software Verification

Document the following:

  • List of faults detected
  • Description of each fault
  • Who was assigned to fix each fault
  • How the fault was fixed

Create a maintenance plan

Maintenance plan (500-700 words - 5%)

How much it will cost to maintain your product for the next year?

Example costs:

  • Costs for hiring developers
  • Monthly or annual fees for servers or domain names
  • Monthly or annual fees for your distribution platform (e.g. app store, XBox live)

Provide details about the time estimate

Provide the details of how you arrived at the time estimate (e.g., LOC, using the Agile
user story method where Projects 1 and 2 represent your inventory of projects)

Document the requirements for the prototype

Use one of the Requirements Engineering artifacts to document the requirements of your
application and identify which requirements you intend to include in the prototype.

Hotkey to cycle through map colors

On the standard Pixelland rainbow world, there could be a hotkey (ie, Space) which would cycle through different color variations and re-render the map as such.

Add texturepack support

Add ability to change game's textures. E.x: minecraft, terraria, stardew valley, monochrome, dungeon

Explain code integration strategy

Describe how your team integrated code from the team members.
Which Integration Strategy do you think your team used?
Explain why. (250-350 words โ€“ 5%)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.