Problems And Exercises Appendix A Questions

Problems And Exercises Appendix A Problemsexercises Questions 1 B

Problems And Exercises · Appendix A, Problems/Exercises, Questions 1 (bottom of page 378) · The use-case diagram shown in Figure A-1 F captures the Student billing function but does not contain any function for accepting tuition payment from students. Revise the diagram to capture this functionality. Also, express some common behaviors among two use cases in the revised diagram by using include relationships. FIGURE A-1 Use-case diagram for a university registration system drawn using Microsoft Visio. · Appendix B, Problems/Exercises, Question 1 (bottom of page 393). · When should you use an Agile method, and when should you use an engineering-based method for developing a system? Support your answer.

Course Project: Petrie's Electronics "No Customer Escapes" Customer Relationship Management (CRM) System 1) Objectives Petrie's Electronics needs to improve its marketing and customer retention by increasing customer loyalty. The marketing department is in need of a Customer Relationship Management (CRM) system. Upper management has selected No Customer Escapes as the top Information Technology project this year. 1. In Week 6, we have completed planning and selection, analysis, and design and are now ready to select an implementation method and prepare for operational use and maintenance of the system by completing all of the activities of the final phase of the system development life cycle (SDLC).

2. In order to implement our CRM system, we will need to document the system, train users, code and test the system, plan for operational support, and maintain the system. 3. We will answer the Petrie's Electronics Case Questions for Chapter 10 on pages 358–359. 4.

In Week 6, we close out our project as described in Chapters 3 and 10 of our book. 5. Project closedown brings the project to an end. A project can have a natural or unnatural termination. When a project terminates, several activities are performed including: (1) closing down the project; (2) conducting post-project reviews; and (3) closing the customer contract.

When closing down the project, the project manager may assess each team member, provide career advice to team members, handle negative personnel issues, notify all interested parties that the project is completed, finalize documentation and financial records, and celebrate the accomplishments of the team. When conducting post-project reviews, the objective is to determine the strengths and weaknesses of project deliverables, the processes used to create them, and the project management process. Closing the customer contract ensures that all contractual terms have been met. Petrie’s Electronics Project Closeout Report: Here are some suggested topics to cover - you can add more! Include an introduction Describe Final System Acceptance Criteria Resources: Were the right personnel assigned to the project?

What are some maintenance challenges you see for the CRM system? How can we reduce the cost for the six types of maintenance mentioned in Chapter 10? What preventive maintenance tasks need to be scheduled? What other types of maintenance will be needed? How can we measure the effectiveness of maintenance?

Describe the process you recommend for controlling maintenance requests and configuration management. Describe the most important lessons learned. Include a Conclusion and Reference Page following APA formatting. 2) Objectives Petrie Electronics implemented its Customer Relationship Management (CRM) system, No Customer Escapes last week. But like any system, the Change Management team receives a request for a change to the system.

The Project Manager reviews the change request, and realizes an alternative development method is needed to analyze and design the changes to the system. An object oriented method must be selected, but it seems Use Cases were not created when the system was first developed. The Project Manager knows the benefits of Use Cases and assigns our team to create one using Unified Modeling Language (UML) notation. 1. In Week 7, we learn some alternative system development life cycle (SDLC) methods, object-oriented analysis and design, and agile methods.

2. In order to implement our CRM system, we will need to create a Use-Case Diagram illustrating the four processes the CRM system identified on page 187 of our book. Week 7 Project Tasks Create a Use Case for the CRM system.

Paper For Above instruction

The initial use-case diagram for a university registration system, as depicted in Figure A-1, primarily captures student billing functions but omits the critical process of accepting tuition payments from students. To accurately reflect this functionality, the diagram must be revised to include a new use case labeled "Accept Tuition Payment." This addition ensures that the system encompasses the complete financial transaction flow, from billing to receiving payments. Moreover, the revised diagram can incorporate include relationships to express common behaviors among different use cases, such as "Verify Student Identity" or "Process Payment," which may be shared across multiple transactions. For instance, both "Make Payment" and "Refund Payment" could include "Verify Student Identity" to emphasize repeated behavior, thereby enhancing the modularity and clarity of the diagram.

