I'm not sure what you mean exactly by that, but I'll take a stab. I'll assume you mean trying to phrase you tests in a more human readable form.
It's possible if you link or build some sort of framework ontop of it. The idea is the framework provides an abstraction between definining the test and the actual implementation code.
We use a proprietary keyword driven framework where keyword can be written on an excel sheet. The keywords can be string together by testers to form tests, while programmers like myself write fixtures that give these keywords meaning.
So a tester might write something like...
click buy button
enter Price $50.00
click confirm button
And in the background my code might be calling..
set aButton = Aliases.currentWindow.buy_button"
set aField = Aliases.currentWindow.price
aField.Value = "50.00"
set aButton = Aliases.currentWindow.confirm_button
Once a keyword fixture is written, they can be strung up in any order with different parameters to form test. Programming is still being done in the background, but allows non-testers to begin writing test specifications without programming knowledge, and leave programing implementation to the framework developers.
Generally speaking, TestComplete supports Descriptive Programming. Other tools require an object repository to work with objects on the screen. TestComplete can access all objects on the screen at any point in time, so it does not require an object repository to run tests.
You can use the Object Browser to examine an object's properties, methods and fields. Please refer to the "Exploring an Application in the Object Browser" help topic to learn how to do this. For information on how objects are identified in TestComplete, please see the "How TestComplete Recognizes Processes, Windows and Controls" help topic.