PRELIMINARY STUDY

Phase PS.3 Generalization

PS.3.1 Purposes

This phase closes the preliminary study. It allows to pass to the logical level and already taking the main physical constraints into account.

 For every selected solution, generalize by taking a greater number of cases into account, and no longer only the 'normal representative cases'

 Go deeper into the study of the impact on the organization

 Evaluate with care the economical impact (required resources, costs, benefits)

 Evaluate with care the impact on the migration (planning, resources, ...)

The purpose is to become able to make the realization decision.

PS.3.2 Realization actions

 Functions

 Take the other procedures into account (special cases, ...). Extend the solution from the limited framework of the normal representative cases.

The cases that are completely exceptional or abnormal need not being managed fully by the system; nevertheless, they need being processed by an exception procedure to be defined.

 Processes

 Describe the logic of the processes. Several logical scenarios are possible for one functions set.

Describe the processes sequences.

Describe the actors and their responsibilities; propose new organizational models.

Who does what ? The tasks groups should be allocated to services.

Logical Processes Model
Procedure: paper purchase orders process
Day	Operation	Office	Process
			man	IT system
D0	Receive the mail	Secretary	process
D0	Identify & validate the customer	Sales	introduce	Validate customer / credit
D0	Introduce the order	Sales	Introduce	Validate item / quantity
D0	Create work order; estimate manufacturing time limit	Sales	Optimize the delivery planning to answer customer requirement; confirm order	Validate components are available & resources; plan; reserve resources
N0-night	Output the confirmation mail	Sales		Batch: print out
N0-night	Send the confirmation mail	Mail	Envelope + stamp Send

 Describe the logic of some functions (flow chart, rules, ...)

  Screen models can be useful tools to help understanding the system.

 At the data level [Logical Data Model]

 complete the data inventory.

 complete the conceptual data model by adding

actors, access rights, data protection ...

historical or last value ?

 describe the different possible states of an entity or of a data group

Entity Life Cycle Diagram

 Take the technical (physical) aspects in charge.

 physical implementation

Describe the IT system: study all needed resources

distribution of data, tasks and processes

constraints linked to hardware, operating system, network, ...

security policy

 identify the main risks factors at operation time.

 backup / restore

 degraded operation mode, accepted time limit, ...

 describe the main users roles and the consequences concerning

the data

the available applications and menus

the internal way applications will run.

 Evaluate the impact on the organization:

 evolution of the services and of the hierarchy; study the changes in the workload and in the required human resources; study the training requirements

PS.3.3 Project management actions

 Integrate all practical constraints (complete the functional aspects)

constraints linked to existing equipment

compatibility constraints

portability constraints

operational constraints

 Integrate the quantitative data

data volume 

processes volume, transactions number.

users number

expected response time

 Set up the migration to the new system

Integrate the migration constraints

Try to merge purposes and constraints coming from the system architecture design, and technical and human constraints.

Set up migration scenarios.

 Set up the final balance of the selected solution in terms of:

 costs, needed resources

  Human resources:

Make an inventory of the needed project tasks and quantify them

Assign the project tasks to project functions

Evaluate the skills required to perform these project functions

 benefits

 planning

 risks

PS.3.4 Quality assurance actions

 Control by second reading, simple or alternate.

 Key factor; UPSTREAM: check that all requirements find a solution

 at the functions & processes level

check systematically that all requirements from the preliminary study will find a solution

evaluate the requirements that would not find a solution

the possible limits, particularly in organization terms (automation level).

 at the data level

make sure that the data inventory is mode under a systematic form .

this inventory can be the base for the specifications, the tests games and the basic customizing.

 at the resources level

make particularly sure that all human resources that will be required during the detailed analyses, realization and launch steps will be effectively available.

 Key factor: focus the quality control as from now, in order that the preliminary study is the base for the evaluation of the final realization.

PS.3.5 Phase closing actions

 Write a summary report of the preliminary study, allowing the decision-makers to choose.

 At the end of this phase, all the aspects of the new solution should be well known and the decision can be made with a full knowledge of the facts:

detailed description of the new processes.

new work organization; required human resources

new architecture; realization budget.

evolution scenario: feasibility, planning, cost

economical balance

 Needed resources

The budgetary constraints should be added to the technical constraints and the ones coming from the System Architecture Design.

The project may be cut in sub-projects.

 You should inform widely about the conclusions of the preliminary study:

all the people who participated to the preliminary study

all the people who will participate to the detailed study

the management