{"title":"What is a Profile?","authors":"C. Severance","doi":"10.1109/2.410156","DOIUrl":null,"url":null,"abstract":"Discusses the value of profiles and how they differ from standards. Profiles address the problem of computer standards not being precisely designed to meet end-user needs. A standard's scope is generally much narrower than an entire computer system. To support user needs, a particular computer system may have to comply with many individual standards. Several factors may limit the scope of each standard. Moreover, no formal standards body requires that standards completely address end-user needs. Finally, a standard's scope is often reduced because an area originally covered by the standard does not have sufficient consensus to be retained in that standard. A consensus-based standard can be produced only in those areas that have sufficient consensus. Profiles are specifications that formally capture an organization's information technology needs. They are becoming a way to map the middle ground between overall user needs and the standards related to those needs. Profiles can be used to inventory an existing computing strategy, support a computing procurement or drive the evolution of an organization's computing strategy. Actually, organizations have been developing profiles for many years. However, they've gone by such names as procurement specifications, bid documents, strategic plans or recommended practices. At a minimum, a profile identifies user requirements and the standards or specifications that meet those requirements. A profile may also include more details on an organization's computing strategy. >","PeriodicalId":343541,"journal":{"name":"The Journal of the Canadian Chiropractic Association","volume":"136 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"The Journal of the Canadian Chiropractic Association","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/2.410156","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1
Abstract
Discusses the value of profiles and how they differ from standards. Profiles address the problem of computer standards not being precisely designed to meet end-user needs. A standard's scope is generally much narrower than an entire computer system. To support user needs, a particular computer system may have to comply with many individual standards. Several factors may limit the scope of each standard. Moreover, no formal standards body requires that standards completely address end-user needs. Finally, a standard's scope is often reduced because an area originally covered by the standard does not have sufficient consensus to be retained in that standard. A consensus-based standard can be produced only in those areas that have sufficient consensus. Profiles are specifications that formally capture an organization's information technology needs. They are becoming a way to map the middle ground between overall user needs and the standards related to those needs. Profiles can be used to inventory an existing computing strategy, support a computing procurement or drive the evolution of an organization's computing strategy. Actually, organizations have been developing profiles for many years. However, they've gone by such names as procurement specifications, bid documents, strategic plans or recommended practices. At a minimum, a profile identifies user requirements and the standards or specifications that meet those requirements. A profile may also include more details on an organization's computing strategy. >