Glossary entry (derived from question below)
English term or phrase:
Part of upfront design
French translation:
partie de la conception initiale de toutes les nouvelles fonctionnalités
Added to glossary by
NikkoTh
Aug 30, 2018 15:47
5 yrs ago
2 viewers *
English term
Part of upfront design
English to French
Other
IT (Information Technology)
Guiding principles for our product application roadmaps include, but are not limited to, the following:
Machine Learning Algorithms learn and improve without explicit programming.
They use all data available – the more data, the better the predictions.
Machine Learning can forecast and mitigate problems before they occur and optimize recovery.
Potential applications include:
Outage prediction and response
DER use optimization
Crew deployment optimization
Autonomous damage assessment
Drone image analysis
Predict and adapt to prosumer behavior
Product and service matching
Social media feed analysis
Increased automation and intelligence
Less repetitive tasks for users
More information to make operational decisions (proposed action and why)
User Configurability
All product components aligned to any utility’s processes (workflows, rules, locations, etc.)
Part of upfront design for all new features (basic vs. advanced options)
Performance and scalability
Real-time application results amidst extra-large network models
Big data archiving, querying, and reporting for all components
Data scalability
Database structure – native virtualization for RT database, big data for web apps and historian
Front-end processing – distributed FEPs with native virtualization
Application scalability
Decoupled design – modules designed to solve on a locational basis with bottom-up approach
Interface architecture – leveraging RESTful APIs (proven web-scalable technology)
User scalability
Machine Learning Algorithms learn and improve without explicit programming.
They use all data available – the more data, the better the predictions.
Machine Learning can forecast and mitigate problems before they occur and optimize recovery.
Potential applications include:
Outage prediction and response
DER use optimization
Crew deployment optimization
Autonomous damage assessment
Drone image analysis
Predict and adapt to prosumer behavior
Product and service matching
Social media feed analysis
Increased automation and intelligence
Less repetitive tasks for users
More information to make operational decisions (proposed action and why)
User Configurability
All product components aligned to any utility’s processes (workflows, rules, locations, etc.)
Part of upfront design for all new features (basic vs. advanced options)
Performance and scalability
Real-time application results amidst extra-large network models
Big data archiving, querying, and reporting for all components
Data scalability
Database structure – native virtualization for RT database, big data for web apps and historian
Front-end processing – distributed FEPs with native virtualization
Application scalability
Decoupled design – modules designed to solve on a locational basis with bottom-up approach
Interface architecture – leveraging RESTful APIs (proven web-scalable technology)
User scalability
Proposed translations
(French)
Proposed translations
+2
26 mins
Selected
partie de la conception initiale de toutes les nouvelles fonctionnalités
Part of upfront design for all new features
4 KudoZ points awarded for this answer.
51 mins
toutes les nouvelles fonctionnalités déjà intégrées
all new features that are part of upfront design = already integrated = basic functions
for advanced options), you have to pay extra
cf .upfront payment = d'avance
for advanced options), you have to pay extra
cf .upfront payment = d'avance
1 hr
partie du projet de conception
http://calenlegaspi.blogspot.com/2014/09/agile-myth-6-agile-...
So now let's discuss upfront design. Agile teams have been told that "Big Design Upfront" is bad, so some interpret that to mean that "No Design Upfront" must be good. The truth is somewhere in the middle - "Minimal Design Upfront", supported by Spikes.
"What's Wrong with Big Upfront Design?
The main problem with "Big Upfront Design" is that after all the time and energy spent in creating a design, we almost always find out that much of the design is wrong only when the team starts coding, or even worse, when the team starts performance testing towards the end of the project!"
So now let's discuss upfront design. Agile teams have been told that "Big Design Upfront" is bad, so some interpret that to mean that "No Design Upfront" must be good. The truth is somewhere in the middle - "Minimal Design Upfront", supported by Spikes.
"What's Wrong with Big Upfront Design?
The main problem with "Big Upfront Design" is that after all the time and energy spent in creating a design, we almost always find out that much of the design is wrong only when the team starts coding, or even worse, when the team starts performance testing towards the end of the project!"
Something went wrong...