Network Administration-Computer Sciences Applications-Project Report, Study Guides, Projects, Research of Applications of Computer Sciences

Download Network Administration-Computer Sciences Applications-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity! 2 Use Case Diagrams 2.1 Customer Use Cases Register Complaint Customer O jh i \ Update Complaint ReOpen Complaint Search Complaint Add Contact Update comma) Figure 2: Customer Use Cases docsity.com  8  2.1.1 Login PreCondition:Userisatloginpage. PostCondition:customerhasaccesstothesystem.  2.1.2 RegisterComplaint PreCondition:customermustbeloggedin. PostCondition:customerhasregisteredanewcomplaintintothesystem.  2.1.3 UpdateComplaint PreCondition:Customermustbeloggedin. PostCondition:existingcomplaintisupdated.  2.1.4 ReopenComplaint PreCondition:complaintmustexistandusermustbeloggedin. PostCondition:complaintstatusischanged.  2.1.5 SearchComplaint PreCondition:customermustbeloggedinandshouldentervalidsearchcriteria PostCondition:customerhastherequiredcomplaintview.  2.1.6 Add/UpdateContact PreCondition:Customermustbeloggedin PostCondition:Customerhasupdated/addedcontactinformation. 2.1.7 Logout PreCondition:Customermustbeloggedin PostCondition:Customerisloggedoutofthesystemandthehomepageisdisplayed.  docsity.com 2.3 Administrator Use Cases Add User Info Administrator Update User Info Delete User Info Logout Figure 4: Administrator Use Cases docsity.com  12  2.3.1 Login PreCondition:Userisattheloginpage. PostCondition:Userisloggedin.  2.3.2 AddUser PreCondition:usermustbeloggedin. PostCondition:newuserisadded.  2.3.3 UpdateUserinformation PreCondition:Usermustexist PostCondition:informationisupdated.  2.3.4 DeleteUserinformation PreCondition:userinformationmustexist PostCondition:Userinformationisdeleted.  2.3.5 Logout PreCondition:Mustbeloggedin PostCondition:Userisloggedoutandhomepageisdisplayed.  3 SystemEntities Thesystemdescription,deducedfromtheanalysisofrequirements,showsthatthereare be5differentsystementities.   Customer  Staff  Administrator  Departments  Complaints docsity.com  13 3.1 Customer Thecustomersoftheorganizationthatneedtointeractwiththesysteminordertoplace their complaints and their feedback regarding services and facilities provided. For any registeredcustomertherearetwoattributes.   Email  Password  FirstName  LastName  Birthday  JoinDate  ContractStart  ContractEnd  Address  MobilePhone  LandlinePhone  ConnectionType 3.2 Staff Thestaffmemberscanalsobedepartmentsupervisorssotheyaredistinguishedonthe basisoftheirdesignation.Eachstaffmemberwillhavefollowingattributes.   Email  Password  FirstName  LastName  PhoneNumber  Department_ID  Designation   Figure5:CustomerEntity Figure6:StaffEntity Staff Email Designation LastName FirstName Phone Department _ ID Password docsity.com  16 4.5 StaffComplaint Staffcanmanagecomplaints;onestaffmembercanhandledifferentcomplaints.  Figure13:StaffComplaintRelation 4.6 StaffCustomer Astaffmembercanhandledifferentcustomers.  Figure14:StaffCustomerRelation 4.7 StaffDepartment Onestaffmembercanonlybelongtoasingledepartment.  Figure15:StaffDepartmentRelation 4.8 StaffStaff Astaffmembercanbedepartmentsupervisor,sohecanmanageotherstaffmembers.  Figure16:StaffStaffRelation docsity.com 5 Entity-Relationship-Diagram (ERD) Entire system entity-relationships can be shown as; Registers Customer Manage Manage Manage Complaint Manage Department Manage Administrator Figure 17: Entity Relationship Diagram docsity.com  18 6 RelationalModel Arelationaldatamodelrepresentsdataintheformofrelations.Arelationisanamedtwo dimensionaltableofdata.Aprimarykeyisanattributethatuniquelyidentifieseachrowin arelation.Aforeignkey isanattribute inarelationofadatabasethatservesasprimary keyofsomeotherrelationinthesamedatabase. 6.1 TransformingERDiagramintoRelations 6.1.1 MappingRegularEntities Regular entities are real world objects and have independent existence. Each regular entityintheERdiagramistransformedintoarelation.Eachattributeoftheentitytype becomes the attribute of the relation. The identifier of the entity type becomes the primarykey. 6.1.1.1 Customer Email Password FirstName LastName Birthday JoinDate ContractStart ContractEnd Address MobilePhone LandlinePhone Connection Type 6.1.1.2 Staff Email Password FirstName LastName PhoneNumber Dept_ID Designation 6.1.1.3 Administrator Email Password FirstName LastName PhoneNumber Designation 6.1.1.4 Complaint Complaint_ID Cust_Email Dept_ID Assigned To Reported Date Time toFix Comments Current Status 6.1.1.5 Department Department_ID DepartmentName 6.1.2 MappingWeekEntities NoweekentityexistsinthesystemasevidentfromERDiagramwhichresultsinskipping ofthisstep. docsity.com  21  Staff–Department  Staff Email Password FirstName LastName PhoneNumber Dept_ID Designation  Department Department_ID Staff_Email DepartmentName  6.1.5.3 MappingbinaryM:NRelationships ThereisnoM:Nrelationshipinthesystem. 6.1.5.4 MappingnArrayRelationships ThesystemdoesnotcontainanynArrayrelationships. 6.1.5.5 MappingSupertype/SubtypeRelationships Nosupertype/subtyperelationsexistinthesystem. 6.1.5.6 MappingAssociativeEntities Noassociativeentitiesexistinthesystem. 7 Normalization It is the process of decomposing relations with anomalies to produce smaller, well structured relations. Normalization is a tool to validate and improve a logical design, so that it satisfies certain constraints and avoid unnecessary duplication of data. Normalizationcanbeaccomplishedinstages,eachofwhichcorrespondstoanormalform. A normal form is a state of relation that results from applying simple rules regarding functional dependencies to that relation. A step by step normalization process is carried outnext. 7.1 1stNormalForm(1NF) Forrelationstobein1NFtheymustsatisfythefollowingconditions.   Nomultivaluedattributes  Everyattributevalueisatomic  Since there are no multivalued attributes in any relation of the system also every attribute value isatomic,hencebothconditionsaresatisfiedforwholesystemandthesystem is in1st normalformandnosolutionstepsarerequiredtobeperformed.  docsity.com  22 7.2 2ndNormalForm(2NF) Forrelationstobein2NFfollowingconditionsmustbesatisfied.   1NFPLUSeverynonkeyattributeisfullyfunctionallydependentontheENTIRE primarykey  Everynonkeyattributemustbedefinedbytheentirekey,notbyonlypartof thekey  Nopartialfunctionaldependencies  Absenceofanycompositekeyinthesystemsatisfiesbothconditionsresultinginasystemthat isin2ndnormalformandnosolutionstepsarerequiredtobeperformed.  7.3 3rdNormalForm(3NF) Systemisin3NFiffollowingconditionissatisfied.   2NFPLUSnotransitivedependencies(functionaldependenciesonnonprimarykey attributes)  Considering the above stated rule no transitive dependencies are found in the system hence thesystemin3rdNormalFormandnosolutionstepsarerequiredtobeperformed.  8 ProjectedFutureWork Implementation of the database physical design, consisting of the data types, null information,tabletypeandcharactersetwillbecarriedoutasanextstep.Thentheactual databaseisthenextstepafterwhichimplementationoftheapplicationwillbecarriedout. Aftertheimplementationofdatabase,theSQLcodewillbetheavailableartifactasacheck pointgoalafterwhichtheapplicationinterfaceImplementationwillbethenextgoal.  9 References [1] ModernDatabaseManagementbyJeffreyA.Hofer.Seventhedition. [2] DatabaseSystemsbyThomasConnolly.Thirdedition. [3] en.wikipedia.org/wiki/SugarCRM [4] www.sugarcrm.com  docsity.com