Tag Info

New answers tagged

2

The goals of most companies is to increase the value of their shares, not to make the whole world better by contributing to open source projects and to help other developers by publishing tutorials. What you are doing at work should go in the same direction as the goals of your company. When you: Work on your project, Teach your colleagues, Improve the ...


0

You should be explicit when talking to your team that this is a trade-off between initial time-to-market of a first version of the student site and the total cost of ownership over the lifetime of the system. I have seen a real system which evolved over a decade built out of PHP where clients have a extranet micro-site where they can upload/download ...


4

The real issue in this case is long-term maintainability of two separate codebases vs. a single codebase. Convincing people who do not understand the problem requires persuasion. Does your school have a computer science department? How about a business school or management department? Some internal support from an instructor would be good. In short, the ...


1

I think I have another take on it. The faculty and staff application is working and is in use. Changing it to create a student application has a large risk. I expect that there are few automated system tests for the faculty and staff application. They will likely run on different servers, so that the student application does not slow down the staff ...


0

putting together a new MVC application Some of the problems I am seeing with making this a separate application are: MANY of the views would actually be the same data being displayed. An argument in favo(u)r of a single app. Both the HTML and model code would have to be copied between the solutions - not to mention the unit tests. I ...


6

Clearly those for 2-apps solution may lack experience. Just imagine 'adding this one more field' made twice. Most MVC frameworks allow you to create separate routings for separate users (think of example.com/admin, example.com/student, example.com/professor). This of course makes a separate views, but (important!) you can extract common parts (RoR calls ...


20

The biggest reason against two applications is that you are very likely to have to implement user rights anyway. Presumably you aren't going to allow an advisor to enter notes about students he doesn't advise, or delete important information without uber-admin privilege, or edit information about advisors other than themselves? Once you have this mechanism ...


15

Others on the team think that it should be two completely separate applications because of the complexity of modifying the views based on the authorization level of the user. Really? they don't realise they have to create these views anyway if they made 2 separate applications? How hard is it to put both views into the same application and decide ...


0

For legacy GUI applications you would benefit two ways: Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is ...


0

To problem with this projects is that you don't want to change the code without adding unit tests, but you usually can't and unit tests without changing the code. If your project is like a typical legacy project, than you have large classes with lot of really long functions, without a clear role. My strategy is the following: Try to identify the roles of ...


3

It sounds like Zen philosophy but the simple answer is "Be the Computer". Let me tell you a story to explain what I mean... When I was a kid an adult friend/mentor logged me into a mainframe computer at his college to play a text-based game called "StarTrek" using a teletype printer with roll-feed paper (CRT monitors were rare back then). I fell in love ...


5

Doing use-cases for an existing manual system is difficult because use-cases require a "system". Where are the boundaries of the "system" in the manual system? If you want your work to be relevant to your planned automated system then you should choose the part being automated as the "system". In which case, both the manual and automated systems should have ...


2

When looking at a system that is going to be (partially) automated, what is considered part of the system (old or new) and who the actors are depends on the scope of the automation project. To take your library example and a project to automate the lending administration. In the non-automated system, the librarian (who records when a book has been borrowed ...



Top 50 recent answers are included