.net - How should I document an existing system -
I started with a sole responsibility for a large job (ISH) financial application. It has approximately 800 stored procedures, 120 SQL server tables and 18 net projects about 1200 code files. And no document except in line comments in the code.
As I am improving the bug and adapting to the data, I want to document the document I am looking for.
The main thing I'm interested in is what happens after the user does (for example, presses a button to upload) how the data changes and how to make that change. The methods / procedures are called in such a way that if a bug is seen by users later, then I can quickly see the path taken through the codes / tables, what should I use this document? Is this a UML use case or sequence diagram? Or something else?
Any ideas are welcome Richard
"Let me record it What is the use of a UML for a case or sequence diagram? "
Both.
User experience is a use case. Let's character and text to describe the user's interaction. You can use state charts or sequence diagrams to provide details, but usually it is a waste of time. Words will be for this.
The implementation sequence diagram may be. Often, this is not enough You probably need some class diagram to describe the data model. Actually, you often need two level class diagrams - a conceptual level and a logical level.
You also want a component diagram showing all the pieces and parts and where everything fits together.
Finally, you want to see (logical, process, component, deployment and use case) as a way to separate the document, so this is not a random heap of notes.
Comments
Post a Comment