Chat with us, powered by LiveChat One set of eight steps for a software project design might consist of the following: Idea: Gather requirements about how to implement the idea. Plan: Define the goal - Writingforyou

One set of eight steps for a software project design might consist of the following: Idea: Gather requirements about how to implement the idea. Plan: Define the goal

 

One set of eight steps for a software project design might consist of the following:

  1. Idea: Gather requirements about how to implement the idea.
  2. Plan: Define the goals, specify the consumers, and begin low-level prototyping.
  3. Market analysis: Collect customer input and improve the design.
  4. Definition: Define resources, tasks, risks, costs, and testing.
  5. Mock-up: Build and test a working high-level prototype
  6. Product development: Refine the working model.
  7. Testing: Conduct user tests.
  8. Launch: Launch the product.

Explain the processes that you would use at each of the eight steps  to assure minimal user frustration for the product in this course’s  project scenario. Do this for all eight of the steps.

Be sure to respond to at least one of your classmates’ posts.

2 hours ago

Cliff Yang

RE: Week 4 Discussion

Collapse

Top of Form

Overall rating of the messa

Hi class,

Each of the eight steps for software project design all have ways to minimize user frustration. I will go through each below.

1. Idea: Gathering the information required means finding ways to be able to expand on the idea and make it better. This would usually mean getting user feedback from surveys and talking with people about what frustrates them when using a product and what design features can be better. It is important to focus on the biggest concerns.

2. Plan: Create a clear and concrete plan that addresses all goals, consumers, and more. Creating user profiles and different types of prototypes is one way to tackle this portion. Recognizing the relationships and viewpoints is especially importnat so that the everyone working on the plan can realize and understand all parts.

3. Market analysis: This ties in with idea since it uses the information and requirement gathering. Usually, one of the best ways to do this is to gather all customer input and output a report of the biggest concerns and start improvement based on the report. This would also mean a general reliance on consumer data.

4. Definition: Everything is defined at this step and a gantt chart is usually used for visual representation for team members. Other aspects and tasks are also given out so that everybody understand what role they play in the project. Testing, development, maintenance, and more included.

5. Mock-up: Again, taken from the plan stage but more fleshed out since everybody understands their role. It should be a matter of testing, followed by feedback, and then more testing, to ensure a great prototype so that future builds work always a hundred percent. 

6. Product Development: Taking the mock-up and building upon its successes and failures. The process should be similar to that of an SDLC where there should be progress either weekly or daily. Each time, there should be more and more improvement as a result

7. Testing: Every aspect needs to be looked at from the beginning of use to the ends of use. All scenarios must be taken in account as well to lower the chance of any bad feedback. Releasing the product to a small group of people to get their opinions is also a great strategy so that it can give a sample size of what everyone can expect.

8. Launch: Needs to be advertised everywhere from social media accounts to word of mouth. Monitoring must be performed so that everything goes smoothly and no hiccups are in the way. This step is mostly regarded as the easiest part but is in fact one of the most difficult since it requires full undivided attention as do all other steps.

References:

1. ECLKC. No Date. Eight Steps in the Design Process. https://eclkc.ohs.acf.hhs.gov/program-planning/article/eight-steps-design-process

Bottom of Form