Skip to main content

Web site life cycle plan

Web site life cycle plan

 A plan should be prepared for managing appropriate life cycle processes for the Web site—acquisition, sup-ply, development, operation, and maintenance. The plan for the Web site should define when, how, and bywhom specific activities are to be performed, including options and alternatives, as appropriate. The planshould include, at least, the following generic items:a) Date of issue and statusb) Scopec) Issuing organizationd) Referencese) Approval authorityf) Planned activities and tasksg) Macro references (policies or laws that give rise to the need for this plan)h) Micro references (other plans or task descriptions that elaborate details of this plan)i) Schedulesj) Estimatesk) Resources and their allocationl) Responsibilities and authoritym) Risksn) Quality control measureso) Costp) Interfaces among parties involvedq) Environment/infrastructure (including safety needs)r) Trainings) Glossaryt) Change procedures and historyu) User support needs (help desk, end-user documentation, telephone line)v) Target community descriptions

Well-engineered Web site requirements specification
 A requirements specification should be prepared for a well-engineered Web site. This specification shouldinclude, at least, the following generic items: a) Date of issue and statusb) Scopec) Issuing organizationd) Referencese) Approval authorityf) Bodyg) Delivery instructionsh) Assurance requirementsi) Conditions, constraints, and characteristicsj) Glossaryk) Change historyNOTE—The items of this specification are quoted from subclause 5.7 of IEEE/EIA 12207.1-1997 [B16]. The architectsof complex well-engineered Web site projects may wish to consider more detailed specifications described elsewhere inIEEE/EIA 12207.1-1997 [B16]. The developers of complex well-engineered Web site projects may also wish to considerthe use of IEEE Std 830-1998 [B5]. 4.1.8 Well-engineered Web site design descriptionA design description should be prepared for the Well-engineered Web site. The design description for theWell-engineered Web site should include, at least, the following generic items:a) Date of issue and statusb) Scopec) Issuing organizationd) Referencese) Contextf) Notation for descriptiong) Bodyh) Summaryi) Glossary j) Change history Aruthra innovations

Web site life cycle plan


The version of HTML, and the features within that version of HTML, should be selected based on the clientenvironment of the target-user community. For example, “frames” and Java scripts are representative of theelements that reflect significant design incompatibilities with older browser versions, and are examples ofthe type of feature that must be given critical evaluation in the design phase. Removal of an architectural fea-ture like “frames” can require significant redesign. Web page developers should be familiar with XML andevaluate how, if, and when to incorporate XML into a well-engineered Web site.As a default, new well-engineered Web pages should use XHTML in its HTML compatible form. Some ofthe XHTML compatible guidelines should be included in the well-engineered Web site project plan, evenwhere older browser compatibility is required (for example, lowercase tags.)Essential elements of XHTML compatibility:a) All tag elements and attributes in lower case.19b) Documents to be well formed, have properly nested elements and have end tags on all elements thathave content (including li, p, etc). Empty elements to have a closing slash in the tag (e.g. <br />—note space before slash in this example for HTML compatibility).c) All attribute values to be quoted.d) Use ‘id’ for fragment identifiers (in addition to 'name' for HTML compatibility, e.g. <aname="IEEE" id="IEEE">).e) Use ‘[CDATA[...]]’ construct for enclosing script, style or other ‘commented’ elements (commentstructures may be stripped by server during delivery process).f) Avoid linebreaks or excess spaces in attribute values.g) Do not include more than one ‘isindex’ element in a page.h) Include both ‘lang’ and ‘xml:lang’ values.i) Include both ‘xml’ and ‘http-equiv’ character encoding statements.j) Specify ampersand as &amp; in attribute values.k) Be aware that CSS defines different conformance for XML and HTML.https://arudhrainnovations.com/ 

Comments

Popular posts from this blog

karthividhyalaya school in kumbakonam

International School in Kumbakonam

Project Center in Trichy

Project Center in Thanjavur, Do IEEE Projects,  learn VMware, learn Android, learn embedded system, Arudhra innovations, project center in Kumbakonam, create your own app, play with your app as per your like, project center in trichy, Learn Hadoop,  Learn Cloud Server, Learn Virtualization, how to burn the program to ic , how the interface devices, how to create an android app, what kind of app we will do, Arudhra innovations, project center in Kumbakonam, learn big data, learn .Net , Do your academic project as your own, project center in trichy, embedded system projects ,vlsi projects ,java projects, android projects, Arudhra innovations, Learn Embedded system, project center in Kumbakonam, publish your own ieee papers Arudhra innovations ,2012 we published 4 IEEE papers, Project center in Kumbakonam,2013 we published 20 IEEE papers, we are planned to publish 100 papers in 2014-2015 academic year, Project Center in Kumbakonam, Project Center in Thanjavur, Project center...

Virtualization Training in Kumbakonam

• Meet Industrial Expert’s •  Learn “How to Create Multiple OS” •   Learn ESXi • Hand on with VMServer • Create Cloud Server • Get Certification on Virtualization We have a dedicated virtualization server with a industrial experienced expert. Virtualization works in between the Operating system and the Hardware. Imagine a single machine which runs by multiple Operating Systems by using the technology virtualization. Contact us: Arudhra Innovations,  City's Bulidings, 504-1 Vatti Pillayar Road, Near Agarwal Hospital, Kumbakonam-6120001 Call us: 0435-2411153, 9790675343, 9791661032 Email: panneerselvam@arudhrainnovation.com Website: www.arudhrainnovations.com