AlexCode Posted July 17, 2005 Posted July 17, 2005 Hi! I kept searching and got no real help... So I decided to start structuring my one of my own. Now here's the deal :) I make the software and you guys give me your knowledge on the matter. Everything you have and know about the applications life cycle (thoughts, knowledge gain over time, specific situations, document templates you have and where you apply them... etc) In exchange I commit myself to: 1. Deliver 2 versions of it: 1.1. A commercial version 1.2. A community version (free with less functionalities) 2. Give a Commercial version to everyone who helps me on this. Again... I don't need coding help, just the already mentioned above. The project will consist, for now, on: - The MSF methodology, combining both Waterfall and Spiral models. - Programming language independent. - Will be able to manage teams and stand-alone developers, including: - Occupation time - Skills by area (programming language, database engines... etc) - Grades (every team and/or person will have a grade at the end of each project, so an average can be calculated for each) - Documents management - Every document created can be stored as part of a project inside the application (Word, Visio, Excel, XML, plain text... whatever) - A simple clients database will also be available - Enabling the ability of project associations with clients... creating historics per client and such analysis. - Adding the project quotation(s) sent to the client - As for the programming helpers, I think some code snippets and some areas do document thoughts would be nice for now. - A bug reports and solutions repository (keeping track of who reported it and who solved it, and how!) - Implementation dates, per client, and version tracking also per client (so we know witch version each client have). I think it's enough for now. I just want you guys to have an idea of what coming up... Give me some feedback on this ok? Thanks, Alex :p Quote Software bugs are impossible to detect by anybody except the end user.
mskeel Posted July 18, 2005 Posted July 18, 2005 This is a HUGE task. Good luck to you. There are a lot of tools out thre already that do most of this sutff -- BUT, it is often times difficutl to find a truly great tool for certian thigns and it would actually be very useful to bring many of these differnt tools together into a single, userfriendly place. That said, I'm able to find tools that do some things very well: CM/Version control and bug tracking. for CM/Version Control I use CVS and TortoiseCVS. Those are pretty much the defacto standards as far as CM/Version control tools go for an open source (free) windows set up. Bug/Issue tracking is a little more difficult. Nearly everything is web-based and even most of the tools I've found for this are not very good. Take bugzilla, for example. It works fine and certianly gets the job done, but the UI is ugly and confusing. It is difficutl to search, and unweildy to use. It's difficutl for programmers, let alone end-users. Bug Genie is better, but it could still use some help. PLUS all of these tools are necesarily web-based. They require a web server of some kind. FogBugz is another tool that may be worth looking into for bug tracking stuff. I haven't looked at it in depth becuase I can get what I need for free elsewhere. The two big things missing out of the the whole process in my opinion are the no-glory, prequisite tools. I have been unable to find a decent tool (open source or otherwise) for either collaberative risk management or collaberative requirements tracing (where you specify requirements and trace them down to the test that actually verifies that the requirement was met). Those are two things that would need to be studied and implimented for a total process, in my opinion. Now, I've probably rambled on and not actually helped with what you needed help with... If you have more specific questions on the kinds of help you are looking for, post it up and I'll try and zero in on a more specific subject. Plus, I'm sure others have things they'd like to contribute as well. This sounds like a cool project, but be careful not to draw the scope too big. Otherwise you may end up with a half finished, mediocre tool and that is never a satisfying thing. Don't get me wrong, though...this sounds really cool Quote
mskeel Posted July 18, 2005 Posted July 18, 2005 Before I forget... The Software Engineering Institue website will be an excellent resource for you... Quote
AlexCode Posted July 19, 2005 Author Posted July 19, 2005 Hi! Thank you very much for your help. I would only ask you for a better description, or some resources on one thing you mentioned... "The two big things missing out of the the whole process in my opinion are the no-glory, prequisite tools. I have been unable to find a decent tool (open source or otherwise) for either collaberative risk management or collaberative requirements tracing (where you specify requirements and trace them down to the test that actually verifies that the requirement was met). Those are two things that would need to be studied and implimented for a total process, in my opinion." I didn't thought about this but, in fact, is a very important thing. Do you have any support on this? Thanks! Alex :p Quote Software bugs are impossible to detect by anybody except the end user.
mskeel Posted July 19, 2005 Posted July 19, 2005 These are both pretty big subjects, but creating something that will meet most people's needs should not be that difficult. Some risk management resources: Know Your Enemy: Software Risk Management Taxonomy-Based Risk Identification Requirements tracing and management is a HUGE beast. You can find a ton of information looking through the other expensive tools (Rational, DOORS, etc...) and at the wealth of infomation available via CMMI. There was one or two projects on Source forge but they weren't that mature. Quote
samsmithnz Posted July 19, 2005 Posted July 19, 2005 This is probably the biggest project I've ever seen posted on this forum... Good luck!! Quote Thanks Sam http://www.samsmith.co.nz
AlexCode Posted July 19, 2005 Author Posted July 19, 2005 Thaks for the support guys!! I really mean to make this great. I have some good support documents... many thanks. Keep your feedback active. Shortly I'll have a web page for this, where the beta releases will be available for download. I also need some samples of documents (real paper prints templates) that you guys may use in some situations... BAsicly, and for starters, some quotations samples for example (the document we give to the client with all the software functionalities description and price)... Again... Many many many thanks for the support... I'll make it worth! :) Alex :p Quote Software bugs are impossible to detect by anybody except the end user.
AlexCode Posted July 19, 2005 Author Posted July 19, 2005 I have some links to some books: http://www.amazon.com/exec/obidos/ASIN/0750658673/qid=1121787831/sr=2-2/ref=pd_bbs_b_2_2/102-0109725-2078539 http://www.amazon.com/exec/obidos/ASIN/0818689064/qid=1121787831/sr=2-1/ref=pd_bbs_b_2_1/102-0109725-2078539 http://www.amazon.com/exec/obidos/ASIN/0818671947/qid=1121787831/sr=2-3/ref=pd_bbs_b_2_3/102-0109725-2078539 Anyone have anything to say about them? thanks, Alex :p Quote Software bugs are impossible to detect by anybody except the end user.
mskeel Posted July 19, 2005 Posted July 19, 2005 Between the web and a good software engineering book you shouldn't need to buy any stuff dedicated soley to software risk management, though I haven't read any of those books specificly. It is a big subject, but I've found that most of it is just based on your ability to identify things before they become a problem and learn how to deal with them -- in other words, experience. A CMM/ISO 9001 book might be a good thing. That dedicates a lot of energy to software process and software management. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.