References ivan marsic 2012 software engineering

This preview shows page 38 - 40 out of 44 pages.

References: Ivan Marsic (2012). Software Engineering , retrieved from . 280 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Mohammad Maysam - Wednesday, 13 February 2019, 5:25 PM Hello Timothy, I appears that you have prior knowledge of web development, and I really enjoyed reading your post, as it answers all the questions. As you mentioned, clear communication is the key to developing the right program and preventing any misunderstandings. Thank You, MM 45 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Cristina Taraburca - Wednesday, 13 February 2019, 7:17 PM Hi Timothy, Great post! Thank you for sharing your experience with us. It is one thing to know the theory and completely another thing to know what happens in real life. I heard that the uncertainty of users is a common issue for many programmers... I appreciate you sharing with us a way to overcome this issue, I bet this knowledge will be useful for many of us further on.
01.04.2019 CS 2401 - AY2019-T3: Week 2 Discussion Question 39/44 Excellent job! 72 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Timothy Frank - Wednesday, 13 February 2019, 8:53 PM Thanks for the feedback! My most recent client was requesting a random generator for likelihood between choosing di²erent "mutations" of body parts with some being unlikely and others being super rare, but couldn't come up with how to balance it. They didn't understand that random in computer science terms isn't really random, and they rejected the ³rst couple prototypes. We talked for almost 6 hours straight at one point working on putting things into a table and sticking percentages onto things. The second problem was they wanted some things to be rare some of the time and common based on certain factors at other times, but weren't willing to work with me to actually graph out the data and expected me to go out of my way to contact them to verify if what I had was how they want it. This particular client and I went on for quite some time... and needless to say I will be screening my clients more carefully, since I do all of my work by myself this was a needless time sink that wasn't worth the dollars it was paying. Such is the life of anyone willing to work on commission, and I'm a little disappointed that the reading material thus far hasn't covered this particular perspective in depth. 216 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Alfredo Schiappa - Wednesday, 13 February 2019, 4:41 PM Hi, Everybody the requirements analysis includes three types of activity, the ³rst of which is the requirements elicitation or requirements gathering activity. The purpose of this activity is to make the developer understand the business context and the customer needs (Marsic, 2012). During this activity, the software developer discovers requirements through communication with customers, system users and other

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture