locked
design problom... RRS feed

  • Question

  • hi
    i'm bulding an application for my coffee shop

    the app has three major modules
    1.the cash register- insert orders print checks etc.. 
    2.payroll- calculate workers salary
    3. reports

    my app has one dataBase and my design is a 3 tier design
    my question is: should i bulid one DAL(shared) to these modules or build a DAL to each module?
     
    thanks a lot:)


    Friday, March 13, 2009 9:39 PM

Answers

  • Hi Elad_me,

    rom your query , You need build your application using three ier Appliction architecture . Need to have separate layer of the dal layer. Do not use sql query inside the dal layer, use stored procedure inside the dallayer.  Use a separate project for sql report . The cash registerand payroll functionality must be included inside the same dal layer.  The functionality can separated in various class files inside assembly dal layer. 

    Some Programming Suggestion :

    • Following good industry coding standards
    • Proper documentaion of the code that you write. 
    • You need to implement the logic in such that reduce the lines of code to such same funtionality.
    Some Design Suggestion

    • You need to have good UML design of your entire modules.
    • Make design in such a way that it is very fexible to added more features to the existing design.
    • Strict adhere to software development methodoldy like SDLC or alige , your choice.
    Hope that this will you out.

    Regards,
    PHIJO MATHEW PHILIP.
    phijomp@gmail.com


    PHIJO MP
    Saturday, March 14, 2009 8:08 AM
  •  I would imagine you could buy a COTS (Commercial Off The Shelf) solution to fullfil your requirements. 

    However, if you need to build a custom solution and you are using Sql server to store data, I would suggest the following;

    1. Entity Framework for Dal
    2. Sql Server Reporting Sevices for reports

    I think splitting the project into the sub-systems as you have is logical.

    Therefore, to answer your question I would be inclined to build a dal for each sub-system.  Even if it is manageable as one project today, it will probably become too unweildy as it grows.

    Hope this helps.
    Pl mark as answer or helpful if you found this useful
    Saturday, March 14, 2009 8:59 AM

All replies

  • Hi Elad_me,

    rom your query , You need build your application using three ier Appliction architecture . Need to have separate layer of the dal layer. Do not use sql query inside the dal layer, use stored procedure inside the dallayer.  Use a separate project for sql report . The cash registerand payroll functionality must be included inside the same dal layer.  The functionality can separated in various class files inside assembly dal layer. 

    Some Programming Suggestion :

    • Following good industry coding standards
    • Proper documentaion of the code that you write. 
    • You need to implement the logic in such that reduce the lines of code to such same funtionality.
    Some Design Suggestion

    • You need to have good UML design of your entire modules.
    • Make design in such a way that it is very fexible to added more features to the existing design.
    • Strict adhere to software development methodoldy like SDLC or alige , your choice.
    Hope that this will you out.

    Regards,
    PHIJO MATHEW PHILIP.
    phijomp@gmail.com


    PHIJO MP
    Saturday, March 14, 2009 8:08 AM
  •  I would imagine you could buy a COTS (Commercial Off The Shelf) solution to fullfil your requirements. 

    However, if you need to build a custom solution and you are using Sql server to store data, I would suggest the following;

    1. Entity Framework for Dal
    2. Sql Server Reporting Sevices for reports

    I think splitting the project into the sub-systems as you have is logical.

    Therefore, to answer your question I would be inclined to build a dal for each sub-system.  Even if it is manageable as one project today, it will probably become too unweildy as it grows.

    Hope this helps.
    Pl mark as answer or helpful if you found this useful
    Saturday, March 14, 2009 8:59 AM