Showing pages 1 to 6 of 22 pages
1Introduction:Semantic information demonstrates in programming designing has different implications:It is a reasonable information display in which semantic data is incorporated. This implies themodel depicts the importance of its occurrences. Such a semantic information model is adeliberation that characterizes how the put away images (the occurrence information) identifywith the genuine world.It is a theoretical information demonstrate that incorporates the capacity to express data thatempowers gatherings to the data trade to decipher meaning (semantics) from the cases, withoutthe need to know the meta-show. Such semantic models are reality situated (instead of questionarranged). Realities are ordinarily communicated by paired relations between informationcomponents, though higher request relations are communicated as accumulations of twofoldrelations. Regularly parallel relations have the type of triples: Object-Relation Type-Object. Forinstance: the Eiffel Tower <is found in> Paris.Regularly the occasion information of semantic information models expressly incorporate thesorts of connections between the different information components, for example, <is found in>.To translate the significance of the truths from the cases it is required that the importance of thesorts of relations (connection sorts) be known. Thusly, semantic information models normallyinstitutionalize such connection sorts. This implies the second sort of semantic informationmodels empower that the examples express truths that incorporate their own particularsignificance. The second sort of semantic information models are typically intended to makesemantic databases. The capacity to incorporate importance in semantic databases encouragesbuilding disseminated databases that empower applications to translate the significance from thesubstance. This suggests semantic databases can be incorporated when they utilize the same
2(standard) connection sorts. This likewise suggests all in all they have a more extensiveappropriateness than social or protest arranged databases.The InternetThe cutting edge web is fueled by an arrangement of conventions (tenets and equations thatportray how to trade information) which PCs use to converse with each other. The HypertextTransfer Protocol (HTTP) is the convention that forces sites, it's the manner by which yourprogram requests a site page and a server some place sends you that page and every one of thepictures and other stuff you see.In any case, HTTP is not secure at all in light of the fact that everything is only a group ofcontent flying around. This obviously won't work for delicate things like managing an account soa convention called SSL was made that permits PCs to scramble information before sending it toeach other. Joining the SSL convention with HTTP gives us HTTPS.What Is SSL?SSL remains for Secure Sockets Layer. It is an encryption convention that gives correspondencesecurity over the Internet. TLS remains for a Transport Layer Security. SSL is a forerunner ofTLS. Both TLS and SSL are utilizing hilter kilter cryptography for verification of key trade,symmetric encryption for classification, and message validation codes for message respectability.How SSL functionsEncryption is finished by utilizing something many refer to as "keys" that come in sets. These areexceptional documents that can just decode stuff that has been encoded by the other. There's anopen key which your PC gets and a private key that lone the server has. Along these lines justyou and the server can read each other's messages and it can't be captured by any other person.
3OpenSSLKeep in mind SSL is only a convention so there still must be programming that really utilizesthese tenets and gives PCs a chance to talk. The most well known programming for this is calledOpenSSL, an open-source venture that is utilized on loads of servers (and heaps of gadgets likeyour web switch and cell phone).Semantic data application Development Process:Requirements analysis plays a crucial role throughout the semantic data application developmentprocess. This paper will thoroughly examine the role of requirements analysis, four traditionalapproaches to requirements analysis that an analyst may use and comparing and contrasting theseapproaches. In addition, I will discuss some new approaches to requirements analysis that arecurrently becoming more commonly used by analysts. After providing this in depth informationof requirements analysis in semantic data application development, I will briefly summarizewhat I’ve learned.Requirements analysis is “the process of analyzing the information needs of the end users, theorganizational environment, and any system presently being used, developing the functionalrequirements of a system that can meet the needs of the end users”. These requirements are thendocumented in various forms such as email, executable prototypes or documents and are oftenreferred to throughout the semantic data application development process. Meaning semanticdata application analysts are using these documents as guidelines in order to meet end userrequirements and needs. The semantic data application must entail efficient features such asreliability, feasibility and speed. In addition analysts need to determine whether too much of thesystem’s resources are being utilized in order for it to function properly. These micro features areessential in enabling end users to use the semantic data application feasibly which would include
4the semantic data application performing an assigned task. Though meeting the end users needsis vital in developing sufficient semantic data application that is compatible with a system, therehave been many problems using requirements analysis.Though requirements analysis is a process that facilitates semantic data application analystsdesigning sufficient semantic data application for end users, there have been numerous problemscreating semantic data application that is compatible with future systems. According to TomDeMarco, he states in his journal “numerous studies have shown that over half of the semanticdata application development projects don’t work.” In other words, when end users are using thesemantic data application, it is not meeting their functionality expectations. This is due toinformation not being properly clarified. This is referred to as the requirements elicitationprocess, which means there is difficulty obtaining information for requirements out of the endusers. When end users are asked about the kind of processes they would like the semantic dataapplication to perform, they are able to identify their wants but not their needs. Though semanticdata application analysts are verbally asking direct questions to the end users and are writtendown as a guideline for analysts to follow, these requests made by the users are not beingautomated. Therefore, when semantic data application analysts are developing semantic dataapplication for future systems, it will never meet the users needs due to them not accuratelystating what they need. Though analysts may follow the requirements elicitation processcompetently, the future system will not meet the user’s needs.Another posing problem with requirements analysis is that it is difficult to pinpointaccurate information to the stakeholders. According to Steve McConnell, communication withend users is very slow, they won’t commit to a set of written requirements and they demand newrequirements once fixed costs have been finalized. Since new changes are being iterated by end
5users consistently during semantic data application development, semantic data applicationanalysts aren’t able to create new semantic data application that meets the functionalityrequirements of the end users. This brings about a time issue when trying to complete semanticdata application development, in addition to requirements not meeting end user expectations.That is why it is crucial for information to be finalized and made clear to stakeholdersbeforehand so the project is completely within a certain time frame. In addition to informationnot being properly mentioned to the stakeholders, there are numerous encounters with acquiringadequate semantic data application analysts who have the necessary experience to devise suchsemantic data application. Though semantic data application analysts must have impeccabletechnical and language skills, their experience will enable them to excel when ascertaining newsystem requirements for end users to follow. In addition, the usage of complex tools and diversemethods may hinder the completion of semantic data application development while gatheringrequirements from end users.Though these are some existing problems with requirements analysis, there is a strong presenceof miscommunication between semantic data application analysts and end users. This is a resultdue to vocabulary difference. Since this language difference is present, it makes is more difficultfor semantic data application analysts to complete a finished product that the end users hadoriginally agreed upon. At this point, business analysts are brought in to bridge the large gapbetween end users and semantic data application analysts by analyzing and documenting thebusiness processes. As a result, business analysts will propose tentative solutions to rectify theindistinctive semantic data application. Another issue is that semantic data application analystsformulate requirements that meet the needs of the current system instead of developing newrequirements that are compatible with a future system. Therefore, the semantic data application
6is not meeting the needs of the end users, which is the main objective. By analysts focusing onmending the current system, it takes away time for them to devise new system requirements forthe future system. This is significant problem because end users want to use new semantic dataapplication for a future system, not current semantic data application that has been fixed. Inaddition, analysis is being carried out by analysts instead of personnel who have great personableskills. Due to this factor, the needs of the end users are being misinterpreted and not properlyiterated to the analysts to create semantic data application that is sufficient. This generates moreissues that aren’t needed and leads to poor system functionality.There are many approaches to facilitate the process of requirements analysis but the approachesthat I will be discussing are use cases, prototyping, agile semantic data application developmentand interviewing. All of these approaches allow end users to feasibly identify requirementsneeded to develop sufficient semantic data application. Though each of these approaches may beeffective, each approach stands out because of its own prevalent features. In order to comprehendthe various features affiliated with each approach, we will take an in depth look at eachapproach. The first approach we will look at will be use cases.Use cases are utilized for capturing functional requirements of a system by each case providingone or more scenarios that suggests to the end user how they should interact with the system.Each use case is focused on portraying how to accomplish a goal or objective, which may entailthe usage of multiple use cases to accept the scope of the new system. Based upon the degree offormality of a semantic data application project, it will influence the detail level that isincorporated into each use case. This is important because the more extensive the detail, thebetter the functionality of the semantic data application. Though use cases treat the currentsystem as a black box, this is due to system interactions and responses that must be analyzed in