In your follow-up Respond, address the following questions:

Consider your classmate's UML diagram. How does it differ from your work? What did your classmate do well? What is one thing they could improve?

Consider your classmate's response about whether it's better to have the same programmers or separate teams to code and test the software. Do you agree or disagree with their response? Why?

Consider the experience your classmate described related to a maintenance issue. Have you ever had a similar experience? How was the issue resolved in your experience?

Dont respond to this post

My post:

I think the program's objectives and domain assist businesses choose the optimal strategy. Software testing isn't always one strategy or another. It could be helpful to have a variety of testers to help uncover issues. Developers that have testing assistance frequently don't thoroughly test their code since they rely on quality control to identify errors. I think testers should handle quality control, and developers would be better off writing code. Systems have caused me problems in the past. When I visited Bermuda, the authorities asked me to submit my covid tests and findings to a website. Once I submitted my results, the website reminded me to wait for a confirmation. Whether I was allowed to enter the nation or not depended on the confirmation. After being instructed to wait for 24 hours, I still had not heard from anyone letting me know that I could travel. I called the government after seeing contact information on the website, waited a long time on hold, and then was transferred to several persons until I eventually spoke with a helpful person. Requests for maintenance would be handled by the system's backend vendors. Users might submit support requests in the form of support tickets. The user would have the choice of reporting a problem directly from the website, contacting help by phone, or sending an email. The support tickets would be handled in order of importance after being prioritized. A competent team member is clear in their communication and aware of their obligations. In development, thorough documentation is crucial. It outlines the system's goals and design. Without adequate documentation, many requests might not be translated correctly, which could result in disagreements, lost time, and expensive mistakes. The user entering the site is depicted in the diagram below. After the user enters and confirms their password, they are then taken to a display page with further site settings.

Respond to this:

Hello everyone!

In your readings, you learned that some companies use the same programmers to code and test their software. Other companies have different teams performing these tasks. Which approach do you think works best? Why? My gut instinct is to have different teams developing and testing software. I think there are multiple benefits that fresh eyes on a project provide. The testing team can act as an intermediary between a developer and and end user, and not be bogged down too much by the concrete details of development. Separate teams also takes advantage of natural competitiveness testers really get a kick out of challenging developers to be thorough and excellent!

Imagine that your design for the DriverPass system was implemented. What process would you suggest for collecting and managing maintenance requests? There are a number of tried and true methods for collecting maintenance/change requests. A contact form somewhere in the web app is very useful for customers, and they can be encouraged to recommend changes by the classic review us! popup. It might even be helpful for the IT officer to be able to provide a standardized form for employees to fill out. They can also share some relevant maintenance requests with the admin or with the original development/planning team.

What does it mean to be a good team member in systems development? How can good documentation help ensure that the developers and other designers on your team can implement your designs? The best team members excel at communication. Communication is everything. This is why documentation is so important in systems development. Nobody is able to keep track of all the ins and outs of a complex system, so documentation must serve as a proxy. It is a bridge between the abstract planning and concrete development aspects of design. It helps developers think like users, and helps them develop a user support plan.

My activity diagram for appointment scheduling is attached. It outlines the process of setting up a new appointment with a driver, and makes sure that the appointment and resources are available. The decision node is there in case the user needs to change their information, and the fork node allows the appointment information to be sent to the relevant parties in the necessary way.

Start View and Order Package Use-Case Add Payment Method Generate Recelpt Display Receipt Add Package to Customer Account Send Errail Contirmation End 8-1 Discussion: Implementation and Maintenance In this activity, you will discuss your readings on the implementation and maintenance phases of the SDLC. You will also get peer feedback on one your UML diagrams for your system design. In your initial post, address the following questions: - In your readings, you learned that some companies use the same programmers to code and test their software. Other companies have different teams performing these tasks. Which approach do you think works best? Why? - Think about the different experiences you have online using different types of systems-for example, the systems you use to access your courses, to see your student information, to make purchases, to manage your music, and so on. Have you ever encountered an issue that required maintenance (for example, broken links, sign-in errors)? How did you report that issue? How was it resolved? What about that process worked well? What could have been improved? - Imagine that your design for the DriverPass system was implemented. What process would you suggest for collecting and managing maintenance requests? - What does it mean to be a good team member in systems development? How can good documentation help ensure that the developers and other designers on your team can implement your designs? - Present one of the following diagrams from your work on Project Two: UML activity diagram, UML sequence diagram, or UML class diagram. Include the diagram and a brief (2- to 3 -sentence) description of it. Download your diagram as a PDF. Be sure to check the "Accessible PDF" box before downloading. In your follow-up posts, address the following questions: - Consider your classmate's UML diagram. How does it differ from your work? What did your classmate do well? What is one thing they could improve? - Consider your classmate's response about whether it's better to have the same programmers or separate teams to code and test the software. Do you agree or disagree with their response? Why? - Consider the experience your classmate described related to a maintenance issue. Have you ever had a similar experience? How was the issue resolved in your experience? Start View and Order Package Use-Case Add Payment Method Generate Recelpt Display Receipt Add Package to Customer Account Send Errail Contirmation End 8-1 Discussion: Implementation and Maintenance In this activity, you will discuss your readings on the implementation and maintenance phases of the SDLC. You will also get peer feedback on one your UML diagrams for your system design. In your initial post, address the following questions: - In your readings, you learned that some companies use the same programmers to code and test their software. Other companies have different teams performing these tasks. Which approach do you think works best? Why? - Think about the different experiences you have online using different types of systems-for example, the systems you use to access your courses, to see your student information, to make purchases, to manage your music, and so on. Have you ever encountered an issue that required maintenance (for example, broken links, sign-in errors)? How did you report that issue? How was it resolved? What about that process worked well? What could have been improved? - Imagine that your design for the DriverPass system was implemented. What process would you suggest for collecting and managing maintenance requests? - What does it mean to be a good team member in systems development? How can good documentation help ensure that the developers and other designers on your team can implement your designs? - Present one of the following diagrams from your work on Project Two: UML activity diagram, UML sequence diagram, or UML class diagram. Include the diagram and a brief (2- to 3 -sentence) description of it. Download your diagram as a PDF. Be sure to check the "Accessible PDF" box before downloading. In your follow-up posts, address the following questions: - Consider your classmate's UML diagram. How does it differ from your work? What did your classmate do well? What is one thing they could improve? - Consider your classmate's response about whether it's better to have the same programmers or separate teams to code and test the software. Do you agree or disagree with their response? Why? - Consider the experience your classmate described related to a maintenance issue. Have you ever had a similar experience? How was the issue resolved in your experience