Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
How to represent a "Produce A" relationship in OOP? I know such one doesn't exist but I want to represent the relationship of an object producing another object. For example, a chicken produces an egg, a musical instrument produces sound. How to represent this relationship?
The UML mechanism for showing that is a dependency relationship with stereotype <<create>>. In general,
<<create>>
Client -----------------> Supplier
More information about dependencies can be found in this Wikipedia article.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I've heard of the concept of "sending" and "receiving" data via an API. "Consuming" data would be "receiving" the data. In terms of "consuming" data, what would be its corresponding opposite term?
Serving
Think of it as the API as a waiter serving your meal, and you consuming it.
In this article the authors use serving as an opposite to consuming: https://stackoverflow.blog/2020/03/02/best-practices-for-rest-api-design/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have realized that most of the problems that I solve on a day to day basis are done via two programming techniques: iteration or recursion.
Are there other techniques out there? Any book recommendations or online references?
the programming techniques that you use to solve the problems can be divided into types of algorithms (not into the loop or technique they use in there program, like you mentioned). some of the methods are..
1. Divide and conquer
2. greedy
3. dynamic programming
you can refer this link to read more..
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
What is a good naming convention for naming linking tables? I have a school project and we are modifying the orig data for the project.
Not sure what language you're going for here, but you can try database naming conventions. This link may help you decide.
http://efsavage.com/blog/posts/database_naming_conventions/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
There is so many option in each programming languages which can be mentioned in the code documentation.
I want to know what are the most important Items which we have to document?
I'd document contracts (this parameter is expected not to be null, this function never returns null, ...) as well as the meaning (this method does that, ...). Besides documenting the API, I'd add comments on pieces of code which are non-trivial but add a significant value to the application (cryptic but real fast, works around a framework bug).
What you document ultimately depends a lor on who will read that documentation...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
not necessary an UML diagram, just a simple way to graphically document the relations between several systems...
the systems can be linked through web services, linked-servers, text files, batch processes, com+ components etc...
I was thinking about a high level map, showing which system is consumming, exposing, resources and by which means...
perhaps a deployment diagram would do, or a completely custom diagram...
what do you use to document this kind of relations?
You can create component dependency diagrams in UML.