This site uses cookies. Some of these cookies are essential to the operation of the site, while others help to improve your experience by providing insights into how the site is being used. For more information, please see the ProZ.com privacy policy.
Cookie settings
  1. KudoZ™ Top
  2. English to Dutch
  3. Management

Technical and business constraints

Dutch translation: Technische en zakelijke beperkingen

GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW)
English term or phrase:Technical and business constraints
Dutch translation:Technische en zakelijke beperkingen
Entered by: Willem Wunderink

19:29 Sep 4, 2017
English to Dutch translations [PRO]
Management
English term or phrase: Technical and business constraints
Voorbeeld zin:

Technical and business constraints pose restrictions on the design of a system or the process by which a system is developed.
petoe
Technische en zakelijke beperkingen
Explanation:
De hele zin: Technische en zakelijke beperkingen stellen beperkingen aan het ontwerp van een systeem of het proces waarmee een systeem wordt ontwikkeld.

--------------------------------------------------
Note added at 12 uren (2017-09-05 07:57:07 GMT)
--------------------------------------------------

Om dubbel 'beperkingen' te vermijden kan eventueel ook 'belemmeringen'of 'randvoorwaarden' worden gebruikt waarbij ik de voorkeur aan de eerste zou geven:
Technische en zakelijke belemmeringen stellen beperkingen aan het ontwerp van een systeem of het proces waarmee een systeem wordt ontwikkeld.
Selected response from:

Willem Wunderink
Netherlands
Local time: 09:01
Grading comment
4 KudoZ points were awarded for this answer



Summary of answers provided
5 +4Technische en zakelijke beperkingen
Willem Wunderink
1technische en zakelijke (zakelijke potentieel) beperkingen
Erzsébet Czopyk
Summary of reference entries provided
technical and business constraints in software/system design
Kitty Brussaard

  

Answers


16 mins   confidence: Answerer confidence 1/5Answerer confidence 1/5
technical and business constraints
technische en zakelijke (zakelijke potentieel) beperkingen


Explanation:
*

--------------------------------------------------
Note added at 16 mins (2017-09-04 19:46:35 GMT)
--------------------------------------------------

E-business en E-commerce: Een Managementperspectief
https://books.google.hu/books?isbn=9043008303 -
Dave Chaffey - 2004 - ‎Business enterprises
... te weten wat de beperkingen (en ook het zakelijke potentieel) van de diverse ...

Erzsébet Czopyk
Hungary
Local time: 09:01
Works in field
Native speaker of: Native in HungarianHungarian

Peer comments on this answer (and responses from the answerer)
neutral  sindy cremer: Why did you add the bit in parentheses?//Agrees can be awarded to correct answers only.
23 hrs
  -> Thank you for your remarks.
Login to enter a peer comment (or grade)

12 hrs   confidence: Answerer confidence 5/5 peer agreement (net): +4
technical and business constraints
Technische en zakelijke beperkingen


Explanation:
De hele zin: Technische en zakelijke beperkingen stellen beperkingen aan het ontwerp van een systeem of het proces waarmee een systeem wordt ontwikkeld.

--------------------------------------------------
Note added at 12 uren (2017-09-05 07:57:07 GMT)
--------------------------------------------------

Om dubbel 'beperkingen' te vermijden kan eventueel ook 'belemmeringen'of 'randvoorwaarden' worden gebruikt waarbij ik de voorkeur aan de eerste zou geven:
Technische en zakelijke belemmeringen stellen beperkingen aan het ontwerp van een systeem of het proces waarmee een systeem wordt ontwikkeld.

Willem Wunderink
Netherlands
Local time: 09:01
Specializes in field
Native speaker of: Native in DutchDutch
PRO pts in category: 4

Peer comments on this answer (and responses from the answerer)
agree  Jan Willem van Dormolen (X)
27 mins
  -> Bedankt, Jan Willem
agree  Edith van der Have: Precies wat ik dacht toen ik het Engels zag. Great minds think alike ;)
3 hrs
  -> :-)
