DETAILED STUDY

Phase DS.1 Detailed conception; functional study

DS.1.1 Purposes

The purpose of this phase is to set up the solution at the logical level

 take all process variants into consideration.

 check the validity of the logical solution

DS.1.2 Realization actions

 For specific developments

 Set up the inventory of the programs (web-applications) and of the functions by program

 Give additional details about the user interfaces

Pages (static and dynamic) and navigation bars models; description and chaining

Users functions (buttons; fields, events and triggered function)

Access mode to the data; preselection screens.

reports and statistics lay-out

 Enrich and complete the Logical Data Model;

define the rules to create, update, delete, archive and consult the data.

consolidate the data model stability to anticipate the possible evolution and the maintenance of the data

improve the data confidentiality and security; set up the users rights and responsibilities.

complete the integrity rules: users rules, business rules

Create the views

 Detail the processes :

 Flow charts

the flow chart describes the conditional functions chaining within the application; the functions should be referenced and described in appendices.

Flow Chart

 Phase Description

the table gives a global overview of the application; the complex functions need being referenced and described in appendices.

Phase Description (for a program of WEB type)
Screen "Introduce an order"
Field / Button / Image	Client / Server	Action or Function	Ref
Customer Name & First Name	-	-	-
Customer Address	Client	Check that the region can be deserved	REF_DELIVER_1
[Details]	Client	Access to the "Order lines detail" screen	REF_DETAIL_1
[Ok]	Server	Check the order; save the order	REF_ORDER_1

 Describe the transactions, i.e. the sets of functions that need necessarily being performed or cancelled all together

This point is especially important in an HTTP application because this protocol provides no native transaction support. Often you will have to collect information during many sequential pages and perform the transaction at the last step.

What is more, it may happen that each online user is not assigned to a singular database transaction because of resource pooling constraints; so you won't be able to use the database-driven transaction support; you will need to manage the transactions programmatically. 

 If necessary, describe the physical distribution of data and processes

distributed database

distributed processes

 For the packages:

 Base yourself upon the differences that you raised between the package possibilities and the requirements and processes set up during the preliminary study:

finalize the specific adaptations analysis

finalize the alternative solutions, mainly at the organizational level.

set up exception solutions for the requirements that do not find a standard solution.

finalize the study of specific complements

"user exits"

Finalize the study of adaptation required from the applications that will be interfaced or concerned.

 In every case : 

 Take all processes into account:

inverse procedure (cancellation, correction)

emergency procedures

closure, start up and migration procedures

backup & restore procedures

control and piloting procedures.

  Materialize the conceptual solution; check the validity of the theoretical solution by applying it to practical cases.

processes: apply them to various samples

data: set up an occurrences inventory (particularly for the parameters table that express the management rules)

Prototypes

Screens designs, reports designs, ...

DS.1.3 Project management actions

 If the realization method is not yet defined, do it now; either be informed of it and adapt it if necessary to the particular case.

 for the packages and subcontracted developments: integrate the customer and supplier methodologies into one specific methodology, applicable to the project.

 use an integrated analysis, realization and maintenance methodology

development tools (Case Tools)

common objects, macros, interfaces, sub-routines

technical documentation, user documentation, operating documentation

 user interface

display and input norms

errors processing norms

reports presentation norms

languages usage norms.

DS.1.4 Quality assurance actions

Check that all requirements find a practical solution: complete the adequacy controls that were already performed during the preliminary study

Note: at this stage, the solution needs being entirely designed; all inventories need thus being exhaustive.

 concerning the functions & processes; it is very important that they are explained in a form that the people representing the users can understand in order for them to be able to validate the designed solution.

 concerning the data

 the Quality Manager should participate to the set up of the integrated analysis, realization and maintenance method.

 care for the general development organization process: releases control and follow-up

  For specific development:

 Check the validity of the solution by alternate control techniques:

entity/function tables, entity-attribute/function tables

 Check that the general functions described during the preliminary study are effectively implemented as a specific function or as a program.

 Check that the solution is coherent.

the analysis method must allow to do this coherence checks systematically.

integration between modules

interfaces

DS.1.5 Phase closing actions

The common result of the 2 detailed study phases, functional and organic, form the Realization Specifications for the next phases: realization and launch.