Usefulness of Simulating and Prototyping in Business

JAD Session Situation The goal of a JAD workshop is to educate the workforce in a concentrated and directive fashion. It is "a results-oriented approach to collecting high quality information and developing project deliverables in a compressed timeframe using facilitated workshops" ("Best practice," 2015). JAD workshops have detailed agendas (in this case a new inventory system) and are designed to produce immediate deliverables by the end of the workshop ("Best practice," 2015). However, in terms of the location, there are both pros and cons to on-site vs. off-site locations.

"The theory used to be that taking people off-site is better because they cannot go back to their desk. Now that everyone has a cell phone it makes less difference. If a workshop will last more than one day, you want to be in the same room all the time and this can often only be achieved by going off-site to a hotel" ("Best practice," 2015). There is also still value in going off-site given the ability to better build team morale and to minimize outside distractions.

Getting the first session started involves creating an environment where ideas can be shared in a freewheeling format. Setting up the workshop site in a U-shape "is very important. It allows all the participants to see and hear each other and the middle of the U. is a useful area for the Facilitator. You can block people out, get between arguing people, move close to people who insist on having side conversations, move close to hear people, etc." ("Best practice," 2015).

The workshop's purpose must be immediately established, along with the guidelines for interaction between the participants, including what constitutes active listening, one of the cornerstones of JAD. This is also why it is so critical for the senior vice president to attend: it sets the tone for the rest of the meetings, underlining how vital it is that sessions are productive and professional in character. Q2. Better hardware marketing system situation Designing a new system is costly and the first ventures will almost inevitably have errors and problems.

Through the use of Unified Modeling Language ™ (UML) a less costly prototype can be generated. Models "must be structured in a way that enables scalability, security, and robust execution under stressful conditions, and their structure - frequently referred to as their architecture - must be defined clearly enough that maintenance programmers can (quickly!) find and fix a bug that shows up long after the original authors have moved on to other projects" ("Introduction," 2014).

UML can ensure that the design is functional and meets business needs "before implementation in code renders changes difficult and expensive to make" ("Introduction," 2014). UML allows for the construction of case diagrams, which depicts the way in which different typical users will interact with the system (for example, someone from sales vs. An administrative assistant) to determine how the system will function in the real world.

Sequence diagrams, in contrast, depict the functionality of the entire system as a whole between the system and all entities in a sequential fashion, versus one specific entity. Understanding how typical users will interact with the system on an individual basis is essential given that the purpose of designing.