Glossary entry (derived from question below)
Romanian term or phrase:
Proiectare
English translation:
Designing stage
Added to glossary by
Alina Dohotaru
Feb 4, 2011 07:09
13 yrs ago
1 viewer *
Romanian term
Proiectare
Romanian to English
Bus/Financial
Finance (general)
IT
Proiectare – constituie etapa care ţine de definirea modelului de raportare, proiectarea dicţionarului de metadate (taxonomiei) pentru introducerea indicatorilor noi, sau pentru modificarea celor existenţi. De asemenea, această etapă ţine de modelarea procesului de raportare, crearea regulilor/scenariilor/excepţiilor pentru colectarea, validarea, procesarea şi diseminarea informaţiei.
Proposed translations
(English)
5 +5 | Designing stage | Cezar GRINEA |
4 +2 | Planning stage | Julia Prazsmary |
References
Systems Development Life Cycle | Cristina Crişan |
Change log
Feb 4, 2011 07:09: changed "Kudoz queue" from "In queue" to "Public"
Proposed translations
+5
11 mins
Selected
Designing stage
-
4 KudoZ points awarded for this answer.
Comment: "multumesc"
+2
44 mins
Planning stage
În literatura de specialitate (management) cel mai des sunt identificate următoarele cinci faze (binențeles, denumirile uneori diferă în funcție de autori) : initiation, planning, execution (sau implementation), monitoring și closing.
Descrierii date se potrivește faza de planning:
”Often the most time-consuming of the phases of project management, the Planning phase is where you lay your project groundwork. In Phase 1 - Initiation, you define your project deliverables through the Project Charter. Now, in Phase 2 - Planning, you create a specific list of things that need to happen in order for your goal or goals to be met.
Your specific list of identifiable steps is documented in the form of tasks....”
Read more: http://www.brighthub.com/office/project-management/articles/...
Descrierii date se potrivește faza de planning:
”Often the most time-consuming of the phases of project management, the Planning phase is where you lay your project groundwork. In Phase 1 - Initiation, you define your project deliverables through the Project Charter. Now, in Phase 2 - Planning, you create a specific list of things that need to happen in order for your goal or goals to be met.
Your specific list of identifiable steps is documented in the form of tasks....”
Read more: http://www.brighthub.com/office/project-management/articles/...
Example sentence:
http://www.brighthub.com/office/project-management/articles/1673.aspx
Peer comment(s):
neutral |
Cristina Crişan
: domeniul este IT :)
1 hr
|
da, adevărat :)
|
|
agree |
Anca Nitu
: planning http://managementhelp.org/infomgnt/techques.htm
10 hrs
|
mulțumesc, Anca!
|
|
agree |
George C.
2 days 2 hrs
|
mulțumesc, George!
|
Reference comments
23 hrs
Reference:
Systems Development Life Cycle
The Systems Life Cycle (SLC) is a type of methodology used to describe the process for building information systems, intended to develop information systems in a very deliberate, structured and methodical way, reiterating each stage of the life cycle.
* Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.
* Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.
* Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
* Implementation: The real code is written here.
* Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
* Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.
* Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
* Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.
* Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.
* Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
* Implementation: The real code is written here.
* Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
* Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.
* Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
Something went wrong...