Software Design Discussion 7

Need 2 seperate discussion response written. 135 words each. Please use Grammarly to make sure it flows and makes sense,  not full of fill words and run-on sentences. Please use proper punctuation. It needs to be in topic 135 words each, not including sources/questions.  See Attachments to complete the discussion topic.

For scope on what we are writing about, here is the original topic.
***************************************************************************************

Should everyone know how to code?
Software development teams typically include highly technical individuals and non-technical users.  This presents a fundamental communications problem.  We probably all know someone in each camp….a programmer who, while brilliant with code, is not a good “people person” and someone who is a subject matter expert on a business process but not very savvy when it comes to technology.  Both are essential to the success of the project.  We need to bridge this gap.  Some might suggest that everyone should learn how to code, almost from birth!  That seems a little unfair as if we are expecting the business side to learn how we do things on the technical side.  But, then again it might just work over time.  In the meantime this is still a challenge.  Do you believe that the Unified Modeling Language (UML) based on Object-oriented development provides us with the best way to help all project team members speak a “common language”?   Why or why not?  Do you have any other suggestions for improving understanding among team members?  Please post your discussion and reply to two other posts. 

********************************************************************************************

Below are the 2 topics to respond to:

1) Discussion 7-Essix 

I agree that it seems a little unfair to expect everyone to learn to code. I think it’s more reasonable for schools to provide courses such as this one to all people. This will help improve the basic understanding of system development for all team members without needing to learn a specific programming language. I also believe that UML is a great way to for project team members to communicate because information and processes are broken down into simple terms that can be visualized.

2) Discussion Topic 7-Kategianes 

          I believe that the Unified Modeling Language otherwise known as UML is a great tool to be used but I am unsure if it is the best option. For instance in software development there are Data Flow Diagrams which are used when modeling static data during software development lifecycle. For their intended purpose they do offer great insights into how the software is going to be created and documented. UML was designed in a way to help standardize many different approaches to software development and to visualize a systems architecture. The only alternative that could stand toe to toe with UML would be ORM. Now Object-Role Modeling is specifically built and tailored towards non-technical individuals that need to understand the technical aspects of varying systems.

          When the need arises for a common ground to be reached so technical and non-technical individuals can understand each other I do not believe it matters what model is used personally. What matters truly is the capabilities of the teams involved and their ability to understand the chosen model that is right for the project or system at hand. There might be instances where using UML may be preferred over other models.

Place your order
(550 words)

Approximate price: $22

Calculate the price of your order

550 words
We'll send you the first draft for approval by September 11, 2018 at 10:52 AM
Total price:
$26
The price is based on these factors:
Academic level
Number of pages
Urgency
Basic features
  • Free title page and bibliography
  • Unlimited revisions
  • Plagiarism-free guarantee
  • Money-back guarantee
  • 24/7 support
On-demand options
  • Writer’s samples
  • Part-by-part delivery
  • Overnight delivery
  • Copies of used sources
  • Expert Proofreading
Paper format
  • 275 words per page
  • 12 pt Arial/Times New Roman
  • Double line spacing
  • Any citation style (APA, MLA, Chicago/Turabian, Harvard)

Our guarantees

Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.

Money-back guarantee

You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.

Read more

Zero-plagiarism guarantee

Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.

Read more

Free-revision policy

Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.

Read more

Privacy policy

Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.

Read more

Fair-cooperation guarantee

By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.

Read more