此頁已歸檔，不再被更新。

我們已經停止提供這種個產品。

AppLife DNA

Manage software requirements and author specifications throughout the life of your application as part of an iterative process.

由以下開發商製作:Kinetic Jump Software
ComponentSource 開始代理銷售的日期:2007年

AppLife DNA 的螢幕截圖

AppLife DNA

AppLife DNA helps you focus squarely on identified requirements, write iterative functional specifications, and effectively communication change over the duration of your project. With AppLife DNA, you can rapidly produce a “living” requirement specification document on-the-fly during any stage of your application development project. AppLife DNA advances iterative software development by transforming requirements analysis and specification authoring from a task to be completed, into a continuous iterative process.

AppLife DNA

Requirement Organization in AppLife DNARequirements can be added and organized into a multi-level hierarchy, allowing the user the ability to analyze and visualize project requirements.
Requirement Organization in AppLife DNARequirements can be added and organized into a multi-level hierarchy, allowing the user the ability to analyze and visualize project requirements.
Requirements Organization in AppLife DNAThe inline view displays Requirements and Categories together in an indented format.
Requirements Organization in AppLife DNAThe inline view displays Requirements and Categories together in an indented format.
Requirement Organization in AppLife DNAThe Group and Filter view supports sorting, grouping and filtering on project Requirements. This image shows requirements grouped on the assigned version, sorted on Effort, and filtered to show only high Priority Requirements.
Requirement Organization in AppLife DNAThe Group and Filter view supports sorting, grouping and filtering on project Requirements. This image shows requirements grouped on the assigned version, sorted on Effort, and filtered to show only high Priority Requirements.
Requirements ReportThe Requirements Report provides the means to communicate project requirements with stakeholders. A requirement report can be generated from any requirement view. This report shown is generated from the previous image view.
Requirements ReportThe Requirements Report provides the means to communicate project requirements with stakeholders. A requirement report can be generated from any requirement view. This report shown is generated from the previous image view.
Defining RequirementsRequirements are elaborated on, or Defined, within Sections. For each project version, Section content can be extended and changed, allowing the user to maintain previous iterative work, author multiple iterations simultaneously, and move content between iterations as project priorities change. Sections that are unchanged between versions inherit content from earlier versions.
Defining RequirementsRequirements are elaborated on, or Defined, within Sections. For each project version, Section content can be extended and changed, allowing the user to maintain previous iterative work, author multiple iterations simultaneously, and move content between iterations as project priorities change. Sections that are unchanged between versions inherit content from earlier versions.
Generated Functional SpecificationsThe user can generate a Functional Specifications document for any version within the project. Notice the list of defined requirements, and the See also link. These lists are optionally included during a spec generation, and identify the requirements that the section content elaborates upon, as well as other sections that define any of the listed requirements.
Generated Functional SpecificationsThe user can generate a Functional Specifications document for any version within the project. Notice the list of defined requirements, and the See also link. These lists are optionally included during a spec generation, and identify the requirements that the section content elaborates upon, as well as other sections that define any of the listed requirements.
Comparison SpecificationsChanges made between any two versions or project snapshots can be clearly distributed using a Comparison Specification. Comparison Specifications adorn content changes in a very readable format. Comparison specs can optionally only include Sections that are new or changed, providing context for the changes while minimizing document size.
Comparison SpecificationsChanges made between any two versions or project snapshots can be clearly distributed using a Comparison Specification. Comparison Specifications adorn content changes in a very readable format. Comparison specs can optionally only include Sections that are new or changed, providing context for the changes while minimizing document size.
點按瞭解更多

圖像1/8

Requirement Organization in AppLife DNARequirements can be added and organized into a multi-level hierarchy, allowing the user the ability to analyze and visualize project requirements.
Requirements Organization in AppLife DNAThe inline view displays Requirements and Categories together in an indented format.
Requirement Organization in AppLife DNAThe Group and Filter view supports sorting, grouping and filtering on project Requirements. This image shows requirements grouped on the assigned version, sorted on Effort, and filtered to show only high Priority Requirements.
Requirements ReportThe Requirements Report provides the means to communicate project requirements with stakeholders. A requirement report can be generated from any requirement view. This report shown is generated from the previous image view.
Defining RequirementsRequirements are elaborated on, or Defined, within Sections. For each project version, Section content can be extended and changed, allowing the user to maintain previous iterative work, author multiple iterations simultaneously, and move content between iterations as project priorities change. Sections that are unchanged between versions inherit content from earlier versions.
Generated Functional SpecificationsThe user can generate a Functional Specifications document for any version within the project. Notice the list of defined requirements, and the See also link. These lists are optionally included during a spec generation, and identify the requirements that the section content elaborates upon, as well as other sections that define any of the listed requirements.
Comparison SpecificationsChanges made between any two versions or project snapshots can be clearly distributed using a Comparison Specification. Comparison Specifications adorn content changes in a very readable format. Comparison specs can optionally only include Sections that are new or changed, providing context for the changes while minimizing document size.

Why AppLife DNA?

  • Are you constantly searching through old and inaccurate requirements documents?
  • Do you suffer from ineffective requirements analysis reviews?
  • Do you struggle to effectively maintain requirements as development inevitably demands change?
  • Would maintaining past application context while analyzing and spec’ing new requirements improve the quality of your analysis efforts?

Software projects are naturally iterative. Most industry experts agree on iterative development practices as...

瞭解更多關於AppLife DNA

最新新聞

Kinetic Jump launches AppLife DNA
Kinetic Jump launches AppLife DNA
December 14, 2009新聞稿
Generate functional specifications and/or iterative comparison documents on-the-fly, with a single click.
One software license is required per user includes one year of software maintenance and phone support, Run-time royalty free。

有任何疑問嗎?

Live Chat現在與我們的Kinetic Jump Software 專家即時聊天詢問。

Kinetic Jump Software
作為官方授權的代理商，ComponentSource 可為您提供Kinetic Jump Software的正版授權。
更多關於 Kinetic Jump Software
開發用作業系統
  • Windows 7
  • Windows Vista
  • Windows XP
更多關於相容性

最近獲得的獎項

PublisherPublisherPublisher