Vous êtes sur la page 1sur 15

Fiche de Demande d’Evolution – FDE – Template V2.

2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Type de fiche / Type of request


✘ Demande d'évolutions (avant projet/lot) Demande d'avenants (pendant projet/lot)
Enhancement Request (before the project/lot) Amendment Request (during the project/lot)

Etat de la fiche / State of the File


● Créée
Impacts < Décision >: Copier la synthèse de décision
Décidée
évalués Change decision Copy the field “Realisation decision”
Created Evaluated Determined

Etape 1 : Identification de la demande


Step 1 : Request identification
Projet / Lot : V20.4.0 Sept 2020 Lot /version US_00495
Product version / lot Version on which is related the request
Date de la demande : 03/08/2020 Numéro de Fiche :
Date of the request File Id

Origine de la Métier ● Informatique Locale Concepteur Fonctionelle Concepteur Technique


demande Business Local IS team Business Analyst Technical Analyst
Request’s origin
Autre Commentaire : functional need
Other Comment  : to precise the origin of request (technical or functional architect, exploitability, other)

En charge de la demande / Request responsible


Métier Informatique Locale Concepteur Fonctionnel Concepteur Technique Développeur
Business person Local IS team Business Analyst Technical Analyst Developer
Nom Nom Annie Nom Fahd HAROUACH Nom Nom Name
Responsable FONTAINE ● Responsable Responsable Responsable
Responsable

Intitulé de la demande / Request title

Create a new sub menus to Read info vehicles and to filter display LOT 1

Contexte général / Global context

Business Team needs a new extract info data accessible by BCV intranet
The new tools will be comparable to actions carried out directly in BCV
Mainframe via Macros.

CONFIDENTIAL
Page 1 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Description de la demande / Request Description

Business Team needs a new extract info data accessible by BCV intranet.
The new tools will be comparable to actions carried out directly in BCV
Mainframe via Macros.

A / Submenus:

Access is limited to users who’s have the authorization to access to menu ( Mass_injection )

B/ When user click into the sub menus, new pages screen will be displayed like this :

CONFIDENTIAL
Page 2 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

1/ Datas will be displayed in a tree for example :


Identifiant:
Identifiant (DAPJI)
Chassis
Argument Lancement
Argument Commercial
Description
Modele
Version
PRODEM
PROTRAD
Pays FG
Options
Teinte
Sellerie
Niveau equipement
Niveau moteur
Pneus
Contremarque
Zone de contremarque

……

2/ User can drag and drop any selected item to the second list

3/ Create a new dynamic API to extract datas from the second list (input of this api are
VIN,INVARIANT OR PJI ), we must manage errors also.

4/ Display into a new screen in a table and put an icon to extract the excel file.

5/ Datas are present in BCVTT, for mapping you can see below from mainframe screen
attached into jira.

6/ It must be possible to save typical settings according to different needs with the

possibility of taking them back for later use.

7/ The datas will be classified by headings corresponding to the existing screens.

8/ A super administrator can show all historical transaction in this functionality ( Users logs

must be managed also ).

C/ Display datas :
Only selected datas from second list must be displayed, a button export Excel must be developed
( for example )

CONFIDENTIAL
Page 3 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

After the Brainstorming of the 05/08/2020:


We decided together to cut this global need into a small technical user story:

Release n°1 :

 US_01: Check in mainframe side :

o if there’s any limited length problem for information coming from BCVEVEN
o Information from BCVOL , BCVINDX, BCVFACT,BCVHEIC are less than the
limited of 32000 ).

 US_02: Call the new Zos connect API (read datas from BCVTT with SELECTED ITEM
OR ALL STATIC DATAS) to be checked .

 US_03: DB2 table for display datas from the listed datas attached in Jira (if we don’t have
time for first release, let’s go for static display and report this US to release n°2).

 US_04: Is to have a Jtree or other component with search functionality and selected item
