Project Description: Organize Meeting And Interpretation Omi

Project Descriptionorganize Meeting And Interpretation Omi Is An Int

Organize Meeting and Interpretation (OMI) is an international organization that offers event organization for world leaders to gather and discuss important world issues. OMI determines the location for the meeting, meeting start and end dates, number of sessions in each meeting, begin and end times for each session, and assigns interpreters to each meeting. The interpreters have a set of language skills. Each meeting has a set of language interpretation needs, and interpreters are assigned to each meeting according to the languages spoken in the meeting. Currently, OMI’s operations are supported by a legacy system that runs on desktops Windows operating system.

The OMI staff access the legacy application via a shared folder. The database supporting the application is a Sybase database management system. Because of the nature of desktop applications, the OMI system is not accessible via a browser, and this limits the OMI staff, especially when traveling. OMI aims to improve their system by migrating to a web application and moving their database to the cloud. The future system (TO-BE system) will be a web-based application with a cloud database that supports the following functionalities:

  • Allow OMI staff to login and access features based on their roles
  • Enable staff to create new meetings, assign start and end dates, create multiple sessions with specific times, select languages, assign interpreters according to language needs, allocate meeting rooms, and select meeting locations
  • Facilitate attendee web access and online registration for meetings
  • Support email notifications to attendees

The system should possess qualities such as fast response times, user-friendly interface, ease of use, and robust security. Interpreters are characterized by their first name, last name, education, languages spoken, proficiency levels, and residence address. Meeting locations are identified by name, address, city, state/province, and country. Meetings have identifiers such as name, start and end dates, and associated sessions.

Paper For Above instruction

Developing an effective and efficient information system for the Organization of Meetings and Interpretation (OMI) requires a comprehensive approach that encompasses methodology selection, system planning, feasibility analysis, project estimation, staffing, requirements gathering, and clear definition of functional and non-functional requirements. This paper discusses these aspects in the context of transforming OMI's legacy desktop application into a modern, web-based, cloud-supported system.

1. Recommended Methodology for System Development

Given the scope and complexity of the OMI project, an agile development methodology such as Scrum is highly suitable. Scrum allows iterative development cycles, which enable continuous stakeholder involvement, flexibility to incorporate changing requirements, and rapid delivery of functional components. Agile methodologies emphasize collaboration, adaptability, and customer feedback, which are essential for meeting the diverse needs of international organizations dealing with complex scheduling, multi-language interpretation, and security concerns. Furthermore, Scrum’s incremental approach aligns with OMI’s goal of migration, allowing testing and refinement at each iteration, thereby reducing risks associated with new technology adoption (Highsmith & Cockburn, 2001).

Alternate methodologies like Waterfall could be considered; however, their linear nature may hinder responsiveness and adaptability during development, particularly for a project with evolving requirements such as user interface design and integration of web and cloud components.

2. System Request for the OMI Project

The system request outlines the high-level business needs and justification for the project:

  • Business need: Transition from a desktop legacy system to a web-based, cloud-supported system to enhance accessibility, scalability, and user experience.
  • Scope: Develop a web application that manages meetings, interpreters, sessions, locations, and attendee registration with notification features.
  • Benefits: Increased accessibility for staff and attendees worldwide, improved security, faster response times, and streamlined operation management.
  • Stakeholders: OMI staff, interpreters, meeting attendees, IT staff, and external vendors.
  • Constraints: Migration of existing data from Sybase to cloud, ensuring security, and maintaining user-friendliness.

3. Feasibility Analysis

Technical Feasibility

The technical feasibility of migrating to a web-based system with cloud-hosted databases is high. Cloud services like Amazon Web Services (AWS) or Microsoft Azure provide robust infrastructure for hosting applications and managing databases with high availability, scalability, and security (Marston et al., 2011). Modern web development frameworks (e.g., React, Angular) facilitate creating responsive, user-friendly interfaces. Compatibility issues with existing data formats can be resolved through data migration tools. The primary technological challenge involves integrating existing data with new cloud systems, but with careful planning, this is manageable.

Economic Feasibility

The economic feasibility considers costs associated with development, migration, licensing, and ongoing maintenance versus benefits such as improved accessibility and efficiency. Cloud computing reduces infrastructure costs and allows pay-as-you-go models, increasing cost-effectiveness (Marston et al., 2011). Although initial development costs may be significant, long-term savings and productivity gains justify the investment, making the project economically feasible.

