Timeline for Senior project environment selection
Current License: CC BY-SA 2.5
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2011 at 8:47 | comment | added | Oliver Weiler | I've done somthing similar in a project with 7 people and I can assure you this can be done in Java(Swing) with decent performance. | |
| Apr 5, 2011 at 8:16 | answer | added | Joonas Pulakka | timeline score: 2 | |
| Apr 5, 2011 at 5:15 | answer | added | Corey Sunwold | timeline score: 1 | |
| Mar 30, 2011 at 19:49 | answer | added | umlcat | timeline score: 0 | |
| Mar 30, 2011 at 19:45 | comment | added | umlcat | I think "project technology" or "project framework" sounds more clear. | |
| Mar 30, 2011 at 4:52 | answer | added | kevin cline | timeline score: 1 | |
| Mar 30, 2011 at 2:32 | answer | added | Sjoerd | timeline score: 2 | |
| Mar 29, 2011 at 20:31 | comment | added | JB King | How well have you nailed down what it is you are building, what features you'll need and what methodology you are using to build it? That would be my initial question back. | |
| Mar 29, 2011 at 19:58 | comment | added | Seregwethrin | @Jeffrey, you have your points. But everything has a starting point. No company built with enterprise level products at the beginning. I just want to choose the best path to reach the success. I know it's hard to achive our goal, it may be unlikely, but with the right steps I want to increase that chance and I'm willing to give it a try. I have nothing to lose, except gainig more experience. | |
| Mar 29, 2011 at 19:51 | comment | added | Seregwethrin | @David, I'm not saying we will finish them all. We made a priority list and those features will be implemented first. If customers like the software and buy it, surely there will be more people on the team because then we could pay for the work. After everything that we thought, analyzed, and gathered could be implemented, of course there may be changes. We may be students, we may be inexperienced, but we can measure our path as well. | |
| Mar 29, 2011 at 19:46 | comment | added | user1249 | Agree. Do not go for a full product. Go for a proof-of-concept implementation, and then decide if you can raise funding when you've got your grade | |
| Mar 29, 2011 at 19:46 | comment | added | Jeffrey | You're mentioning fears about speed because it's a "really big project" and are looking for experience from "huge software" developers - but that really isn't what this is. It's a school project developed by three people - not exactly enterprise level. You'll still need to watch out for a slow app due to bad code design, but you shouldn't simply rule out Java because of a "slow GUI". You won't have that kind of code bloat. | |
| Mar 29, 2011 at 19:43 | comment | added | David Thornley | With three relatively inexperienced people working for a year or two, you intend to produce an application with more features than Outlook, a very rich and configurable GUI, and industrial-strength reliability? I think you're getting overambitious. I'd pick one thing and do it well. | |
| Mar 29, 2011 at 19:40 | history | edited | Seregwethrin | CC BY-SA 2.5 | edited body; added 3 characters in body |
| Mar 29, 2011 at 19:33 | history | edited | Michael K | CC BY-SA 2.5 | some formatting and spelling corrections |
| Mar 29, 2011 at 19:26 | history | asked | Seregwethrin | CC BY-SA 2.5 |