Methodology and Documentation for ASP.NET MVC Projects

Asked

Viewed 634 times

0

In the company where I work I have always been free to develop the requested applications. I always worked in a unique way despite having a co-worker because, we both developed separate projects.

From next week, I will be working with two assistants and I’m thinking of applying some methodology to develop in small team and in addition, documenting all the applications, something that does not happen nowadays.

Currently working with Asp.Net MVC 4 and C#. What would be the methodology of development / documentation which would be more suitable to this model of mine and, I intend to document the old projects?

Is it interesting to unlock the application layers in MVC and assign each to a team contributor? I don’t see this as a very practical solution, but as I said, I have no experience in team development.

Although it sounds like a question of opinion with several answers, my intention is to receive an indication of a good way forward to apply the best possible practice in my new situation.

c# asp.net-mvc documentation methodology
  • 2

    In fact it is a question whose answers cannot be substantiated without a long discussion. A very cool discussion, I just don’t think it’s valid for the OS format.

  • 2

    http://meta.pt.stackoverflow.com/questions/297/quando-se-deve-colocaro-nome-da-linguagem-no-t%C3%Adtulo Try to find a title that explains your problem in a short sentence, where you’re going. Avoid very generic titles.

  • 1

    Opinion: to) just create the documents that are missing and if you have a clear indication of how they will help from now on (for example, a document explaining how to set up the development environment can be useful and the new team member can create it). b) Invest more in the design and code itself than in documents that explain them. c) Do not split tasks by layers but by resources/features/end-to-end requirements". d) Do not divide tasks, each one has to develop the ability to work on the next priority of the list.

  • 2

    There’s no mention in the question about Revision control... There are already votes to close as "based on opinions", it would not be the case to give more context of the situation-in-question in relation to the workflow-of-software-current?

1 answer

1


I’ll answer a part of your question.

Is it interesting to unlock the application layers in MVC and assign each to a team contributor? I don’t see this as a very practical solution, but as I said, I have no experience in team development.

No. Unlocking layers causes a complication for configuration (packages, Web.config, and so on), in addition to which the IDE does not work very well with this layer separation. For example, if you use the package Dotnetopenauth Entensions, the IDE gets lost and marks errors that do not exist if the configuration is not strictly correct.

Currently working with Asp.Net MVC 4 and C#. What would be the methodology of development / documentation which would be more suitable to this model of mine and, I intend to document the old projects?

It depends on the current working model. There are some development methodologies you can use:

  • Scrum
  • Agile
  • Extreme Programming

For the documentation you can use the standard . NET comment feature.

Browser other questions tagged c# asp.net-mvc documentation methodology

You are not signed in. Login or sign up in order to post.