Agile Walk Through - Free Beta

Describing project design

Start with project outline

You can start doing your project design from creating requirements or views, depending on the appoach you choose (i.e. interfaces first or requirement scenarios first). Most likely, some of the requirements you add will be described with sufficient details level, and others - just mentioned. You will be able to distinguish which of them don't have sufficient explanation by yet by giving them draft state so that won't clutter your project plan.

  • Create-requirement

It's possible to add connected entities when creating requirement or view. If those entities (e.g. connected views during creation of the requirement) don't exist, they will be automatically created. Requirements created from view form will get draft state after creating. This gives you possibility to quickly outline skeleton of the project and fill it with the "flesh" later.

  • Create-requirement-defined-views

Ensure coverage, fill gaps in structure

The main ways to check if project design description is sufficient enough is to check coverage and density of definitions.

  • Coverage can be checked by overviewing requirements and views and finding the parts you should pay more attention to:
    • Firstly you can view the hierarchy of requirements with chosen depth, making sure that there are sufficient number of requirements for all areas,
    • Next you can skim through the hierarchy of views (sitemap for a website) to be certain that there are user-interface means for all necessary interactions with users,
  • Density of definitions helps to find areas which were covered in requirements or views and were missed in requirements or views respectively:
    • By checking views you can make sure that every view is defined by some requirements, and if you found a view with no connections to requirements is clear sign of missing connections to existing requirements or even missing requirements,
    • It is also helpful to check the completeness of views by checking references from requirements. Going through requirements list we check how many defined views every requirement has to make sure that it's represented in UI (if necessary).
  • Views-list-with-definitions

Update whenever needed and keep people informed

You can update design entities any time during analysis phase and it's recommended to update them even during the development phase if some new relevant information emerges or becomes available.

Copyright 2007-2010 Agile Walkthrough