Transcription
國立臺灣大學101 are Requirement SpecificationMeeting 中教授成員: 、黃柏皓1
OutlineOutline. 2Revision history . 31. System Architecture . 41.1 Introduction . 41.2 Architecture Expression . 42. Functional Requirement . 73.2.1 Front-end Functional Requirements . 72.2 Back-end Functional Requirements . 8Interface Requirement . 103.1 External Interface Requirements . 103.2 Internal Interface Requirements . 114. Nonfunctional Requirement . 135. Goal-driven Use Case Diagram. 145.1 Introduction to Goal-driven Approach. 145.2 Objective Statement . 155.3 Goal-driven Use Case Diagram. 175.4 Actor Description and Actor Use Case Matrix . 185.5 Use case specification . 206. Traceability Matrix . 566.1 Traceability Matrix of Requirements V.S Requirements . 566.2 Traceability Matrix of Requirements V.S Use Case . 586.3 Traceability Matrix of Requirements V.S subsystem function. 602
Revision SRS 功能需求 組員修改系統架構圖、功能性需 圖、功能性需 04/22/13Modify Architecture Expression3全體組員04/22/13
1. System Architecture1.1 組織(ex. 可利用此系統，管理休閒活動 (ex. 1.2 Architecture ExpressionFollowing are the main functionalities of the system and system architecture:ModuleDescriptionsLogin ModuleProvides login functionality.Registration ModuleProvides registration functionality.4
Meeting Function ModuleProvides meeting related functionalities, including initiating,participating, managing a meeting. Provides a meeting calendar.User Function ModuleProvides functionalities of modifying personal profile, managingmessages and sending messages.Management ModuleSettings of back-end parameters and back-end datasynchronization.Authentication ModuleProvides functionalities of user authentication and registrationauthentication.Message Management ModuleProvides back-end management functionality.Synchronization ModuleProvides back-end data synchronization managementfunctionality.Meeting Scheduler ModuleProvides an algorithm to support back-end meeting scheduling.5
Figure 1: System Architecture6
2. Functional Requirement2.1 Front-end Functional RequirementsMeeting Function ModuleFFR1Initiate a MeetingThe user can initiate a meeting in the system. When the user initiates themeeting, he/she can choose the type of meeting, select the time intervaland location, decide the item for discussion, and select the person whomshould be invited.FFR2Participate in MeetingIf the user receives the invitation from other users’ meeting, this functionwill alert the user to decide the desire for participation, and send theresults to Database.FFR3Meeting CalendarProvides the user an interface to show the meetings that the userparticipate in and the scheduling status of the meetings that the user mayparticipate in.FFR4Meeting ManagementThe user manages meetings with administrative access rights.User Function ModuleFFR5User SettingThis function manages user's personal information. The user can use thisfunction to maintain user information.FFR6Message ManagementThis function lets users to manage asynchronous messages in the system,receive messages from other users, and access to message history.FFR7Sending MessagesThis function provides a user interface to allow users for communicatingand passing messages.Registration ModuleFFR8RegistrationProvide an interface to a new user and register him/her as a user of thissystem.7
2.2 Back-end Functional RequirementsLogin ModuleBFR1LoginThis function provides a user interface to allow users to enter login theinformation which used for the back-end user authentication.Management ModuleBFR2Parameter SettingThis function provides the interface which allows the administrator tomanage information which includes actors of meetings, meeting-levels,and user-levels by adding, modifying and deleting them.BFR3Data Synchronization SettingThis function provides the interface which allows the Administrator to setdata fields which will be synchronized between External EmployeeDatabase.Authentication ModuleBFR4User AuthenticationThis function checks whether the login person is a system user or not andreturn results.If the login person is a system user, the Authentication Module willregister him/her into Database and allow him/her to use systemfunctions.If the login person is already in the system, the Authentication Modulewill kick out the previous user and authenticate the current login person.BFR7Registration AuthenticationThe system registers a new user, and checks him/her with the ExternalEmployee Database, then sends messages to Registration Module.Message Management ModuleBFR5Message ManagementThis function manages messages that user transmitted to others by thefront-end User Function Module, so messages can be correctly deliveredand stored to Database.Messages are passed asynchronously.Synchronization ModuleBFR8Data SynchronizationEmployee’s information will be synchronized between External EmployeeDatabase and Database in a certain time.Meeting Scheduler Module8
BFR6Meeting Scheduler AlgorithmThis function provides an algorithm to manage and schedule meetingsinitiated by users.The meeting will be scheduled for whether participants want toparticipate in the time/location or not.The Meeting Scheduler gives the meeting a schedule-level which is usedto solve the priority conflict of time / location.When the number of meeting participants’ demands are more than acertain value, the system will start the corresponding meeting scheduleand import the meeting to Meeting Scheduler.When the time gets closer to the start time of a meeting, the system willstart a schedule of it and import the meeting to Meeting Scheduler.9
3. Interface Requirement3.1 External Interface RequirementsEIR1Administrator Identity AuthenticationAn Administrator inputs an account and a password to judge thequalification of entering back-end system to manage other modules.EIR2User Identity AuthenticationThe user inputs an account and a password in order to determinewhether he/she has the permission or not to enter the system to view oruse other modules.EIR3User and Registration ModuleA non-registered user can enter an email through this interface and theemail will be sent to the back-end module for identity verification andregistration.EIR4Registration Authentication and External Employee DatabaseThe system queries External Employee Database to check whether theE-mail is valid or not when a user completes the registration.EIR5Synchronization Module and External Employee DatabaseThe system reads the information of External Employee Database whensynchronizing.EIR6User Authentication and External Employee DatabaseThe system queries External Employee Database to check whether thepassword is valid or not after a user logged in.10
3.2 Internal Interface RequirementsIIR1Administrator and ManagementAfter an Administrator gained access rights by login confirmation, he/shecan perform actions in back-end modules.IIR2Administrator and User AuthenticationAn Administrator logins through Login Module which sends the logininformation to Authentication Module. Authentication Module checkswhether the user is an Administrator of the system or not.IIR3Management Module and DatabaseAn Administrator can manage meeting-levels, actors of meetings,user-levels and the parameter settings of data synchronization throughback-end management provided by the system.IIR4Registration authentication Module and DatabaseAfter a user email is authenticated by External Employee Database,Authentication Module will register his/her personal information toDatabase.IIR5Message Management Module and DatabaseThe Message Management Module manages messages sent by users andstores them to Database temporarily.IIR6Meeting Scheduler Module and DatabaseMeeting Scheduler Module retrieves the states of meetings and thestates of participants from Database to perform Meeting SchedulerAlgorithm and stores the result to Database.IIR7Login Module and User Authentication ModuleA user logins through Login Module which sends login information toAuthentication Module. Authentication Module checks whether the userhas access rights of front-end or not.IIR8Login Module and Meeting Management ModuleIf a user passes login validation, he/she can use meeting managementfunctionality, including initiating a meeting, managing a meeting, andparticipating in a meeting.IIR9Login Module and User Function ModuleIf a user passes login validation, he/she can use message managementfunctionality, including sending messages, managing messages sent fromother users, and managing the user profile through the user interface.IIR10Meeting Function Module and DatabaseWhen a user uses Meeting Management Module, the system will11
generate documents and send them to Database.IIR11User Setting and DatabaseThis function provides a user interface which allows the user to accessthe user’s personal profile from Database.IIR12Meeting Scheduling Algorithm and Meeting CalendarMeeting Calendar will get the current user states of participation inmeetings and initiation of meetings from Meeting Scheduler Algorithm.IIR13Front-end Message Management and back-end Message ManagementThe messages managed by users will communicate with messagemanagement in the back-end in order to increase the convenience oftransmitting and receiving messages.IIR14Sending Messages and Message managementWhen a user sends messages to other users through the interface, thesystem will send messages to the back-end, which sends messagestogether and stores them to Database temporarily.This function bases on asynchronous message management.IIR15Front-end Registration and back-end Registration ValidationThe system sends user information to the back-end and checks if theidentity is valid or not when the user completes the registration.IIR16Data synchronization and DatabaseSynchronization between External Employee Database and Database in acertain time.IIR17Data Synchronization Setting and Data SynchronizationAn Administrator can set parameters of Data Synchronization.12
4. Nonfunctional RequirementNFR1FlexibilityUsers can attend meetings flexibly. Users can choose which meeting theywant to attend (e.g. desired meeting or important meeting).NFR 2EfficiencySet a threshold which provides rules of scheduling meetings at propertime. System can assume participants’ attendance by default. By doingabove things system can maximize the scheduling efficiency.NFR 3Maximum ease of agendaLet all project discussion participants can attend the meeting.NFR 4Maximum number of attendantMaximize the number of attendants at all meetings in the system.13
5. Goal-driven Use Case Diagram5.1 Introduction to Goal-driven Approach本專案採用 Goal Driven(目標導向)Use Case ；相反的將之稱為非功能性目標。14
5.2 Objective Statement目標名稱目標屬性Optimize e re the attendance ofprimary actors(S,A,N)Satisfy the maximumnumber of 較多的參與者參與。Satisfy the requirements(R,A,F)of Modify user informationconveniently(R,A,F)Manage 標。Can participate 的會議。15
Identify users(R,A,F)Manage onal表 1: 目標屬性說明16
5.3 Goal-driven Use Case DiagramFigure2: Goal-driven Use Case Diagram17
5.4 Actor Description and Actor Use Case MatrixActor NameActor DescriptionUserUsers who use Meeting Scheduler.ParticipantThe person who is invited to attend a meeting.InitiatorThe person who can coordinate, manage a meeting.Primary InitiatorThe person who initiates a meeting, and he/she can manageand coordinate the meeting.AdministratorThe person who manages Meeting Scheduler.Table 2: Actor Description TableUse CaseUserTransmit MessagesVUser SettingsVLogin to the SystemVUser 動安排會議Primary InitiatorVV18Administrator
User Data SynchronizationSettingsVManage meeting-levelsVManage actors of meetingVManage user-levelsVTable 3: Actor Use Case Matrix19
5.5 Use case specificationUse Case IDUC-CU-001Use Case NameTransmit MessagesGoalAchieve “CommunicateConveniently”Requirement[FFR7: Sending messages][FFR6: Message management][BFR5: Message Management]DescriptionA user can transmit messages to specific onditionsPost-ConditionsBasic native FlowsExceptional FlowsUse Use CaseExtends Use CaseBusiness Rules20
Special 管理員ArtifactsUse Case Glossary訊息訊息 發訊人 接收人 發訊時間 訊息內容21
Use Case IDUC-CU-002Use Case NameUser SettingsGoalAchieve [FFR5: User setting]DescriptionA user can modify his/her personal information and choosethe time periods which are available for certain types 間傾向: 若有會議符合使用者所設定的條件, 且該使用者被列為參與者, 下確定Basic FlowAlternative FlowsExceptional 件, 且使用者被列為參與者Use Use CaseExtends Use CaseBusiness RulesSpecial 席會議22
Artifacts使用者基本資料 姓名 性別 職稱時間傾向表 使用者 ID 時間區間Use Case 接受參與哪種類型的會議, 件23
Use Case IDUC-CU-003Use Case NameLogin to the SystemGoalAchieve “IdentifyUsers”Requirement[BFR1: Login]、[BFR4: User authentication]DescriptionLet users login to the system and enable them to usesystem orityPre-ConditionsPost-ConditionsBasic FlowAlternative 是否有相符的已註冊帳號、密碼2.1 平台使用本系統2.2 者操作平台管理本系統2.3 冊，並無法登入本系統Exceptional FlowsUse Use CaseExtends Use CaseBusiness RulesSpecial Requirements24
ArtifactsUse Case Glossary登入驗證登入驗證 帳號 密碼25
Use Case IDUC-CU-004Use Case NameUser RegistrationGoalAchieve “IdentifyUsers”Requirement[FFR8: Registration]、[BFR7: Sending messages]DescriptionLet a user have an account and a password in order to lethim/her login to the ConditionsPost-ConditionsBasic 成功註冊並能登錄本系統1.使用者輸入 E-mail 系統檢查是否有相符的 Email 並寄發註冊確認信給使用者Alternative FlowsExceptional FlowsUse Use CaseExtends Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case 號密碼 外部員工資料庫密碼26
Use Case IDUC-IP-001Use Case NamePlan a MeetingGoalAchieve ”MeetingRequestSatisfied”Requirements[FFR1: Initiate a Meeting][FFR3: Meeting Calendar][FFR4: Meeting Management][BFR5: Message Management][BFR6: Meeting Scheduler Algorithm]DescriptionThe user uses this function to initiate, maintain a meetingand invite people to participate in the tyPre-ConditionsHigh1. 使用者必須為本系統認可使用者2. 使用者必須先登入系統Post-ConditionsBasic 請之參與者。1. 起1.1 使用者點選發起會議1.2 編輯會議名稱、類型、角色1.3 使用者編輯會議項目、議程[UC-IP-003: Establish aAgenda for Discussion]1.4 使用者新增邀請參與人[UC-IP-002: Add newParticipants]1.5 設定參與者重要性[UC-IP-007: Set an Importanceof Participants]1.6 :27
Extend the Range of Time/Location]1.7 設定會議參與人數限制1.8 設定召集人[UC-IP-008: Set initiator permissions]2. 使用者點選”會議管理”2.1 顯示具有管理權限之欄位2.2 管理會議內容3. ive Flows1.7.1 若人數限制不做調整，則預設為 50%3.1 送出3.1.1 主席，並送出會議發起單3.1.2 用者繼續填寫Exceptional Flows2.1 不顯示在可管理會議上面3.2 停止發起此會議。Use Use CaseExtend Use CaseBusiness RulesSpecial Requirements28
ArtifactsUse Case Glossary會議發起單會議發起單 會議編號 會議等級 召集人編號 會議目的 工作項目及負責人 參與者編號 時間選項 地點選項 備註29
Use Case IDUC-IP-002Use Case NameAdd new ParticipantsGoalMaintain “MaxNumberOfParticipants”Requirements[FFR1: Initiate a Meeting][FFR4: Meeting Management][BFR5: Message Management][BFR6: Meeting Scheduler Algorithm]DescriptionManage a meeting and add new participants to ConditionsHigh1. 使用者必須登入系統2. 訊息傳送至被新增之使用者。Basic Flow1. 使用者新增一位參與者2. 調整使用者重要性[UC-IP-007: 設定參與者重要性]3. 按確定送出Alternative FlowsExceptional Flows2.1 給予1.1 時間/地點傾向Use Use Case[UC-IP-006] Extend the Range of Time/Location[UC-IP-007] Set an Importance of ParticipantsExtend Use Case[UC-IP-001: Plan a Meeting]Business Rules30
Special RequirementsArtifactsUse Case Glossary31
Use Case IDUC-IP-003Use Case NameEstablish a Agenda for DiscussionGoalMaintain ” MaxConvenientSchedule”Requirements[FFR1: Initiate a Meeting][FFR4: Meeting Management][BFR5: Message Management][BFR6: Meeting Scheduler Algorithm]DescriptionSet responsible people for each item of discussion and givethem certain weight of participation in a schedule in orderto make sure that responsible people can participate themeeting in this meeting iorityPre-ConditionsMedium3. 使用者必須登入系統4. 重要性，送至排程系統中排程Basic Flow1. 使用者新增一條討論項目2. 針對單一討論項目新增負責人3. 07: Set anImportance of Participants]Alternative Flows32
Exceptional Flows2.1 時間/地點傾向[UC-IP-006: Extend the Range of Time/Location]Use Use Case[UC-IP-006: Extend the Range of Time/Location][UC-IP-007: Set an Importance of Participants]Extend Use Case[UC-IP-001: Plan a Meeting]Business RulesSpecial RequirementsArtifactsUse Case GlossaryUse Case IDUC-IP-004Use Case NamePerformance MaintenanceGoalOptimize PerformanceRequirements[BFR6: Meeting Scheduler 不參加Sets the deadline for meeting starting into the meetingscheduler, and sets the people who have not decided ets the deadline for scheduling meetings in meetingscheduler, and informs every participant the information onditionsHigh必須發起會議成功33
Post-ConditionsBasic Flow1. 入排程2. 參與者參與狀態，將會議導入排程3. Alternative FlowsExceptional FlowsUse Use CaseExtend Use Case[UC-IP-001: 規劃會議]Business RulesSpecial RequirementsArtifactsUse Case GlossaryUse Case IDUC-IP-005Use Case NameTends to important meetingGoalProvide FlexibilityRequirements[FFR1: Initiate a Meeting][FFR4: Meeting Management][BFR5: Message Management][BFR6: Meeting Scheduler 意願。If there are conflicts between meetings, the system willinform participants of important meeting notification, and34
ask user whether he/she wants to change the Willingnessof re-ConditionsMedium1. 使用者必須登入本系統2. Post-ConditionsBasic 議。1. 本時間上會議有所衝突Alternative Flows1.1 否更改參與會議傾向1.2 使用者是否更改參與會議傾向1.3 息通知使用者會議衝突通知Exceptional FlowsUse Use CaseExtend Use Case[UC-IP-001: 規劃會議]Business RulesSpecial RequirementsArtifacts35
Use Case GlossaryUse Case IDUC-IP-006Use Case NameExpansion of time/spaceGoalRequirementsDescription[FFR1: Initiate a Meeting][FFR4: Meeting Management][BFR5: Message Management][BFR6: Meeting Scheduler ministrator manages meeting (e.g. Expands or modifiesthe time, space or willingness of participation High1. 使用者必須登入本系統2. st-ConditionsBasic FlowAlternative 能參與者1. 新增原本以外的時間/地點調查1.1 繼續填寫1.1.1 1.1.2 繼續填36
寫1.2 繼續填寫1.1.1 1.1.2 繼續填寫1.3 則直接結束本案例Exceptional FlowsUse Use CaseExtend Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case GlossaryUse Case IDUC-IP-007Use Case NameSet the important of participantsGoalRequirements[FFR1: initiate a meeting][FFR4: meeting management][BFR6: meeting scheduler algorithm]DescriptionThe meeting manager can set the importance ofparticipants which have some influence on yMedium37
Pre-Conditions3. 使用者必須登入本系統4. st-ConditionsBasic 1. 出現使用者參與重要性2. 會議管理者可以藉由滑動 slide bar，來調整此參與者重要性Alternative Flows2.1 Exceptional FlowsUse Use CaseExtend Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary38
Use Case IDUC-IP-008Use Case NameSet initiator permissionsGoalManage meetings convenientlyRequirements[FFR1: initiate a meeting][FFR4: meeting management]DescriptionSet initiator permissions in order to manage the iorityPre-ConditionsMedium5. 使用者必須登入本系統6. st-ConditionsBasic 來維護會議3. 新增一召集人4. 、新增受邀參與者Alternative FlowsExceptional FlowsUse Use CaseExtend Use Case[UC-IP-001: meeting management]Business RulesSpecial RequirementsArtifactsUse Case Glossary39
Use Case IDUC-PT-001Use Case NameParticipate in meetingsGoalAchieve ”participate in meetings”Requirement[FFR2:participate in a meeting]、[FFR3:meeting calendar]、[BFR6:meeting scheduler algorithm]DescriptionParticipants receive invitation of a meeting and decide thedesire for 會議Basic 之參與意願單Alternative FlowsExceptional FlowsUse Use CaseExtend Use CaseBusiness RulesSpecialRequirementsArtifactsUse Case Glossary參與意願單參與意願單 意願單編號 會議編號 參與者列表 可參與時間 可參與地點 攜帶物品清單40
41
Use Case IDUC-PT-002Use Case Nameschedule meetings automaticallyGoalAppropriate performanceRequirement[FFR3:meeting calendar]、[FFR5:user setting]、[BFR6:meetingscheduler algorithm]DescriptionAccording to the preferred time of the user and the availabletime of the meeting, the system will help the user to decide thedesire for sic Flow1. 時間2.1 否在會議舉行時間區間內2.1.2 會議2.2 型相符2.2.1 並參與此會議AlternativeFlows2.1.1 若是，本案例結束2.2.2 束ExceptionalFlowsUse Use Case42
Extend Use Case[UC-PT-001:participate in meetings]Business RulesSpecialRequirementsArtifactsUse CaseGlossary43
Use Case IDUC-SU-001Use Case NameUser Data Synchronization SettingsGoalAchieve “Manage systems conveniently”Requirement[BFR3:Data Synchronization Setting][BFR8:Data Synchronization]DescriptionSet parameters for synchronization 參數更新，啟動自動資料同步。1. 點選使用者資料同步設定。2. 料庫名稱、資料表名稱。3. 職位、電子郵Basic Flow件資料庫欄位。4. 填寫資料庫同步時間。4. 完成動作後，點選確定。5. 「取消」，回到先前畫面。Alternative Flows1. tional Flows2. 定使用案例。44
Use Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary45
Use Case IDUC-SU-002Use Case NameManage meeting-levelGoalAchieve “Manage systems conveniently”Requirement[BFR2:Parameter Setting]DescriptionAdd, modify and delete to the ntsPriorityPre-ConditionsPost-ConditionsBasic 會議等級參數更新1. 點選參數設定。2. 點選設定會議等級參數。3.1 點選新增選項。3.2 點選修改選項。3.3 點選刪除選項。4.1 2 逐一修改欲修改項目。4.3 逐一選擇要刪除的選項。5. 完成動作後，點選確定。6. 」，回到先前畫面。Alternative Flows46
Exceptional Flows1. 若有欄位未填妥，系統發出警告。2. 案例。Use Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary47
Use Case IDUC-SU-003Use Case NameManage actors of meetingGoalAchieve “Manage systems conveniently”Requirement[BFR2:Parameter Setting]DescriptionAdd, modify and delete to the actors of orityPre-ConditionsPost-ConditionsBasic 會議角色參數更新1. 點選參數設定。2. 點選設定會議角色。3.1 點選新增選項。3.2 點選修改選項。3.3 點選刪除選項。4.1 填寫會議角色名稱。4.2 逐一修改欲修改項目。4.3 逐一選擇要刪除的選項。5. 點選確定。6. 消」，回到先前畫面。Alternative Flows48
Exceptional Flows1. 若有欄位未填妥，系統發出警告。2. 案例。Use Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary49
Use Case IDUC-SU-004Use Case NameManage user-levelGoalAchieve “Manage systems conveniently”Requirement[BFR2:Parameter Setting]DescriptionAdd, modify and delete to the PriorityPre-ConditionsPost-ConditionsBasic 使用者等級參數更新。1. 點選參數設定。2. 點選設定使用者等級參數。3.1 點選新增選項。3.2 點選修改選項。3.3 點選刪除選項。4.1 4.2 逐一修改欲修改項目。4.3 逐一選擇要刪除的選項。5. 點選確定。6. 消」，回到先前畫面。Alternative Flows50
Exceptional Flows1. 若有欄位未填妥，系統發出警告。2. 用案例。Use Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary51
Use Case IDUC-ALGO-001Use Case NameFCFS StrategyGoalAppropriate PerformanceRequirements[BFR6] Meeting Scheduler AlgorithmDescriptionPerform FCFS StrategyActorInitiator, Host Agent, Guest ons3. User must login the system4. Host Agent should create a meeting firstPost-Conditions1. If FCFS passes, set the meeting into calendar2. If FCFS doesn’t pass, run HR StrategyBasic Flow2. An initiator create a meeting first3. Run FCFS Strategy4. Set the meeting into participants’ calendarAlternative Flows2.1 If FCFS Strategy failed to arrange the meeting2.2 Run HR StrategyExceptional FlowsUse Use CaseExtend Use Case[UC-ALGO-002: HR Strategy]Business RulesSpecial RequirementsArtifactsUse Case Glossary52
Use Case IDUC-ALGO-002Use Case NameUse High Rank StrategyGoalAchieve “Appropriate Performance”RequirementDescriptionA meeting will be scheduled by HR strategy.ActorHost onsThe FCFS strategy is failedPost-Conditions3. If HR passes, set the meeting into calendar4. If HR doesn’t pass, run voting StrategyBasic Flow1. Check the booked meetings is movable or fixed2. If movable, choose the meeting with the highestpriority or use voting strategy3. If the requested meeting is the meeting which have thehighest priority, add the requested meeting andreschedule the booked meeting4. If one or more booked meeting have higher than therequested meeting, reschedule the requested meetingAlternative FlowsExceptional FlowsUse Use CaseExtends Use CaseBusiness RulesSpecial RequirementsArtifactsUse Case Glossary53
dUse Case IDUC-ALGO-003Use Case NameVoting StrategyGoalAchieve “AppropriatePerformance”Requirement[BFR6: Meet
IIR7 Login Module and User Authentication Module A user logins through Login Module which sends login information to Authentication Module. Authentication Module checks whether the user has access rights of front-end or not. IIR8 Login Module and Meeting Management Module If a user passes login validation, he/she can use meeting management