When deciding between an Agile and an engineering-based development approach, the context and project requirements are instrumental. Agile methodologies are best suited for projects with evolving requirements, high stakeholder engagement, and a need for rapid delivery. They emphasize iterative development, flexible planning, and collaboration, making them ideal for dynamic environments where requirements may change frequently. Conversely, engineering-based methods, such as the Waterfall model, are better suited for projects with well-defined, stable requirements and where thorough documentation and design are prioritized before implementation. For example, in developing safety-critical systems like avionics or medical devices, engineering-based methods provide the rigor and structure needed to ensure compliance and reliability. On the other hand, software projects involving innovative features or customer-facing applications benefit from Agile's adaptability and faster feedback cycles.

The Petrie’s Electronics CRM implementation project highlights the importance of carefully selecting the system development approach. During initial phases, a structured, engineering approach might have been favored to scope system specifications comprehensively. However, as the project progresses and requirements become clearer or subject to change—such as additional processes like "Accept Tuition Payment"—an Agile approach allows the development team to adapt and incorporate these changes efficiently. For example, iterative cycles can facilitate frequent testing and refinement, ensuring the CRM system aligns with user needs and operational goals, which is crucial for customer retention and loyalty.

The project’s final phases include documentation, training, coding, testing, and support planning, following the SDLC. Effective documentation ensures maintainability and future enhancements, while comprehensive training facilitates smooth user adoption. Rigorous testing validates system functionalities, such as new use cases, before deployment. Planning for operational support ensures ongoing system stability, and maintenance encompasses handling bugs, user requests, and system updates. One of the main challenges in maintenance is managing increasing complexity as the system evolves, which necessitates robust configuration management and request control processes. Implementing preventive maintenance tasks, such as regular system backups and security audits, can reduce downtime and operational costs. Additionally, establishing clear metrics—like system availability, bug resolution time, and user satisfaction—helps measure maintenance effectiveness.

Regarding maintenance costs, strategies to reduce expenses include automating routine tasks, leveraging cloud-based solutions for scalability, and adopting proactive monitoring to detect issues early. Preventive measures can involve scheduled updates and patches, security checks, and performance assessments to prevent major failures. Moreover, effective change management processes should be implemented to control maintenance requests, ensure proper configuration management, and facilitate communication among stakeholders. Lessons learned from the CRM project can inform future initiatives by highlighting the importance of early requirement analysis, user involvement, and flexible project management techniques that accommodate change.

In summary, choosing the appropriate development methodology depends on project scope, complexity, and stakeholder needs. Agile methods offer flexibility and responsiveness for dynamic projects, while engineering-based approaches provide structure and predictability for stable, regulated environments. For Petrie's Electronics CRM system, blending these methodologies—adopting Agile practices during implementation and maintenance—can optimize success and system longevity. Proper documentation, rigorous testing, strategic maintenance, and continuous learning are essential components to ensure the system fulfills its purpose of enhancing customer loyalty through effective relationship management.

References

• Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., ... & Thomas, D. (2001). Manifesto for Agile Software Development. Agile Alliance. https://agilemanifesto.org/
• Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language User Guide (2nd ed.). Addison-Wesley.
• Pressman, R. S. (2014). Software Engineering: A Practitioner’s Approach (8th ed.). McGraw-Hill Education.
• Highsmith, J. (2002). Agile Software Development Ecosystems. Addison-Wesley.
• Royce, W. W. (1970). Managing the Development of Large Software Systems. Proceedings of IEEE WESCON, 26(8), 1-9.
• Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall.
• Jacobson, I., Booch, G., & Rumbaugh, J. (1999). The Unified Software Development Process. Addison-Wesley.
• Humphrey, W. S. (1989). Managing the Software Process. Addison-Wesley.
• ISO/IEC/IEEE 12207:2017, Systems and software engineering — Software life cycle processes.
• Alistair Cockburn. (2006). Agile Software Development: The Cooperative Game. Addison-Wesley.