Mastering Development Software

Architecture of new SW documentation

I hope I picked the proper part of StackExchange to ask the question.

My question is related to designing new SW. Let’s say I work in a medium-sized company that has a core product (SW). Now we want to start with new SW (purpose of the application is different than the core product) with a completely different approach. There is a document with the main features from business point of view. Now I think we should specify a solution and at least not last we specify language, libraries, etc. Am I right? If so, how to do it? I know how to document the last part with UML, use-cases, etc. But how to document that we want SW to be able to run as standalone service, a replicated service in a clound, need of authentication, etc.

Is there any standard, methodology, or something?

Thank you very much

Leave a Reply

Your email address will not be published. Required fields are marked *