dc.contributor.author |
Mungalpara, Harsh L. |
|
dc.contributor.author |
Devmurari, Harshil D. |
|
dc.date.accessioned |
2024-02-20T07:17:43Z |
|
dc.date.available |
2024-02-20T07:17:43Z |
|
dc.date.issued |
2023 |
|
dc.identifier.citation |
Mungalpara, H. L., Devmurari, H. D. (2023). Midwest Machinery. Department of Information Technology Faculty of Engineering and Technology Atmiya University. |
en_US |
dc.identifier.uri |
http://10.9.150.37:8080/dspace//handle/atmiyauni/1323 |
|
dc.description.abstract |
This Report describes all the requirements for the project. The purpose of this research is to provide a virtual image for the combination of both structured and unstructured information of my project ―Midwest machinery‖. The abstract factory pattern provides a way to encapsulate a group of individual factories that have a common theme without specifying their concrete classes.[1] In normal usage, the client software creates a concrete implementation of the abstract factory and then uses the generic interface of the factory to create the concrete objects that are part of the theme. The client does not know (or care) which concrete objects it gets from each of these internal factories, since it uses only the generic interfaces of their products.[1] This pattern separates the details of implementation of a set of objects from their general usage and relies on object composition, as object creation is implemented in methods exposed in the factory interface. |
en_US |
dc.language.iso |
en |
en_US |
dc.title |
Midwest Machinery |
en_US |
dc.type |
Other |
en_US |