Design pattern for chance of few modules in future.

Question

0.00/5 (No votes)

See more:

C#

Dear All,

I received an requirement for an project regarding purchasing stocks [like TV, Mobiles] in huge quantity. The project maintains the record of the stock, warehouse and shipments.
Each stocks will have different work flow, purchase order.
It seems initially 20-25  modules will be there, but after an year there will be adding another 20 modules will be added. 

Query:
What design pattern should follow on scratch of the project?
Where to start with?

What I have tried:

I have not tried anything, trying catch up where to start the project

Posted 20-Feb-16 18:00pm

Mathan_CodeProject

Updated 20-Feb-16 21:18pm

Add a Solution

Comments

Garth J Lancaster 21-Feb-16 0:52am

what is a 'module' ? - it seems like you are defining something/some unit without explaining in more detail what the requirements are. I doubt you have enough information there for people to help you much.

OriginalGriff 21-Feb-16 2:16am

Reply from OP, posted as an answer:

Dear Garth,

Here the modules refers to an product which consists own approval flow, shipments, costing and other operational requirements.
Ex: TV is an product, it purchased from xyz city. The cost, approvals shipments,inventory are maintained by TV section in company.This whole process is considered as Module
Mobile is an another product, but it purchased from another city called ABC.Here, the cost, approvals, shipments, inventory are totally different from TV module.
Hope I make it clear for the term module in project.
Now the company handling 20 products[modules] in this year. They are projecting for the next year 2017 to add up some more modules.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2016-02-20T21:18:00

Solution 2

Start with Software design pattern - Wikipedia, the free encyclopedia[^]. See also related questions on this page.

Posted 20-Feb-16 21:18pm

Richard MacCutchan

Updated 20-Feb-16 21:19pm

v2