HOPEX360 Website Template Documentation
HOPEX360Website Template documentationFBTV12020/06/26MEGA Internationalmega.com
Error! Reference source not found.Content1. Overview . 41.1. Technical limitations . 41.1.1. HOPEX Version . 41.1.2. Web browser Version . 41.1.3. Resolution . 41.1.4. Licensing . 41.1.5. Deployment . 41.1.6. Languages . 51.2. Data scope . 51.3. Homepage . 61.3.1. Overview . 61.3.2. Client specific . 61.4.1.5.1.6.1.7.Site Map . 7List index . 7Tree list index . 8Search . 92. Configuration . 92.1. Installation. 92.2. Required files . 102.3. Translation. 112.3.1. Code Templates . 112.3.2. Limitations . 122.4. Post-generation script JSON files . 132.4.1. CIO Dashboard JSON . 142.4.2. Tree list JSON. 162.4.3. Application page JSON . 172.4.4. Search. 183. CIO Dashboard . 183.1. Main dashboard . 183.1.1. Portfolio filter . 183.1.2. Drill down . 193.1.3. Indicators . 193.1.4. Application Evolution. 213.1.5. Technology Compliance . 213.1.6. Privacy management . 223.1.7. Applications per Capability . 233.1.8. Applications per Vendors . 233.1.9. Hosting model. 243.2. Technology Obsolescence . 243.3. Strategic Planning . 253.4. Rationalization . 25Page: 2 /35
CLIENTXX Architecture Repository implementation project Sommaire3.4.1. Rationalization Map . 253.4.2. Rationalization Table . 264. Indexes Details . 274.1. Tree lists . 274.1.1. Overview . 274.1.2. Structure. 274.1.3. Capabilities Tree list . 274.1.4. Processes Tree list . 284.2. Lists. 294.2.1. Overview . 294.2.2. Structure. 294.2.3. Capabilities list . 294.2.4. Processes list . 304.2.5. Concepts list . 304.2.6. Application portfolios list . 304.2.7. Applications list . 304.2.8. Projects list . 314.2.9. Technology Portfolios list . 314.2.10.Technologies list . 314.2.11.Vendors list . 315. Object pages details . erview . 31Business Capability Map. 32Business Capability . 32Business Process . 33Concept . 33Application portfolio. 33Technology portfolio. 33Application . 33Project . 34Technology . 34Vendor . 35Page: 3 /35
1.Overview1.1. Technical limitations1.1.1.HOPEX VersionThis website template is qualified against the HOPEX V3 version.1.1.2.Web browser VersionThis website template is qualified against the following web browser:-Firefox 75 and above-Chrome 81 and above1.1.3.ResolutionThis website is optimised for a 1920 x 10801.1.4.LicensingIt only considers the scope of the ITPM and ITBM licence.1.1.5.DeploymentOnce generated, the static website needs to be hosted on an IIS webserver to enableall the functionalities.The functionalities that require IIS include but are not limited to:-Application Force Diagram-Capabilities and Process Tree ListPage: 4 /35
-1.1.6.LanguagesThe website structure is available in both English and French. The translations can beamended using the Code Templates referenced in the descriptors.The website will be generated in the language set on the user running the webgeneration.The translation of the content itself relies on the available languages of HOPEX.1.2. Data scopeHOPEX360 covers the following data. For more details, refer to the tables at the endof the document.Page: 5 /35
1.3. Homepage1.3.1.Overview1.3.2.Client specific1.3.2.1. DescriptionThe 4 tiles down the tiles will not point anywhere. It is up to the consultant and/or theclient to update the links in the Homepage descriptor.The purpose of these links is to point to:-Client specific charter: online document-Missing content: email to a dedicated email address-Governance Process: online document-Provide feedback: email to a dedicated email address1.3.2.2. CustomisationTo modify:-Open the “HOPEX EA General Menu” Descriptor-Open the “Bottom Tiles” text-Add a link within the h6 tag:oClient specific charter: line 47Page: 6 /35
oMissing content: line 92oGovernance Process: line 145oProvide feedback: line 1881.4. Site MapThe top menu allows to navigate through the pages.Here is a breakdown of the navigation:Navigation nTechnologyAnalysisCapabilities Tree list: searchable hierarchical listCapabilities list: alphabetically sorted flat listProcesses Tree list: searchable hierarchical listProcesses list: alphabetically sorted flat listAssociated ObjectBusiness Capability MapsBusiness CapabilitiesBusiness ProcessesDictionaryConcepts list: alphabetically sorted flat listConceptPortfoliosApp portfolios list: alphabetically sorted flat listPortfolio typed as ApplicationApplicationsApplications list: alphabetically sorted flat listApplicationProjectsProjects list: alphabetically sorted flat listProjectPortfoliosTech portfolios list: alphabetically sorted flat listPortfolio typed as TechnologyTechnologiesTechnologies list: alphabetically sorted flat listTechnologyVendorVendors list: alphabetically sorted flat listOrg Unit typed VendorMain dashboardSpecific report pageCIODashboardTechnology ObsolescenceSpecific report pageStrategic PlanningSpecific report pageRationalizationSpecific report pageReports list: alphabetically sorted flat listSpecific report pagePop up to type in key wordsResults shown in tableReportsSearch1.5. List indexPage: 7 /35
1.6. Tree list indexPage: 8 /35
1.7. SearchThe search is implemented by the Fusejs library (https://fusejs.io/)2.Configuration2.1. InstallationThe website template is delivered as a Solution Pack. So the steps are as follows:-Download the package from the HOPEX Store into the HOPEX Installationfolder \Utilities\Solution PackMEGA InternationalHeadquarters: 9 avenue René Coty - 75014 Paris, FrancePhone 33 (0)1 42 75 40 00 - Fax 33 (0)1 42 75 40 95 - www.mega.com
-Unzip it in the same location-Open the HOPEX Admin module-Select HOPEX360 and click OK-The Website Template and all its components will be installed2.2. Required filesThe HOPEX environment Mega Usr folder will be updated with the files required bythe website template. This includes:-CSS files-JS files-Images-FontsPage: 10 /35
2.3. Translation2.3.1.Code TemplatesTranslations are available on the following items:-Menu-Section-Widget-Table headerFor each of them, a reference is written in the code to the relevant Code Template, assuch:[Variable CodeTemplate Id 8F68A4995E7868E4/]Where the Id is the hexaidabs of the code template, as shown below in the Codetemplate properties pageThe text can be modified in General TranslationPage: 11 /35
2.3.2.LimitationsSome texts are managed by Javascript librairies (Charts.JS, Datatables.JS, DX ) andare not translatable. They are available in English onlyIt includes:-Lists : pagination-Tree listsPage: 12 /35
2.4. Post-generation script JSON filesJSON files are generated as part of the website generation to cover differentfunctionalities. These files are stored in the \json folder of the generated website.Those JSON files contain the key data used in the reporting, via java script functions.This is implemented through 4 MetaCommand Managers triggering the relevantmacros:-HOPEX EA Post Generation Script App JSON. This generated on JSON perApplication to enable the Application Impact force diagram. The files are namedas follows:o-- Application hexaidabs integration.jsonHOPEX EA Post Generation Script CIO Dashboard JSON: this generates 4 chnology.jsoDatasArrayPortfolioTimePeriod.jsHOPEX EA Post Generation Script Process and Capa Trees erarchy.jsoDatasArrayBCMRationalization.jsPage: 13 /35
-“HOPEX EA Post Generation Script Search Indexing” (/!\ : for relative linksreason, this JSON is stored in the \standard\assets\js foldero2.4.1.searchindexcontent.jsonCIO Dashboard JSONThe ‘HOPEX EA Post Generation Script CIO Dashboard JSON’ MetaCommand Managergenerates 4 JSON files2.4.1.1. DatasArrayCapabilityMap.jsTopicPurposePagesusing thefileJSON datastructureKey informationThis is a list of Business Capability Maps including:- Name- HexaIdAbsThe main purpose is to enable a filter for key reportsThe following 2 pages use this data as a filter on the Box in Box:- Strategic Planning- Rationalizationvar datasArrayCapabilityMap [{capabilityMapName: "BCM To Be (EN) ",capabilityMapHexaIdAbs: "726B7F225E84F5C5",},];2.4.1.2. sePagesusing thefileJSON datastructureKey informationThis is a list of Applications, the Portfolios they are connected to andthe Business Capabilities they support.The following pages use this data:- Main Dashboard: in the Application per Capability Widget- Main Dashboard: in the Capabilities indicator- Rationalization: to filter out the Applications overlayed on theBCM box in boxvar datasArrayPortfolioBusinessCapability [{portfolioName: " Toutes les Applications",portfolioHexaIdAbs: "#",applicationName: "API Gateway (EN) ",applicationHexaIdAbs: "D37AD7455CF088CA",applicationType: "D\u00e9veloppement Sp\u00e9cifique",currentState: "Production",applicationHosted: "Nuage : IaaS",dataFreshness : " 6M",gdprCompliance: "App OK",overallCompletness: "75",businessCapabilityName: "Gestion des clients (EN) ",businessCapabilityHexaIdAbs: "F034F0705CF050BA",},];Page: 14 /35
2.4.1.3. sing thefileJSON datastructureKey informationThis is a list of Applications, the Portfolios they are connected to andthe supporting Technologies.The following pages use this data:- Main Dashboard: in the Technology Compliance Widget- Main Dashboard: in the Obsolete Applications indicator- Main Dashboard: in the Vendors indicator- Main Dashboard: in the Application per Vendor widgetvar datasArrayPortfolioTechnology [{portfolioName: " Toutes les Applications",portfolioHexaIdAbs: "#",applicationName: "API Gateway (EN) ",applicationHexaIdAbs: "D37AD7455CF088CA",applicationType: "D\u00e9veloppement Sp\u00e9cifique",currentState: "Production",applicationHosted: "Nuage : IaaS",dataFreshness : " 6M",gdprCompliance: "App OK",overallCompletness: "75",technologyName: "No technology",technologyHexaIdAbs: "",companyStandard: "",technologyEndOfSupport: "",technologyEndOfExtendedSupport: "",obsolescenceDate: "",vendor: "",},];2.4.1.4. sing thefileJSON datastructureKey informationThis is a list of Applications, the Portfolios they are connected to andthe attached Time PeriodsThe following pages use this data:- Main Dashboard: in the Application Evolution widgetvar datasArrayPortfolioTimePeriod [{portfolioName: " Toutes les Applications",portfolioHexaIdAbs: "#",applicationName: "API Gateway (EN) ",applicationHexaIdAbs: "D37AD7455CF088CA",applicationType: "D\u00e9veloppement Sp\u00e9cifique",currentState: "Production",applicationHosted: "Nuage : IaaS",dataFreshness : " 6M",gdprCompliance: "App OK",overallCompletness: "75",Page: 15 /35
];2.4.2.timePeriodName: "API Gateway (EN) [Pr\u00e9paration]",timePeriodHexaIdAbs: "F5AD10F15E7ECB46",timePeriodStatus: "Pr\u00e9paration",timePeriodAbsoluteStartDate: "2016/10/04 12:00:00",timePeriodAbsoluteEndDate: "2018/01/01 12:00:00",},Tree list JSONThe ‘HOPEX EA Post Generation Script Process and Capa Trees JSON’ MetaCommandManager generates 2 JSON files2.4.2.1. DatasArrayBCMHierarchy.jsTopicPurposePagesusing thefileJSON datastructureKey informationThe purpose is to provide the full hierarchical structure of theBusiness Capabilities and their supporting applications.The following page uses this JSON data:- Business Capability Tree Listvar products [{text: "BCM To Be (EN) ",modification date:"2020/04/14 08:06:47",performance:"", execution:"",link: "726B7F225E84F5C5.htm",id: "726B7F225E84F5C5",parent:"0",applications: [{text:"N/A"}},];2.4.2.2. g thefileJSON datastructureKey informationThe purpose is to provide the full hierarchical structure of theBusiness Processes and their supporting applications.The following page uses this JSON data:- Business Process Tree Listvar products [{text: "Business Process-2 (EN) ",modification date:"2020/04/16 10:48:07",performance:"3",execution:"3",link: "51797E5D5E77826E.htm",id: "51797E5D5E77826E",parent: "9ACC0F275D444F86",applications:[{text:"API Gateway (EN) ",Page: 16 /35
},},]link: "D37AD7455CF088CA.htm"];2.4.2.3. ing thefileJSON datastructure2.4.3.Key informationThe purpose is to provide the full hierarchical structure of theBusiness Capabilities and the applications decommissing dateThe following page uses this JSON data:- Rationalization Tablevar sales [{BCM: "BCM As Is",BC1:"Market Access",BC2:"Gestion des clients",link: "F034F0705CF0502C.htm",id: "F034F0705CF0502C",date:"2020/06/27 12:00:00",amount:"1"}]Application page JSONThe ‘HOPEX EA Post Generation Script App JSON’ MetaCommand Manager generatesone JSON file per Application.TopicPurposePagesusing thefileJSON datastructureKey informationThe JSON file enables the Impact force diagram on each ApplicationpageEach Application Object Page{"root" :{"id":"D37AD7485CF08ECB","name":"service-draws (EN) ","type id":"B1EDB2562C14016F","type "image":"./standard/appl.ico.gif","states":[ ":"FD280B395C926AC9","name":"AngularJS 1.7 (EN)","type id":"2885299152A85717","type age: 17 /35
"SearchThe “HOPEX EA Post Generation Script Search Indexing” MetaCommand Manager hasa Macro attached which generates a ‘searchindexcontent.json’ fileTopicPurposePagesusing thefileJSON datastructure3.Key informationThis JSON file is used to reference all the objects included in thewebsite to enable a full text searchIn every page, the menu includes a magnifying glass to toggle thesearch tool.This search is implemented using the Fuse library (https://fusejs.io/){pages":[{"title":"","Object type":"","Modification Date":"","text":"","tags":"","url":""},{"title":" img src './standard/APPL.ICO.gif' API ate":"2020/04/16 8CA.htm"},],};CIO Dashboard3.1. Main dashboard3.1.1.Portfolio filterAll the widgets shown on this page are filtered by Portfolio. This options list shows thefollowing values:-All Applications-All Applications without Portfolio-Each PortfolioOn load, the page will consider the “All Applications” as default.Page: 18 /35
3.1.2.Drill downOn click, all the widgets but the Application Evolution can be drilled down. A detailedlist will be shown at the bottom of the page, as shown below.3.1.3.Indicators3.1.3.1. ApplicationsPurposeSource JSON fileData structureKey informationThis widget shows the number of Applications in the selectedPortfolioDatasArrayPortfolioTechnology.js- (optional) Portfolio- ApplicationPage: 19 /35
Example3.1.3.1. Obsolete ApplicationsPurposeSource JSON fileData structureKey informationThis widget shows the number of Obsolete Applications. This isthe list of Applications linked to a Prohibited Technology(linked Software Technology with a ‘Prohibited’ CompanyStandard)DatasArrayPortfolioTechnology.js- (optional) Portfolio- Application- Technology – Company Standard ProhibitedExample3.1.3.1. CapabilitiesPurposeSource JSON fileData structureKey informationThis widget shows the number of Capabilities supported bythe Applications of the selected Portfolio. This is the list ofCapabilities linked to at least one Application of the - (Optional) Portfolio- Application- Business CapabilityExample3.1.3.1. VendorsPurposeSource JSON fileData structureKey informationThis widget shows the number of Vendors providingTechnologies supporting the Applications of the selectedPortfolio. This is the list of Org Units typed as Vendor linkedto at least one Technology supporting at an Application of thePortfolio.DatasArrayPortfolioTechnology.js- (Optional) Portfolio- Application- Technology- VendorExamplePage: 20 /35
3.1.4.Application EvolutionThis widget cannot be drilled down.PurposeSource JSON fileData structureKey informationThis shows the number of Applications by state over time forthe selected perimeter(s)DatasArrayPortfolioTimePeriod.js- (optional) Portfolio- Application- Object Life- Time PeriodsExample3.1.5.Technology CompliancePurposeSource JSON fileData structureKey informationThis shows the number of Technologies supporting Applicationsof the selected perimeter(s) broken down by Company StandardDatasArrayPortfolioTechnology.js- (optional) Portfolio- Application- Technology – Company StandardPage: 21 /35
Example3.1.6.Privacy managementPurposeSource JSON fileData structureKey informationThis shows the number of Application within the selectedperimeter(s) that are compliant to the privacy managementDatasArrayPortfolioTechnology.js- (Optional) Portfolio- Applicationo GDPR Content of Noticeo GDPR ContentLogicContent ofNotice / Consent empty YNYWYONRNDK empty App OKApp OKApp OKApp at RiskUnknownUnknownApp OKApp OKApp OKApp at RiskUnknownUnknownApp at RiskApp at RiskApp at RiskApp at RiskUnknownUnknownPage: 22 /35
Example3.1.7.Applications per CapabilityPurposeSource JSON fileData structureKey informationShows the number of Applications by Capability. The output is abar chart filtered on the top 10 Capabilities sorted bydescending number of supporting js- Application- Business CapabilityExample3.1.8.Applications per VendorsPurposeSource JSON fileData structureKey informationShows the number of Applications by Vendor. The output is abar chart filtered on the top 10 Vendors sorted by descendingnumber of supported ApplicationsDatasArrayPortfolioTechnology.js- Application- TechnologyPage: 23 /35
-VendorExample3.1.9.Hosting modelPurposeSource JSON fileData structureKey informationShows the number of Applications by Hosting modelDatasArrayPortfolioTechnology.js- Application – Hosting ModelExample3.2. Technology ObsolescencePurposeFilterSource JSON fileKey informationShows the number of Applications by Technology Obsolescence,whichLifecycle statusNone. The data is generated within the Hopex DescriptorPage: 24 /35
Data structure-Application – Application TypeObject Lifecyle - Time PeriodTechnology – End of Support / End of Extended SupportLogic: At a given point in time, if a Technology linked to a givenApplication is no longer supported, then this Application isobsoleteExample3.3. Strategic PlanningPurposeFilterSource JSON fileData structureKey informationThe report shows an automatic box in box report. This is agraphical view of the Business Capability Map hierarchy.This is a standard Hopex ReportA list of existing Business Capability Map allows to switch fromone to anotherNone- Business Capability Map- Business Capability and their Components to the 4th levelExample3.4. Rationalization3.4.1.PurposeFilterRationalization MapKey informationThe report shows an automatic Timed box in box report. This isa graphical view of the Business Capability Map hierarchy,overlayed with the supporting Applications.This is a standard Hopex Report- A list of existing Business Capability Map allows to switchfrom one to another- Portfolio to narrow down the overlayed Applications- Time spots to assess the evolution over timePage: 25 /35
Source JSON fileData structureNone- Business Capability Map- Business Capability and their Components to the 4th level- For each Business Capability, the supporting Applicationswithin the selected Portfolio, colour coded with theirlifecycle status at the selected Time sportExample3.4.2.Rationalization TablePurposeFilterSource JSON fileData structureKey informationThis shows the Application Retirement Plan per CapabilityNoneDatasArrayBCMRationalization.js- Business Capability Map- Business Capability level 1- Business Capability level 2- Application – Decommission DateExamplePage: 26 /35
4.Indexes Details4.1. Tree lists4.1.1.OverviewA Tree List displays a hierarchical structure through a table. The end user can filter,expand / fold and search.Only two lists use this rendering:-Business Capability Maps / Business Capability-Business Processes4.1.2.StructureThese pages which implements jQuery. More details can be found at the following Demo/TreeList/Overview/jQuery/Light/The data is generated from an HOPEX post generation script and is stored under the website folder /json/4.1.3.Capabilities Tree list4.1.3.1. RenderingThe Capabilities Tree list shows the following informationColumnBusiness CapabilityPerformanceKey informationBusiness Capabilities hierarchy starting from theBusiness Capability Maps, through the BusinessCapability CompositionPerformance assessment of relevant Business CapabilityExecutionExecution assessment of relevant Business CapabilitySupporting AppsList of applications linked to the Business Capability asRealisersLast modification date of the Business CapabilityModification Date4.1.3.2. CustomisationThis page uses the DevEpress JS library. For more details mo/TreeList/Overview/jQuery/Light/Page: 27 /35
This page relies on two components:-The HOPEX Descriptor : HOPEX EA Index Business Capa Tree List. Thiscontains the HTML and thee Javascript part-A post generation script “HOPEX EA Post Generation Script Process and CapaTrees JSON.Macro”. This generates a JSON file containing the data:./json/DatasArrayBCMHierarchy.jsThe structure of this file is as follows:var products [{text: "Business Capability Name",modification date:"2020/04/14 08:06:35",performance:"",execution:"",link: "F034F0705CF0502C.htm",id: "F034F0705CF0502C",parent:"F03JKSLMP5CF0502C ",applications: [{text:"Application Name"}]},]4.1.4.Processes Tree list4.1.4.1. RenderingThe Processes Tree list shows the following informationColumnBusiness ProcessPerformanceKey informationBusiness Process hierarchy, through the Owner BusinessProcess linkPerformance assessment of relevant Business ProcessExecutionExecution assessment of relevant Business ProcessSupporting AppsList of applications linked to the Business ProcessModification DateLast modification date of the Business Process4.1.4.2. CustomisationThis page uses the DevEpress JS library. For more details mo/TreeList/Overview/jQuery/Light/This page relies on two components:-The HOPEX Descriptor : HOPEX EA Index Business Process Tree List. Thiscontains the HTML and thee Javascript partPage: 28 /35
-A post generation script “HOPEX EA Post Generation Script Process and CapaTrees JSON.Macro”. This generates a JSON file containing the data:./json/DatasArrayBCMHierarchy.jsThe structure of this file is as follows:var products [{text: "Business Process Name",modification date:"2020/04/14 08:06:35",performance:"",execution:"",link: "F034F0705CF0502C.htm",id: "F034F0705CF0502C",parent:"F03JKSLMP5CF0502C ",applications: [{text:"Application Name"}]},]4.2. Lists4.2.1.OverviewThese are flat list of items, showing key attributes or associations4.2.2.StructureThe data is being generated from the relevant HOPEX Descriptor.The rendering is managed by a single HOPEX Descriptor for all lists (HOPEXEA General DataTable JS) and includes:-Filtering-Excel export-PaginationMore information on the “Datatable” java script library: https://datatables.net/4.2.3.Capabilities listColumnBusiness CapabilityCommentKey informationName of the Business CapabilityComment of the Business CapabilityParentParent Business CapabilityComponentsList of the Business Capability ComponentsSupportingApplicationsList of the supporting Applications (realizer)Page: 29 /35
4.2.4.Processes listColumnBusiness ProcessCodeKey informationName of the Business ProcessComment of the Business ProcessOwnerPerson defined as the Business Process OwnerParentParent Business CapabilityDirect Sub-ProcessList of the Business Capability ComponentsStatusCurrent workflow status of the Business ProcessReleaseModification date4.2.5.Concepts listColumnNameSubject AreaKey informationName of the ConceptBusiness Dictionary containing the ConceptCommentComment of the ConceptStorageImplementationImplementationBusiness Information Realizing the Concept4
1.1. Technical limitations 1.1.1. HOPEX Version This website template is qualified against the HOPEX V3 version. 1.1.2. Web browser Version This website template is qualified against the following web browser: - Firefox 75 and above - Chrome 81 and above 1.1.3. Resolution This website is optimised for a 1920 x 1080 1.1.4. Licensing
This HOPEX360 for V4 website template is qualified against the HOPEX V4 version. 1.1.2. Web browser Version This website template is qualified against the following web browser: - Firefox 75 and above - Chrome 81 and above 1.1.3. Resolution This website
Website Small Standard Enterprise 199 Baht/Month/User (Annual plan, prepaid) 599 Baht/Month/User (Annual plan, prepaid) 1099 Baht/Month/User (Annual plan, prepaid) 3099 Baht/Month/User (Annual plan, prepaid) 1 Website 1 Website 1 Website 1 Website Free 120 Website template Free 120 Website template Free 120 Website template Free 120 Website .
Henry Makow website . I am A Domestic Terrorist website . Candle Crusade website . Harris is a House Negro website . Stop Number 24 website . They Are Attacking The Children website . Arrest Biden website . National Straight Pride Coalition website . Constitution Party of California website . fight the power website . vaxeed website . Cordie .
Initiate a Template-Based Hire – Casual AUPE Hourly (Project) Step 2: Access Template Selection 1. Click the Look up Select Template button (magnifying glass) next to the Select Template field. The Look up Select Template window is displayed. Step 3: Select Template The template
P-245 - Term Contract Template for Gen. Services P-250 - Purchase Order Template P-520 - Equipment Lease Template P-530 - Equipment Maintenance Template P-600 - Professional Services Template P-601 – Professional Services Template (Individuals) P-606 - Chapter 6 Professional Services Template P-650 – Prof. Services Amendment Template
also design a beautiful website like they are editing a word document. It is very friendly web design software for new web designers. For this application note, there are two ways for novice to build a nice website: 1. Download the website template from the free web template website. 2. Build the website using "design view" on the Dreamweaver .
2 Process Documentation Template in a Nutshell The IEEE FIPA DPDF working group has recently proposed a template for documenting AO methodologies. Here we report only a brief presentation of the template—interested readers can refer to [8] for the details of the template. The template is based on the definition of
dan kinetik dari neuromuskuloskeletal tulang belakang (1,2,3). II. Anatomi Tulang Belakang Lumbosakral 2.1 Elemen-Elemen Tulang 2.1.1 Vertebrae Lumbal Ukuran tulang vertebrae lumbal semakin bertambah dari L1 hingga L5 seiring dengan adanya peningkatan beban yang harus disokong. Pada bagian depan dan sampingnya, terdapat sejumlah foramina kecil untuk suplai arteri dan drainase vena. Pada bagian .
