Using Below Monash Video Library Case Study You Are To Prep

Using below Monash Video Library Case Study, you are to prepare User Requirements Document

Using the Monash Video Library case study, you are to prepare a User Requirements Document. The framework for the document should include: Business Overview (Goals, Business Objectives, Current Business Situation, Problems, Gaps, Opportunities); Data Gathering and Data Analysis; Logical Process Modelling; Data Modelling and Normalisation; Feasibility Analysis; Business requirement specifications (Functional and Non-Functional); Business proposed solution; and Implementation Issues.

Paper For Above instruction

The Monash Video Library case study presents a compelling scenario for the development of a comprehensive User Requirements Document (URD). This document is essential for guiding the creation of a new, integrated information system that enhances efficiency, customer service, and competitive advantage. This paper systematically addresses each component outlined in the framework, providing a detailed analysis and logical progression from business overview to implementation considerations.

Business Overview

The core goal of the Monash Video Library is to efficiently manage the purchase, cataloging, and lending of video cassettes to its members. Its primary business objective is to generate profit by providing a convenient rental service while maintaining a competitive edge within the entertainment rental industry. Currently, the business operates through three stores, each utilizing a standalone version of an outdated PC-based management system. This fragmented approach hampers operational efficiency and customer service. Major problems include slow loan processing, errors in tracking borrowed videos, and limited data insights for decision-making. Identified gaps involve lack of centralized data, inadequate catalog management, and absence of predictive analytics. Opportunities include implementing a shared database system to streamline operations, improve catalog accuracy, and analyze borrowing patterns to tailor marketing strategies.

Data Gathering and Data Analysis

Data collection for the new system involves gathering detailed information on current inventory, member records, borrowing history, video categories, and procurement details. This can be achieved through interviews with staff, review of existing records, and observation of daily operations. Key data points include video titles, genres, actors, availability status, member details, loan dates, due dates, and purchase records. The analysis of this data reveals usage patterns, peak rental periods, common genres, and member borrowing habits, facilitating better system design and business decisions.

Logical Process Modelling

The core processes involve members browsing or searching the catalog, placing holds, borrowing videos, returning videos, and paying fines. Each process can be modeled logically to depict data flow and decision points. For instance, when a member searches for a video, the system queries the inventory, checks availability, and processes the hold or loan transaction. Process modeling also maps the interactions between member records, video inventory, and borrowing transactions, illustrating how data moves and is manipulated within the system.

Data Modelling and Normalisation

The data model must support core entities such as Members, Videos, Borrowings, Purchases, and Suppliers. Relationships between entities include members borrowing videos, videos belonging to categories, and suppliers providing videos. Normalisation up to the third normal form (3NF) ensures elimination of redundancy and maintains data integrity. For example, member details should be stored separately from borrowing transactions, which refer to members via foreign keys. Similarly, video details are stored independently from inventory status, allowing flexible querying and reporting.

Feasibility Analysis

Feasibility considerations include technical, economic, operational, and legal aspects. Technically, implementing a shared database and a user-friendly interface is achievable with current technology. Economically, the investment in system development is justified by expected improvements in operational efficiency and profit margins. Operations-wise, staff training and process changes are manageable. Legally, data privacy and security measures must comply with regulations. Overall, the project is deemed feasible given the potential benefits outweigh the costs and risks involved.

Business Requirement Specification

Functional requirements include a comprehensive video catalog with categorization, search and filter options, availability status, hold placement, loan processing, due date reminders, and member account management. Non-functional requirements encompass system usability, performance, accuracy, security, and scalability. The system should support rapid queries, data integrity, access controls, and future expansion to additional stores or services.

Business Proposed Solution

The proposed solution involves developing a centralized database system accessible across all stores, integrated with a user-friendly interface. The system will feature a real-time catalog for videos, member management, loan tracking, and reporting tools. It will enable members to search, place holds, and view their borrowing history online. Management will gain insights into borrowing trends and member reliability, enabling targeted marketing and customized membership plans. The solution also includes vendor management features to streamline procurement and cost analysis.

Implementation Issues

Key implementation issues encompass system integration with existing hardware, user training, data migration, and ensuring system security. Resistance to change among staff must be managed through comprehensive training programs. Data migration from the old standalone systems needs careful planning to avoid data loss. Additionally, infrastructure upgrades may be necessary to support the new system’s performance requirements. Ongoing maintenance and support are vital to ensure system robustness and adaptability.

Conclusion

The Monash Video Library case study highlights the critical need for an integrated, efficient, and user-friendly system to support its expansion and competitive strategies. The structured approach from understanding business goals to addressing implementation issues provides a clear roadmap for system development. A well-designed User Requirements Document rooted in thorough analysis ensures the final system meets business needs, enhances operational efficiency, and delivers superior customer service.

References

• Booch, G. (2006). Object-oriented analysis and design with applications. Addison-Wesley.