Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs
(or are passionate about them). Participation is free and the site has a strict confidentiality policy.
|English to Romanian translations [PRO]|
Tech/Engineering - IT (Information Technology) / Business process
|English term or phrase: business use cases|
|SOMA is the methodology that supports the design of SOA solutions. SOMA facilitates the identification, specification and realization of services, components and flows (through choreography of services.) The service identification process consists of a combination of top-down, bottom-up, and middle-out techniques of domain decomposition, existing asset analysis, and goal-service modeling. In the top-down view, a blueprint of business use cases provides the specification for business services. This top-down process is often referred to as domain decomposition, which consists of the decomposition of the business domain into its functional areas and subsystems, including its flow or process decomposition into processes, sub-processes, and high-level business use cases. These use cases often are very good candidates for business services exposed at the edge of the enterprise, or for those used within the boundaries of the enterprise across lines of business. In the bottom-up portion of the process or existing system analysis, existing systems are analyzed and selected as viable candidates for providing lower cost solutions to the implementation of underlying service functionality that supports the business process. In this process, you analyze and leverage API's, transactions, and modules from legacy and packaged applications. In some cases, componentization of the legacy systems is needed to re-modularize the existing assets for supporting service functionality. |
Mulţumesc. Am pus context mai mare. Poate ajută...
|caz de utilizare profesionistă/comercială|
"A use case is a technique used in software and systems engineering to capture the functional requirements of a system. Use cases describe the interaction between a primary system actor—the initiator of the interaction—and the system itself, represented as a sequence of simple steps. Actors are something or someone which exist outside the system under study, and who (or which) take part in a sequence of activities in a dialogue with the system, to achieve some goal: they may be end users, other systems, or hardware devices. Each use case is a complete series of events, from the point of view of the actor."
"A. Rafinarea diagramei cazurilor de utilizare
În această etapă se pot identifica şi alte ***cazuri de utilizare*** şi alţi actori, la un alt nivel de detaliu. De asemenea în cursul analizei proceselor de afaceri se poate dezvolta modelul al cazurilor de utilizare pentru întreg sistemul şi se pot construi mai multe pachete pentru reprezentarea unor diverse arii ale afacerii. Fiecare pachet poate fi apoi descompus şi reprezentat printr-o diagramă ce conţine cazurile de utilizare corespunzătoare domeniului şi interacţiunile cu actorii."
http://sinf.ase.ro/seminar/Etape de realizare a proiectului....
Selected response from:
4 KudoZ points were awarded for this answer
17 mins confidence: peer agreement (net): +1
Return to KudoZ list
KudoZ™ translation help
The KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.
Search millions of term translations