agree  Natasha Ziada (X): Mooie oplossing om de dubbele 'beperking' te vermijden/comment aangepast vanwege OT opmerking
4 hrs
  -> Bedankt Natasha: ever so kind... :-)
neutral  Erzsébet Czopyk: Of course, natives are always better. But your answer was a copy of mine. #fair play
13 hrs
  -> Well, you sound a bit sour Erzsebet, there's no reason for that. We just try to help each other, it's not a competition. The facts: your answer contains an erroneous admission. On top of that I give a solution for the entire sentence; the extra mile.
agree  Kitty Brussaard
1 day 6 hrs
Login to enter a peer comment (or grade)




Reference comments


1 day 18 mins peer agreement (net): +1
Reference: technical and business constraints in software/system design

Reference information:
In software architecture design, constraints come in two basic flavors - technical and business. On most projects there are only a handful of constraints, but these constraints are a highly influential architectural driver. Constraints, as the dictionary definition above indicates, are a limiting factor and severely restrict options for making design decisions. They are also fixed design decisions that cannot be changed and must be satisfied. You could think of constraints as the ultimate non-negotiable, "must have" requirement. It is for this reason that architecture design constraints must be created and accepted with care.

Technical Constraints in Software Architecture

Technical constraints are fixed technical design decisions that absolutely cannot be changed. Most often technical constraints are provided by stakeholders (perhaps after some digging) at the outset of the project. Sometimes a team may choose to create a constraint, perhaps to simplify the world in which they are working. Regardless of the origin, these architecture drivers are technical in nature and are considered unchangeable and indeed very soon become so.

There are many common examples of technical constraints that you've likely seen.

Programming language - often times a specific programming language will be required for various reasons. For example, the customer may be a Java or Ruby or Microsoft shop. You might simply prefer a certain language over another, or have specific expertise that dictates using a particular programming language. Nearly always, once you've picked a language you are stuck with that choice for the remainder of the project,
Operating system or platforms supported - It must work on Windows, or Linux, or iOS, or Qt on Solaris, or IE 6 on Windows XP, or ... building software that does not satisfy the platform constraint means you have failed to design a software system that satisfies stakeholders' key concerns.
Use of a specific library or framework - Sometimes a specific library might be required to be used. The specific origin might come from the business but the influence is very technical. A common example at many companies is the use of specific open source libraries. Some companies might require that open source always be used. Other companies, might have an approved list indicating which open source software may be used. An interesting example at IBM is that we are required to target the "Blue" JVM, IBM's JDK for all JVM-based projects.

Business Constraints

Business constraints are unchangeable business decisions that in some way restrict the software architecture design. Business constraints are similar to technical constraints in that they are decisions that cannot be changed, but rather than influencing structures directly through technology, the influence occurs indirectly through business decisions. It might be easiest to discuss some examples.

Schedule - "We have to be ready to demo at the trade-show in November." The final delivery date is fixed based on input from the business and cannot be changed. It is now up to you to design a system that can be built within the required schedule.
Budget - I've found that this is less true for product development, but nearly every development contractor must learn to deal with budget constraints. In some cases you might be able to increase the budget, but often budgets, whether fixed through contract or expectations, become constraints on the project and team building the software.
Team composition and make-up - In some cases there may be requirements that specific personnel be used or not used during project. For example, someone may be unavailable, already committed to another project or you may be required to include specific individuals, perhaps for training purposes.
Software licensing restrictions or requirements - Often times you will be required to use specific software components because they are already owned. I've also seen situations where components have been used in very... interesting... ways to satisfy specific licensing restrictions. Legal considerations are extremely constraining.
https://www.neverletdown.net/2014/10/dealing-with-constraint...

Kitty Brussaard
Netherlands
Specializes in field
Native speaker of: Native in DutchDutch
PRO pts in category: 30

Peer comments on this reference comment (and responses from the reference poster)
agree  Erzsébet Czopyk
1 day 13 hrs
  -> Thank you, Erzsébet.
Login to enter a peer comment (or grade)



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.

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.

See also:
ProZ.com term search
Search millions of term translations
Close search
Term search
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search