like (https://vuetifyjs.com/fr-FR/components/treeview/#searching-a-directory).

o Drag and drop or selected item or any other solution (choose the simple for your
development).
o In this URL , you can find the Github , to export solution, look if we can explore the
Searching directory and the checkbox color solution.

CONFIDENTIAL
Page 4 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

 US_05: Test the display result into bcv intranet for a huge number of selected item (if not
good we will propose only excel file extract )

o (if we don’t have time for first release, let’s go for static display and report this US to
release n°2).
o Errors must be displayed into excel or txt file.

As agreed, we will deal with this needs in a second release and probably some :
release n°2 :
 US_06: Template config and settings for users ( every user can have more than 1
settings ).to be managed into a Json file ?

 US_07: Logs use of read_info_bcv ( ipn, date, maybe info .... ) Log4j or Json format.

Périmètre de déploiement / Deployment perimeter


Préciser les pays/sites à déployer,leur nombre et le nombre d'utiliateurs concernés.
List the countries/sites to deploy, their number and the number of impacted users.
Pièces jointes pour préciser la demande / Attached documents to clarify the request
PJ1 : PJ2 : PJ3 : PJ4 :
Justification de la nécessité et l’urgence de l’évolution (gains métier, contraintes légales, informatiques, …)
Justification for evolution and high priority (business stakes, legal constraints, IS/IT constraints, …)
.

CONFIDENTIAL
Page 5 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Criticité Critique Important ● Mineur


Functional priority
High Middle Low
Priorité de livraison Délai souhaité / Expected date : Urgent
Delivery Priority
Evénement métier associé :
Related business event
● Non Urgent

CONFIDENTIAL
Page 6 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Etape 2 : Analyse de la demande et de son impact - Faisabilité


Step 2: Evaluation of the request & of their impact - Feasibility
Analyse de la demande et éléments de solution (Concepteur fonctionnel)
Evaluation result and solution elements (Business Analyst)

Analyse de la demande et solution proposée (Concepteur Technique)


Evaluation result and solution elements (Technical Analyst)

Analyse d’impact Analyse Concepteur fonctionnel Compléments apportés par le


Result of impact analysis Analysis by Business Analyst Concepteur Technique
Analysis complements by Technical Analyst
Impacts organisationnels (client, processus, …) Processus + mode dégradé Changement de l’infra associée
Organizational impacts (users, processes, …) Evolution du périmètre d’utilisation
Impacts techniques, développements Performance et niveaux de services Architecture technique ou applicative
Technical modifications and developments
Impacts documentaires (les plans et documents de Modification de liaison connexe Traitements associés et leur nature
test, documents de spécification, CLA, …) Modification/Ajout de cas d’utilisation Ecrans
Impacts documentary (plans and documents of test, Modification/ajout de règles de gestion métier Reporting, états
documents of specification, CLA, …)
Impacts sur les données Reprise de données Traitements associés
Data evolution Données modifiées ou ajoutées Contrôles associés
Cycles de vie et/ou règles de gestion associés
Impacts Qualité : les revues, les validations et
vérifications
Quality: reviews and validation activities
Impacts industrialisation
Impacts industrialization
Autres points impactés
Other impacted points

Impacts Charges Estimated work


Impacts Coûts Estimated Costs
Impacts Délais
Estimated Time for the change

Etape 3 : Décision sur la demande


Step 3 : Decision on the request
Décision de réaliser ● Acceptée Refusée Reportée
Realization decision
Accepted Refused Postponed
Date de décision : dd/mm/yyyy Instance de décision :
Decision date Decision committee

Documents de référence
Related documents

CONFIDENTIAL
Page 7 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Etape 4 : Conception


Step 4: Design Specification

En charge de la Conception
Design Responsible
Concepteur Fonctionnel C.gascoin Launch date 19/08/2018
Business Analyst
Concepteur Technique Launch date
Technical Analyst
MOE en charge de la validation Validation date: / /
Project Manager in charge of the validation

Summary
1. Use Cases impacted [BuA]................................................................................................................... 6
2. TP Use Case “XXX”................................................................................................................................. 6
2.1. Brief description [BuA]...................................................................................................................................... 6
2.2. Scenario(s) description [BuA]........................................................................................................................... 6
2.3. Business Rules [BuA]....................................................................................................................................... 6
2.4. Description of modifications [TechA]................................................................................................................... 6
2.5. Description of dialog related to use case (windows navigation) [TechA].........................................................6
2.6. Window xxx [TechA]......................................................................................................................................... 7
Drawing....................................................................................................................................................................... 7
Control/Action/Answer diagram................................................................................................................................... 7
3. Description of common elements [TechA]............................................................................................. 8
4. Batch Use Case xxx................................................................................................................................. 8
4.1. Brief description [BuA]...................................................................................................................................... 8
4.2. Scenario(s) description [BuA]........................................................................................................................... 8
4.3. Business Rules [BuA]....................................................................................................................................... 8
4.4. Technical diagram of the batch [TechA]...........................................................................................................8
5. Reporting................................................................................................................................................. 8
5.1. Report / form xxx [TechA]................................................................................................................................. 8
Drawing of the report................................................................................................................................................... 8
Description of the output fields.................................................................................................................................... 8
6. Services xxx............................................................................................................................................. 8
6.1. Functional Specification [BuA].......................................................................................................................... 8
6.2. Technical Specification [TechA]....................................................................................................................... 8
Software components modified................................................................................................................................... 8
Description of the modifications.................................................................................................................................. 8
7. Description of interfaces [BuA].............................................................................................................. 9
8. Description of data................................................................................................................................... 9
8.1. MCD - Conceptual Data Model [BuA]...............................................................................................................9
8.2. MPD – Physical Data Model [TechA]...............................................................................................................9

CONFIDENTIAL
Page 8 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

1. Use Cases impacted [BuA]

2. TP Use Case “XXX”


2.1. Brief description [BuA]

2.2. Scenario(s) description [BuA]

2.3. Business Rules [BuA]

2.4. Description of modifications [TechA]

2.5. Description of dialog related to use case (windows navigation) [TechA]


In order to define the interactive exchanges between the user and the information system, describe the new
dialogue or the modifications made to the existing dialogue. Use an overall diagram of the navigation between
screens.
 The requirements to be inserted here belong to FCT (Functional) category, UC (Use Case) or SCR (Screen)
sub-category.

CONFIDENTIAL
Page 9 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

2.6. Window xxx [TechA]


Drawing
Include the drawing of the page or screen.

Control/Action/Answer diagram
Describe here for each graphic control or field on the page or screen the possible actions (from the user's point of
view) and the application's responses (Control Action Response diagram) specifying calls to services if necessary.
 The requirements to be inserted here are the FCT (Functional) category and the SCR (screen) sub-category.

CONFIDENTIAL
Page 10 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

3. Description of common elements [TechA]


Common element denotes user and error messages as well as information and warning windows. Only those
common elements that are affected by the modification are described.
 The requirements to be inserted here belong to FTC (Functional) category. For sub-categories, use the
permitted values in the Table of Categories and Sub-categories.

4. Batch Use Case xxx


4.1. Brief description [BuA]
This paragraph briefly describes the use case (goal, summary, scope, etc.)
4.2. Scenario(s) description [BuA]
Describe the modification in the scenario steps. The scenario could be the nominal scenario but also altenative
scenarios
 The requirements to be inserted here are the FCT (Functional) category and the UC (Use case) sub-category.

4.3. Business Rules [BuA]


Describe the business rules to implement
4.4. Technical diagram of the batch [TechA]
N/A

5. Reporting
5.1. Report / form xxx [TechA]
For each status report updated or created by the modification, the different elements which describe it must be
documented (Definition of the status report/form, calling conditions/context, type of execution, data, report design,
etc.).
 The requirements to be inserted here are the FCT (Functional) category and the REP (Report) or FRM
(Form) sub-categories.
Drawing of the report
Insert the drawing of the report here.
Description of the output fields
Fill out the table below to describe the fields output

6. Services xxx
For each impacted service, describe the modification
6.1. Functional Specification [BuA]
Reserve this chapter to the description of functional services, delayed processing or processing on request as well
as downgraded processes that are updated or added because of the modification.
 The requirements to be inserted here belong to FCT (Functional) category, SVC (Service) or BAT (Batch)
sub-category.
6.2. Technical Specification [TechA]
Software components modified
Cite the software components which have been changed or created for the needs of the modification.
Description of the modifications
Comment on the modifications introduced to the software by explaining the processes (algorithm), the management
rules, the operations performed on the data and the transactional and batch process readouts.

CONFIDENTIAL
Page 11 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

7. Description of interfaces [BuA]


Identify the associated links impacted by the modification and, for each of these connections, document the general
information describing them, indicating, if necessary, any added or updated Application Link Contracts.
 The requirements to be inserted here are theFCT (Functional) category and the INT (Interface) sub-category.

8. Description of data
8.1. MCD - Conceptual Data Model [BuA]
Describe and highlight the data and relations that have been updated or added by the modification by recovering,
whether fully or in part, the first level Conceptual Data Model (MCD) and the Physical Data Model (MPD).
 The requirements to be inserted here are the FCT (Functional) category and the DAT (Data description) sub-
category.
8.2. MPD – Physical Data Model [TechA]
Describe the tables and columns impacted by the modification and describe the processes to be performed on the
data (modifications, loading, cleaning, etc.) as well as the inspection procedures.
Modify the resulting optimized MPD.

CONFIDENTIAL
Page 12 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

GUIDE
Couverture  : la FDE est à utiliser pour toutes les demandes de modifications qui interviennent dans le cycle
d’un projet, d’un lot d’évolution ou d’une maintenance. Gérer les fiches dans le Portefeuille des Demandes et
suivi des Versions (PDV).

Cover: the FDE is to be used for all the requests for modifications which intervene in the cycle of a project, a batch of evolution or
maintenance. Manage the cards in the Portfolio of request & version tracking (PDV).

Criticité Critique : produit ne peut pas fonctionner sans l’implémentation de la demande


Functional priority Important : le fonctionnement du produit est dégradé sans l’implémentation de la demande
Mineur : l’implémentation de la demande souhaitable
Cette information est donnée par le demandeur et doit permettre d'aider la prise de décision
Critical : product cannot run without the implementation of the request
Important : product can still function but with problems
Minor : Nice to have
This information is given by the applicant and must allow d' to help decision making
Priorité de livraison En maintenance :
Delivery priority Urgent : doit être intégré au lot ou à la demande en cours
Non urgent : peut attendre
(suivant l'étude d'impact, lors de la décision, on aura alors le choix entre
- décider de l’implémentation de la demande et donc l'embarquer dans le lot en cours ou
- attendre, et donc ne pas le traiter immédiatement et le mettre en portefeuille pour un lot ultérieur.
En projet :
Cette information n'a d'intérêt que sur certaines phases du projet.
Urgent : doit être intégré à la prochaine livraison (si on est en phase de dev ou de recette, il doit
être fait avant la mise en prod, si on est déjà en prod, il doit être livré au plus tôt, au besoin par une
livraison spécifique)
Non urgent : si on est en dev ou en recette, il peut être traité après la mise en prod. Si on est déjà
en prod, la livraison peut attendre
Cette information est donnée par le demandeur et doit permettre d'aider la prise de décision
In maintenance:
Urgent: must be integrated into the batch or the implementation of the request in progress
Non urgent: can wait
(according to study the impacts, at the time of the decision, one will have the choice then enters
- decide the evolution and thus to embark in the batch in progress or
- wait, and thus not to treat it immediately and put it in the portfolio for a later batch.
In project:
This information not has any interest that on certain phases of the project.
Urgent: must be integrated into the next delivery (if one is in phase of Dev. or receipt, it must be
made before the setting in prod, if one is already in prod, it must be delivered as soon as possible,
with the need by a specific delivery)
Non urgent: if one is in Dev. or receipt, it can be treated after the setting in prod. If one is already in
prod, the delivery can wait
This information is given by the applicant and must allow to help decision making

CONFIDENTIAL
Page 13 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

Historique des évolutions du livrable du projet/application


MODIFICATIONS
VERSIONS DATE AUTEUR
(NATURE ET CHAPITRES CONCERNES)

1.0 13/10/15 Detailed Study Thamizhselvi S

Historique des évolutions du template


MODIFICATIONS
VERSIONS DATE AUTEUR
(NATURE ET CHAPITRES CONCERNES)

V1 Version initiale Equipe PRIMA


V1.1 30/01/07 Révision suite à projet pilote : ATOS [C. Mourant]
- Ajout de questions criticité / priorité
- Révision de style & de l’entête (ref du doc et ref du modèle)
- Révision du guide
- Ajout d’un tableau de suivi des évolutions du modèle
- Elargissement des tableaux (alignement entête de page)
V1.2 26/11/07 Fusion avec la FRE Expert (Fiche de Rapport d’Evénement) G GAUGE, MH RETOURNE,
- Ensemble du document SOGETI [G Darblade]

V1.3 22/07/08 Complément d’anglais pour PRIME 3 SOGETI [G Darblade]


V1.4 19/03/09 Utilisation de la FCE (Fiche de changement d’exigence) pour construire R Coussedière
la fiche de changement d’exigences ou d’évolutions
- Inclusion d’un type de fiche
- Simplification du guide de rédaction
V1.5 15/05/09 Ancienne référence = PRIMA-SP02-MD-296-Fiche de changement R Coussedière
d'exigence
Nouvelle référence = 50805.09.CPR.475
Changement de nom de la fiche :
la FCE (Fiche de changement d’exigence) devient la FDE (Fiche de
Demande d’Evolution)
V1.6 20/05/09 Uniformisation de la terminologie avec le PDV (Portefeuille des R Coussedière
Demandes et du suivi des Versions) suite à remarques PRIMA
- Evolution ou avenant sur le type de fiche
V1.7 25/06/09 Prise en compte des remarques d’Atos [C. Mourant] R Coussedière
- Introduction d’un tableau d’historique du livrable
- Correction de terminologie et d’orthographe
- Précision dans les exemples donnés dans le tableau d’impacts
V1.8 02/11/09 Correction d’erreur de regroupement de radio bouton R Coussedière
V1.9 27/05/10 Mise à jour des rôles G. Giraud
V2.0 29/06/12 Extended FDE : additional chapter 4 to describe functional and M.H. Retourné
technical specification
V2.2 16/07/12 Extended FDE : modification in request identification M.H. Retourné
Attention : Version à reporter dans l’entêtes de pages

CONFIDENTIAL
Page 14 / 15 PROPERTY OF RENAULT

Confidential C
Fiche de Demande d’Evolution – FDE – Template V2.2
PRISM3 BCV
US_00495 - Read vehicles info API & display in sub menus
Mass_injection Lot1

CONFIDENTIAL
Page 15 / 15 PROPERTY OF RENAULT

Confidential C

Vous aimerez peut-être aussi