Grocery+Store+Object

Submitted by: Submitted by

Views: 634

Words: 325

Pages: 2

Category: Literature

Date Submitted: 03/27/2011 03:32 PM

Report This Essay

Deliverable Length: 5-7 Paragraphs diagrams and code c# see attached

You are deep in thought after spending many weeks developing a grocery store software application. You think about all of the things you have been coding for, and you realize there are many commonalities in the code you have been writing. You start to think about that Product class that all of your store items inherited from, and you realize that you never want to create a generic product. Similarly, you realize all of your store items have common behaviors like reordering, sorting, and searching. You think about all of the concepts you have been learning. In an insightful moment, you realize that all products have an internal object type of label that you only want to be created when a store item object exists. To your surprise, you see a perfect opportunity to apply all that you know about inner classes, abstract classes, concrete classes, and interfaces. You want to use best practices, so you define and encapsulate these objects to the best of your ability.

You have been tasked with a challenge to perform a feasibility study for a redesign of an existing grocer’s application. Your task is to evaluate any grocery store and determine how you will design a system that allows for the management of the items in the store. For each real-world object, you will need to create new classes that you observed as being necessary for your application. You demonstrate your ability to apply your object-oriented knowledge as you create at least one inner class, abstract class, concrete class, and interface that applies to this scenario.

Your deliverables for this assignment are one class diagram highlighting your solution combined with a Word document containing the code needed to accomplish this object model. Your solution should contain a minimum of four parts including one of each of the following:

inner class

abstract class

concrete class

interface