Contents INTRODUCTION...........................................................................................................................3 MAIN BODY..................................................................................................................................3 CONCLUSION..............................................................................................................................13 2
INTRODUCTION A system model is basically representing the different aspects of CRM system and its environment. It is mainly considered as a process of developing the abstract model of system witheachmodelgeneratemultipleperspectives.Itwilldevelopusescasesofcustomer relationship management system on the basis of system functionality. Furthermore, it also creates test plan to check their overall functionality of CRM. MAIN BODY 1. Create Use Cases of Customer relationship management system. Use Case-1 Figure1Use Case Diagram 3
Use case Description: Use Case NameMaintain staff details Triggering event Brief DescriptionThe use case is based on maintain staff details by administrator that can update, modify the data as per requirement. Admin assigns the job of each staff members and maintain information in proper manner. ActorsMain actors involved are: Staff Administrator Manager Related use casesMaintain Job Scheduler use case Management of staff role Track staff data StakeholdersMain stakeholders involved are: Staff Manager End users of the system PreconditionsAdministrator views the details of staff with the help for system. Manager creates individual database for storing information of employee in proper manner. Post conditionsWhen information of staff members changes by manager for updating individual tables. Manager delete the database of individual table for each staff members. Staff view the status in their system. Flow of ActivitiesActor ActionSystem Response 4
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Enterusernameand password Update staff details Capture / track data Check staff qualification View status Check staff experience Login into the system Save staff details Filter qualified data View leads Assign leads to the staff members 5
2. Activity Diagram It is basically generating the flow of control in system and also refer to include use cases executions. It is another type of UML diagram that describe dynamic aspects of system and represent the flow of activities in step by step manner. Activity-1 Figure2Activity diagram 6
3. Sequence Diagram It refers to the interaction diagram that mainly describe how group of objects work together in proper manner. It mainly used for designer to understand the actual requirement of new system and also analyse the documents of existing system. Sequence-1 Maintain Staff details Sequence diagram Figure3Maintain Staff details Sequence diagram 7
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4. Test plan of use cases Thetestplanisbasicallyderivedaccordingtotherequirements,detaileddesign specificationsanditsfunctionalspecification.Itmainlydeterminedthetestdetailsthat associated with the test cases. Test plan to maintain staff details S. No.Test caseShort DescriptionTest conditionTest DataExpected Output 1.LoginCheckthecorrect usernameand passwordofstaff members. If staff members are notaddingcorrect details,itwill generateerror message. Grant Accessto themain application. Staff successfully loginthe systemto check details. 2.Addstaff name Ensure that new staff membersaddedto the system. Ifnewstaff membersalready added so that it will generateerror messages. Test the staff nameand generate confirmation messageof changes shouldbe displayed Dataisin theform alteredand submit easily. Whenclick ondatabase that generate successfully messages. 3.Checking for creating database Testthedatabase when manager create individualdatabase andassignspecific job role to each staff Wheneverthe database is created, manager assign the job task of each staff members Testthe databaseof individual staff tables. Database hasbeen successfully createdand manager can viewthe 8
members.team. Table: 3 CONCLUSION In above discussion, it has been successfully designed use cases, Activity and sequence diagram of customer relationship management system. It can be determined the functionality of system with the help for creating test plans. 9