modeling

I need to model a concrete generic class inheriting from a base generic class. First, see below: ActivityFacade should be implemented this way: public class ActivityFacade : BaseFacade<Activity, int> { } How can I model this in a VS2012 UML class diagram? Looking at the diagram, it is obvious that ActivityFacade inherits from BaseFacade, but what's not obvious is the generic type parameters that it is passing in, namely: Activity and int . You need to add a new binding class ( BaseFacade <Activity, int> ) connect it to your parameterized class ( BaseFacade<T, TKey> ) with a template binding

I have implemented a new statistical model in R and it works in my sandbox, but I would like to make it more standard. A good comparison is lm() , where I can take a model object and: apply the summary() function extract the coefficients of the model extract residuals from the fitted (training) data update the model apply the predict() function apply plot() to pre-selected descriptive plots engage in many other kinds of joy I've looked through the R manuals, searched online, and thumbed through several books, and, unless I'm overlooking something, I can't find a good tutorial on what should go

Are there any best practices (or even standards) to store addresses in a consistent and comprehensive way in a database ? To be more specific, I believe at this stage that there are two cases for address storage : you just need to associate an address to a person, a building or any item (the most common case). Then a flat table with text columns (address1, address2, zip, city) is probably enough. This is not the case I'm interested in. you want to run statistics on your addresses : how many items in a specific street, or city or... Then you want to avoid misspellings of any sorts, and ensure

I didn't find any question that would be this general. Please post whatever you find to be a useful rule for oject-oriented design. There are many, many OOD practices (Google it!) if you had to pick over others I would go with SOLID an acronym for; Single Responsibility Principal Open/closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle I have recommended the Head First Design Patterns book many times. It gives you a good intro to the GoF Design Patterns (a more advanced book that you also should read), but also a good intro to sound OOP

I'm tinkering with some cross-validation code from the PySpark documentation, and trying to get PySpark to tell me what model was selected: from pyspark.ml.classification import LogisticRegression from pyspark.ml.evaluation import BinaryClassificationEvaluator from pyspark.mllib.linalg import Vectors from pyspark.ml.tuning import ParamGridBuilder, CrossValidator dataset = sqlContext.createDataFrame( [(Vectors.dense([0.0]), 0.0), (Vectors.dense([0.4]), 1.0), (Vectors.dense([0.5]), 0.0), (Vectors.dense([0.6]), 1.0), (Vectors.dense([1.0]), 1.0)] * 10, ["features", "label"]) lr =

UML is a standard aimed at the modeling of software which will be written in OO languages, and goes hand in hand with Java. Still, could it possibly be used to model software meant to be written in the functional programming paradigm? Which diagrams would be rendered useful given the embedded visual elements? Is there a modeling language aimed at functional programming, more specifically Haskell? What tools for putting together diagrams would you recommend? Edited by OP Sept 02, 2009: What I'm looking for is the most visual, lightest representation of what goes on in the code. Easy to follow