Search results
* Corporate Communications include (a) the annual report; (b) the interim report; (c) a notice of meeting; (d) a listing document; (e) a circular; and (f) a proxy form. ^ Non-registered shareholder refers to such person or company whose shares are held in the Central Clearing and Settlement System (CCASS）and who has notified the Company from time to time through Hong Kong Securities Clearing ...
Visit Henderson Land’s Investor Information page for stock information, interim and annual reports, investor presentations and the latest announcements.
Henderson Land’s core business comprises property development and investment. Visit our website for the Group's Interim, Annual and Sustainability Reports.
- Overview
- What is an architecture decision record?
- How to start using ADRs
- How to start using ADRs with tools
- How to start using ADRs with git
- File name conventions for ADRs
- Suggestions for writing good ADRs
- ADR example templates
- Teamwork advice for ADRs
- For more information
An architecture decision record (ADR) is a document that captures an important architecture decision made along with its context and consequences.
Contents:
•What is an architecture decision record?
•How to start using ADRs
•How to start using ADRs with tools
•How to start using ADRs with git
An architecture decision record (ADR) is a document that captures an important architectural decision made along with its context and consequences.
An architecture decision (AD) is a software design choice that addresses a significant requirement.
An architecture decision log (ADL) is the collection of all ADRs created and maintained for a particular project (or organization).
An architecturally-significant requirement (ASR) is a requirement that has a measurable effect on a software system’s architecture.
All these are within the topic of architecture knowledge management (AKM).
The goal of this document is to provide a fast overview of ADRs, how to create them, and where to look for more information.
To start using ADRs, talk with your teammates about these areas.
Decision identification:
•How urgent and how important is the AD?
•Does it have to be made now, or can it wait until more is known?
•Both personal and collective experience, as well as recognized design methods and practices, can assist with decision identification.
•Ideally maintain a decision todo list that complements the product todo list.
You can start using ADRs with tools any way you want.
For example:
•If you like using Google Drive and online editing, then you can create a Google Doc, or Google Sheet.
•If you like use source code version control, such as git, then you can create a file for each ADR.
•If you like using project planning tools, such as Atlassian Jira, then you can use the tool's planning tracker.
•If you like using wikis, such as MediaWiki, then you can create an ADR wiki.
If you like using git version control, then here is how we like to start using ADRs with git for a typical software project with source code.
Create a directory for ADR files:
For each ADR, create a text file, such as database.txt:
Write anything you want in the ADR. See the templates in this repository for ideas.
If you choose to create your ADRs using typical text files, then you may want to come up with your own ADR file name convention.
We prefer to use a file name convention that has a specific format.
Examples:
•choose-database.md
•format-timestamps.md
•manage-passwords.md
Characteristics of a good ADR:
•Rationale: Explain the reasons for doing the particular AD. This can include the context (see below), pros and cons of various potential choices, feature comparions, cost/benefit discussions, and more.
•Specific: Each ADR should be about one AD, not multiple ADs.
•Timestamps: Identify when each item in the ADR is written. This is especially important for aspects that may change over time, such as costs, schedules, scaling, and the like.
•Immutable: Don't alter existing information in an ADR. Instead, amend the ADR by adding new information, or supersede the ADR by creating a new ADR.
Characteristics of a good "Context" section in an ADR:
ADR example templates that we have collected on the net:
•ADR template by Michael Nygard (simple and popular)
•ADR template by Jeff Tyree and Art Akerman (more sophisticated)
•ADR template for Alexandrian pattern (simple with context specifics)
•ADR template for business case (more MBA-oriented, with costs, SWOT, and more opinions)
•ADR template of the Markdown Any Decision Records (MADR) project (both simple and elaborate version; the latter emphasizes options and their pros and cons)
If you're considering using decision records with your team, then here's some advice that we've learned by working with many teams.
You have an opportunity to lead your teammates, by talking together about the "why", rather than mandating the "what". For example, decision records are a way for teams to think smarter and communicate better; decision records are not valuable if they're just an after-the-fact forced paperwork requirement.
Some teams much prefer the name "decisions" over the abbreviation "ADRs". When some teams use the directory name "decisions", then it's as if a light bulb turns on, and the team starts putting more information into the directory, such as vendor decisions, planning decisions, scheduling decisions, etc. All of these kinds of information can use the same template. We hypothesize that people learn faster with words ("decisions") over abbreviations ("ADRs"), and people are more motivated to write work-in-progress docs when the word "record" is removed, and also some developers and some managers dislike the word "architecture".
In theory, immutability is ideal. In practice, mutability has worked better for our teams. We insert the new info the existing ADR, with a date stamp, and a note that the info arrived after the decision. This kind of approach leads to a "living document" that we all can update. Typical updates are when we get information thanks to new teammates, or new offerings, or real-world results of our usages, or after-the-fact third-party changes such as vendor capabilties, pricing plans, license agreements, etc.
Find the latest SEC Filings data for Henderson Land Development Co. Ltd. ADR (HLDCY) at Nasdaq.com.
Henderson Land has a long-standing commitment to sustainability and corporate social responsibility. The Group has included a section related to sustainability in its Annual Report since 2006 and we have continually improved our disclosure.
People also ask
Where can I find information about Henderson Land?
Does Henderson Land have a commitment to sustainability?
What is Henderson Land's core business?
How do I create an ADR file?
Henderson Land Development Co. Ltd. ADR company facts, information and financial ratios from MarketWatch.
