|
First off I would look for an existing package and see if it meets your requirements.
If between you and Sunil Kokkiligadda wrote: few in-house developers
you do not have any architecture skills I suggest getting in a consultant to do the initial work for you, at least the data structures. You are not going to be able to build such an application from forum support.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
My rates are pretty competitive if you need some professional help...
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
Can I have a detailed info on the services, in this context, that you can provide and your price?
You can send me a personal email.
|
|
|
|
|
I was being sarcastic.
BTW: you shouldn't put your email address in a post: you'll get spammed.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
tart 
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
It doesn't take a Sherlock level of intelligence to jump on an opportunity like that. (useewhatididthar?)
I personally commend him!
Don't forget to rate my post if it helped! 
"He has no enemies, but is intensely disliked by his friends."
"His mother should have thrown him away, and kept the stork."
"There's nothing wrong with you that reincarnation won't cure."
"He loves nature, in spite of what it did to him."
|
|
|
|
|
Hi sunil,
Back end plays major role in any application. So while you are developing the Employee Portal ,take help from the experts and start learning from it.
Hope you will be good DB Designer.
Regards,
Srinivas
|
|
|
|
|
I currently working on a project in MVC .net and I found my self asking how far is to far for separation of concerns? A little back history. The project I am working on is separated into business logic, data access, and business entity layers. It is a web app that is developed using the MVC pattern so it also has Controllers and Views. We are currently using our business entity objects as our model for this project. But now one of the developers I work with wants to implement view models that inherit from the business entities. 99.9% of the time the view model will just be an empty class that inherits from the business entities. I am against using adding another layer to the app and I want to find out what some other peoples opinions are.
|
|
|
|
|
He says it is easy to code generate and we may use it in the future so why not just do it. To me it add more complexity to the project when 99 percent of the time we won't need the view models. I would rather just create the view models when we need them. The reason he would like to inherit from the business entities is so we don't need to map a view model to a business entity. We could just pass the view model to the business logic directly.
|
|
|
|
|
GateKeeper22 wrote: 99.9% of the time the view model will just be an empty class that inherits from
the business entities.
Presumably there is real business functionality represented by that 00.1% rather than pie in sky whimsy by developer(s) about some nebulous thing occuring in the future.
If no then absolutely not.
If yes then what happens to the funtionality represented by that 00.1% if you don't implement another layer? It is impossible to do or just a bit awkward? If impossible then do it. If just awkward then stick to awkward because nothing is perfect and that is what comments are for.
|
|
|
|
|
On the .1% of the time I add a view model to handle the difference and have a mapper function to copy the data from the business entity to the view model. It has only happened once so I only have one view model. I do it when it is need and the other developer wants to make it a standard an do it all the time even if it isn't needed.
|
|
|
|
|
You don't re-arch a system based on extreme corner cases when work around exists.
There are many real reasons why one doesn't do that for non-trivial applications which a multiple person system always is. Some of the ones that come to mind.
1. It adds complexity which increases maintenance cost.
2. There is no way to eliminate all corner cases.
3. A corner case can document itself but a re-arch requires much more explanation (and back to 1.)
4. The cost of a re-arch is much higher than implementing the corner case.
|
|
|
|
|
GateKeeper22 wrote: I am against using adding another layer to the app and I want to find out what some other peoples opinions are.
What value does it add, and what will it cost?
Good idea = (AddedValue > Cost)
Bastard Programmer from Hell 
|
|
|
|
|
I can't see that it will add any value. It is pretty easy to implement if I do it by inheriting from the business entity. If I do it the way I have been by mapping the view model to the entity it would take more time but not to much. To me it isn't worth the extra work because we aren't really getting anything out of it expect another layer.
|
|
|
|
|
GateKeeper22 wrote: To me it isn't worth the extra work because we aren't really getting anything out of it expect another layer.
Sounds like a good idea to delay it until you do need it.
How much hours (and thus, money) would your co-worker spend on implementing it, and what benefit does he see in having that layer that's worth that cost?
Bastard Programmer from Hell
|
|
|
|
|
He would just add it to code generation so it wouldn't cost anytime. I haven't really gotten a good answer on what benefits it would give us. He just says it would be easy to generate and not take much time to implement so why not do it. To me that isn't a very good answer. I need to see the value that the layer will give us before I implement it. I would rather implement it on a case by case bases.
|
|
|
|
|
GateKeeper22 wrote: He would just add it to code generation so it wouldn't cost anytime.
"Does not cost any time"? So you are sure that it doesn't need maintenance and will not cause bugs?
GateKeeper22 wrote: I haven't really gotten a good answer on what benefits it would give us.
That makes it simple; we can generate a 2Gb data-file with random contents. That doesn't have much benefit either.
GateKeeper22 wrote: He just says it would be easy to generate and not take much time to implement so why not do it.
..because it doesn't add any value to the project, only extra code. That code has to be tested, and not having that extra load of code means that there cannot be any bugs in there 
Bastard Programmer from Hell
|
|
|
|
|
That is a good point about adding more bugs even if it is generated. Thank you for the info. I am adding all of your points to my argument. I am also glad to see that I am not the only one out there that would be against this.
|
|
|
|
|
GateKeeper22 wrote: He would just add it to code generation so it wouldn't cost anytime.
That means something needs to change.
And you suggested that you are adding a layer and I use a lot of code generation and I can't think of a single example where adding a layer is a trivial fix.
GateKeeper22 wrote: He just says it would be easy to generate and not take much time to implement so
why not do it.
Nonsense.
Almost everything in programming is easy. It is the sum of the parts that means that software costs money. Every addition costs money.
Nothing that you have described suggests that this will have any net benefit. It certainly doesn't meet a business need. And it doesn't seem to meet any implementation need. So the other developer is attempting to rationalize some idealized view of how the world should be and ignoring the realities of large scale development.
|
|
|
|
|
That is what I am thinking. We just took a class that had view models in it so now he wants to implement them. I have pretty much shot him down on it and I think the rest of the team is behind me on it. But only time will tell. Posting on this form helped me to realize that I am correct it is just adding another layer when one isn't needed. At least for the project we are currently working on it isn't. In future projects there may be a benefit to using them.
|
|
|
|
|
If the reason is to remove presentation logic from the presentation layer ie sorting, FullName things like that. It sounds like a good idea.
If the reason is because you are using an ORM and this means you can blow away the entities and recreate without losing that 0.1% of logic, it also sounds like a good idea.
Doing it for the sake of it doesn't sound like a good idea.
"You get that on the big jobs."
|
|
|
|
|
sexy girlï¼video for adult ï¼ more than 30 videos.http://sharecash.org/download.php?file=2531204
|
|
|
|
|
In a software for a company, we usually have customers, employees and suppliers in what regards humans.
Therefore a reasonable (meaning a good one) OOP approach would be to have a class 'Persons' with attributes such as name, surname, address etc. and then let the classes 'Customers', 'Employees' and 'Suppliers' derive from the class 'Persons'.
But, on a second thought there is a problem. How do we deal with customers and suppliers which are companies?
|
|
|
|
|
And what if yet another kind of organisation knocks at your door? The government, for example. Perhaps you should get yourself some inspiration from how lawyers deal with different kinds of 'entities'. The real question still is wether or not you are overdesigning, just for design's sake.
And from the clouds a mighty voice spoke:
"Smile and be happy, for it could come worse!"
And I smiled and was happy
And it came worse.
|
|
|
|
|
You could have a base class called Contact which would have properties like Name, Address1, Address2, City, Email etc. Then your other classes would Inherit from this class, with the Employee class just having extra Propeties FirstName and Surname, and concatenating these two to provide the Name property, whereas Customer and Supplier would just use Name as Company Name.
When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