Organizational Feasibility

The organization’s readiness to adopt new technology is high, given OMI's current dependence on desktop systems and motivation to improve access. Staff training and change management will be needed, but with proper planning, resistance can be minimized. The project aligns with organizational goals of modernization and international collaboration, supporting its organizational feasibility.

4. Project Selection Process

The project selection involves evaluating strategic alignment, costs, benefits, and risks. Using a scoring model, OMI can assess factors such as increased operational efficiency, global accessibility, security improvements, and stakeholder satisfaction. Given the strong strategic alignment with OMI's goals, high benefits, and manageable risks, the project warrants prioritization within the organization’s project portfolio.

5. Project Effort Estimation

Effort estimation through Use Case Points involves identifying actors, use cases, and complexity levels. Major actors include OMI staff, interpreters, and attendees. Key use cases encompass login, meeting creation, session scheduling, interpreter assignment, registration, and notifications. Estimating complexity based on those factors suggests approximately 350-400 person-hours, distributed among requirements analysts, developers, testers, and project managers, considering iterative development cycles.

6. Staffing Plan

The project team should include:

  • Project Manager: Oversees project execution, communication, and timeline management.
  • Business Analyst: Gathers requirements, interacts with stakeholders.
  • UX/UI Designer: Designs user-friendly interface.
  • Web Developers (2-3): Develop front-end and back-end components.
  • Database Specialist: Manages data migration and cloud database configuration.
  • Security Expert: Ensures system security and compliance.
  • QA/Testers (2): Conduct testing for functionality, security, and performance.

The organizational chart positions the Project Manager at the top, with functional leads for development, design, database, and security reporting to the manager. The team collaborates in Agile sprints for iterative development.

7. Requirements Gathering Techniques

Effective techniques include:

  • Interviews with stakeholders (OMI staff, interpreters, attendees)
  • Workshops for collaborative discussion of features and workflows
  • Observation of current system usage to identify pain points
  • Questionnaires for broader stakeholder input
  • Document analysis of existing legacy system specifications

These methods facilitate comprehensive understanding of functional and non-functional needs, ensuring the new system meets user expectations.

8. Requirements Definition

Functional Requirements

  • Users can log in with role-based access control.
  • OMI staff can create and manage meetings, sessions, interpreters, and locations.
  • Attendees can register online and receive email notifications.
  • The system supports multi-language interpretation assignment based on language proficiency.
  • Meeting schedules and attendee details are stored securely and retrievable.

Non-Functional Requirements

  • The system responds within 2 seconds for 95% of transactions.
  • The UI is intuitive and accessible on various devices.
  • The system maintains data security and user privacy.
  • The system ensures high availability with 99.9% uptime.
  • Data migration processes are reliable with minimal data loss.

In conclusion, transitioning OMI into a web-based, cloud-supported platform is a strategic move that requires meticulous planning, stakeholder engagement, and adherence to best practices in system development. Employing an agile methodology, assessing feasibility thoroughly, estimating effort accurately, and defining clear requirements are fundamental to delivering a successful system that enhances operational efficiency and stakeholder satisfaction.

References

  • Highsmith, J., & Cockburn, A. (2001). Agile Software Development: The Business of Innovation. Computer, 34(9), 120-127.
  • Marston, S., Li, Z., Bandyopadhyay, S., Zhang, J., & Ghalsasi, A. (2011). Cloud Computing - The Business Perspective. Decision Support Systems, 51(1), 176-189.
  • Selby, R. W., & Cowling, A. (1998). Understanding Requirements Engineering. IEEE Software, 15(2), 53-59.
  • Pressman, R. S. (2014). Software Engineering: A Practitioner’s Approach. McGraw-Hill Education.
  • Sommerville, I. (2016). Software Engineering. Pearson.
  • Beck, K., & Andres, C. (2004). Extreme Programming Explained: Embrace Change. Addison-Wesley.
  • Wiegers, K. E., & Beatty, J. (2013). Software Requirements. Microsoft Press.
  • Brooks, F. P. (1995). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley.
  • Leffingwell, D. (2011). Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley.
  • Ambler, S. (2003). The Requirements Architecture. Agile Modeling.

Related Assignments