github.com/awslabs/clencli@v0.0.0-20210514234156-7ecf17182a20/box/resources/init/clencli/hld.yaml (about)

     1  # Show at a high level how:
     2  #   * Users interact with the app as a whole
     3  #   * Data lifecycle is managed
     4  #   * Integrations with and dependencies on other systems
     5  #   * Use numbers/letters on diagram to populate table showing what each object does."
     6  #   * Do not include deployment mechanism in same diagram as high-level application design.
     7  architecture:
     8    description: Blandit massa enim nec dui nunc mattis.
     9    currentstate:
    10      description:  Lorem ipsum dolor sit amet.
    11      diagram:
    12        label: Dui ut ornare lectus sit amet est.
    13        url: https://via.placeholder.com/512x512.png
    14    targetstate:
    15      description: Senectus et netus et malesuada fames ac turpis.
    16      diagram:
    17        label: Elementum curabitur vitae nunc sed velit.
    18        url: https://via.placeholder.com/512x512.png
    19  
    20  # List applicable automation techniques used in the solution:
    21  #   * OS
    22  #   * Application bootstrap/packaging
    23  automation: |-
    24    Gravida arcu ac tortor dignissim. Magna etiam tempor orci eu lobortis. Magna sit amet purus gravida.
    25    * aliquet
    26    * risus
    27    * feugiat
    28  
    29  # What is the overall availability achieved as a result on individual components availability targets. 
    30  # Include exceptions where a single point-of-failure exists
    31  availability: |-
    32    Sagittis purus sit amet volutpat consequat mauris nunc congue nisi.
    33    Congue quisque egestas diam in.
    34    Vulputate eu scelerisque felis imperdiet.
    35    Blandit massa enim nec dui nunc mattis.
    36  
    37  # requirements: details of any compliance requirements to be adhered by the solution
    38  compliance:
    39    requirements: Fermentum leo vel orci porta non.
    40  
    41  # category: application's criticality rating. RTO/RPO
    42  criticality:
    43    category: Volutpat blandit aliquam etiam erat velit scelerisque.
    44  
    45  data:
    46    classification: In tellus integer feugiat scelerisque varius morbi.
    47  
    48  decisions:
    49  - context: Tellus at urna condimentum mattis.Nisl nisi scelerisque eu ultrices vitae auctor.
    50    date: January 1st, 2019
    51    description: Adipiscing enim eu turpis egestas pretium aenean.
    52    status: backlog
    53  - context: Integer malesuada nunc vel risus commodo.
    54    date: January 1st, 2020
    55    description: In metus vulputate eu scelerisque felis imperdiet proin.
    56    status: in-progress
    57  
    58  devops:
    59  - label: code
    60    url: https://
    61  - label: build
    62    url: https://
    63  - label: release
    64    url: https://
    65  - label: artifacts
    66    url: https://
    67  
    68  environments:
    69    - name: Development
    70      identifier: dev
    71    - name: Test
    72      identifier: tst
    73    - name: Production
    74      identifier: prd
    75  
    76  #  List all systems the solution will integrate with:
    77  #    * AD
    78  #    * NAS Filer
    79  #    * Logging solution
    80  #    * Batch system
    81  #    * Alarming system
    82  #    * ITSM tool
    83  integration: |-
    84    * Leo - integer malesuada nunc vel.
    85    * Gravida - neque convallis a cras semper.
    86  
    87  # What level of reliability is achieved for the data hosted in cloud (e.g. s3 reliability)  
    88  reliability: Viverra vitae congue eu consequat ac.
    89  
    90  # List components that are re-used from others services:
    91  # * AD
    92  # * OS Images
    93  # * Backups
    94  # * Internet Proxy
    95  # * Anti-virus Agents
    96  # * AWS CloudTrail
    97  # * Naming Standards
    98  # * Tagging Standards
    99  reusable: |-
   100    * Hendrerit - dolor magna eget.
   101    * Integer - malesuada nunc vel risus commodo.
   102  
   103  # Describe how the solution components meet scalability standards, 
   104  # include if it does not need/meet any scalability targets.
   105  scalability: Pretium vulputate sapien nec sagittis.
   106  
   107  target:
   108    golive: dd/mm/yyyy