Skip to main content

Stack and Queue Implementation with JUnitTesting according to UML

Objectives:

After completing this assignment the student should be able to,

  1. Write concrete classes that implement Java Interfaces according to specifications given in UML.
  2. Implement a last-in-first-out (LIFO) stack class in java.
  3. Implement a first-in-first-out (FIFO) queue class in Java.

Requirements:


For this assignment you are given the following Java source code files:
CSE205_Assignment03.java (This file is complete – you will make no changes to this file)
IStack.java (This file is complete – you will make no changes to this file)
IQueue.java (This file is complete – you will make no changes to this file)
MyStack.java (you must complete this file)
MyQueue.java (you must complete this file)
The specifications for the files are given below (including the UML diagram on the following page).
Special requirements:
Both MyStack and MyQueue Classes

 http://bit.ly/Hjsoft-JavaHelp

  • size method
    1. Returns the number of items in the collection.
  • empty method
    1. Returns true if the size of the collection is zero; otherwise returns false.
  • peek method
    1. Returns the item at the front or top of the collection.
    2. Throws a NoSuchElementException is the collection is empty
  • 4. search method
    1. Returns the (zero-based) number of elements from the front or top of the collection where the specified item is first found. Returns -1 if the item is not found in the collection.
  • MyStack
    1. You must implement the IStack interface as either a linked list or an array list (refer to your work from Assignment 02). Your MyStack must not be arbitrarily limited to any fixed size at run-time.
    2. push method
    3. Insert the new item at the top of the stack.
    4. pop method
    5. Remove and return the item at the top of the stack.
    6. Throws a NoSuchElementException is the stack is empty
  • MyQueue
    • You must implement the IQueue interface as either a linked list or an array list (refer to your work from Assignment 02). Your MyQueue must not be arbitrarily limited to any fixed size at run-time.
    • add method
      1. Insert the new item at the back of the queue.
    • remove method
      1. Remove and return the item at the front of the queue.
      2. Throws a NoSuchElementException is the queue is empty

CONTACT DETAILS

For any other questions or other tasks please feel free to contact me
via email: mhassnainjamil@gmail.com
via WhatsApp: +92-324-7042178
via skype: hassnainjamil1

Comments

Popular posts from this blog

Are you looking for the article. Congratulations! you are at the right place

Please comment on this post for Article requests Kindly Write Following things in comment: 1)  Name 2)  Article Link 3)  Your Email Id We will process your request as soon as possible. Note: Share this post with friends to help them.

Human Physiology by Stuart Ira Fox [PDF] (12th edition) free download

The Zoo Management System - entity relationship diagram & MS Access Database

Zoo Management System - Project Details: You are the employee of a big, worldwide working Zoo Management Company. Your company is responsible for the Zoo management. Your boss thinks it would be a great idea to store all data for each Zoo in a brand new self-developed ZOO Management System. Up to now, the ZOO management company has maps of each ZOO available. Your boss knows that you took a course in introduction on an ERP system, so he asks you if you could help designing such a system. Each ZOO must have the same organizational structure, which should look like this: Each Zoo has a Zoo-Address. Each Zoo has many visitors (Visitor Ticket Process (VTP). Many Zoo-Attractions belong to a Zoo. Module 1: Entity Relationship Diagram Design a ER (entity-relationship) diagram for your ZOO Management System. Use the information provided below with the entities and its attributes. Put the entities in the correct relationship to each other (organizational structure). Module 2: DB Implem...