本文介绍了工具生产和放大器;管理规范/要求(不车票跟踪)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我很感兴趣,如果有任何网站或软件赫然出现在最初的项目来帮助设计,然后将项目的设计随着时间的推移管理为特征implmented,发现错误,等...我的设计将包括要求(功能和安培;非功能性),用例,以及基本的数据库架构设计

最抢手的特点:


  • 可以定义要求,并跟踪其随时间的变化(即如何为1.5版本比1.0有什么不同?)

尼斯对富人:


  • 的规格放在一起时能够与其他项目经理和团队协作

什么我的的寻找:


  • 票务跟踪(JIRA,FogBugz的,等...)

  • 软件版本控制系统

  • 维基(除非它们是内置在考虑需求管理)

感谢。


解决方案

Most requirement management tools work on textual and diagrammatic end artifacts. For version control, I prefer to use a DVCS like Mercurial. How ever the tool must provide traceability.

I have used Rational tools and many others and my personal experience has not been very good at all. I have spent more time dealing with the tool than using it for other productive means.

Some of the products that caters for this requirement:

  1. Rational Requisite Pro and IBM Rational DOORS (heavy, costly and not to my liking)
  2. Web based requirement management tool: django-req
  3. A promising free opensource tool rmtoo

There are various design documentation tools that targets specific type of design and outputs different design artifacts. Say Entity Relationship Tool. You will have to check out what you need.

UML tools are very helpful and are the good way to document use cases.

  1. UML based diagramming tool yED.
  2. A UML based modelling tool StarUML
  3. This is my favourite : argouml

People can get creative with the tools they use for design purposes.

  1. Using mind map
  2. Uml is still a prevalent design tool
  1. SQL Designer does a good job
  2. Check out the free : dbdesigner4
  3. MySql Workbench
  4. SQL Power Architect is very promising.

There are plethora of tools that can do project management including the MS tool that you mentioned. You only need to search them in google.

For collaborative software development, there are many was like google code, bitbucket , collabnet ...

这篇关于工具生产和放大器;管理规范/要求(不车票跟踪)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-27 08:31