Week3

1. Functional Requirements for Each Subsystem

a. Resort Relations Subsystem:

• Information Entry: Resorts should be able to enter and update information about their facilities, including prices and special features.
• Booking Management: The subsystem should allow resorts to view and manage their bookings for each week.
• Damage Reporting: Resorts should have the ability to report and collect damages caused by guests during their stay.

b. Student Booking Subsystem:

• Room Search and Booking: Students should be able to search for available rooms at various resorts and complete the booking process online.
• Payment Processing: The system must facilitate secure payment processing for deposits and final payments.
• Contract Management: Students should be able to enter contract information and receive confirmations of their bookings.

c. Accounting and Finance Subsystem:

• Transaction Tracking: The subsystem should track all financial transactions related to bookings, payments, and refunds.
• Reporting: It should generate financial reports for SBRU management to analyze revenue and expenses.
• Resort Payments: The system must manage payments to resorts based on bookings, ensuring timely and accurate transactions.

d. Social Networking Subsystem:

• User Profiles: Students should be able to create and manage profiles, including sharing experiences and photos.
• Event Planning: The subsystem should allow students to organize and join events related to their trips.
• Communication Tools: Features for messaging and connecting with other students before and during the trip should be included.

2. Non-Functional Requirements

a. Usability:

• The system should have an intuitive and user-friendly interface that allows students and resorts to navigate easily. This includes clear instructions, accessible design, and responsive layouts for various devices (e.g., desktops, tablets, smartphones).

b. Performance:

• The system should be capable of handling a high volume of simultaneous users, especially during peak booking seasons. It should ensure quick response times for loading pages and processing transactions to enhance user experience.

c. Security:

• The system must implement robust security measures to protect sensitive user data, including personal information and payment details. This includes encryption, secure authentication methods, and compliance with relevant data protection regulations.

3. Stakeholders for SBRU and Their Interests

a. Students:

• Interest in Subsystems: Student Booking Subsystem (for booking trips, managing payments) and Social Networking Subsystem (for connecting with peers and sharing experiences).

b. Resorts:

• Interest in Subsystems: Resort Relations Subsystem (for managing bookings and updating resort information) and Accounting and Finance Subsystem (for tracking payments and reporting damages).

c. SBRU Management:

• Interest in Subsystems: All subsystems, particularly the Accounting and Finance Subsystem (for financial oversight) and Resort Relations Subsystem (for managing partnerships and contracts with resorts).

d. Customer Support Staff:

• Interest in Subsystems: Student Booking Subsystem (to assist students with bookings) and Resort Relations Subsystem (to handle inquiries from resorts).

there are two method for categorizing information technology project:
存在两种分类信息技术项目的方法：

1. Categorisation based on project impetus: Problems, Opportunities, Directives.
   基于项目动因的分类：问题驱动、机遇驱动、指令驱动。
   • Problems: Projects initiated to solve specific issues within the organization.
     问题：为解决组织内部特定问题而发起的项目。
   • Opportunities: Projects that aim to capitalize on new opportunities or innovations.
     机遇：旨在利用新机遇或创新的项目。
   • Directives: Projects that are mandated by regulations or organizational directives.
     指令性项目：由法规或组织指令强制执行的项目。
2. Categorisation based on project time window: How long will it take to complete a project and what is the deadline for completing it?
   基于项目时间窗口的分类：完成一个项目需要多长时间，以及完成项目的截止日期是什么？

what is a weighted scoring model?

A weighted scoring model is a systematic process used for selecting projects based on multiple criteria. It allows decision-makers to evaluate and prioritize projects by assigning weights to different criteria that reflect their importance and then scoring each project against these criteria.

how  is it created?

1. Identify Criteria: determine the criteria that are important for project selection process/

2.assign weight: assign weight to each criteria so that the total adds up to 100%.

3.score projects: for each project being considered,assign scores for each criteria

4.calculate weighted scores: Multiply the scores for each criterion by their corresponding weights. This will give you the total weighted score for each project.

5.Compare Projects: compare the total weighted scores of the projects to determine which project(s) should be selected based on the highest scores.

Core Process 3: Discover and Understand Details involves several key activities aimed at thoroughly understanding the problem or need. The activities include:

1. Preliminary Fact-Finding: Conduct initial investigations to gather information about the requirements.
2. Identifying Use Cases: Document what users need to do with the system, including defining use cases for relevant subsystems.
3. Identifying Domain Classes: Determine the categories of objects that will be represented in the system, akin to tables in a database.
4. Building Preliminary Domain Class Diagrams: Create diagrams to visually represent the identified domain classes.
5. In-Depth Fact-Finding: Perform detailed investigations to further understand requirements and gather comprehensive information.
6. Documenting Detailed Workflows: Understand and document the workflows associated with each use case.
7. Defining User Experience: Sketch out screens and reports needed for each use case to clarify the user experience.