Km Enterprise Information Systems Assignment One Learning Ou

104km Enterprise Information Systemsassignment Onelearning Outcomes1

Designing a comprehensive enterprise information system for Denby’s Video Hire involves understanding organizational structures, evaluating data collection methods, constructing system models, and developing diagrams that reflect system requirements. The system must support multi-branch operations, member management, DVD rentals, transfers, and real-time data access, with integration supported by appropriate modelling techniques and CASE tools.

Paper For Above instruction

Introduction

Development of an effective enterprise information system (EIS) for Denby’s Video Hire is critical to streamline operations, enhance customer service, and support business growth. The system must accommodate multi-branch access, facilitate member management, streamline DVD rentals and transfers, and enable real-time data sharing. This paper explores the system design through a detailed analysis and modelling using UML diagrams, including use case diagrams, class diagrams, and sequence diagrams, supported by assumptions necessary due to limited client interaction.

Understanding Organizational Structure and Role of Information Technology

The organizational structure of Denby’s Video Hire comprises ten stores operating within Coventry & Warwickshire. The structure appears to be decentralized with individual branches managed locally but connected through a central system. Information technology plays a pivotal role in integrating these branches, ensuring data consistency, and enabling efficient management of memberships, DVD inventory, and transactions. The networked system allows live data access, essential for operational coordination and customer satisfaction. Additionally, IT supports administrative functions such as data updates, payments, and transfer requests.

Methods of Data Collection and Retrieval

Data collection is primarily based on member registration information, DVD inventory, rental transactions, overdue charges, and transfer requests. Data retrieval relies on a centralized database system accessible across branches, facilitating real-time updates to member details, rental status, and inventory levels. Efficient retrieval methods involve structured query languages (SQL) and database management systems (DBMS), enabling quick access to data needed for operations and decision-making.

Design of System Models

Use Case Diagram

At the core, the use case diagram depicts actors such as Members, Branch Staff, and System Administrator. Main use cases include 'Join Video Club,' 'Rent DVD,' 'Return DVD,' 'Update Membership Details,' 'Discontinue Membership,' 'Request DVD Transfer,' and 'Pay Charges.' Relationships show that 'Rent DVD' includes steps like verifying membership and DVD availability, while optional extensions like 'Overdue Charges' or 'Transfer DVD' are modeled with > or > relationships where appropriate. The diagram visually summarizes system functionalities and interactions.

Assumptions

  • The system is designed for online operation across all branches with real-time data synchronization.
  • Members are limited to two per household, and each must register with valid ID, verified during membership registration.
  • DVDs are identified by unique codes; transfer requests are processed with an additional fee handled within the system.
  • Membership, rental, and payment data are stored securely, complying with data privacy standards.
  • User authentication is based on membership card number and pin/password.

Class Diagram

The class diagram encapsulates key entities such as Member, DVD, Store, Rental, and Payment. Attributes include member ID, name, address, DVD ID, title, genre, rental date, due date, overdue charges, and transfer requests. Operations cover registerMember(), updateDetails(), rentDVD(), returnDVD(), processPayment(), and requestTransfer(). Associations illustrate that a Member can rent up to three DVDs simultaneously, with multiplicities reflecting system constraints. Inheritance models include 'Membership' as a base class with 'ActiveMembership' and 'DiscontinuedMembership' subclasses.

Sequence Diagram for 'Rent DVD'

The sequence diagram details interactions when a member rents a DVD. Objects involved are Member, Store System, DVD Inventory, and Payment Gateway. The flow starts with the member initiating a rental request, system verifying membership status, DVD availability, then processing the rental transaction. The diagram emphasizes message flows, synchronizations, and conditional paths such as overdue status or transfer requests.

Discussion and Analysis

Developing this system involves addressing potential ambiguities, such as the handling of overdue DVDs, transfer fee calculations, and data consistency across branches. Assumptions clarified that all DVDs have unique identifiers, and members are responsible for returning DVDs to the original branch unless transfer is approved. The use of UML and CASE tools like Rational Rose streamlines model creation, ensuring clarity and correctness of system design. The diagrams serve as communication tools between developers and stakeholders, aligning system features with business objectives.

Conclusion

The proposed design offers a detailed blueprint for Denby’s Video Hire, combining organizational understanding with technical modelling. It facilitates efficient business operations, improves user experience, and supports expansion through scalable and integrated system architecture. Effective use of UML diagrams, supported by assumptions and modelling best practices, ensures the system's functionality aligns with business needs and technical constraints.

References

  • Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach (8th ed.). McGraw-Hill Education.
  • Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language User Guide. Addison-Wesley.
  • Object Management Group. (2017). UML Specification. Retrieved from https://www.omg.org/spec/UML/2.5.1
  • Fowler, M. (2004). UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley.
  • Rahman, M., & Babar, M. A. (2013). Empirical investigation of factors influencing UML tool adoption. Empirical Software Engineering, 18(1), 36-70.
  • Reenskaug, T. (1979). The Pattern of a Model-View-Controller. In Middleware Conference.
  • Ambler, S. W. (2002). The Object Primer: Agile Model-Driven Development with UML 2. Cambridge University Press.
  • Fairley, R. (2009). Managing Systems Development Projects. IEEE Software Series. Addison-Wesley.
  • Leffingwell, D., & Widrig, D. (2003). Managing Software Requirements: A Use Case Approach. Addison-Wesley.
  • Ambler, S. W. (2003). Agile Model Driven Development. IBM Systems Journal, 42(4), 638–651.

Related Assignments