When we start of on a project, what are the parameters we need to check before coming to a conclusion on the quantum of architecture we need to define for a project.

Ex Scenarios:

  1. If the project is a simple one, with very few users.
  2. Project is Simple, but Large user base.
  3. Complex Functionality and complex algorithms, but few user base.
  4. High complexity along with a large user base.
  5. Project with Large Data sets.
  6. Enterprise Applications vs. Standalone applications.

My question is, do we have any standard guidelines or checklist which we need to follow while defining a project architecture?

New contributor
Vikram Cirigiri is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

put on hold as too broad by gnat, dagnelies, Christophe, Robert Harvey, Bart van Ingen Schenau Oct 12 at 17:07

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • This is a really open-ended question with a lot of parameters, and doesn't fit the guidelines for this board. You really need to do some research, including on this board, to narrow down the scope of your question to something we can answer. – BobDalgleish Oct 12 at 15:11
  • Thank you bob for your feedback. I understand the question looks open-ended, but we start of on a project, most of the things are generally vague. We have a new customer who has a requirement and we need to start the project. At this stage things will not be clear. As we have defined some guidelines on how to set up the system, do we have any general guidelines which everyone can use to simplify their decision making. If you still think it is too much open ended, we shall remove the question then. Thanks again for your time. – Vikram Cirigiri Oct 12 at 15:19
  • 1
    Your question could just as easily be applied to designing a bridge. "do we have any standard guidelines or checklist which we need to follow while defining a project architecture?" Yes; they're called "building codes." There are a few things like that in software development, like Sarbanes Oxley, but for the most part, no, they don't exist. How do you find out? The same way bridge builders do: by reading books, taking classes and otherwise becoming educated on the subject, and then applying that education to your specific project. – Robert Harvey Oct 12 at 15:49
  • I have just given a talk two days ago (see this slides) with an introduction relevant to your concerns. There is no simple approach to your issues. – Basile Starynkevitch 2 days ago