Outline dự án marketing mix cho chiến dịch Đã cầm ly để Be cầm lái của BeDriver Mục tiêu Tăng nhận diện thương hiệu BeDriver Tăng số lượng tài xế đăng ký sử dụng app BeDriver Tăng số lượng khách hàng sử dụng dịch vụ của BeDriver Bối cảnh Ngành xe công nghệ tại Việt Nam đang phát triển mạnh mẽ, với sự cạnh tranh gay gắt giữa các hãng. BeDriver là một hãng xe công nghệ mới, cần xây dựng thương hiệu và phát triển thị phần. Tỷ lệ tai nạn giao thông do sử dụng rượu bia ở Việt Nam là rất cao. Khách hàng mục tiêu Những người đã sử dụng đồ uống có cồn và cần một phương tiện di chuyển an toàn. Những người quan tâm đến vấn đề an toàn giao thông. Những người trẻ, năng động, thích trải nghiệm những dịch vụ mới. Phân tích SWOT Điểm mạnh: Thương hiệu mới, có nhiều tiềm năng phát triển. Mức giá cạnh tranh. Đội ngũ tài xế đông đảo, chất lượng. Điểm yếu: Nhận diện thương hiệu còn hạn chế. Số lượng tài xế chưa nhiều ở một số khu vực. Cơ hội: Ngành xe công nghệ đang phát triển mạnh mẽ. Tỷ lệ người sử dụng rượu bia ngày càng cao. Thách thức: Sự cạnh tranh gay gắt giữa các hãng xe công nghệ. Nhận thức của người dân về vấn đề an toàn giao thông còn hạn chế. Chiến lược sáng tạo Big idea: Đã cầm ly để Be cầm lái Concept: Nhắc nhở người dân về sự nguy hiểm khi lái xe sau khi sử dụng rượu bia và khuyến khích họ sử dụng dịch vụ của BeDriver để di chuyển an toàn. Key message: Đã uống rượu bia thì không nên lái xe IMC roadmap: Giai đoạn 1: Khởi động (Tháng 7 năm 2023) Tăng nhận diện thương hiệu BeDriver Phát sóng các quảng cáo trên truyền hình, đài phát thanh, báo chí,... Tổ chức các sự kiện, hội thảo,... để giới thiệu app BeDriver đến với khách hàng tiềm năng. Giai đoạn 2: Phát triển (Tháng 8 tháng 9 năm 2023) Tăng số lượng tài xế đăng ký sử dụng app BeDriver Thực hiện các chiến dịch truyền thông trên mạng xã hội với thông điệp Đã cầm ly để Be cầm lái. Tổ chức các chương trình khuyến mãi, ưu đãi hấp dẫn cho tài xế. Giai đoạn 3: Tăng trưởng (Tháng 10 tháng 12 năm 2023) Tăng số lượng khách hàng sử dụng dịch vụ của BeDriver Tổ chức các sự kiện, hội thảo,... để giới thiệu app BeDriver đến với khách hàng tiềm năng. Tăng cường chăm sóc khách hàng, cung cấp dịch vụ chất lượng cao cho khách hàng. Kết luận Chiến dịch Đã cầm ly để Be cầm lái của BeDriver có thể đạt được hiệu quả cao trong việc đạt được các mục tiêu marketing của BeDriver. Chiến dịch này có những điểm mạnh sau: Big idea phù hợp với đối tượng khách hàng mục tiêu. Key message dễ nhớ, dễ truyền tải. IMC roadmap được triển khai đồng bộ và hiệu quả. Chiến dịch này cũng có một số hạn chế cần khắc phục, chẳng hạn như: Cần tăng cường truyền thông trên các kênh truyền thông trực tuyến để tiếp cận đối tượng khách hàng trẻ. Cần xây dựng các chương trình khuyến mãi hấp dẫn hơn để thu hút tài xế. Cần nâng cao chất lượng dịch vụ để giữ chân khách hàng. Khuyến nghị, giải pháp Để chiến dịch đạt được hiệu quả cao hơn, BeDriver có thể thực hiện các khuyến nghị, giải pháp sau: Mở rộng phạm vi truyền thông trên các kênh truyền thông trực tuyến, đặc biệt là mạng xã hội. Xây dựng các chương trình khuyến mãi hấp dẫn hơn, phù hợp với nhu cầu và sở thích của tài xế.
Introduction
Purpose of the document
Th is Functional Specification Document (FSD) is created to describe in detail how the information management system will operate, including functional requirements and specific functional descriptions This document is based on the high-level requirements identified in the Business Requirements Document and provides clarity on how the system will implement the functional requirements It also includes non- functional requirements and a specific description of the user interface.
Project Scope
The scope of this project is to build an information management system for JKL Company, specializing in training actors and managing activities related to actors and MCs This system will help JKL Company manage actors and their activities more effectively by replacing information management on paper and Excel files.
Scope of the document
This document applies to the entire project of building an information management system for JKL Company It includes detailed functional descriptions, non-functional requirements, reporting requirements, and integration requirements[ CITATION Ahm20 \ l 1066 ].
Related documents
Project proposal: Provides an overview of the project objectives and scope.
System requirements document: Outlines the overall requirements for the information management system.
User interface design document: Specifies the design and layout of the user interface.Database schema document: Describes the structure and organization of the database.
Terms/Acronyms and Definitions
Table 1.5: Terms/Acronyms and Definitions
Context Diagram A visual diagram that depicts the relationship between the system and external components.
It focuses on relevant entities or systems and indicates the flow of information or interactions between them.
Interface Diagram A diagram that describes the interface components of a system and how they interact with each other.
It showcases user interfaces, application interfaces, system interfaces, and the flow of information between them.
Data Flow Diagram (DFD) A diagram that illustrates the flow of information and data processing within a system.
It uses graph symbols to represent processes, data flows, data stores, and data processing entities.
Application Screen Flow Describes the screens and transitions between them in an application.
It displays screens, user actions, and conditions for transitioning between screens.
Sitemap A diagram or organizational structure that describes the architecture of a website or web application.
It shows the pages, their relationships, and the hierarchical structure of the content.
Process Flow Describes the steps and procedures in a specific activity or process.
It presents the sequence of steps, decision points, and information flow to complete a task or objective.
Describes the roles and responsibilities of users in the system, as well as the requirements for permissions and access for each role.
It identifies the roles and responsibilities of users and the permissions and access they need in the system.
Use Case A scenario or situation that describes how users interact with the system.
It identifies actions, scenarios, and expected outcomes in a specific situation.
Mock-up A static or interactive version of a user interface or a part of it.
It is used to present design ideas or test user feedback It is often a drawing, maquette, or static model of the user interface.
Risks and Assumptions
● Technical challenges during system development and deployment.
● Resistance to change comes from employees familiar with manual processes.
● Have the necessary hardware and software resources available for the system.
● Provide full training and support to employees during the transition to the new system.
System/ Solution Overview
Context Diagram/ Interface Diagram/ Data Flow Diagram, Application Screen Flow, Sitemap, Process Flow
● Context Diagram cho Actor Management
● Register and update actor information: The system receives registration information and updates actor information from the "Management Actor Info" module.
● Manage interviewers: The system receives information about interviewers from the "Manage Casting Person" module.
● Manage interview videos: The system receives and stores actor interview videos from the "Manage Interview Video" module.
● Managing gift sending: The system receives information about gifts and sending addresses from the "Manage Sending Presents" module.
● Manage audition schedules: The system receives and displays information about audition schedules from the module "Manage Audition Schedules".
Figure 2.1.1: Flowchart of Context Diagram for Actor Management
■ Data flow "Actor Information" to Management Actor Info.
■ Data flow "Casting Details" to Manage Casting Person.
■ Data flow "Actor Information" to Actor Info Database.
■ Data flow "Casting Details" to Manage Casting Person.
■ Data flow "Casting Details" from Management Actor Info.
■ Data flow "Interview Details" to Manage Interview Video.
■ Data flow "Interview Details" from Manage Casting Person.
■ Data flow "Present Details" to Manage Sending Presents.
■ Data flow "Present Details" from Manage Interview Video.
■ Data flow "Audition Schedule" to Manage Audition Schedules.
■ Data flow "Audition Schedule" from Manage Sending Presents.
■ Data flow "Actor Information" from Management Actor Info.
■ Data flow "Interview Details" from Manage Casting Person.
● ProcessFlow Diagram for Actor Management
Figure 2.1.3: Process Flow Diagram for Actor Management
- This is the starting point of the flowchart, representing the beginning of the process.
- A rectangular shape representing the module for managing actor information.
- This module includes actions such as viewing a list of actors, adding new actors, and editing existing actor details.
● Decision: Is there a New Actor?
- A diamond shape indicating a decision point in the process.
- It checks whether there is a new actor to be added.
- A rectangular shape representing the action of adding a new actor.
- This is the path taken if there is a new actor to be added.
- A rectangular shape representing the action when there is no new actor to be added.
- This is the path taken if there is no new actor.
- A rectangular shape representing the module for managing casting persons.
- This module includes actions such as viewing a list of casting persons, adding new casting persons, and editing existing casting person details.
- A rectangular shape representing the module for managing interview videos.
- This module includes actions such as viewing a list of interview videos, uploading new videos, and viewing details of interview videos.
- A rectangular shape representing the module for managing the process of sending presents.
- This module includes actions such as viewing a list of gifts, adding new gifts, and tracking the gift-sending process.
- A rectangular shape representing the module for managing audition schedules and events.
- This module includes actions such as viewing audition schedules, adding new events, and editing existing audition schedules.
- This is the endpoint of the flowchart, signifying the completion of the process.
Figure 2.1.4: Site map for Actor Management
- A page for managing detailed information about actors.
- Includes functions such as viewing a list of actors, adding new actors, and editing existing actor information.
- A page for managing information about casting persons and related personnel.
- Includes functions like viewing a list of casting persons, adding new casting persons, and editing casting person information.
- A page for managing interview videos with actors and casting persons.
- Provides the ability to view a list of interview videos, upload new videos, and view details of each video.
- A page for managing the process of sending gifts to actors or casting persons.
- Allows you to view a list of gifts, add new gifts, and track the gift-sending process.
- A page for managing audition schedules and related events.
- Includes functions to view audition schedules, add new events, and edit existing audition schedules.
System Actors
2.2.1 User Roles and Responsibilities / Authority Requirements
Table 2.2.1: User Roles and Responsibilities / Authority Requirements
User/Role Example Frequency of Use
John Smith Frequent Manage purchase orders, vendor management
Requires full access to procurement module
Occasional Manage department budget, generate reports
Requires access to financial and reporting features
Frequent Create and manage course content, grade assignments
Requires access to course management tools and student data
Frequent Enroll in courses, submit assignments
Requires access to course registration and submission features
Purchasing Managers, such as John Smith, have frequent use of the system to manage purchase orders and vendor management They require full access to the procurement module to perform their responsibilities effectively.
Dept Admins, like Emily Johnson, have occasional use of the system to manage department budgets and generate reports They need access to financial and reporting features to fulfill their duties.
Faculty members, represented by Sarah Wilson, have frequent use of the system to create and manage course content and grade assignments They require access to course management tools and student data for effective teaching.
Students, like David Thompson, have frequent use of the system to enroll in courses and submit assignments They need access to course registration and submission features to participate in their academic activities.
Dependencies and Change Impacts
Based on the requirements of JKL Company and the designed data flow diagram, the proposed solution will have the following dependencies on other systems:
● Human Resources Management System (HRMS): The proposed solution may depend on the HRMS to access information about existing employees, including actors, and perform employee management tasks.
● Product Management System (PMS): If the proposed solution involves managing information about movies, it may depend on the PMS to access information about movies and update data.
● Sending Presents Management System: If the proposed solution includes the management of sending presents, it may depend on the Sending Presents Management System to record information about sending and receiving presents.
The implementation of the new solution will impact the existing modules in JKL Company's management system The following modules will be affected by the deployment of the proposed solution:
● Management Actor Info Module: The new solution will replace or integrate with the existing module to efficiently manage actor information.
● Manage Casting Person Module: The new solution will impact the management of casting personnel information and may require integration or replacement of the existing module.
● Manage Interview Video Module: The new solution will impact the management of interview videos and may require integration or replacement of the existing module.
● Manage Sending Presents Module: The new solution will impact the management of sending presents and may require integration or replacement of the existing module.
● Manage Audition Schedules Module: The new solution will impact the management of audition schedules and may require integration or replacement of the existing module.
Functional Specifications
Management Actor Info
The purpose of the "Manage Actor Info" module is to provide functionality for the administrator to add, update, delete, and search for actor information within the system This module allows the system to maintain a comprehensive database of actor details for casting and management purposes[ CITATION Wha3 \l 1066 ].
Table 3.1.2: Use case of Manage Actor Information
Trigger Administrator selects the "Manage Actor Info" option from the system menu.
Pre-conditions The administrator is logged into the system.
The administrator has appropriate permissions to access the
Post-conditions Actor information has been successfully added, modified, or deleted in the system.
The administrator selects the "Manage Actor Info" option.
The system displays a list of existing actors.
The administrator can add a new actor by providing the required information, such as name, contact details, and special skills. The administrator can update the information of an existing actor, including personal details, portfolio, and availability.
The administrator can delete an actor from the system.
The administrator can search for actors based on specific criteria, such as name, age, or skills.
Extensions If no actors are found, the system displays a message indicating no results.
If the administrator attempts to add or update an actor without providing the mandatory information, the system displays an error message prompting the administrator to fill in the required fields.
The system should support the ability to upload and manage actor headshots and portfolio materials.
Figure 3.1.3: Mock-up of Manage Actor Info
● Header: The first part of the interface contains the title "Manage Actor Info", creating emphasis and defining the main goal of the page.
● Split Screen Part: The interface is divided into two main parts:
○ Actor List: This section is the actor list and provides an overview of the available data It helps administrators view the list of actors in the system.
○ Actor Info: This is the section for adding, updating and viewing information of a specific actor Information fields include actor name, contact email and contact phone number.
○ Add Actor: This button allows the administrator to add a new actor to the system.
○ Update Actor: Used to update information of the currently selected actor.
○ Delete Actor: Delete an actor from the system.
○ Search Actors: Search for actors based on specific criteria.
● Form Actor Info: Used to display detailed information of the currently selected actor or to enter new information Information fields include actor name, contact email and contact phone number Admins also have the ability to upload actor avatars and profile documents.
● Error Message: If the administrator does not fill in all the information or enters invalid information, the interface will display an error message so they can fix it.
Table 3.1.4 Functional Requirements of mudule 3.1
The system shall display a list of existing actors.
The system shall allow the administrator to add a new actor by providing the required information.
The name field is mandatory.
The contact details should be in a valid format (e.g., email, phone number).
The system shall allow the administrator to update the information of an existing actor.
The administrator can update personal details, such as name, age, and address.
The administrator can update the actor's portfolio, including headshots, resume, and demo reels.
The administrator can update the actor's availability for future projects.
The system shall allow the administrator to delete an actor from the system.
The system shall allow the administrator to search for actors based on specific criteria.
The search criteria can include actor name, age, gender, skills, and availability.
Table 3.1.5.1: Field level specifications of mudule
Textbox Yes Yes Alpha numer
Textbox Yes Yes Email None - john@exa mple.com
Textbox No Yes Nume ric
Form Business Rules and Dependencies
Table 3.1.5.2: Form Business Rules and Dependencies of mudule 3.1
The actor name field is mandatory.
"Please provide the actor's name."
The contact email should be in a valid email format.
"Please provide a valid email address."
The contact phone should contain only numeric characters.
"Please provide a valid phone number."
Perform necessary operation s to add a new actor to the system
Table 3.1.5.3: Buttons, Links and Icons of mudule 3.1
Actor necessary operation s to update the informati on of an existing actor
Perform necessary operation s to delete an actor from the system
Perform necessary operation s to search for actors based on specific criteria
Manage Casting Person Info
The purpose of the "Manage Casting Person" module is to provide functionality for the administrator to add, update, delete, and search for casting person information within the system This module allows the system to maintain a comprehensive database of casting person details for casting and management purposes.
Table 3.2.2: Use case of Manage Casting Person Information
UC-1 Manage Casting Person Information
Stakeholders and Interests Casting director, production manager
Trigger Administrator selects the "Manage Casting Person" option from the system menu.
Pre-conditions The administrator is logged into the system.
The administrator has appropriate permissions to access the "Manage Casting Person" module.
Post-conditions Casting person information is successfully managed and updated in the system.
Main Success Scenario The administrator selects the "Manage Casting
The system displays a list of existing casting persons. The administrator can add a new casting person by providing the required information, such as name, contact details, and role.
The administrator can update the information of an existing casting person, including personal details, assigned projects, and availability.
The administrator can delete a casting person from the system.
The administrator can search for casting persons based on specific criteria, such as name, role, or assigned projects.
Extensions: If no casting persons are found, the system displays a message indicating no results.
If the administrator attempts to add or update a casting person without providing the mandatory information, the system displays an error message prompting the administrator to fill in the required fields.
Special Requirements The system should support the ability to assign casting persons to specific projects and track their availability.
Figure 3.2.3 Mock-up: Manage Casting Person Info
● Display list of Casting Persons:
○ The interface displays a list of casting people currently in the system.
○ Allows you to view details about each casting person including name, email address, phone number and action options such as editing and deletion.
○ Provide a form for users to add information about the new casting person.
○ Requires entering mandatory information such as name, email address and phone number.
○ Allows users to add information about roles, related projects, and availability.
○ Allows users to update the details of an existing casting person.
○ In particular, allows editing personal information, roles and availability of casting person.
○ Allows users to delete a casting person from the system after confirmation.
● Provides the ability to search for casting people based on criteria such as name, role and participating project.
● Display search results so users can see detailed information of casting people that match the search criteria.
Table 3.2.4: Functional Requirements of module 3.2
Spec ID Specification Description Business Rules/ Data Dependency
Specification Description The system shall allow the administrator to add a new casting person by providing the required information.
Specification Description The system shall allow the administrator to add a new casting person by providing the required information.
Business Rules/Data The name field is mandatory.
Dependency The contact details should be in a valid format (e.g., email, phone number).
Specification Description The system shall allow the administrator to update the information of an existing casting person.
The administrator can update personal details, such as name, age, and address.
The administrator can update the casting person's assigned projects and availability.
Specification Description The system shall allow the administrator to delete a casting person from the system.
Specification Description The system shall allow the administrator to search for casting persons based on specific criteria.
The search criteria can include casting person name, role, and assigned projects.
Table 3.2.5.1: Form Elements of module 3.2
Textbox Yes Yes Alpha numer ic
None NA Jane Doe User entry n
Textbox Yes Yes Email None NA jane@ex ample.co m
Textbox No Yes Nume ric
Form Business Rules and Dependencies:
Table 3.2.5.2: Form Business Rules and Dependencies of mudule 3.2
The casting person name field is mandatory.
"Please provide the casting person's name."
The contact email should be in a valid email format.
"Please provide a valid email address."
The contact phone should contain only numeric characters.
"Please provide a valid phone number."
Table 3.2.5.3: Buttons, Links and Icons of module 3.2
Perform necessar y operatio ns to add a new casting person to the system
Perform necessar y operatio ns to update the informat ion of an existing
Perform necessar y operatio ns to delete a casting person from the system
Perform necessar y operatio ns to search for casting persons based on specific criteria
Manage Interview Video
The purpose of the "Manage Interview Video" module is to provide functionality for the administrator to upload, view, edit, and delete interview videos within the system This module allows the system to maintain a collection of interview videos for casting and review purposes.
Table 3.3.2: Use case of Manage Interview Video
Stakeholders and Interests Casting director, production manager
Trigger Administrator selects the "Manage Interview Video" option from the system menu.
Pre-conditions The administrator is logged into the system.
The administrator has appropriate permissions to access the "Manage Interview Video" module.
Post-conditions Interview videos are successfully managed and updated in the system.
Main Success Scenario The administrator selects the "Manage Interview
The system displays a list of existing interview videos.
The administrator can upload a new interview video by selecting the appropriate file and providing relevant details, such as title, description, and associated casting person.
The administrator can view an interview video by selecting it from the list, which opens a video player. The administrator can edit the details of an interview video, including the title, description, and associated casting person.
Extensions: If no interview videos are found, the system displays a message indicating no results.
If the administrator attempts to upload an invalid video file format, the system displays an error message.
Special Requirements The system should support the ability to upload and store interview videos of various formats and provide a video player for playback.
Figure 3.3.3 Mock-up: Manage Interview Video
○ Purpose: Displays a list of available interview videos so users can select and manage.
○ The interview video list allows users to view and select specific videos to view, edit, or delete.
○ Purpose: Displays the interview video detail form and management options.
○ Purpose: Allows users to add, view, edit and manage interview video details.
○ Includes title, description, and dropdown input fields to select participants.
Table 3.3.4: Functional Requirements of mudule 3.3
Spec ID Specification Description Business Rules/ Data Dependency
Specification Description The system shall display a list of existing interview videos.
Specification Description The system shall allow the administrator to upload a new interview video by selecting the appropriate file and providing relevant details.
The uploaded video file should be in a valid format (e.g., MP4, AVI).
The title field is mandatory.
The associated casting person should be selected from the existing casting persons in the system.
Specification Description The system shall allow the administrator to update the information of an existing casting person.
The administrator can update personal details, such as name, age, and address.
The administrator can update the casting person's assigned projects and availability.
Spec ID: Specification Description The system shall allow the
3.3.4.4 administrator to edit the details of an interview video, including the title, description, and associated casting person.
The associated casting person should be selected from the existing casting persons in the system.
Specification Description The system shall allow the administrator to delete an interview video from the system.
Business Rules/Data Dependency none
Table 3.3.5.1: Form Elements of module 3.3
1 Title Textbox Yes Yes Alphan umeric
None NA Interview with John
Textarea No Yes Text None NA A conversati on about previous roles
Dropdown Yes Yes Alphan umeric
List of existi ng castin g perso
Form Business Rules and Dependencies:
Table 3.3.5.2: Form Business Rules and Dependencies of module 3.3
Title The title field is mandatory.
"Please provide the video title."
The associated casting person should be selected from the existing casting persons in the system.
"Please select a valid casting person."
Table 3.3.5.3: Buttons, Links and Icons of module 3.3
Perform necessary operations to upload a new interview video to the system
Open the selected interview video in a video player
Perform necessary operations to edit the details of an interview video
Perform necessary operations to delete an interview video from the system
Manage Sending Presents
The purpose of the "Manage Sending Presents" module is to provide functionality for the administrator to manage the process of sending presents to individuals or groups within the system This module allows the system to facilitate the selection, tracking, and delivery of presents to recipients.
Table 3.4.2: Use case of Manage Sending Presents
Stakeholders and Interests Gift coordinator, recipients
Trigger Administrator selects the "Manage Sending Presents" option from the system menu.
Pre-conditions The administrator is logged into the system.
The administrator has appropriate permissions to access the "Manage Sending Presents" module.
The presents and recipient information are available in the system.
Post-conditions: Presents are successfully managed and sent to the recipients.
Main Success Scenario The administrator selects the "Manage Sending
The system displays a list of available presents.
The administrator can search for presents by various criteria such as name, category, or recipient.
The administrator can select one or more presents from the list for sending.
The administrator can select the recipient(s) for the selected presents.
The administrator can specify the delivery details, such as the address, delivery date, and any special instructions.
The system validates the availability of the selected presents and recipient information.
The system confirms the successful sending of the presents and provides a unique tracking ID.
The administrator can track the status of sent presents using the tracking ID.
Extensions: If no presents are available, the system displays a message indicating no results.
If the selected present is not available, the system displays an error message.
If the recipient information is incomplete or incorrect, the system displays an error message.
Special Requirements The system should support the ability to track the status of sent presents and provide notifications to the administrator and recipients.
Figure 3.4.3 Mock-up: Manage Sending Presents
○ Purpose: Displays a list of gifts available to send Users can view this list to choose the gift they want to send.
○ Purpose: List the available gifts in the system for users to choose from.
○ Purpose: Displays the main content of the interface, including the gift details form, where users can fill in the necessary information to send the gift.
○ Purpose: Allows users to enter detailed information about the gift they want to send, including gift name, category, recipient, delivery address, delivery date, and special instructions.
○ Purpose: Allows users to enter special instructions or personalized
○ Purpose: Buttons perform specific operations, including:
○ Search Presents: Search for gifts based on selected criteria.
○ Select Presents: Select the gifts you want to send.
○ Select Recipient: Select recipients for selected gifts.
○ Send Presents: Execute sending of selected gifts.
○ Purpose: Displays a unique tracking number for the gift sending process, helping users track the status of sent gifts.
○ Purpose: Displays the status of the gift delivery, for example "Delivery",
Table 3.4.4.1: Functional Requirements of module 3.4
Spect ID Specification Description Business Rules/ Data
3.4.4.1 The system shall display a list of available presents.
3.4.4.2 The system shall allow the administrator to search for presents by various criteria such as name, category, or recipient.
3.4.4.3 The system shall allow the administrator to select one or more presents from the list for sending.
3.4.4.4 The system shall allow the administrator to select the recipient(s) for the selected presents.
The recipient information should be available in the system.
3.4.4.5 The system shall allow the administrator to specify the delivery details, such as the address, delivery date, and any special instructions.
3.4.4.6 The system shall validate the availability of the selected presents and recipient information.
The selected present(s) should be available.
The recipient information should be complete and accurate.
3.4.4.7 The system shall confirm the successful sending of the presents and provide a unique tracking ID.
3.4.4.8 The system shall allow the administrator to track the status of sent presents using the tracking ID.
Table 3.4.5.1: Form Elements of module 3.4
UI Control Mand Edit able
Textbox Yes No Alphan umeric
2 Category Dropdown No No Alphan umeric
3 Recipient Textbox Yes No Alphan umeric
4 Address Textarea Yes Yes Text None NA "123
Datepicker Yes Yes Date 5 Deliver y Date
Textarea No Yes Text None NA "Please handle it with care."
Form Business Rules and Dependencies:
Table 3.4.5.2: Form Business Rules and Dependencies of module 3.4
Category - - None Read-only field
Recipient The recipient field is mandatory.
"Please provide the recipient's name."
The delivery date should be a future date.
Table 3.4.5.3: Buttons, Links and Icons of module 3.4
Perform necessar y operatio ns to search for presents based on the selected criteria.
Select the presents for sending.
Select the recipient for the selected presents.
Perform necessar y operatio ns to send the selected presents to the selected recipient
Manage Audition Schedules
The purpose of the "Manage Audition Schedules" module is to provide functionality for the administrator to manage audition schedules within the system This module none allows the administrator to create, update, and track audition schedules for various events or performances.
Table 3.5.2: Use case of Manage Audition Schedules
Stakeholders and Interests Event coordinators, performers, administrators
Trigger Administrator selects the "Manage Audition
Schedules" option from the system menu.
Pre-conditions The administrator is logged into the system.
The administrator has appropriate permissions to access the "Manage Audition Schedules" module. The event information and performer profiles are available in the system.
Post-conditions Audition schedules are successfully managed and updated in the system.
Main Success Scenario The administrator selects the "Manage Audition
The system displays a list of existing audition schedules.
The administrator can search for audition schedules by event name, date, or location.
The administrator can create a new audition schedule by providing the event details, date, time, and location.
The administrator can assign performers to the audition schedule by selecting them from the available performer list.
The administrator can update the audition schedule by modifying the event details, date, time, location, or performer assignments.
The system validates the availability of performers and conflicting schedules.
The system confirms the successful creation or update of the audition schedule.
The administrator can track the status and details of audition schedules.
Extensions: If no audition schedules are available, the system displays a message indicating no results.
If the selected event or performer is not available, the system displays an error message.
If there are scheduling conflicts, the system alerts the administrator and provides options to resolve them.
Special Requirements The system should support the ability to track the status of audition schedules, notify performers about their assigned schedule, and handle scheduling conflicts.
Figure 3.5.3 Mock-up: Manage Audition Schedules
● Title: The web page has a main title at the top, with the text "Manage Audition Schedules" to define the primary function of the interface.
○ Event Name Field: Users can enter the name of the audition event in this field.
○ Date Field: Users can select the audition date using a date picker.
○ Time Field: Users can choose the audition time using a time picker.
○ Location Field: This field allows users to input the audition location.
○ This list displays detailed information about audition schedules, including ID, event name, date, time, location, and the list of performers participating.
● Pagination: Below the list of performers, there is a pagination section that provides information about the current page and a "Next" button to navigate to the next page if applicable.
● Create Audition Schedule Button: Users can use this button to create a new audition schedule based on the entered information.
● Update Audition Schedule Button: This button enables users to update the details of the current audition schedule.
○ Search Field: Users can use the search field to look for audition schedules based on event name, date, or location.
○ Search Button: The "Search" button allows users to perform a search based on the information entered in the search field.
● Audition Schedule Details: Finally, there is a section that displays the details of an audition schedule, where detailed information about the audition schedule is shown after the user selects one from the list.
Table 3.5.4: Functional Requirements of module 3.5
Spec ID Specification Description Business Rules/ Data Dependency
Specification Description The system shall display a list of existing audition schedules.
Specification Description The system shall allow the administrator to search for audition schedules by event name, date, or location.
Specification Description The system shall allow the administrator to create a new audition schedule by providing the event details, date, time, and location.
Specification Description The system shall allow the administrator to assign performers to the audition schedule by selecting them from the available performer list.
The performer information should be available in the system.
Specification Description The system shall allow the administrator to update the audition schedule by modifying the event details, date, time, location, or performer assignments.
Business Rules/Data Dependency none
Specification Description The system shall validate the availability of performers and conflicting schedules.
The selected performers should be available.
There should be no scheduling conflicts for the audition schedule.
Specification Description The system shall confirm the successful creation or update of the audition schedule.
Business Rules/Data Dependency none
Specification Description The system shall allow the administrator to track the status and details of audition schedules.
Business Rules/Data Dependency none
Table 3.5.5.1 Form Elements of module 3.5
Yes Yes Date None NA 2023-10-
Yes Yes Time None NA "10:00
None None NA "Audito rium"
Form Business Rules and Dependencies:
Table 3.5.5.2: Form Business Rules and Dependencies of module 3.5
Event Name Event Name field must be filled in.
Please provide an event name.
Date Date must be a future date.
Location Location field must be filled in.
Performers At least one performer must be selected.
Please select at least one performer.
Table 3.5.5.3:Buttons, Links and Icons of module 3.5
Create the audition schedule based on the entered informat ion.
None Yes Enabled if all mandatory fields are filled in.
N/A Validate that all mandatory fields are filled in.
None Yes Enabled if all mandatory fields are
N/A Validate that all mandatory fields are
None with any changes made to the entered informat ion. filled in filled in.
System Configurations
○ Purpose: Store detailed information about the actors that JKL company has recruited.
■ Create a data table "Actors" with information fields such as Actor Code, Actor Name, Date of Birth, Gender, Address, Phone Number, Email, Acting Experience.
■ Ensure uniqueness of the Actor ID and set up the primary key for the table.
■ Create data constraints to ensure the accuracy and completeness of input information.
■ Set access rights for users so that only authorized people can operate on this database.
● Purpose: Manage information about movies that JKL company participates in producing, including participating MCs.
○ Create a "Movie" data table with information fields such as Movie code, Movie name, Release date, Genre, Director, Producer.
○ Create a data table "MC" with information fields such as MC Code, MC Name, Date of Birth, Gender, Address, Phone Number, Email.
○ Establish a relationship between the "Movie" table and the "MC" table through a foreign key to manage information about MCs participating in each movie.
○ Ensure uniqueness of Movie Code and MC Code and set primary key for the tables.
○ Create data constraints to ensure the accuracy and completeness of input information.
○ Set access rights for users so that only authorized people can operate on this database.
5 Other System Requirements/ Non-Functional Requirements:
○ System response time when searching and retrieving data must not exceed 2 seconds.
○ The system must handle the large amount of actor and movie data that JKL company manages.
○ The system must have a user authentication mechanism to ensure that only authorized people can access and edit information.
○ Data must be encrypted and securely protected to avoid personal information leakage.
○ The system must provide a periodic data backup function to ensure data safety in the event of a problem.
○ Ability to restore data from previous backups.
● Scope and Format: The system should generate reports on actor management, cast management, interview video management, gift sending management, and audition schedule management Reports can be printed (e.g., PDF) or accessed electronically, providing both summary and detailed information.
● Data Elements and Content: For each management area, the required data elements include actor/cast information, availability/verification status, history, and additional optional details.
● File Types and Extraction: Reports can be exported as PDF, Excel, or CSV files Automatic scheduling and email delivery of reports should be supported.
● Users and Access Levels: Authorized users, such as managers, producers, and administrators, can access the reports Access to specific reports may be restricted based on user roles and permissions.
● Report Extraction Frequency: Reports can be generated on-demand or scheduled automatically, with options for daily, weekly, or monthly generation.
● User Interface: The system should have a user-friendly interface, allowing users to select reports, set parameters, and generate them easily.
● Security and Data Protection: The system must have robust security measures, ensuring authorized access and protecting data via encryption during storage and transmission?
● Connect to the recruitment system:
○ The system needs to integrate with the recruitment system to receive information about potential candidates and conduct the selection process.
○ Information that needs to be integrated includes candidate profiles, interview results, assessments, and final results.
● Connect to document storage system:
○ The system needs to integrate with the document storage system to manage and access documents related to actors and movies.
○ Documents include contracts, actor photos, movie scripts, and other related documents.
○ The system needs to integrate with the accounting system to manage information about film production costs, income and payments to actors.
○ Information that needs to be integrated includes invoices, income and expenditure reports, and actor payroll.
Table 7.1: Exception Handling/ Error Reporting
Error ID Error Cause Cause Solution Strategy
Unable to connect to the database.
Check network connectivity and database configuration Notify the user of the error and log error information.
User does not have access rights.
Verify login credentials and user access permissions Display an error message and provide user guidance.
EX03 Data Import Error Data is in the wrong format or lacks information.
Validate data format and mandatory fields Notify the user of the error and request re-entry of data.
To implement a new management information system, JKL company needs to migrate and convert data from the current system to the new system Here are some data migration and conversion requirements[ CITATION 7St1 \l 1066 ]:
Identify current data sources and data formats.
Design data transformation processes, including data extraction, transformation, and loading.
Determine the conversion schedule and conversion data testing plan.
Identify prerequisites for data transformation.
Recommend a data backup and recovery strategy in case of conversion failure.
Excel file User name Actor Actor Create a new management name record in the actor management system.
Excel file Skill Actor management
Skill Convert skill lists into separate entries in the system.
Excel file Contract Actor management
Contract Create a new record in the actor management system.
7 Steps to Include in your Data Migration Plan (n.d.) pp https://nordic-backup.com/.
7 Steps to Include in your Data Migration Plan (n.d.) pp https://nordic-backup.com/. Ahmad Tri Hidayat, S S (2020, november) The Development of Website on
Management Information System for E-commerce and Services, Andi
Muhammad Dirham Dewantara p https://www.researchgate.net.
Flowchart Tutorial (with Symbols, Guide and Examples) (n.d.) p Visual Paradigm. What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
Issue Raised By Raise d On
Develop an actor information management system.
Establish a registration and verification process for new casting persons.
Build a secure and protected system for storing interview videos.
Set up a process to record information about gift sending and receiving.
TBD TBD Open audition schedules for actors.
Establish a reliable data backup and recovery process.
Propose measures to optimize system performance
Build a user access control system.
Integrate the system with external APIs for data sharing.
Develop reporting and data analysis capabilities for the system.
● "Raised By" is assumed based on appropriate roles to ensure the person proposing the issue is relevant and knowledgeable about the issue.
Movie management system
Other System Requirements/ Non-Functional Requirements
○ System response time when searching and retrieving data must not exceed 2 seconds.
○ The system must handle the large amount of actor and movie data that JKL company manages.
○ The system must have a user authentication mechanism to ensure that only authorized people can access and edit information.
○ Data must be encrypted and securely protected to avoid personal information leakage.
○ The system must provide a periodic data backup function to ensure data safety in the event of a problem.
○ Ability to restore data from previous backups.
Reporting Requirements
● Scope and Format: The system should generate reports on actor management, cast management, interview video management, gift sending management, and audition schedule management Reports can be printed (e.g., PDF) or accessed electronically, providing both summary and detailed information.
● Data Elements and Content: For each management area, the required data elements include actor/cast information, availability/verification status, history, and additional optional details.
● File Types and Extraction: Reports can be exported as PDF, Excel, or CSV files Automatic scheduling and email delivery of reports should be supported.
● Users and Access Levels: Authorized users, such as managers, producers, and administrators, can access the reports Access to specific reports may be restricted based on user roles and permissions.
● Report Extraction Frequency: Reports can be generated on-demand or scheduled automatically, with options for daily, weekly, or monthly generation.
● User Interface: The system should have a user-friendly interface, allowing users to select reports, set parameters, and generate them easily.
● Security and Data Protection: The system must have robust security measures, ensuring authorized access and protecting data via encryption during storage and transmission?
Integration Requirements
● Connect to the recruitment system:
○ The system needs to integrate with the recruitment system to receive information about potential candidates and conduct the selection process.
○ Information that needs to be integrated includes candidate profiles, interview results, assessments, and final results.
● Connect to document storage system:
○ The system needs to integrate with the document storage system to manage and access documents related to actors and movies.
○ Documents include contracts, actor photos, movie scripts, and other related documents.
○ The system needs to integrate with the accounting system to manage information about film production costs, income and payments to actors.
○ Information that needs to be integrated includes invoices, income and expenditure reports, and actor payroll.
Table 7.1: Exception Handling/ Error Reporting
Error ID Error Cause Cause Solution Strategy
Unable to connect to the database.
Check network connectivity and database configuration Notify the user of the error and log error information.
User does not have access rights.
Verify login credentials and user access permissions Display an error message and provide user guidance.
EX03 Data Import Error Data is in the wrong format or lacks information.
Validate data format and mandatory fields Notify the user of the error and request re-entry of data.
Data Migration/ Conversion Requirements
To implement a new management information system, JKL company needs to migrate and convert data from the current system to the new system Here are some data migration and conversion requirements[ CITATION 7St1 \l 1066 ]:
Identify current data sources and data formats.
Design data transformation processes, including data extraction, transformation, and loading.
Determine the conversion schedule and conversion data testing plan.
Identify prerequisites for data transformation.
Recommend a data backup and recovery strategy in case of conversion failure.
Excel file User name Actor Actor Create a new management name record in the actor management system.
Excel file Skill Actor management
Skill Convert skill lists into separate entries in the system.
Excel file Contract Actor management
Contract Create a new record in the actor management system.
References
7 Steps to Include in your Data Migration Plan (n.d.) pp https://nordic-backup.com/.
7 Steps to Include in your Data Migration Plan (n.d.) pp https://nordic-backup.com/. Ahmad Tri Hidayat, S S (2020, november) The Development of Website on
Management Information System for E-commerce and Services, Andi
Muhammad Dirham Dewantara p https://www.researchgate.net.
Flowchart Tutorial (with Symbols, Guide and Examples) (n.d.) p Visual Paradigm. What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
What are the key differences and similarities between system requirements and functional specifications? (n.d.) p https://www.linkedin.com/.
Open Issues
Issue Raised By Raise d On
Develop an actor information management system.
Establish a registration and verification process for new casting persons.
Build a secure and protected system for storing interview videos.
Set up a process to record information about gift sending and receiving.
TBD TBD Open audition schedules for actors.
Establish a reliable data backup and recovery process.
Propose measures to optimize system performance
Build a user access control system.
Integrate the system with external APIs for data sharing.
Develop reporting and data analysis capabilities for the system.
● "Raised By" is assumed based on appropriate roles to ensure the person proposing the issue is relevant and knowledgeable about the issue.