INFORMATION SYSTEM ARCHITECTURE DESIGN

Phase SD.2 Scenario for a new solution

SD.2.1 Purposes

Design one or several scenarios

 Target scenario: Imagine and choose a target scenario for the new information system

 Evolution scenario: Define the path leading from the current situation to this new target state

The scenarios description should allow:

to measure the stakes and risks

to evaluate the costs and the planning of the solution.

SD.2.2 Realization actions

 Describe the applications , by domain & interfaces between domains

Description of the system applications

 search for conceptual solutions; design, still in a gross way:

Conceptual Data Model

Conceptual Functions (processes) Model

Note: you can find the description of these techniques in the preliminary study step.

 propose choices of logical organization

automation level

sharing of responsibilities, organization, documents and information flow

 Architecture, for the global system

search for sketchs of technical solutions: hardware, software, networks, development tools, ...

define the main validation and selection criteria concerning the new hardware, software, development tools, programming techniques, ...

SD.2.3 Project management actions

 Do a first balance of the various scenarios in terms of

costs, needed resources

benefits

planning

risks

SD.2.4 Quality assurance actions

 Control by second reading, simple or alternate.

 Key factors:

 verify that all requirements find a solution within the scenario

 evaluate with precision

the requirements that would not find a solution

the possible limits of the solution (never perfect), between others in terms of organization.

SD2.5 Phase closing actions

At the end of this phase, you should:

 choose one target scenario, and one evolution scenario.

(or at least the lowest possible number)

 agree on the selected technical orientations: validity and selection criteria.