package-design | 易学教程

Database Guy Asks: Object-Oriented Design Theory?

阅读更多关于 Database Guy Asks: Object-Oriented Design Theory?

问题 I've worked with designing databases for a loooong time, and these days I'm working in C# too. OO makes sense to me, but I don't feel that I have a good grounding in the deep theory of OO design. In database land, there's a lot of theory around how to design the structure of a database, the main notion being normalisation. Normalisation directly steers the structure of a database and to some extent dictates how to arrange entities in a database. Are there any similar concepts behind how to

Visualizing and keeping track of your package development state

阅读更多关于 Visualizing and keeping track of your package development state

问题 What is a good way of keeping track of the state of development and/or visualizing how all your R packages are linked to each other (and its "third-party" dependencies)? I usually try to apply a "divide and conquer" strategy which by now - 5 years down the road - lead to quite some amount of packages with a clear-cut functional scope. But I've reached a state where things have (perceivably) become so scattered that I can't wrap my head around all the dependencies and "where are the lego

Visualizing and keeping track of your package development state

阅读更多关于 Visualizing and keeping track of your package development state

Your thoughts on “Large Scale C++ Software Design” [closed]

阅读更多关于 Your thoughts on “Large Scale C++ Software Design” [closed]

问题 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 last year . Reading the reviews at Amazon and ACCU suggests that John Lakos' book, Large-Scale C++ Software Design may be the Rosetta Stone for modularization. At the same time, the book seems to be really rare: not many have ever read it, and no pirate electronic copies are floating

Your thoughts on “Large Scale C++ Software Design” [closed]

阅读更多关于 Your thoughts on “Large Scale C++ Software Design” [closed]

Reading the reviews at Amazon and ACCU suggests that John Lakos' book, Large-Scale C++ Software Design may be the Rosetta Stone for modularization. At the same time, the book seems to be really rare: not many have ever read it, and no pirate electronic copies are floating around. So, what do you think? MadKeithV I've read it, and consider it a very useful book on some practical issues with large C++ projects. If you have already read a lot about C++, and know a bit about physical design and its implications, you may not find that much which is terribly "new" in this book. On the other hand, if

Is package by feature approach good? [closed]

阅读更多关于 Is package by feature approach good? [closed]

Recently I came across this javalobby post http://java.dzone.com/articles/how-changing-java-package on packaging java code by feature. I like the idea, but i have few questions on this approach. I asked my question but didn't get a satisfactory reply. I hope someone on StackOverflow can clarify my questions. I like the idea of package by feature which greately reduces the time for moving across the packages while coding and all the related stuff will be at one place(package). But what about interactions between the services in different packages? Suppose we are building a blog app and we are

Are there any rules for OOP?

阅读更多关于 Are there any rules for OOP?

Recently I heard that there are 9 rules for OOP(Java). I know only four as Abstraction, Polymorphism, Inheritance and Encapsulation. Are there any more rules for OOP? Seems like what you're looking for are the Principles of Object-Oriented Design . Summarized from Agile Software Development Principles, Patterns, and Practices . These principles are the hard-won product of decades of experience in software engineering. They are not the product of a single mind, but they represent the integration and writings of a large number of software developers and researchers. Although they are presented

Circular dependencies

阅读更多关于 Circular dependencies

I have 2 projects. Project#2 has a reference to Project#1 Now I need to reference Project#2 in Project#1, but vs.net is complaining about a circular dependency. Is there a way out of this? Craig Wilson Absolutely not. Circular dependencies are a indication of bad design. I don't mean to be harsh. There are some ways out of this. 1) You can refactor common code to another project, say Project#0 2) You can fix your design, which is probably the way to go. Uncle Bob has a good article on Packaging Principles which includes the Acyclic Dependencies Principle. http://www.objectmentor.com/resources

Circular dependencies

阅读更多关于 Circular dependencies

问题 I have 2 projects. Project#2 has a reference to Project#1 Now I need to reference Project#2 in Project#1, but vs.net is complaining about a circular dependency. Is there a way out of this? 回答1: Absolutely not. Circular dependencies are a indication of bad design. I don't mean to be harsh. There are some ways out of this. 1) You can refactor common code to another project, say Project#0 2) You can fix your design, which is probably the way to go. Uncle Bob has a good article on Packaging

Is package by feature approach good? [closed]

阅读更多关于 Is package by feature approach good? [closed]

问题 Recently I came across this javalobby post http://java.dzone.com/articles/how-changing-java-package on packaging java code by feature. I like the idea, but i have few questions on this approach. I asked my question but didn\'t get a satisfactory reply. I hope someone on StackOverflow can clarify my questions. I like the idea of package by feature which greately reduces the time for moving across the packages while coding and all the related stuff will be at one place(package). But what about