<commit_before>Development Workflow
====================

Having described the fundamental concepts of Yii, we show the common
workflow for developing a web application using Yii. The workflow assumes
that we have done the requirement analysis as well as the necessary design
analysis for the application.

   1. Create the skeleton directory structure. The `yiic` tool described in
[Creating First Yii Application](/doc/guide/quickstart.first-app) can be
used to speed up this step.

   2. Configure the [application](/doc/guide/basics.application). This is
done by modifying the application configuration file. This step may also
require writing some application components (e.g. the user component).

   3. Create a [model](/doc/guide/basics.model) class for each type of data
to be managed. Again, `yiic` can be used to automatically generate the
[active record](/doc/guide/database.ar) class for each interested database
table.

   4. Create a [controller](/doc/guide/basics.controller) class for each
type of user requests. How to classify user requests depends on the actual
requirement. In general, if a model class needs to be accessed by users, it
should have a corresponding controller class. The `yiic` tool can automate
this step, too.

   5. Implement [actions](/doc/guide/basics.controller#action) and their
corresponding [views](/doc/guide/basics.view). This is where the real work
needs to be done.

   6. Configure necessary action
[filters](/doc/guide/basics.controller#filter) in controller classes.

   7. Create [themes](/doc/guide/topics.theming) if the theming feature is
required.

   8. Create translated messages if
[internationalization](/doc/guide/topics.i18n) is required.

   9. Spot data and views that can be cached and apply appropriate
[caching](/doc/guide/caching.overview) techniques.

   10. Final [tune up](/doc/guide/topics.performance) and deployment.

For each of the above steps, test cases may need to be created and
performed.

<div class="revision">$Id$</div>
<commit_msg>Fixes issue 1468<commit_after>Development Workflow
====================

Having described the fundamental concepts of Yii, we show the common
workflow for developing a web application using Yii. The workflow assumes
that we have done the requirement analysis as well as the necessary design
analysis for the application.

   1. Create the skeleton directory structure. The `yiic` tool described in
[Creating First Yii Application](/doc/guide/quickstart.first-app) can be
used to speed up this step.

   2. Configure the [application](/doc/guide/basics.application). This is
done by modifying the application configuration file. This step may also
require writing some application components (e.g. the user component).

   3. Create a [model](/doc/guide/basics.model) class for each type of data
to be managed. The `Gii` tool described in
[Creating First Yii Application] (doc/guide/quickstart.first-app#implementing-crud-operations)
and in [Automatic Code Generation] (doc/guide/topics.gii) can be used to
automatically generate the [active record](/doc/guide/database.ar) class
for each interested database table.

   4. Create a [controller](/doc/guide/basics.controller) class for each
type of user requests. How to classify user requests depends on the actual
requirement. In general, if a model class needs to be accessed by users, it
should have a corresponding controller class. The `Gii` tool can automate
this step, too.

   5. Implement [actions](/doc/guide/basics.controller#action) and their
corresponding [views](/doc/guide/basics.view). This is where the real work
needs to be done.

   6. Configure necessary action
[filters](/doc/guide/basics.controller#filter) in controller classes.

   7. Create [themes](/doc/guide/topics.theming) if the theming feature is
required.

   8. Create translated messages if
[internationalization](/doc/guide/topics.i18n) is required.

   9. Spot data and views that can be cached and apply appropriate
[caching](/doc/guide/caching.overview) techniques.

   10. Final [tune up](/doc/guide/topics.performance) and deployment.

For each of the above steps, test cases may need to be created and
performed.

<div class="revision">$Id$</div>

{'fraction_non_alphanumeric': 0.089179548156956, 'fraction_numerical': 0.007134363852556481, 'mean_word_length': 4.434108527131783, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4415252', 'n_tokens_mistral': 1208, 'n_tokens_neox': 1118, 'n_words': 510}