Sequoia it development methodology
 | welcome page | projects | contact us | get  the free off-line version |

INFORMATION SYSTEM ARCHITECTURE DESIGN

Phase SD.1 General requirements analysis

SD.1.1 Purposes

(-) be informed of the existing system

The study of the existing system must always be limited to the essential. It may not become an extended description of all the details of the current system. Nevertheless, it is mandatory that the requirements analysis is built upon a sufficient knowledge of the existing system.

(-)  structure the scope of the study into functional domains

describe the main flows between domains.

(-) identify the main constraints

(-) quantify the volumes to be processed

(-) identify the requirements

identify the main information requirements (satisfied & not satisfied)

identify the functions & purposes by domain

set the priorities.

(-) give a first diagnostic

also in terms of performances and cost of the current system

(-) propose new evolution possibilities.

management choices

organization choices

technological choices: IT, telecom, ...

SD.1.2 Realization actions

(-)  Interviews & workshops

(-)  Study of the existing system

(-) Enquiry (organization chart, workforce, available resources, main functions of the services, documents inventory, documents flow)

(-) Study of the existing documentation:

regulation

reports of the direction committee & reports of the IT committee, previous architecture designs, audit reports, ...

analysis documents, user documentation, applications mapping.

(-) General description of the current information system

describe the main processes and their functions.

Note: When a part of the documentation lacks, it is sometimes necessary to do a more detailed analysis of the existing system. A this stage, the analysis will anyway always stay focused to the identification of the requirements (satisfied requirements by the way).

(-) Estimate the results of the current systems :

information system performances

realizations, volumes, delays, working and maintenance costs, resources, performances.

(-)  Study of the new requirements, that may raise from the evolution of the domain or of its environment.

(-)  economical, marketing and customer requirements

(-)  regulation

(-)  taxes

(-)  organization

(-)  users basic requirements

qualification, responsibilities, working hours, friendliness, ...

(-)  technology

(-) Identify the main constraints

(-) Write a first diagnostic

SD.1.3 Project management actions

(-) Propose an action plan for the next phase

SD.1.4 Quality assurance actions

(-) Control by a second reading, simple or alternate.

(-) Key factors:

identify and take all needed information sources into account

brainstorm efficiently to imagine the future evolution

SD.1.5 Phase closing actions

At the end of this phase, you should:

(-) select the requirements that need being satisfied; rank them by priority.

(-) agree on a limited number of "acceptable" orientations .

(-) agree on the methodology for the next phase.


copyright (c) séquoia sprl (www.sequoia.be), belgium, 1999-2000. all right reserved.